Integration guides · October 15, 2026

WooCommerce EDI Integration: Complete Guide

Adding retail EDI to a WooCommerce store — 850s becoming Woo orders, stock levels publishing as 846 feeds, and tracking numbers driving the 856.

WooCommerce powers a vast share of independent ecommerce, which means a vast share of the brands now being invited into retailer dropship programs run their businesses on WordPress. Those invitations come with an EDI requirements document, and the honest reaction of most Woo store owners is: with what? The store has products, orders, and stock — it has never heard of X12. Bridging that gap is precisely scoped work, and it's worth seeing how small the gap actually is.

Dropship EDI is a storefront pattern

For WooCommerce merchants, EDI almost always means dropship: a retail partner lists your products and forwards each consumer sale for you to fulfill. Squint and that's just... an online order — which is why the integration can lean so heavily on what Woo already does. The partner needs three things your store already knows: what's in stock, confirmation you received the order, and the tracking number once it ships. EDI is those three facts in a formal costume, and it's the loop retailers like Chewy and Wayfair operate with thousands of suppliers.

Translating between Woo and X12

The EDISQ connector maps each flow onto native WooCommerce data:

  • Stock levels → 846. Your product inventory publishes to the partner on the cadence their program requires, keeping listings live and preventing the oversells that dropship programs charge back.
  • 850 → WooCommerce order. Each retailer PO arrives, passes partner-rule validation, and is created as a Woo order — the partner's item identifiers resolved to your products, the consumer's ship-to address attached. Fulfillment sees it like any other order.
  • Confirmation → 855, returned automatically so the partner's clock never runs out on you.
  • Tracking number → 856. When the order ships and tracking exists, the connector composes the ship notice — carrier and tracking included, since that's what populates the retailer's customer-facing tracking page — and transmits at handoff.
  • Order data → 810. WooCommerce doesn't issue invoices to retail partners, so the connector generates the per-order invoice from order and shipment data, referenced the way the partner's payables require.

What setup involves

Standing this up doesn't resemble a WordPress plugin install so much as a short data project. The connector links to your store; the trading partner is enabled from EDISQ's directory, which loads that program's certified maps and validation; then comes the substantive step — cross-referencing the partner's SKUs and identifiers to your WooCommerce products, the table every document will consult from then on. Testing replays the partner's own scenarios in a sandbox before anything touches production, and connectivity — AS2, SFTP, or VAN, per the partner's requirement — exists on EDISQ's side with nothing to host in your WordPress stack. The broader dropship operating rhythm, including inventory cadence and ASN timing expectations, is covered in our retail solutions overview and the dropship operations deep-dive.

One caution specific to the platform: WooCommerce stock accuracy is only as good as the store's discipline. If your Woo inventory drifts from physical reality — manual adjustments, offline sales, a warehouse spreadsheet on the side — the 846 faithfully transmits the drift, and the partner's oversell charges land on you. Dropship programs effectively convert inventory hygiene from a nice-to-have into a billable obligation, so tighten the stock process before connecting the feed, not after the first charge.

Priced for stores, not enterprises

An independent Woo merchant's first dropship program might move a few dozen orders a month, and EDISQ's model is deliberately survivable at that scale: the first 25 documents monthly are free, and past them each document bills from $0.50, sliding to $0.10 as volume grows, on strictly marginal tiers. Mapping, setup, and transport are simply part of the service; building and testing on Self-Serve carries no monthly fee, and going live is a $100/month Production minimum applied in full to usage. A small program can start at zero in the sandbox and scale linearly from there — the ladder is on the pricing page, alongside the WooCommerce integration page for connector details.

FAQ

Can WooCommerce handle EDI orders natively?

No — WooCommerce is a WordPress storefront with no EDI capability of its own. The EDISQ connector translates retailer documents into Woo orders and builds outbound EDI from your store's order and stock data.

Which EDI documents does a WooCommerce dropship program use?

Typically the 846 inventory feed out, the 850 order in, an 855 confirmation, the 856 with tracking, and an 810 invoice per order — the standard dropship loop layered onto your existing store.

Does my fulfillment process have to change?

Barely. EDI orders appear alongside your DTC orders and ship the same way; the connector watches for the tracking number and handles the partner-facing documents from there.