Does Target Require an EDI 856 for Every Shipment?

Yes. Under Target's Perfect Order Program, an EDI 856 ASN is required for 100% of purchase orders, and it must be transmitted before the shipment's in-yard date and time. Sending an ASN after the shipment arrives at the DC is a compliance defect even if all other data is accurate. Timing and accuracy are scored separately, and both carry real money on the line.

What exactly is Target's Perfect Order Program?

It's Target's ASN-focused compliance framework, launched on May 4, 2025 for domestic suppliers, setting compliance standards for ASN availability, ASN accuracy, and physical barcode quality. The program is modeled on Walmart's Supplier Quality Excellence Program and represents Target's most structured supplier compliance framework to date.

It sits alongside, not instead of, Target's older On-Time Fill Rate program. Target revised its OTFR policy on August 4, 2024, and suppliers may see legacy fines at 5% of COGS for violations before that date, while the current policy applies uniformly at 5% COGS per non-compliant violation. If your VRS or EDI trading partner config still reflects pre-2024 fine logic, that's worth a look before your next audit.

What counts as an ASN accuracy defect?

A defect is any mismatch between the 856 and the physical shipment at item, quantity, or carton level, not just a missing document. The ASN must match the physical shipment at ASIN, quantity, and carton level exactly. Specifically, ASN Accuracy measures both item-level attributes (vendor case pack information) and shipment-level data (store ship information).

• Carton labels need SSCC-18 identification matching the ASN, and a mismatch triggers a chargeback and pushes the carton to a manual receive path, breaking Target's automated DC receiving process.
• ASN failures at Target typically stem from quantity mismatches between the EDI 856 and the physical shipment, incorrect PO or item references, timing errors, and formatting errors specific to Target's EDI specifications.
• The most insidious ASN failures are configuration-related — they occur consistently on every shipment until the root cause is identified and fixed, generating chargebacks with each occurrence.

That last point is the one most EDI teams miss. A one-off keying error costs you once. A bad mapping template costs you on every single ASN until someone catches it in the scorecard.

How much does a barcode or ASN defect actually cost?

Straightforward: non-compliant cartons are charged at $0.75 per defective unit for barcode issues, with the same rate applying to ASN accuracy defects. Each carries a fine of $0.75 per non-compliant carton with a $100 minimum.

ASN Availability (a missing or late 856) is treated differently. The minimum fine for EDI 856 availability is $100, unless Target rejects or can't acknowledge the 856 ("Not in 'A' status"), in which case there is no minimum, meaning even a single-carton shipment without an acknowledged ASN generates a charge. Repeated or severe failures escalate further: Strike Violations result in immediate non-compliance, a minimum $25,000 fine, and at least a 1-year suspension.

Do the math on volume. A supplier shipping 1,000 cartons per PO with a missing ASN now faces a $750 fine on that single shipment alone. Multiply that across a week of RDC shipments and a mapping bug becomes a five-figure problem fast.

Can you dispute a Perfect Order Program chargeback?

Yes. Synergy is the dispute portal for OTFR chargebacks and Vendor Compliance Policy violations, accessed through Partners Online, and disputes require solid documentation and must be submitted within Target's dispute window.

What to keep on file: VRS entry confirmations, carrier pickup receipts, POD, BOL, and EDI transmissions, archived for 12+ months. From an EDI ops standpoint, that means your 997/999 functional acknowledgment logs and 856 transmission timestamps need to be queryable, not buried in a VAN's rolling 90-day retention window. If your provider purges transmission logs after 60 or 90 days, you'll lose your evidence before the dispute window even opens on a slow-moving chargeback.

How does this compare to Walmart's OTIF/SQEP model?

Philosophically identical, structurally narrower. Walmart's version, the Supplier Quality Excellence Program, rolled out on February 1, 2021 to ensure a "defect-free" supply chain, and Walmart pairs it with OTIF, where Walmart expects approximately 98% OTIF compliance, with failures triggering chargebacks of 3% of the affected order value, measured monthly.

Target's Perfect Order Program covers less ground than SQEP, focusing squarely on the ASN and barcode layer rather than broader packaging and documentation audits, but the two share the same underlying logic. As one 2026 compliance overview puts it, retailer EDI compliance is the set of enforceable rules Walmart, Amazon and Target apply on top of basic EDI capability: a required communication protocol (AS2), mandatory certification testing before go-live, ASN and acknowledgment timing windows, and automated chargeback systems that penalize violations without manual review.

What's the minimum EDI transaction stack Target requires?

You need five transaction sets running cleanly: EDI 850 (Purchase Order), EDI 856 (Advance Ship Notice), EDI 810 (Invoice), and EDI 997 (Functional Acknowledgment), plus the 855 PO acknowledgment. Vendors must connect via AS2 protocol or through an approved VAN, with providers like SPS Commerce, TrueCommerce, and DiCentral commonly handling that layer for mid-market suppliers.

What often gets missed is where the routing and carrier-scan data that feeds the 856 actually originates. Freight execution platforms like MercuryGate, Descartes, Blue Yonder, and Manhattan Active handle the heavy TMS lifting, and multi-carrier connectivity tools such as Cargoson increasingly sit alongside them as the layer that captures the actual carrier pickup event, which is what determines whether your 856 posts before or after the in-yard cutoff.

How can transportation systems help hit the in-yard ASN deadline?

By making sure the carrier's actual departure or pickup scan reaches your EDI generation process in near real time, not by fixing your mapping. Submit your EDI 856 before the carrier departs your facility, not when it arrives at the Target DC — the in-yard time is the cutoff, and there is no way to submit retroactively once the truck has arrived.

That's a transportation-execution problem more often than a data-mapping one. If your ASN trigger depends on a warehouse clerk manually confirming trailer close-out, you're adding a lag that a busy dock will eventually blow past. Hybrid architectures that push carrier milestone events (pickup confirmed, trailer sealed, in-transit) directly into your EDI generation step close that gap. Platforms in this space, from Uber Freight and FreightPOP to Alpega and Cargoson, exist specifically to get that milestone data moving before someone has to remember to send it.

Next step if you ship to Target: pull your Supplier Performance Management Dashboard in Partners Online this week, not at month-end, and check whether your ASN defects cluster around timing or accuracy. That split tells you whether the fix is in your EDI mapping or your dock's carrier hand-off process, and those are two very different projects.