Amazon Updates Fulfillment Inbound API With Detailed Packing and Weight Guidelines
On March 20 2024 Amazon refreshed the Fulfillment Inbound API (v2024‑03‑20) by adding a supportedPackingMethods array to the listInboundPlanOptions response, exposing a maxWeightLbs attribute for each method and retiring the older supportedConfigurations field. The change is live for US, CA, MX and EU marketplaces (DE, FR, IT, ES, UK), enabling automated weight checks that can reduce inbound shipment rejections.
Overview
Amazon has refreshed the Fulfillment Inbound API (version 2024‑03‑20) by adding a new supportedPackingMethods field. The update, which replaces the deprecated supportedConfigurations attribute, supplies precise packing options and weight caps for each inbound plan. Sellers that depend on third‑party logistics software or custom integration scripts should expect fewer inbound rejections and smoother shipment creation.
Key Points
- New property introduced — The
listInboundPlanOptionscall now returns asupportedPackingMethodsarray that details allowable packing styles and their weight limits. - Legacy field retired — The older
supportedConfigurationselement is marked for removal, forcing developers to migrate their codebases. - Weight limits exposed — Each packing method now includes a maximum weight value, enabling automated checks before a shipment is submitted.
- Marketplace coverage — The change is live for Amazon’s North American (US, CA, MX) and European (DE, FR, IT, ES, UK) sites, with plans to roll out to additional regions.
- Improved validation — By delivering granular packing rules through the API, Amazon reduces the need for hard‑coded assumptions in third‑party tools.
- Impact on rejection rates — Early compliance checks based on the new data can cut inbound shipment refusals, saving sellers time and repackaging costs.
What's Changing
- SupportedPackingMethods replaces SupportedConfigurations — The response payload for
listInboundPlanOptionsnow contains asupportedPackingMethodslist. For example, a standard inbound plan might return entries such as “Boxed” with a 50‑lb ceiling and “Polybag” with a 10‑lb ceiling, whereas the old field only indicated that a plan was “supported” without specifics. - Explicit weight thresholds per method — Each packing method entry includes a attribute. If a seller attempts to assign a 55‑lb weight to a “Boxed” method, the API can flag the issue before the shipment is created.
Analysis & Recommendations
Why This Matters
Developers can now programmatically enforce packing rules, preventing errors that previously caused inbound rejections and repackaging fees. Sellers operating in North America and Europe will see fewer shipment refusals and faster inventory availability thanks to pre‑flight validation using the new maxWeightLbs data.
Key Takeaways
- supportedPackingMethods replaces the deprecated supportedConfigurations field in listInboundPlanOptions.
- Each packing method now includes a maxWeightLbs value (e.g., Boxed = 50 lb, Polybag = 10 lb).
- The update applies to US, CA, MX and EU marketplaces (DE, FR, IT, ES, UK).
- Early validation using maxWeightLbs can cut inbound shipment refusals and repackaging costs.
Recommended Actions
- →In your integration code (e.g., Python scripts), replace any reference to plan['supportedConfigurations'] with plan['supportedPackingMethods'] and ...
- →Add a pre‑submission validation step that compares each package's calculated weight to the maxWeightLbs returned for the selected packing method, a...
- →Update the shipment creation UI to display the weight ceiling next to each packing option (e.g., "Boxed – up to 50 lb") using the marketplace‑speci...
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!