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 896 Product Dimension Maintenance

The X12 document used to provide the physical characteristics of items for use in computerized shelf space management systems.

Sent by
Manufacturer or supplier
Received by
Retailer or category management provider
Standard
ANSI ASC X12

What is an EDI 896?

The EDI 896 Product Dimension Maintenance is the ANSI X12 transaction set used to provide information about the physical characteristics of items for use in computerized shelf space management systems.

Planogram software needs the height, width and depth of each product, and how it can be displayed, to plan shelf layouts. Accurate dimensions from the supplier avoid planograms that do not fit the real shelf, and the need for stores to measure products themselves. Planogram accuracy depends on it. Updates follow packaging changes.

How the EDI 896 worksDiagram of the EDI 896 Product Dimension Maintenance. Manufacturer or supplier sends it to retailer or category management provider. 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 detail: the required 0200 loop with ID1 (Item Detail Dimensions). 0 optional loops are listed by their first segment.How the EDI 896 worksProduct Dimension Maintenance: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 896SENDERManufacturer orsupplierRECEIVERRetailer or categorymanagement provider997 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 896ST … SEHEADINGRequired loop 0100 · repeats up to 10N1Party IdentificationDETAILRequired loop 0200 · repeats up to 999ID1Item Detail DimensionsBlue 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 896. Your trading partner's implementation guide adds its own requirements.
How the EDI 896 worksDiagram of the EDI 896 Product Dimension Maintenance. Manufacturer or supplier sends it to retailer or category management provider. 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 detail: the required 0200 loop with ID1 (Item Detail Dimensions). 0 optional loops are listed by their first segment.How the EDI 896 worksProduct Dimension Maintenance: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 896SENDERManufacturer orsupplierRECEIVERRetailer orcategorymanagementprovider997 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 896 (ST … SE)HEADINGRequired loop 0100 · repeats upto 10N1Party IdentificationDETAILRequired loop 0200 · repeats upto 999ID1Item Detail DimensionsBlue 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 896. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 896, 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 896 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

  • Sending dimensions for new products
  • Updating dimensions after packaging changes
  • Supporting planogram and space planning

Where it fits in the document flow

This document 896 Product Dimension Maintenance
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 896 (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
  • ID1
  • SE

Practical example

The 896 in practice

A cereal maker redesigns a box, making it slightly taller. It sends retailers an 896 with the new height, width, depth and display characteristics, effective from the first production date. The retailers' space planners update planograms before the new boxes reach stores.

Implementation

Implementation considerations for the 896

  • Measure products using consistent methods.
  • Send dimension changes before new packaging ships.
  • Keep dimensions consistent with item data in the 888.
  • Include display orientation details where relevant.

How ECOM helps

Automate the 896 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

B2B Integration

Connect every customer, supplier, carrier and bank across EDI, API, file and portal channels.

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 896?

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

Request a Demo Contact us