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 893 Item Information Request

The X12 document distributors and brokers use to request complete item information from manufacturers, suppliers or agents.

Sent by
Distributor or broker
Received by
Manufacturer, supplier, broker or agent
Standard
ANSI ASC X12

What is an EDI 893?

The EDI 893 Item Information Request is the ANSI X12 transaction set distributors and brokers use to request complete item information from manufacturers, suppliers, brokers or agents. The item information is returned using the Item Maintenance transaction set (888).

Distributors need full item data, such as identifiers, descriptions, pack sizes, dimensions and pricing references, before they can stock a product. Requesting it electronically, item by item or for a group of items, saves chasing data by email. Requests can cover one item or many.

How the EDI 893 worksDiagram of the EDI 893 Item Information Request. Distributor or broker sends it to manufacturer, supplier, broker or agent. It usually starts the exchange. It is usually followed by 888 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B2A (Set Purpose) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with G39 (Item Characteristics - Vendor's Selling Unit). 0 optional loops are listed by their first segment.How the EDI 893 worksItem Information Request: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 893SENDERDistributor or brokerRECEIVERManufacturer,supplier, broker oragent997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY888Item Maintenance997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code AMGS … GETransaction set 893ST … SEHEADINGB2ASet PurposeRequired loop 0100 · repeats many timesN1Party IdentificationDETAILRequired loop 0200 · repeats many timesG39Item Characteristics - Vendor's Selling UnitBlue 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 893. Your trading partner's implementation guide adds its own requirements.
How the EDI 893 worksDiagram of the EDI 893 Item Information Request. Distributor or broker sends it to manufacturer, supplier, broker or agent. It usually starts the exchange. It is usually followed by 888 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: B2A (Set Purpose) and the required 0100 loop with N1 (Party Identification) and detail: the required 0200 loop with G39 (Item Characteristics - Vendor's Selling Unit). 0 optional loops are listed by their first segment.How the EDI 893 worksItem Information Request: who sends it, whereit fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 893SENDERDistributor orbrokerRECEIVERManufacturer,supplier, brokeror agent997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY888Item Maintenance997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code AM (GS … GE)Transaction set 893 (ST … SE)HEADINGB2ASet PurposeRequired loop 0100 · repeatsmany timesN1Party IdentificationDETAILRequired loop 0200 · repeatsmany timesG39Item Characteristics -Vendor's Selling UnitBlue 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 893. Your trading partner'simplementation guide adds its own requirements.

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

  • Requesting data for new items
  • Requesting refreshed data for existing items
  • Filling gaps in item master data

Where it fits in the document flow

This document 893 Item Information Request
Usually followed by 888 Item Maintenance997 Functional Acknowledgment

Structure

Mandatory segments in the 893 (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
  • B2A
  • N1
  • G39
  • SE

Practical example

The 893 in practice

A grocery wholesaler adds a manufacturer's new product line. It sends the manufacturer an 893 requesting item information for the line's GTINs. The manufacturer returns the full item data in an 888, and the wholesaler sets up the items for ordering.

Implementation

Implementation considerations for the 893

  • Identify the requested items precisely, for example by GTIN.
  • Track requests until item data is received.
  • Validate returned data before setting up items.
  • Combine requests with regular item maintenance updates.

How ECOM helps

Automate the 893 with ECOM

Industry

Wholesale Distribution

Customer orders, supplier purchasing, catalogs and drop-ship for distributors.

Industry

Food and Beverage

Grocery and foodservice EDI for food and beverage manufacturers, with lot, date and inventory data.

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

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

Request a Demo Contact us