Retailer requirements · September 2, 2026

Macy's EDI Requirements: How to Become Compliant

Macy's vendor standards and EDI — PO types that drive validation, GS1-128 label matching, scan-based receiving, and weekly 852 sales data.

Macy's writes its expectations down. The vendor standards — routing, ticketing, EDI — are published, versioned, and enforced with chargebacks, which makes Macy's one of the most learnable programs in department-store retail: the test comes with a study guide. The work is building a document flow that passes the standards automatically, because manual compliance at Macy's volume does not survive contact with a busy season.

PO type decides the rules

The first field to read on a Macy's 850 is the order type. Basic, fashion, and dropship orders carry different rules, and the type drives what downstream validation expects — a dropship order needs customer-facing handling that a basic replenishment order never sees, while fashion orders bring their own cadence. Item identification is UPC-led, with style, color, and size expanding per line in the usual apparel matrix.

A map that branches on PO type, applying each program's rules automatically, converts the vendor standards from reading assignment into configuration.

Scan-based receiving and the 856

Macy's receiving scans freight against the ship notice, which elevates three requirements from Macy's 856 spec:

  • GS1-128 labels matching MAN serials — the most-cited chargeback in the department-store channel. The label on the carton and the serial in the document must be the same fact, which happens naturally when both are generated from one carton record and never happens reliably otherwise.
  • Full pick-and-pack hierarchy describing cartons as physically packed.
  • ASN before the freight reaches the DC, so the dock plans from your data.

Ticketing and packing round out the chargeback surface; like the ASN rules, they are deterministic once the upstream data is right.

The weekly 852 earns its keep

Replenishment vendors receive 852 product activity files weekly — sales and stock positions by location. Macy's expects vendors to plan against this data, and it is genuinely useful: location-level sell-through shows you which doors are moving product before the reorder does. Feed it into forecasting rather than archiving it; the vendors with the healthiest fill rates at Macy's are the ones treating the 852 as an input, not a report.

Dropship raises the tempo

If your Macy's program includes dropship, expect the operating rhythm to change more than the documents do. Each order is a single consumer shipment: the ship-to comes off the 850 rather than a DC table, the ASN carries the data that becomes the customer's tracking experience, and the invoice follows per order instead of per truckload. Volume arrives as a stream of small documents rather than a few large ones — which is exactly the shape manual processing handles worst and automation handles best. Wire the dropship branch of the map to run untouched end to end, and reserve human attention for the exceptions queue.

The recurring mistakes

Three errors account for most early chargebacks at Macy's: labels and ASNs generated by separate processes that eventually drift apart, PO-type rules applied uniformly when the programs differ, and 852 data left unread while fill rate slides. All three are process-design decisions rather than execution failures — which is good news, because they get fixed once in the integration instead of policed forever on the floor.

Building the connection

The setup path holds no surprises: Macy's vendor onboarding, system connection (Blue Yonder for supply-chain-driven vendors, NetSuite, or 30+ other systems), UPC cross-reference load, then sandbox certification per document type. EDISQ ships certified Macy's maps with the vendor-standards validation baked in, so documents get checked before Macy's ever sees them; the EDI portion typically completes in 2–3 days.

After go-live the costs track shipping activity and nothing else. Twenty-five documents ride free every month; from there, per-document pricing starts at $0.50 and eases to $0.10 across ascending volume tiers, applied marginally, with a $100/month Production minimum that counts entirely toward usage. EDISQ charges nothing for the connection itself and nothing for maps or setup — terms in full on the pricing page.

FAQ

What are Macy's vendor standards?

Macy's published routing, ticketing, and EDI requirements for all vendors, enforced with chargebacks. EDISQ validates documents against the standards before they transmit.

Do different Macy's PO types have different rules?

Yes — basic, fashion, and dropship orders each carry their own validation. The PO type on the 850 determines what downstream documents must contain.

What is the most common department-store chargeback?

GS1-128 carton labels that fail to match the ASN's MAN serials. Generating labels and the 856 from the same carton data prevents the mismatch.

How much is Macy's EDI with EDISQ?

First 25 documents free each month, then from $0.50 per document trending down with volume. No monthly platform, partner, or mapping fees.