X12 transaction code
EDI 888 Item Maintenance (X12 888)
EDI 888 is the X12 Item Maintenance transaction set, used when product attributes are added or maintained. A manufacturer, supplier, or broker sends the 888 to retailers or distributors, which acknowledge receipt with a 997 Functional Acknowledgment.
- Standard
- X12
- Code
- 888
- Partner references
- 1
At a glance
EDI 888 at a glance
What the 888 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 888 Item Maintenance |
|---|---|
| Business record | Item master record |
| Who sends it to whom | A manufacturer, supplier, or broker sends the 888 to retailers or distributors, which acknowledge receipt with a 997 Functional Acknowledgment. |
| When it is sent | 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. |
| Match on | Item identifier, supplier and change effective date |
| Partner references | 1 trading partner in this directory |
| Related documents | X12 879 Price Information, X12 889 Promotion Announcement |
Key segments in an EDI 888
The business segments in the one partner document reference listed below. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BGN | Beginning Segment | To indicate the beginning of a transaction set. | 1 of 1 |
| N1 | Party Identification | To identify a party by type of organization, name, and code. | 1 of 1 |
| G62 | Date/Time | To specify pertinent dates and times. | 1 of 1 |
| G53 | Maintenance Type | To identify the specific type of item maintenance. | 1 of 1 |
| LX | Transaction Set Line Number | To reference a line number in a transaction set. | 1 of 1 |
| G39 | Item Characteristics - Vendor's Selling Unit | To identify a vendor's selling unit or to provide physical characteristics relative to a vendor's selling unit. | 1 of 1 |
| G69 | Line Item Detail - Description | To describe an item in free-form format. | 1 of 1 |
| N9 | Extended Reference Information | To transmit identifying information as specified by the Reference Identification Qualifier. | 1 of 1 |
| UIT | Unit Detail | To specify item unit data. | 1 of 1 |
| PAL | Pallet Type and Load Characteristics | To identify the type and physical attributes of the pallet, and, gross weight, gross volume, and height of the load and the pallet. | 1 of 1 |
Stacksync connects EDI documents such as the X12 888 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 888 mapping and validation
X12 888 Item Maintenance is used when product attributes are added or maintained. Preserve item identifier, supplier and change effective date so the item master record in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | item master record item identifier, supplier and change effective date |
|
| Update the receiving system | Processing the item master record ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the item master record Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 879 Price Information
price information: grocery or product pricing is distributed.
- X12 889 Promotion Announcement
promotion record: a promotion is announced or revised.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when product attributes are added or maintained. Name the operational owner of the item master record and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map item identifier, supplier and change effective date. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic item master record data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful item master record processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 888 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic item master record data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out item master record without processing it twice.
Document structure
X12 888 Item Maintenance at the element level
The X12 888 reference contains 26 segment entries and 82 data elements; 43 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Find your trading partner for X12 888
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 888 Item Maintenance appears in this catalog
The largest groups of classified 888 catalog entries are in grocery & food.
By industry
- grocery & food 1 channel
FAQ
EDI 888 questions
What is an EDI 888?
EDI 888 is the X12 Item Maintenance transaction set. Trading partners use it when product attributes are added or maintained. It carries the data for the item master record, and your system matches it on item identifier, supplier and change effective date.
Who sends an EDI 888 and who receives it?
A manufacturer, supplier, or broker sends the 888 to retailers or distributors, which acknowledge receipt with a 997 Functional Acknowledgment. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 888 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 888?
The one partner document reference listed here includes BGN (Beginning Segment), N1 (Party Identification), G62 (Date/Time), G53 (Maintenance Type), LX (Transaction Set Line Number), G39 (Item Characteristics - Vendor's Selling Unit). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 888 and EDI 879?
The 888 carries the item master record and is used when product attributes are added or maintained. The 879 carries the price information and is used when grocery or product pricing is distributed.
What should I map for X12 888?
Start with item identifier, supplier and change effective date and the target item master record. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 888 error handling?
Change a package attribute without assigning a new identity to an unrelated item. Validate an item discontinuation against outstanding orders and inventory. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 888?
The directory on this page links 1 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
