X12 transaction code
X12 888 Item Maintenance
Stop Mapping. Start Trading.
- Standard
- X12
- Code
- 888
- Trading partners
- 1
Specification summary
X12 888 Item Maintenance at the element level
The X12 888 specification defines 26 segments carrying 82 data elements, 43 of which are mandatory.
- Segments
- 26
- Data elements
- 82
- Mandatory elements
- 43
| Segment | Elements | Mandatory |
|---|---|---|
| BGN | 3 | 3 |
| N1 | 4 | 1 |
| G53 | 1 | 1 |
| LX | 1 | 1 |
| G69 | 1 | 1 |
| N9 | 2 | 1 |
| G55 | 14 | 2 |
| QTY | 2 | 1 |
| PID | 3 | 1 |
| REF | 2 | 1 |
| LDT | 3 | 3 |
- Transaction Set Purpose Code
- Reference Identification
- Date
- Entity Identifier Code
- Maintenance Type Code
- Assigned Number
- Free-form Description
- Reference Identification Qualifier
Trading partners that support X12 888
1 partner, 1 channel. Click a channel for the full segment guideline.
Usage breakdown
Who trades X12 888 Item Maintenance
888 is used most heavily in grocery & food.
The 888 distributes product master data in consumer goods markets: new item introductions and changes to descriptions, measurements, pack and pallet configurations, and other specifications. Trading partners require it so their item files stay synchronized with the supplier's catalog before orders and invoices reference the new data. Price changes are explicitly out of scope and travel on the 879 instead. A manufacturer, supplier, or broker sends the 888 to retailers or distributors, which acknowledge receipt with a 997 Functional Acknowledgment. A supplier introduces a new product or changes an existing item's specification, such as pack size, packaging, or description, and must notify buyers before the change reaches orders and shipments.
By industry
- grocery & food 1 channel
FAQ
X12 888 questions
What is X12 888 Item Maintenance?
X12 888 (Item Maintenance) is an EDI transaction set defined by ANSI ASC X12 for exchanging item maintenance between trading partners. It is one of over 300 X12 transaction sets used across retail, healthcare, manufacturing, and logistics. 1 Stacksync trading partner supports this code across 1 channel.
Which trading partners use X12 888?
1 Stacksync partner accepts X12 888: Thrive Market. Each partner has its own implementation guideline that Stacksync pre-validates before sending. Browse the full directory above.
How do I integrate X12 888 with my ERP?
Stacksync handles the full X12 888 integration: partner channel certification (AS2, VAN, FTP), transaction-set mapping per the trading partner's implementation guide, translation to your ERP's native data model, and real-time delivery. Typical time from kickoff to production is 3 to 10 business days for a single partner connection.
Ready to automate your EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
