Macy’s EDI Requirements
Macy’s, Inc. runs Macy’s and Bloomingdale’s under shared Vendor Standards, governed through the MacysNet portal on VICS / X12 v5010. There are three channels — traditional wholesale/warehouse, Vendor Direct to Consumer (V2C) drop-ship, and the Macy’s Merchandising Group (private brand) — and a distinctive item-level RFID mandate layered on top of standard GS1-128 labeling.
Required EDI documents
| Document | Name | Notes |
|---|---|---|
| EDI 850 | Purchase Order | select/applicable vendors |
| EDI 855 | PO Acknowledgment | select/applicable vendors |
| EDI 856 | Advance Ship Notice (ASN) | required of all vendors |
| EDI 810 | Invoice | required of all vendors |
| EDI 860 | PO Change | optional |
| EDI 820 | Remittance | supported |
| EDI 997 | Functional Acknowledgment | required of all vendors |
Labeling & packaging
- GS1-128 (UCC-128) carton label with SSCC-18 on every carton; label data must reconcile to the 856 at the UPC/GTIN and location level.
- Reported label spec: 4“x6” or 3“x8”, GS1-128 subset C, ~20 mil X-dimension, on the longest (conveyable) side; goods must arrive floor-ready (fold vs. hang per buyer; garment-on-hanger rules apply).
- Item-level RFID: Macy’s mandates passive UHF EPC Gen 2 tags from a pre-approved list on covered replenishment categories (intimates, men’s bottoms/denim/dress, etc.) — confirm current category scope on MacysNet.
Connection & portal
- MacysNet (macysnet.com) is the vendor portal hosting Vendor Standards and EDI Mapping Guides (5010, plus legacy 4010/4030/4050). VAN, AS2, and FTP/SFTP are supported; the 856 must carry the carrier’s 4-character SCAC.
- GXS (OpenText) is reported as Macy’s preferred VAN. Drop-ship (V2C/VDF) onboards via SPS Commerce, and non-EDI vendors can use browser-based Rithum/CommerceHub.
Onboarding & testing
Onboarding and EDI certification run through MacysNet (New Vendor Onboarding Instructions); data must be tested against Macy’s Mapping Guides before going live. V2C drop-ship ships to the consumer within 2 business days and returns the 856 same day. Specific calendar timelines are gated behind MacysNet login.
Compliance & chargebacks
- • Macy’s uses “expense offsets” — deductions for deviations from Vendor Standards (late/missing 856, invalid EDI data, UPCs rejected at POS, GS1-128/floor-ready violations).
- • ASN timing: allow ~3 hours processing; transmit the 856 immediately after the trailer door closes, and it must be in Macy’s system before the shipment arrives at the DC.
- • No public per-violation expense-offset schedule — the fee schedule lives in the gated MacysNet Vendor Standards (treat any dollar figures as third-party estimates).
Worth knowing
- • Item-level UHF RFID (EPC Gen 2) mandate is Macy’s most distinctive requirement, on top of GS1-128/UPC ticketing.
- • Three channels with different standards docs (wholesale, V2C/VDF drop-ship, Macy’s Merchandising Group); Macy’s and Bloomingdale’s share one program.
How EndlessEDI helps with Macy’s
EndlessEDI builds SSCC-matched 856s timed to Macy’s DC-arrival rules, supports VICS 5010, and keeps UPC and invoice data accurate to avoid expense offsets — across wholesale and V2C drop-ship.
Explore EndlessEDIMacy’s EDI FAQ
What EDI documents does Macy’s require?
The 856 (ASN), 810 (invoice), and 997 are required of all vendors, with the 850 and 855 for applicable vendors and the 860/820 supported. Macy’s uses VICS / X12 v5010 (with legacy 4010/4030/4050 maps still published).
Does Macy’s require RFID?
Yes, for covered categories. Macy’s mandates passive UHF EPC Gen 2 RFID tags from a pre-approved list on certain replenishment categories (e.g., intimates, men’s bottoms/denim/dress). Confirm the current category scope on MacysNet.
What is a Macy’s expense offset?
An expense offset is Macy’s term for a chargeback — a deduction for deviating from Vendor Standards, such as a late or missing ASN, invalid EDI data, or GS1-128/floor-ready violations. The exact fee schedule is in the gated MacysNet Vendor Standards.
EDI requirements and penalty schedules change and vary by program. Figures marked “reported” come from third-party sources, not the retailer’s published fee schedule — always confirm against the retailer’s current routing guide and your vendor agreement.
