X12
Outbound

Ulta Beauty X12 855 Purchase Order Acknowledgment

Ulta Beauty (Legacy ISA ID: 608168597)
The EDI 855 confirms receipt and acceptance of a Ulta Beauty Purchase Order. Suppliers must respond promptly indicating whether the order is accepted, rejected, or accepted with changes to maintain compliance standing.
14segments
4loops
5mandatory

Schema Reference

14 segments · X12 855 Purchase Order Acknowledgment

ISA ISA Interchange Control Header
Mandatory Max: 1
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 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 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
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
BAK Beginning Segment for Purchase Order Acknowledgment
Mandatory Max: 1
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
BAK06 Request Reference Number
O AN 1-45
CUR Currency
Optional Max: 1
CUR01 Entity Identifier Code
M ID 2-3
CUR02 Currency Code
M ID 3-3
REF Reference Identification
REF01 Reference Identification Qualifier
M ID 2-3
REF02 Reference Identification
C AN 1-50
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
PO1 Loop Repeat: 100,000
PO1 Baseline Item Data
Optional Max: 1
PO101 Assigned Identification
O AN 1-20
PO102 Quantity Ordered
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
PID Loop Repeat: 1,000
PID Product/Item Description
Optional Max: 1
PID01 Item Description Type
M ID 1-1
PID02 Product/Process Characteristic Code
O ID 2-3
PID05 Description
C AN 1-80
PO4 Item Physical Details
PO401 Pack
O N0 1-6
ACK Loop Repeat: 104
ACK Line Item Acknowledgment
Optional Max: 1
ACK01 Line Item Status Code
M ID 2-2
ACK02 Quantity
C R 1-15
ACK03 Unit or Basis for Measurement Code
C ID 2-2
ACK04 Date/Time Qualifier
O ID 3-3
ACK05 Date
C DT 8-8
DTM Date/Time Reference
Optional Max: 10
DTM01 Date/Time Qualifier
M ID 3-3
DTM02 Date
C DT 8-8
CTT Loop Repeat: 1
CTT Transaction Totals
Optional Max: 1
CTT01 Number of Line Items
M N0 1-6
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Ulta Beauty 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

Ulta Beauty via OpenText
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.
Ulta Beauty (Legacy ISA ID: 3103438052)
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.

Ulta Beauty EDI 855 FAQ

Common questions about 855 Purchase Order Acknowledgment transactions with Ulta Beauty.

How quickly must I respond to a Ulta Beauty 850 with an EDI 855?

Ulta Beauty compliance programs generally require an EDI 855 Purchase Order Acknowledgment within 24 to 48 hours of receiving the 850. Some Ulta Beauty business units or time-sensitive product categories may have tighter windows. Failing to acknowledge within the deadline can result in compliance penalties, reduced scorecard ratings, and in some cases automatic PO cancellation. Stacksync can send 855 acknowledgments automatically the moment your system processes the incoming PO, well within Ulta Beauty's required timeframe. The platform logs every acknowledgment with timestamps for compliance auditing.

What status codes can be sent in a Ulta Beauty EDI 855?

The Ulta Beauty EDI 855 supports several acknowledgment status codes in the BAK and ACK segments: accepted as ordered (AC), accepted with changes (AD), backorder (BO), rejected (RJ), and item not found (IF). You can acknowledge the entire PO at the header level or respond line by line with different statuses — for example, accepting most items while backordering one and rejecting another. Stacksync lets you define business rules that automatically assign these status codes based on your inventory availability, pricing validation, and fulfillment capacity, removing the need for manual line-by-line review.

Is an EDI 855 required for every Ulta Beauty Purchase Order?

Most Ulta Beauty compliance programs require an 855 for every 850 PO received. However, some Ulta Beauty divisions or product categories may not enforce the requirement, especially for smaller suppliers or specific fulfillment models. Even when not strictly mandatory, sending an 855 is best practice — it confirms receipt, prevents duplicate PO transmissions, and establishes a clear audit trail. Stacksync configures 855 responses per Ulta Beauty business unit, so you can automate acknowledgments where required while handling exceptions for divisions with different compliance expectations.

What happens if I reject a line item in a Ulta Beauty EDI 855?

When you reject a line item in the Ulta Beauty 855 using the RJ status code, Ulta Beauty's ordering system is notified that you cannot fulfill that specific item. Depending on Ulta Beauty's policies, they may issue a revised 850 with alternative items, cancel the line, or source the product from another supplier. Partial rejections — where you accept some lines and reject others — are common and supported through line-level ACK segments. Stacksync tracks rejected lines and can trigger alerts so your sales or fulfillment team can follow up with Ulta Beauty proactively.

Can Stacksync automate Ulta Beauty EDI 855 responses?

Yes. Stacksync automates Ulta Beauty 855 responses by connecting to your inventory and order management systems. When a Ulta Beauty 850 arrives, Stacksync checks stock levels, validates pricing against your catalog, and confirms fulfillment capacity. Based on configurable business rules, it generates the appropriate 855 with acceptance, modification, or backorder status codes — all without manual intervention. You can set thresholds for automatic acceptance (e.g., accept if all items are in stock) and escalate edge cases to your team for review. The entire response cycle typically completes in under a minute.

Ready to automate Ulta Beauty EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding