SP-API Breaking Change: 'DEFAULT' Value Added to getCompetitiveSummary Starting June 6
Amazon adds a new enum value "DEFAULT" to the customerMembership field of the getCompetitiveSummary SP‑API operation. The revised OpenAPI spec is published on March 28 2025 and the live change takes effect on June 6 2025, giving roughly 70 days to update clients.
Overview
Amazon will introduce a third enumeration value, DEFAULT, to the customerMembership field returned by the Selling Partner API (SP‑API) getCompetitiveSummary operation on June 6 2025. The change expands the existing binary options—PRIME and NON_PRIME—to cover cases where a shopper’s membership status cannot be classified. Sellers who rely on this endpoint must adjust their code before the rollout, or risk runtime errors and data‑pipeline failures.
Key Points
- New enum entry — Starting June 6 2025, API responses may contain
customerMembership: "DEFAULT"alongside the currentPRIMEandNON_PRIMEvalues. - Breaking impact — Applications that enforce strict enum validation or use exhaustive
switch/caselogic for the three values will throw exceptions whenDEFAULTappears. - Global rollout — The modification applies to every Amazon marketplace, from the United States to Japan and Europe.
- Two‑phase deployment – The updated Swagger definition is released on March 28 2025, giving developers roughly 70 days to regenerate clients and test the new value.
- Database risk – Any schema that restricts the
customerMembershipcolumn to the original two values will reject incomingDEFAULTentries, causing insert errors. - Business‑logic shift – Repricing algorithms that separate data into “Prime” and “non‑Prime” buckets must decide how to treat the new “Default” segment.
What's Changing
-
Swagger model update — On March 28 2025 Amazon publishes a revised OpenAPI specification that adds
DEFAULTto thecustomerMembershipenum.- Example: A Java client generated from the old spec will list only and ; after regeneration, the enum class will include a third constant, .
Analysis & Recommendations
Why This Matters
From June 6 2025 the API may return "DEFAULT", causing strict enum checks or ENUM‑constrained columns to throw errors and halt pricing pipelines. Without updates, sellers risk runtime exceptions, failed database inserts, and inaccurate repricing decisions across all marketplaces.
Key Takeaways
- New enum entry "DEFAULT" joins existing PRIME and NON_PRIME values in customerMembership.
- Swagger update released March 28 2025, ~70 days before the June 6 2025 rollout.
- Database columns limited to ENUM('PRIME','NON_PRIME') will reject "DEFAULT" rows, causing insert failures.
- Any exhaustive switch/case logic without a fallback will raise exceptions once "DEFAULT" appears.
Recommended Actions
- →Download the updated Swagger file from Seller Central > API > SP‑API > Documentation (March 28 2025) and regenerate SDKs for all languages used.
- →Alter DB schema: run ALTER TABLE competitive_prices MODIFY membership_type ENUM('PRIME','NON_PRIME','DEFAULT') NOT NULL; in your MySQL console.
- →Update code validation: replace strict checks with membership in ('PRIME','NON_PRIME','DEFAULT') or add an else branch that logs unexpected values.
Comments
Join the discussion
Log in or create an account to share your thoughts on this update.
No comments yet. Be the first to share your thoughts!