Amazon Direct Fulfillment EDI
Amazon Direct Fulfillment EDI is how Amazon sends dropship orders to you as a Vendor Central supplier, and you ship each one straight to the end customer rather than to an Amazon warehouse. It runs on the same Vendor Central account as Wholesale, as its own EDI connection, which we build inside your ERP.
+ RULES
Amazon Direct Fulfillment EDI documents
-
850Dropship purchase order. Amazon places an order on behalf of the end customer, which your ERP has to fulfil directly rather than from Amazon-held stock. -
856Advance ship notice, to the end customer. Carrier and delivery details have to match what was actually arranged for shipping to the customer, not an Amazon fulfillment center. -
810Invoice. Billed to Amazon for the dropshipped order, matched against the ASN as with any other invoice.
How we build Amazon Direct Fulfillment EDI inside your ERP
Shipping to the customer, not to a warehouse
Every dropship order goes to an individual address, so the ship notice is built from the carrier and service actually used for that parcel rather than from a warehouse-to-warehouse assumption.
Built separately from Wholesale
Even on the same Vendor Central account, Direct Fulfillment gets its own mapping, because a rule change in one program should never touch the other. See Amazon EDI integration for how Direct Fulfillment, Wholesale and Seller Central fit together.
Direct connection to Amazon
Direct Fulfillment connects straight to Amazon, with no network in between. Every X12 file is read and generated inside your ERP using the EdiFabric .NET library. For what each document does, see EDI transaction sets explained.
Amazon Direct Fulfillment EDI in a live ERP
- Off Sage, with the operating history intact: Customers, vendors, items and transaction history were migrated from Sage into a browser-based ERP covering order-to-cash and procure-to-pay, with a full general ledger, receivables and payables, so the business changed systems without losing its records.
- Native EDI inside the ERP: Every X12 document, including 850, 855, 856, 810, 846 and 997, is read and generated inside the ERP using the EdiFabric .NET library, with the mapping in its own code and no external translation service. Amazon Vendor Central (Wholesale and Direct Fulfillment) and Adorama connect directly over SFTP. Best Buy Optics, Costco Wholesale and Colony Brands run through SPS Commerce. Best Buy Purchasing, Bluestem Brands, QVC, Staples Advantage and Staples the Office Superstore run through CommerceHub (Rithum). BI Worldwide and Mason Companies run through Radial. The ERP uploads its own files to each network's FTP and reads the files the network delivers, and the network validates them and delivers them to the retailer. HSN, Harco Industries, Knocking and Verdi Commerce run on automated file exchange over FTP. Scheduled EDI jobs poll FTP on schedules as short as every ten minutes. Walmart runs through its API. The Walmart API integration imports WFS and seller-fulfilled orders, sends shipment confirmation and tracking back for seller-fulfilled orders, marks WFS orders shipped and invoices them automatically, turns returns into credit memos, and creates WFS inbound shipments. Every job is tracked on a monitoring dashboard.
- Every channel in one order queue: Amazon Vendor Central and Seller Central (SP-API), Walmart, HSN, QVC, Costco, several Shopify storefronts, eBay and direct wholesale accounts land in one system. Vendor Central purchase orders are accepted or rejected back to Amazon from the same screen that shows system, 3PL and allocated stock.
- Multi-warehouse and multi-3PL stock: Real-time inventory across an owned warehouse operated with a logistics partner, a second third-party warehouse and Amazon fulfillment locations, with warehouse transfer orders and an Amazon inbound shipment request action for FBA.
- FBA inbound shipment automation: End-to-end FBA inbound automation via SP-API: shipment creation, selection of the lowest-cost shipping plan, packing slip generation, label download and routing to the warehouse.
Amazon Direct Fulfillment EDI questions
Do we need a separate Amazon account for Direct Fulfillment?
No. Direct Fulfillment runs on the same Vendor Central account as Wholesale, but Amazon treats the two as separate programs with different rules.
How is Direct Fulfillment different from Wholesale?
Wholesale ships stock to Amazon fulfillment centers. Direct Fulfillment ships each order straight to the customer, so the order, ship notice and invoice flow is built separately.
Why do Direct Fulfillment ship notices get rejected?
Start by comparing the ship notice with the order and with what actually shipped to the customer, field by field, using the raw file that was sent. We trace a rejection to the specific mismatch rather than resending blind.
Is EDI 753/754 used with Amazon Direct Fulfillment?
No. 753 routing requests and 754 routing instructions are used with Vendor Central Wholesale shipments, not Direct Fulfillment. See EDI 753 and 754 routing.
What if a Direct Fulfillment EDI order has a problem?
EDI is the normal path. When Direct Fulfillment EDI orders have a problem, the orders can be imported from a CSV file as a fallback, so dropship orders keep shipping while the EDI issue is fixed.
Can this integrate with our own carrier rate-shopping?
Yes. Since you are shipping directly to the end customer rather than an Amazon fulfillment center, live carrier rate-shopping across FedEx, UPS and USPS fits naturally into the same order flow.
Related to Amazon Direct Fulfillment EDI
Shipping dropship orders for Amazon and fighting rejected ship notices?
Tell us what the rejection message says and we will tell you whether it is a carrier, delivery detail or address mismatch.