06-reference/research

amazon premium a plus modules vs projects threshold

2026-10-26·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
amazona-plus-contentpremium-a-plussquarelyecommerce

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)

What the web says

Convergences and contradictions

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

Related

Sources

Amazon-published (primary):

Blocked (not reached, stated for the record):

Secondary / practitioner (evidence of the confusion, not of the answer):

Vault: