Reported details
What happened
Starting October 1, 2026, Merchant Fulfillment API v0 is scheduled to introduce DeliveryConfirmationWithIdentityCheck and DeliveryConfirmationWithNameVerification.
The new enum values apply to the DeliveryExperience and DeliveryExperienceOption fields.
Amazon identifies the affected operations as getEligibleShipmentServices and createShipment.
The documented change is specific to domestic shipments in the Germany Amazon store; the event carries a global market-applicability label, but no broader store-level rollout is stated.
Business relevance
Why it matters
Any integration that validates, maps, or stores delivery-experience enum values could need an update before the effective date.
If a merchant’s workflow uses the affected operations for Germany domestic shipments, unrecognized values could require handling in application logic or operational review.
Editorial perspective
Analysis & judgment
This is an enum-expansion change rather than evidence of a new merchant obligation. Its practical significance depends on whether a seller or software provider consumes these fields and assumes the current value set is exhaustive.
The two names indicate distinct confirmation options, but the supplied evidence does not explain their operational rules, carrier availability, eligibility criteria, or customer-facing behavior. Those details should be confirmed in Amazon’s current API documentation before implementation.
Applicability
Seller impact
Sellers using custom or third-party shipping integrations for domestic Germany orders may need their provider to recognize the two additional values.
Merchants relying on strict enum validation should check whether their systems fail, discard, or safely pass through an unfamiliar DeliveryExperience or DeliveryExperienceOption value.
Action plan
What to do now
- 1
Identify affected integrations
nowIf you use getEligibleShipmentServices or createShipment for domestic shipments in the Germany Amazon store, ask your developer or integration provider whether these fields are parsed or validated against a fixed enum list.
- 2
Plan a compatibility check
this-weekBefore October 1, 2026, test or review handling for DeliveryConfirmationWithIdentityCheck and DeliveryConfirmationWithNameVerification if your integration can receive or submit the affected fields.
- 3
Recheck Amazon documentation
monitorMonitor the official Amazon Selling Partner API Release Notes and related API documentation for eligibility, carrier, and rollout details that are not included in the supplied announcement.
What not to do yet
- Do not assume that every Amazon store, shipment type, carrier, or fulfillment workflow supports the new values; the supplied evidence only identifies domestic shipments in the Germany Amazon store.
Sources & context
Evidence and sources
A source may provide only a headline or summary. Read the evidence scope below. Links and workflow checks are not independent fact verification. Internal confidence values are workflow signals, not probabilities of factual correctness.
- 01Source link
Starting October 1, 2026, the Merchant Fulfillment API v0 will introduce two new enum values:DeliveryConfirmationWithIdentityCheck and DeliveryConfirmationWithNameVerification for the DeliveryExperience and DeliveryExperienceOption fields in the getEligibleShipmentServices and createShipmentAPIs. Th...
Amazon Selling Partner API Release Notes · Workflow status: single-source
Retrieved: September 16, 2026 at 10:07 p.m. UTC
Claim is bounded to the ingested title or summary; no source body or quotation is retained.