Update: ShipFromSupplySourceId attribute added to Order feeds attributes
In early 2024 Amazon added the required ShipFromSupplySourceId attribute to order‑fulfillment feeds (POST_ORDER_FULFILLMENT_DATA and POST_FLAT_FILE_FULFILLMENT_DATA). Sellers must send Amazon‑assigned IDs such as “AMZ‑WS‑001” or the feed fails with InvalidSupplySourceId.
Overview
Amazon rolled out a new feed attribute named ShipFromSupplySourceId in early 2024 for its order‑fulfillment submissions. The field lets sellers pinpoint the exact warehouse, sortation center, or third‑party logistics partner that dispatched each order. Updating integrations to include this identifier is essential to avoid feed rejections and to keep inventory counts aligned with the correct fulfillment node.
Key Points
- Attribute introduction — ShipFromSupplySourceId is now a required element in both XML‑based and flat‑file order‑fulfillment feeds.
- Applicable feeds — The field is only relevant for the POST_ORDER_FULFILLMENT_DATA and POST_FLAT_FILE_FULFILLMENT_DATA endpoints.
- Supply‑source ID format — Sellers must supply the internal Amazon‑assigned identifier (for example, “AMZ‑WS‑001”) that corresponds to the location that shipped the order.
- Inventory reconciliation — Tagging each shipment with the correct source enables Amazon’s inventory engine to deduct stock from the right node, preventing oversell alerts and stock‑out mismatches.
- Error response — Omission of the attribute or use of an unregistered ID triggers a FeedProcessingError with the code
InvalidSupplySourceId, causing the entire feed to fail. - Automation impact — Systems that generate feeds automatically will need to pull the latest supply‑source list and map it to every fulfillment line before submission.
How ShipFromSupplySourceId Works
-
Retrieve the list of active supply sources — Call the GET /supplySources API to obtain every warehouse or 3PL ID linked to the seller account.
- Example: A seller operating two fulfillment centers receives “AMZ‑WS‑001” for the East‑Coast hub and “AMZ‑WS‑002” for the West‑Coast hub.
-
— In the XML feed, add a element; in a flat‑file, populate the “ship‑from‑supply‑source‑id” column for every line item.
Analysis & Recommendations
Why This Matters
Missing or incorrect ShipFromSupplySourceId triggers a FeedProcessingError that rejects the entire feed, causing order delays and inventory mismatches. Correct IDs ensure stock is deducted from the right warehouse, preventing oversell alerts and preserving Buy Box performance.
Key Takeaways
- ShipFromSupplySourceId is now mandatory in both XML and flat‑file order‑fulfillment feeds for POST_ORDER_FULFILLMENT_DATA and POST_FLAT_FILE_FULFIL...
- Feeds lacking the attribute or using an unregistered ID return FeedProcessingError code InvalidSupplySourceId, causing full feed failure.
- Supply‑source IDs must match Amazon‑assigned values (e.g., “AMZ‑WS‑001”); retrieve the current list via the GET /supplySources SP‑API endpoint.
- When validated, Amazon deducts inventory from the specified node, improving stock accuracy across multiple fulfillment locations.
Recommended Actions
- →Update your feed generation code or Seller Central templates to add a <ShipFromSupplySourceId> element or a “ship‑from‑supply‑source‑id” column for...
- →Create a nightly job that calls GET /supplySources via SP‑API, stores the IDs locally, and uses the lookup when building feeds.
- →Run a pilot feed of ≤10 orders with mixed IDs, submit to POST_ORDER_FULFILLMENT_DATA, and verify the Feed Processing Report shows no InvalidSupplyS...
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!