972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Master data

EDI 888 Item Maintenance

The X12 document a manufacturer, supplier, broker or agent uses to give a trading partner detailed product information for finished goods.

Sent by
Manufacturer, supplier, broker or agent
Received by
Retailer, wholesaler or distributor
Standard
ANSI ASC X12

What is an EDI 888?

The EDI 888 Item Maintenance is the ANSI X12 transaction set used to provide detailed finished goods product information to a partner in a consumer goods market. A manufacturer, supplier, broker or agent sends it to add new items or to change and maintain the data held for existing ones.

Item data typically includes identifiers, descriptions, pack configurations, dimensions and weights. Retailers and wholesalers use it to set up items for ordering, warehousing and shelf planning, so errors here flow into every later document.

How the EDI 888 worksDiagram of the EDI 888 Item Maintenance. Manufacturer, supplier, broker or agent sends it to retailer, wholesaler or distributor. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required 0100 loop with N1 (Party Identification) and G62 (Date/Time) and detail: the required 0300 loop with G53 (Maintenance Type) and the required 0310 loop with LX (Transaction Set Line Number). 4 optional loops are listed by their first segment.How the EDI 888 worksItem Maintenance: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 888SENDERManufacturer,supplier, broker oragentRECEIVERRetailer, wholesaler ordistributor997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code QGGS … GETransaction set 888ST … SEHEADINGRequired loop 0100 · repeats many timesN1Party IdentificationG62Date/Time+ 1 optional loop, starting with:LMDETAILRequired loop 0300 · repeats many timesG53Maintenance TypeRequired loop 0310 · repeats many timesLXTransaction Set Line Number+ 3 optional loops, starting with:N1G55LMBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 888. Your trading partner's implementation guide adds its own requirements.
How the EDI 888 worksDiagram of the EDI 888 Item Maintenance. Manufacturer, supplier, broker or agent sends it to retailer, wholesaler or distributor. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: the required 0100 loop with N1 (Party Identification) and G62 (Date/Time) and detail: the required 0300 loop with G53 (Maintenance Type) and the required 0310 loop with LX (Transaction Set Line Number). 4 optional loops are listed by their first segment.How the EDI 888 worksItem Maintenance: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 888SENDERManufacturer,supplier, brokeror agentRECEIVERRetailer,wholesaler ordistributor997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code QG (GS … GE)Transaction set 888 (ST … SE)HEADINGRequired loop 0100 · repeatsmany timesN1Party IdentificationG62Date/Time+ 1 optional loop, starting with:LMDETAILRequired loop 0300 · repeatsmany timesG53Maintenance TypeRequired loop 0310 · repeatsmany timesLXTransaction Set LineNumber+ 3 optional loops, starting with:N1G55LMBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 888. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 888, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 888 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Setting up new consumer goods items with a customer
  • Changing pack, dimension or weight data
  • Maintaining descriptions and identifiers over time

Where it fits in the document flow

This document 888 Item Maintenance
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 888 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • N1
  • G62
  • LM
  • LQ
  • G53
  • LX
  • G55
  • SE

Practical example

The 888 in practice

A household products company changes the case pack of a detergent from six to eight bottles. It sends an 888 with the new pack configuration, case dimensions and weight. The retailer's distribution centers update slotting and pallet plans before the new cases arrive, avoiding receiving errors.

Implementation

Implementation considerations for the 888

  • Keep product data in one master source so the 888, catalogs and ship notices agree.
  • Send changes to physical attributes before the changed product ships.
  • Confirm whether the partner expects full item records or only changed values.

How ECOM helps

Automate the 888 with ECOM

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related master data documents

All 25 master data documents

Need help with the EDI 888?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us