Amazon's Premium A+ Threshold Counts Whole Projects, Not Modules — One Five-Module Basic Project Does Not Satisfy It
The question
"Is Amazon's Premium A+ eligibility threshold denominated in individual A+ modules or in whole projects/submissions — and does one Basic A+ project containing five modules satisfy it?" This is the unit ambiguity surfaced (but not resolved) by [[2026-08-16-squarely-a-plus-five-project-accumulation-path]]: Amazon's canonical wording says "modules," the entire secondary literature says "projects," and the two readings differ by roughly 5x in drafting effort.
What we already know (from the vault)
- [[2026-08-16-squarely-a-plus-five-project-accumulation-path]] fetched the canonical Amazon announcement directly and confirmed it reads "Five approved A+ Content modules in the last 12 months" — then flagged in its own open follow-ups that no vault brief had ever noticed the modules-vs-projects conflict.
- [[2026-07-05-amazon-a-plus-premium-per-brand-vs-per-seller]] carries both phrasings without reconciling them: its title and question say "5 approved A+ projects," while the Amazon text it quotes says "five approved A+ Content modules." The conflict sat unexamined inside a single document.
- [[2026-06-19-kdp-premium-a-plus-eligibility]] resolved the conjunctive-vs-disjunctive question (the criteria are AND, not OR) but used "projects" throughout and never addressed the unit.
- [[2026-06-25-kdp-a-plus-premium-tally-brand-registry-carryover]] reported the thresholds removed around May 2026; [[2026-08-16-squarely-a-plus-five-project-accumulation-path]] downgraded that to UNCONFIRMED against the primary source. That downgrade still stands as of this brief.
- The vault has repeatedly asserted that Basic A+ "tops out at 5 modules." This brief corrects that (see below).
What the web says
- The only Amazon-published statement of the threshold still says "modules," and only "modules." The Seller Central forums announcement from the
News_Amazonaccount lists exactly two bullets: "Brand Story module published on all of your brand-owned product listings" and "Five approved A+ Content modules in the last 12 months." The words "projects" and "submissions" do not appear on the page. The post is ~3 years old, unedited, with no Amazon reply clarifying the unit — including no reply to a seller who explicitly asked whether it meant "modules not whole A+ 'pages'?" (Amazon Seller Forums). - Amazon's own public developer documentation makes "an approved module" a non-entity. In the Selling Partner API, approval is submitted and returned strictly at the content document level:
POST /aplus/2020-11-01/contentDocuments/{contentReferenceKey}/approvalSubmissions, andAPPROVEDis a status property of the content document, described as "The content is approved and published to the applied ASINs" (Create, edit, and publish A+ content). Modules carry no independent approval state anywhere in the model. A counter of "approved modules" would have nothing to count in Amazon's own systems; a counter of approved content documents would. - Amazon defines the container/module relationship explicitly. "A+ content consists of collections of modules (known as a content document)" (A+ Content API use case guide). The content document is what Seller Central's UI calls an A+ "project."
- Two Amazon-side human sources use the project framing. An Amazon staff account replying on the Seller Central Europe forums wrote that eligibility turns on whether "your last five projects have been approved and published within the past year" (
Ezra_Amazon, thread). Separately, a seller quoted an Amazon Support email verbatim: "It requires five individual A+ content project submissions rather A+ content on five different ASINs" (thread). - The vault's module-ceiling figure is wrong for sellers. Amazon: "Content documents for selling partners can contain up to seven modules; content documents for vendors can contain up to five content modules" (Create, edit, and publish A+ content). Five is the vendor ceiling, not the seller ceiling.
- The grant mechanism is batched and the cadence is contradictory. The announcement says only that "Once your brand is enrolled and eligible, you'll see a banner notification in your A+ Content Manager."
Ezra_Amazonsays "Obtaining the Premium A+ access is a monthly process, and it's not automatically granted," with enrollment "during the next monthly enrollment cycle at the beginning of the month." The quoted Support email instead says "Enrollment will be processed every Friday." Amazon's own channels disagree on weekly vs monthly. - The count itself is not stable across Amazon's channels either. A seller in the EU thread stated their requirement as "at least 15 approved A+ Content project submissions in the past 12 months" — evidently from Amazon support or UI copy — and
Ezra_Amazonreplied referencing "last five projects" without reconciling the discrepancy. - The May 2026 "thresholds removed" story remains uncorroborated by any Amazon-published page. Practitioner coverage continues to report Premium A+ opened to all Brand-Registered sellers, quoting a Seller Central notification ("Premium A+ is now available to all Seller Central Brand Owners"), plus a new A+ content quality score (My Amazon Guy; EcomCrew). The evidence is still screenshots and community reports, not an Amazon publication.
Convergences and contradictions
- The literal wording and the mechanism point opposite ways, and the mechanism wins. The single Amazon-published sentence says "modules." But Amazon's own canonical data model has no per-module approval state to count, and both Amazon human channels that have ever elaborated on the rule say projects/submissions. The most economical explanation is that "modules" in a three-year-old forum announcement is loose shorthand — plausibly contaminated by the adjacent bullet, where "Brand Story module" is a genuine, correct use of the term.
- This corrects the vault's prior handling rather than overturning its conclusions. [[2026-07-05-amazon-a-plus-premium-per-brand-vs-per-seller]] used both phrasings interchangeably; that was sloppy but it landed on the right unit. [[2026-06-19-kdp-premium-a-plus-eligibility]] and [[2026-08-16-squarely-a-plus-five-project-accumulation-path]] used "projects" throughout and are confirmed correct. The one brief that was literally accurate — quoting "modules" — was accurate about Amazon's words and misleading about Amazon's meaning.
- Amazon contradicts itself on three separate parameters of the same gate: the unit (modules vs projects), the number (5 vs 15), and the re-evaluation cadence (weekly vs monthly). No single Amazon surface states all criteria consistently. Any confident restatement of "the" Premium A+ gate is overstating the source material.
- One seller data point suggests the count is necessary but not sufficient. A seller reported 16 published Basic A+ pages plus Brand Stories and still no Premium access. That is comfortably over the threshold under either reading, which means something else — batching, Brand Registry role, or an unpublished filter — also gates the grant.
Synthesis for RDCO
Verdict: the threshold is denominated in whole projects/submissions, and one Basic A+ project containing five modules does not satisfy it. The decisive evidence is not a better-worded Amazon sentence — it is Amazon's own data model. Approval in the A+ Content API is an operation performed against a content document and a status returned on a content document. Modules are child elements of that document and never carry an approval state of their own. A rule that counted "approved modules" would be counting something Amazon does not track. Add that the only two Amazon human channels to ever expand on the rule both said "projects" and "project submissions," and the forum announcement's "modules" reads as imprecise drafting rather than a distinct, cheaper eligibility regime. Confidence: medium-high, and it is important to be exact about the shape of the gap. This is a well-grounded inference from Amazon-published primary sources, not a direct quote from an Amazon help page saying "projects." The Seller Central help page that would settle it verbatim is auth-gated and was not reached: sellercentral.amazon.com/help/hub/reference/GHT3GHYARK3M4ZH3 302s to /ap/signin under plain curl and under a real Playwright browser session, and the Wayback Machine holds no captures of Seller Central help nodes because crawlers hit the same sign-in wall. That is an authentication gate, not a Cloudflare-style bot block, so the Playwright workaround that has rescued other fetches here cannot help without credentials. On the narrow question "does an Amazon help page say projects," the honest answer is UNRESOLVED.
The practical consequence is that the swing resolved in the expensive direction, and that is the useful part. The cheap reading — bank one five-module Basic project, clear the gate in a single review cycle — is the one that fails. Five approved projects means five separate authored submissions, five review cycles, and the project-fragmentation strategy [[2026-08-16-squarely-a-plus-five-project-accumulation-path]] sketched under its "threshold still applies" branch. That brief's effort estimate was therefore correct and does not need revising downward, and its recommendation to draft four additional A+ module sets is not relieved by this finding. A secondary correction lands here too: the vault has been carrying "Basic A+ tops out at 5 modules," which is Amazon's vendor ceiling. Sellers get seven. The hypothetical this brief was asked to test was thus built on a wrong ceiling as well as a wrong unit.
Honest framing of the stakes: this closes a research thread rather than unlocking work. Two independent findings drain the practical consequence out of the verdict. First, Premium A+ has no KDP-author equivalent at all — qualifying approvals are Seller-Central, brand-owned-ASIN approvals, so Squarely's books do not sit on the surface where the counter lives ([[2026-08-16-kdp-premium-a-plus-vendor-central-gating]]). Second, the sibling brief filed tonight, [[2026-10-26-squarely-kdp-vs-seller-central-unit-economics]], finds the Seller Central channel migration uneconomic on its own terms. So the correct read is not "we now know how to unlock Premium A+ for Squarely"; it is "the cheaper path we half-hoped existed does not exist, and the expensive path runs through a channel migration we have separately decided against." The value delivered is avoided work: RDCO should not draft four more A+ module sets on the theory that a single five-module project might clear the gate, and should stop spending research cycles on Premium A+ accumulation mechanics.
The methodological lesson is worth more than the answer. This cluster shows a specific failure mode: an Amazon forum post written once, three years ago, with one imprecise noun, propagated into a dozen agency guides and then into four vault briefs — and the one brief that quoted Amazon exactly was the one that transmitted the wrong meaning most convincingly. Verbatim fidelity to a primary source is not the same as correctness when the primary source is itself loose. The thing that actually resolved it was a structural artifact (an API schema) that had no motive to be imprecise, because it has to execute. When a natural-language policy page and a machine-readable schema from the same publisher disagree about what a unit is, the schema is the better witness. That generalizes well beyond Amazon and is worth carrying into how RDCO resolves other vendor-policy ambiguities.
Why this is in the vault
This closes open follow-up #1 of [[2026-08-16-squarely-a-plus-five-project-accumulation-path]] and corrects the loose "modules"/"projects" interchange in [[2026-07-05-amazon-a-plus-premium-per-brand-vs-per-seller]], so the Squarely A+ cluster stops carrying an unexamined 5x effort ambiguity. Operationally it tells RDCO not to draft four additional Squarely A+ module sets as a Premium unlock, and to retire Premium A+ accumulation as an active research line given the channel-migration finding.
Open follow-ups
- Does Amazon's Seller Central help documentation (as opposed to its forum announcements) state the Premium A+ threshold, and in which unit? Unreachable without a signed-in Seller Central account; worth re-attempting only if RDCO ever holds one.
- Why do Amazon's own channels give 5 versus 15 as the count, and is the 15 figure a different marketplace, a different era, or a different content type? Both appear in Amazon-side text within the same thread.
- Is the re-evaluation cadence weekly or monthly? An Amazon staff reply and an Amazon Support email directly contradict each other, which matters for sequencing if the threshold is ever live for an RDCO brand.
- Does the A+ content quality score reported alongside the May 2026 opening function as a replacement gate with its own threshold, and does a brand with no A+ history start below it? Carried forward unresolved from the parent brief.
- Can more than one A+ content document be published against a single ASIN simultaneously? The SP-API has a
getContentDocument-by-ASIN operation that may answer this from public schema documentation alone.
Related
- [[2026-08-16-squarely-a-plus-five-project-accumulation-path]] — the parent brief; this closes its open follow-up #1 and confirms its effort estimate was correct
- [[2026-07-05-amazon-a-plus-premium-per-brand-vs-per-seller]] — carried both phrasings unreconciled; this brief corrects the terminology, not its per-brand conclusion
- [[2026-06-19-kdp-premium-a-plus-eligibility]] — established the conjunctive structure; its "projects" usage is confirmed correct
- [[2026-06-25-kdp-a-plus-premium-tally-brand-registry-carryover]] — reported the thresholds removed; still UNCONFIRMED against any Amazon-published page
- [[2026-08-16-kdp-premium-a-plus-vendor-central-gating]] — Premium A+ does not exist on the KDP surface where Squarely's books live
- [[2026-10-26-squarely-kdp-vs-seller-central-unit-economics]] — sibling brief finding the Seller Central migration uneconomic, which is what drains the stakes here
- [[2026-06-27-kdp-a-plus-content-brand-registry-squarely]] — the Brand Registry gate on the KDP side
- [[2026-06-11-amazon-a-plus-content-draft]] — the existing copy-ready Squarely module set, project one of the five the parent brief called for
Sources
Amazon-published (primary):
- Amazon Seller Forums — "Update to Premium A+ Content eligibility requirements" (
News_Amazon; the only Amazon statement of the threshold; says "modules"): https://sellercentral.amazon.com/seller-forums/discussions/t/301e6741-8ef5-485f-8829-a14c55647f9c - Amazon SP-API — Create, edit, and publish A+ content (approval is a content-document operation and status; seller module ceiling of seven): https://developer-docs.amazon.com/sp-api/docs/create-edit-publish-aplus-content
- Amazon SP-API — A+ Content API use case guide ("A+ content consists of collections of modules (known as a content document)"): https://developer-docs.amazon.com/sp-api/docs/a-plus-content-api-use-case-guide
- Amazon SP-API — A+ Premium Modules (confirms Premium modules ride the same contentDocument endpoints; states no eligibility criteria): https://developer-docs.amazon.com/sp-api/docs/a-plus-premium-modules
- Amazon Seller Forums EU — "Premium A+ Content Eligibility Help" (
Ezra_Amazon: "your last five projects have been approved and published within the past year"; monthly enrollment cycle): https://sellercentral-europe.amazon.com/seller-forums/discussions/t/4c2e17f0-494b-4d45-afab-09a8e9960376 - Amazon Seller Forums — "Premium A+ not eligible after all criteria were met" (seller-quoted Amazon Support email: "five individual A+ content project submissions rather A+ content on five different ASINs"; "Enrollment will be processed every Friday"): https://sellercentral.amazon.com/seller-forums/discussions/t/58b27f5b-ca2a-473d-a825-92ae67fc5126
Blocked (not reached, stated for the record):
- Amazon Seller Central help hub, A+ Content reference node GHT3GHYARK3M4ZH3 — 302 to
/ap/signinunder curl and under a real Playwright browser; authentication gate, not a bot block. No Wayback captures exist for Seller Central help nodes.
Secondary / practitioner (evidence of the confusion, not of the answer):
- My Amazon Guy — Amazon Premium A+ Content free for all sellers: https://myamazonguy.com/news/amazon-premium-a-content-free-for-all-sellers/
- EcomCrew — Premium A+ now free for all Brand-Registered sellers: https://www.ecomcrew.com/amazon-premium-a-content-is-now-free-for-all-brand-registered-sellers/
Vault:
~/rdco-vault/06-reference/research/2026-08-16-squarely-a-plus-five-project-accumulation-path.md~/rdco-vault/06-reference/research/2026-07-05-amazon-a-plus-premium-per-brand-vs-per-seller.md~/rdco-vault/06-reference/research/2026-06-19-kdp-premium-a-plus-eligibility.md~/rdco-vault/06-reference/research/2026-06-25-kdp-a-plus-premium-tally-brand-registry-carryover.md~/rdco-vault/06-reference/research/2026-08-16-kdp-premium-a-plus-vendor-central-gating.md~/rdco-vault/06-reference/research/2026-06-27-kdp-a-plus-content-brand-registry-squarely.md~/rdco-vault/01-projects/squarely-puzzles/2026-06-11-amazon-a-plus-content-draft.md