Direct-to-consumer brands on Shopify eventually get the email every founder wants: a retailer would like to carry the product. Then comes the attachment about EDI requirements, and suddenly a storefront that has only ever spoken webhooks needs to speak X12. The good news is that dropship EDI — the form most Shopify merchants encounter first — maps almost perfectly onto what a Shopify store already does all day: receive an order, fulfill a parcel, hand back a tracking number.
The dropship shape of Shopify EDI
When a retail partner lists your catalog and you ship to their customers, three document flows carry the whole program. Inventory goes out as an 846 so the partner knows what's sellable. Orders arrive as 850s with a consumer's home address as the ship-to. Fulfillment goes back as an 856 whose tracking number feeds the customer's order-status page — the exact loop partners like Wayfair and Chewy run at scale, and the one covered broadly in our retail solutions overview.
What maps to what
The EDISQ connector rides Shopify's own objects rather than inventing parallel ones:
- Shopify inventory levels → 846. Stock positions publish to the partner on their required cadence, keeping listings live and oversells at bay.
- Inbound 850 → Shopify order. Each PO becomes an order with your variants resolved from the retailer's item identifiers and the consumer ship-to intact. Your team — or your 3PL watching the same store — fulfills it like any other order.
- 855 out — order confirmation returned to the partner automatically.
- Shopify fulfillment → 856. The moment a fulfillment with a tracking number exists, the connector composes the ASN — carrier, tracking, shipment detail — and transmits it. No portal, no spreadsheet.
- 810 invoice out. Shopify isn't an invoicing system, so the connector generates the invoice from the order and fulfillment data, referencing the PO the way the partner's payables process demands.
Item mapping deserves the setup attention: retailers order by their SKUs and UPCs, Shopify thinks in variants, and the cross-reference between them is what makes the whole loop hands-free.
The arrangement also plays well with outsourced fulfillment. If a 3PL app already fulfills your Shopify orders, EDI orders inherit that path automatically — they enter as orders, the 3PL ships them, the tracking number posts back, and the connector turns it into the partner-facing ASN. Nothing about your fulfillment stack has to know EDI exists.
Going live
Four moves: install the connection against your store; pick your partner from the directory (each with certified maps preloaded); wire the item cross-reference between the partner's identifiers and your variants; then test — the sandbox replays the partner's scenarios so certification passes without surprises. Dropship programs also come with service-level expectations around inventory freshness and ASN timing, which is precisely why the integration automates those two flows first. For program-level specifics, the Wayfair requirements guide shows what a demanding dropship partner actually measures.
Scaling to a second or third retail partner is where the architecture pays off. The Shopify side never changes — same store, same products, same fulfillment. Each new partner is a new set of maps and cross-references on the EDISQ side, so a brand can go from one dropship program to five without its operations team feeling the difference.
The bill for a storefront
Dropship generates many small documents — an 846 here, four documents per consumer order there — and EDISQ's meter was built for that texture. Monthly documents start free through 25, then price from $0.50 apiece, declining to $0.10 in the top bracket, with each tier's rate applying only to the documents inside it. Little else appears on the invoice: no mapping or setup line, the AS2/SFTP/VAN transport included, and a $100/month Production minimum that applies in full to document usage. Estimate your order volume against the ladder on the pricing page.
FAQ
Why would a Shopify store need EDI?
Because wholesale and dropship partners require it. Selling your DTC catalog through a retailer's site or shelves means trading POs, ship notices, and invoices as EDI documents — Shopify alone doesn't speak that language.
How do EDI orders get into Shopify?
The connector converts each inbound 850 into a Shopify order, with the retailer's items mapped to your variants and the consumer ship-to carried through, so fulfillment runs exactly like your DTC orders.
Where does the 856 come from?
From your normal fulfillment step. When the order is fulfilled with a tracking number, the connector builds and transmits the ASN — carrier and tracking included — without separate data entry.