Macy's EDI 855 PO Acknowledgment

Schema Reference

11 segments · X12 855 Purchase Order Acknowledgment

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Repetition Separator M MIN 1 MAX 1 ID: I65 Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Interchange Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

BAK01 Transaction Set Purpose Code

M ID 2-2

BAK02 Acknowledgment Type

M ID 2-2

BAK03 Purchase Order Number

M AN 1-22

BAK04 Date

M DT 8-8

DTM01 Date/Time Qualifier

M ID 3-3

DTM02 Date

C DT 8-8

PO1 Loop Repeat: 100,000

PO102 Quantity

C R 1-15

PO103 Unit or Basis for Measurement Code

O ID 2-2

PO104 Unit Price

C R 1-17

PO105 Basis of Unit Price Code

O ID 2-2

PO106 Product/Service ID Qualifier

C ID 2-2

PO107 Product/Service ID

C AN 1-48

PO108 Product/Service ID Qualifier

C ID 2-2

PO109 Product/Service ID

C AN 1-48

PO110 Product/Service ID Qualifier

C ID 2-2

PO111 Product/Service ID

C AN 1-48

PO112 Product/Service ID Qualifier

C ID 2-2

PO113 Product/Service ID

C AN 1-48

PO114 Product/Service ID Qualifier

C ID 2-2

PO115 Product/Service ID

C AN 1-48

CTP02 Price Identifier Code

C ID 3-3

CTP03 Unit Price

C R 1-17

SDQ01 Unit or Basis for Measurement Code

M ID 2-2

SDQ02 Identification Code Qualifier

O ID 1-2

SDQ03 Identification Code

M AN 2-80

SDQ04 Quantity

M R 1-15

SDQ05 Identification Code

C AN 2-80

SDQ06 Quantity

C R 1-15

SDQ07 Identification Code

C AN 2-80

SDQ08 Quantity

C R 1-15

SDQ09 Identification Code

C AN 2-80

SDQ10 Quantity

C R 1-15

SDQ11 Identification Code

C AN 2-80

SDQ12 Quantity

C R 1-15

SDQ13 Identification Code

C AN 2-80

SDQ14 Quantity

C R 1-15

SDQ15 Identification Code

C AN 2-80

SDQ16 Quantity

C R 1-15

SDQ17 Identification Code

C AN 2-80

SDQ18 Quantity

C R 1-15

SDQ19 Identification Code

C AN 2-80

SDQ20 Quantity

C R 1-15

SDQ21 Identification Code

C AN 2-80

SDQ22 Quantity

C R 1-15

SLN Loop Repeat: 1,000

SLN01 Assigned Identification

M AN 1-20

SLN03 Relationship Code

M ID 1-1

SLN04 Quantity

C R 1-15

SLN06 Unit Price

C R 1-17

SLN07 Basis of Unit Price Code

O ID 2-2

SLN09 Product/Service ID Qualifier

C ID 2-2

SLN10 Product/Service ID

C AN 1-48

SLN11 Product/Service ID Qualifier

C ID 2-2

SLN12 Product/Service ID

C AN 1-48

SLN13 Product/Service ID Qualifier

C ID 2-2

SLN14 Product/Service ID

C AN 1-48

SLN15 Product/Service ID Qualifier

C ID 2-2

SLN16 Product/Service ID

C AN 1-48

SLN17 Product/Service ID Qualifier

C ID 2-2

SLN18 Product/Service ID

C AN 1-48

CTT Loop Repeat: 1

CTT01 Number of Line Items

M N0 1-6

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Macy's EDI 855

Stacksync validates, transforms, and delivers your 855 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync generates and sends 855 Purchase Order Acknowledgments automatically when your system confirms an order. Accept, reject, or modify line items through your ERP — Stacksync handles the EDI formatting and transmission.

Business unit variations

Macy's CHub DS 5135797000CH

Macy's EDI 855 FAQ

Common questions about 855 Purchase Order Acknowledgment transactions with Macy's.

How long does it take to set up Macy's EDI with Stacksync?

Most suppliers are fully connected and processing live Macy's EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Macy's?

No. Stacksync handles the entire EDI transport layer. We connect directly to Macy's's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Macy's compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Macy's?

Stacksync supports all EDI document types required by Macy's — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Macy's EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Macy's's EDI network and your system in real time.

What happens when Macy's updates their EDI specifications?

Stacksync monitors Macy's's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.