New Enum Values for Domestic Shipments in the Germany Amazon Store
Amazon is updating the Merchant Fulfillment API v0 to include new enum values for DHL Paket National Shipping in Germany. Starting October 1, 2026, the schema will include `DeliveryConfirmationWithIdentityCheck` and `DeliveryConfirmationWithNameVerification`.
Back to All 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. These value-added delivery verification services are available through the DHL Paket National Shipping service in the Germany (DE) Amazon store. ❗️
Important
Schema change notice: If your integration strictly validates or deserializes enum values against a fixed list, it may fail when encountering the new values. We strongly recommend implementing flexible enum handling to accommodate new values gracefully.
Which Amazon Stores are affected?
This change applies to the Germany (DE) Amazon store. 📘
Note
The API schema changes (new enum values) are global and will be present in the worldwide API model.
Who is affected?
Developers with applications that integrate with the Merchant Fulfillment API v0 (getEligibleShipmentServices, createShipment) are affected by this change. This is particularly relevant for:
- Germany Amazon store merchants using DHL Paket National Shipping service
- Integrators who strictly validate API response schemas
What action is required?
If you have an application that is affected by this change, you must:
- Update your shipping service processing logic to handle DeliveryConfirmationWithIdentityCheckand DeliveryConfirmationWithNameVerificationas new values in the DeliveryExperienceand DeliveryExperienceOptionenum fields in the getEligibleShipmentServices/createShipmentAPI request and response.
- Update your deserialization logic to accept these new values if you use strict enum validation.
- Implement flexible enum handling to accommodate new values gracefully. This will protect your integration against future enhancements as well.
For more information
To learn more about the getEligibleShipmentServices API, refer to getEligibleShipmentServices reference documentation.
Analysis & Recommendations
Why This Matters
Developers using rigid deserialization or hardcoded enum lists in the `getEligibleShipmentServices` and `createShipment` endpoints risk total shipment processing failures. Failure to implement flexible validation could halt logistics pipelines for German domestic orders.
Key Takeaways
- New enum values `DeliveryConfirmationWithIdentityCheck` and `DeliveryConfirmationWithNameVerification` will be integrated on October 1, 2026.
- The update specifically targets the DHL Paket National Shipping service within the Amazon Germany (DE) marketplace.
- Affected API endpoints include `getEligibleShipmentServices` and `createShipment` via the Merchant Fulfillment API v0.
- The schema expansion affects the `DeliveryExperience` and `DeliveryExperienceOption` fields.
Recommended Actions
- →Audit codebase for all calls to `getEligibleShipmentServices` and `createShipment` to identify hardcoded enum validation logic.
- →Refactor shipping software to use flexible deserialization or a 'graceful degradation' pattern for unknown enum values.
- →Use the Amazon developer sandbox to simulate the new identity check strings to verify system stability.
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!