
30 Jun 2026
Amazon Is Retiring the Legacy Sponsored Brands Product Collection API. Here Is Your Migration Timeline.
If your team, agency, or software relies on the Amazon Ads API to create Sponsored Brands ads, a deprecation clock has started. The legacy Product Collection ad type is being phased out of the API in two stages, and the second stage removes any safety net.
What Is Actually Changing
Amazon’s Sponsored Brands API has long supported the Product Collection ad format as a core ad type alongside Store Spotlight and Brand Video. That format is now being consolidated into the newer Sponsored Brands Collections structure — primarily Manual Collection ads — across both API and self-service interfaces.
This is not happening in isolation. Amazon already replaced Sponsored Brands Product Collections on the UI side with an AI-powered format starting January 28, 2026, requiring a minimum of three ASINs and up to ten per ad, and eliminating custom creative — no custom headlines, no lifestyle images. Amazon’s AI now dynamically selects which products to show based on the individual shopper’s browsing history, purchase patterns, and search intent, rather than advertisers controlling a fixed creative.
The API deprecation is the second half of that same transition — bringing programmatic ad creation in line with what the self-service console already enforces.
The Two-Stage Timeline
Starting in September 2026, old API requests that create a Product Collection ad will still be processed, but Amazon will automatically convert them into a Manual Collection ad behind the scenes. If your integration submits a custom image with the request, the API will accept it without error, but the image will not display anywhere on the live ad. This is the dangerous middle stage: no error message, but the output silently does not match the request.
Starting in January 2027, the legacy endpoints will shut down entirely. Any tool, script, or automation that still attempts to create the old Product Collection format will receive an outright error, with no automatic fallback to the new structure.
For teams running automated campaign creation at scale, the September-to-January window is when integrations appear to be working while quietly producing ads that do not look as configured. That gap is the real operational risk — not the eventual shutoff.
Two Technical Details That Trip Up Migrations
Manual Collection ads require at least 3 ASINs. This mirrors the three-ASIN minimum already enforced on the self-service side since January 2026. Any API request with fewer than three products will fail outright once it routes through the new structure — there is no fallback to a single-product format.
This applies across both API versions. If your integration is built on V1 and uses the productCollectionSettings field, that field maps automatically to manualCollectionSettings under the new structure. Functionally, the mapping happens transparently — but it means the underlying ad behavior, including the loss of custom creative support, applies even to V1 integrations that were not explicitly updated for the new format.
Why This Matters Beyond a Technical Footnote
Brands with fewer than three ASINs lose access to product collections entirely under the new structure. If your campaign architecture relies on single-product or two-product Sponsored Brands collections — a common setup for brands with limited catalog depth or for highlighting a hero product — those campaigns cannot be recreated under the new API structure once the legacy endpoints shut down in January 2027.
Existing campaigns with fewer than three ASINs can continue running, but no new ad groups can be created with fewer than three products, and Amazon is expected to retire legacy campaigns entirely over time. That is a structural constraint, not a temporary inconvenience — brands need to plan their collection campaigns around the 3-to-10 ASIN range as a permanent requirement.
The removal of custom creative is the other change worth internalizing. Custom headlines, lifestyle images, and branded creatives are eliminated entirely under the new format, replaced by Amazon’s standardized, AI-driven presentation. Any agency or team that built differentiation into Sponsored Brands through custom imagery will need to shift that creative investment elsewhere — A+ Content, Brand Store design, or DSP creative — since Sponsored Brands Collections no longer supports it.
What PPC Teams and Software Providers Should Do Before September
The action items here are specific and time-sensitive.
Audit every integration, script, or third-party tool that creates Sponsored Brands ads through the API. Identify which ones are still building requests against the legacy Product Collection format. This includes internal automation, agency tooling, and any third-party software your team relies on for bulk campaign management.
Test the new Manual Collection structure now, while both formats are still live and before the September silent-conversion period begins. Confirm your integration correctly builds requests with a minimum of three ASINs, and verify that any creative assets you are submitting are either compatible with the new format or being phased out of your workflow.
Review every existing Sponsored Brands collections campaign with fewer than three ASINs. These campaigns can continue running for now, but cannot be expanded or recreated under the new structure. If a single-product Sponsored Brands placement is core to your strategy, plan an alternative — restructuring to a qualifying multi-ASIN collection, or shifting that budget to a different ad type — before the legacy infrastructure disappears.
If you manage Sponsored Brands programmatically through V1 and rely on productCollectionSettings, confirm with your engineering team or software provider that the automatic mapping to manualCollectionSettings has been tested and produces the ad behavior you expect — not just that the API call succeeds without error.
The Bigger Pattern
This deprecation is consistent with the direction Amazon has been moving across its advertising stack throughout 2026: standardized, AI-driven ad formats replacing manual creative control, and infrastructure consolidation that reduces the number of legacy formats advertisers and developers need to support.
For PPC teams, agencies, and software providers, the practical takeaway is straightforward: September 2026 is when the risk becomes invisible — requests succeed, but the creative silently fails to display. January 2027 is when the risk becomes loud — requests fail outright with no fallback. The right time to migrate is before either date, so testing and validation can proceed without disrupting the live campaign.
If you want to stay updated on Amazon changes, subscribe to our blog.
If you need support with PPC, DSP, AMC, analytics, or a long-term growth strategy, contact the ANavigator team at info@anavigator.co
Book a call to get a FREE AUDIT by the link below: 

Book a call – FREE AUDIT
Follow my Weekly Newsletter on LinkedIn:
/ amazon-digest-for-brands-7232361008185372672
Follow me on LinkedIn:
/ ookovalov
Follow ANavigator on social media:
/ anavigator
/@anavigator_official
/ anavigator7
/ @anavigators
LinkedIn page to contact us:



