Burlington EDI Requirements: How to Become Compliant

Every Burlington purchase order is a one-shot deal. Off-price buys arrive with final quantities and firm ship windows, and no reorder behind them — the PO in your inbox is the entire transaction, and the vendor guide tells you exactly how Burlington expects it executed. Compliance with Burlington is therefore a precision exercise: one order, one window, one chance to match the paperwork to the freight.

The routing guide is the contract

Burlington publishes its expectations — routing, labeling, ASN rules — in the vendor guide, and its vendor compliance program enforces them with chargebacks focused on routing and ASN performance. This is worth internalizing early: the guide isn't advisory reading, it's the standard your shipments are graded against. The efficient response is to encode the guide's document rules into your EDI layer once, so every 856 that leaves your system is already compliant rather than hopefully compliant.

Processing the one-shot PO

The 850 carries a Burlington item and UPC cross-reference, with assortments expanding at the line level. Because quantities are final, order intake deserves ceremony: land the PO in your system unmodified, resolve every line against your item master immediately, and surface anything unmappable the same day — with a firm window, discovery time is fulfillment time you don't get back.

Assortment expansion is the quiet risk. A prepack that unfolds incorrectly at order intake becomes a carton-content mismatch at packing, which becomes a chargeback at receiving. Validate the expansion logic during setup, against real orders, before the first live buy.

Three artifacts, one truth

At the DC, Burlington audits what most off-price retailers audit: the packing list and the cartons must agree, and UCC-128 carton labels must match the MAN serials in the 856. The ASN itself must be in Burlington's system before the freight arrives.

The engineering answer is single-sourcing. Capture carton contents once, at pack time, and let that dataset generate the labels, the packing list, and the ASN. Three artifacts from one source cannot contradict each other; three artifacts from three processes eventually will, and the audit will find it.

Watch the acknowledgments both ways

With no reorder to absorb a failed transmission, delivery of the documents themselves deserves monitoring. Every 850 Burlington sends should be receipted with a 997 from your side within minutes, and every ASN you transmit should produce one from theirs. Silence in either direction is actionable intelligence: an unacknowledged ASN retransmitted the same afternoon is a non-event, while the same document discovered missing after the freight arrives is a chargeback plus a receiving delay. For an episodic vendor this matters double — you may not have another Burlington document flowing for weeks, so nothing else will surface the problem for you.

A setup path with no drama

Burlington readiness follows the familiar shape, compressed: vendor onboarding on Burlington's side; connection to whatever runs your inventory — Sage Intacct, NetSuite, or another of 30+ supported systems; item and assortment cross-reference load; then sandbox replay of order-to-ASN scenarios until the flow passes end to end. EDISQ's certified Burlington maps carry the vendor-guide validation, and the EDI portion typically wraps in 2–3 days.

The ongoing cost fits the episodic rhythm of off-price selling. EDISQ meters documents and nothing else: each month's first 25 are free, further documents start at $0.50 and descend to $0.10 through the volume tiers, and billing is marginal per tier. Quiet months cost no more than the $100 Production minimum — applied in full to usage — and big buys cost a few dollars of EDI against a shipment worth thousands. No mapping or setup invoices, connectivity included — the arithmetic is on the pricing page.

FAQ