Amazon has scheduled changes to required and optional listing attributes and accepted values for November 16, 2026, according to its November 11 developer notice. The update applies when integrations create or edit products with offers through Listings Items API v2021-08-01 or JSON_LISTINGS_FEED.
For sellers who use catalog software or an internal integration, the immediate task is to have the integration owner check the affected product types and field mappings. This notice does not establish that every existing listing needs an edit.
Filter Amazon’s November workbook to Upcoming changes before reviewing your catalog. The same file also contains changes marked Published, which should not be presented as new November 16 requirements.
Which submissions are covered
Amazon addresses both private and public developers. Its notice excludes product-only listings, XSD uploads and XML uploads. The metadata update table lists 23 stores for November 16, including the U.S., Canada, Mexico, the UK, Germany, Japan and Australia. The individual changes depend on the store and product type.
The changes cover whether a field is required or optional and which predefined values Amazon accepts. An integration that sends an outdated value or omits an applicable required field may need a mapping or validation update. That is a workflow risk to check, not evidence that submissions are already failing.
Three U.S. examples are conditional
The workbook’s Upcoming U.S. rows include these exact display labels, each marked for both first-party and third-party contributors:
ALARM: Compliance – Power Source Type.ANIMAL_CARRIER: Compliance – Animal Carrier Type.AREA_DEODORIZER: Compliance – Area Care Physical Form.
For each example, Amazon says the new attribute becomes required when a dependent attribute is filled. The workbook does not name that dependency in these rows. These are display labels, not verified JSON property names, and they should not be treated as universally required fields.
What to check with your integration owner
- Confirm whether your catalog connection uses one of the two affected submission methods and creates or edits products with offers.
- Match Upcoming workbook rows to your marketplace, product type and contributor type. Review the update description and accepted values for each match.
- Compare affected mappings with the relevant product-type definitions. Resolve conditional dependencies before deciding which records need additional data.
- Validate a representative submission for each affected workflow and inspect its returned issues. Keep a record of the field, value and response so a mapping problem can be traced.
Avoid a catalog-wide edit based solely on this announcement. November 16 is the stated effective date. The reviewed sources do not provide a separate blanket suppression deadline, remediation window or precise activation time.
Sources and scope
Checked November 12, 2026 at 9:00:33 a.m. EST. Sources: Amazon’s November 11 announcement, SP-API metadata update table and November 2026 workbook. The three documents come from one Amazon source organization, not three independent confirmations.
The examples above use only Upcoming rows. The table and workbook do not establish their original publication dates. Seller Squash has not tested a seller account or API submission, and no broad seller impact has been verified. The featured image is an editorial illustration, not an Amazon interface or actual listing.

