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 · Communications

EDI 886 Customer Call Reporting

The X12 document a broker or manufacturer uses to report store-level findings from retail visits, such as shelf conditions and displays.

Sent by
Broker or manufacturer's field team
Received by
Manufacturer or broker
Standard
ANSI ASC X12

What is an EDI 886?

The EDI 886 Customer Call Reporting is the ANSI X12 transaction set a broker or manufacturer uses to communicate retail store level information gathered on store visits. That includes the condition of products, shelf space allocation, store conditions, marketing programs in effect, competitor products, selective pricing and display information.

The 886 turns field observations into structured data. Manufacturers use it to check that programs they paid for are in place, to spot out-of-stocks and to compare their shelf presence with competitors across many stores.

How the EDI 886 worksDiagram of the EDI 886 Customer Call Reporting. Broker or manufacturer's field team sends it to manufacturer or broker. 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: N1 (Party Identification) and detail: the required 0100 loop with ENT (Entity). 1 optional loops are listed by their first segment.How the EDI 886 worksCustomer Call Reporting: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 886SENDERBroker ormanufacturer's fieldteamRECEIVERManufacturer or broker997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code UBGS … GETransaction set 886ST … SEHEADINGN1Party IdentificationDETAILRequired loop 0100 · repeats up to 5,000ENTEntity+ 1 optional loop, starting with:N1Blue 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 886. Your trading partner's implementation guide adds its own requirements.
How the EDI 886 worksDiagram of the EDI 886 Customer Call Reporting. Broker or manufacturer's field team sends it to manufacturer or broker. 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: N1 (Party Identification) and detail: the required 0100 loop with ENT (Entity). 1 optional loops are listed by their first segment.How the EDI 886 worksCustomer Call Reporting: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 886SENDERBroker ormanufacturer'sfield teamRECEIVERManufacturer orbroker997 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 UB (GS … GE)Transaction set 886 (ST … SE)HEADINGN1Party IdentificationDETAILRequired loop 0100 · repeats upto 5,000ENTEntity+ 1 optional loop, starting with:N1Blue 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 886. Your trading partner'simplementation guide adds its own requirements.

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

  • Reporting the results of store visits
  • Confirming that displays and promotions are in place
  • Reporting shelf space, pricing and competitor activity

Where it fits in the document flow

This document 886 Customer Call Reporting
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 886 (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
  • ENT
  • G28
  • SE

Practical example

The 886 in practice

A food broker's representatives visit 300 supermarkets during a promotion. After each visit the broker's system sends the manufacturer an 886 recording whether the promotional display was up, the shelf facings counted, the shelf price, any out-of-stocks and competitor promotions seen. The manufacturer's sales team follows up with the chains where displays were missing.

Implementation

Implementation considerations for the 886

  • Agree on the observations to report and their codes so data can be compared across stores.
  • Use store identifiers that match the retailer's account data (885).
  • Report promptly, since store conditions are only actionable while a promotion runs.
  • Combine call reports with sales data to measure program compliance.

How ECOM helps

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

Supply Chain Visibility

Track orders, shipments and invoices across partners and catch exceptions early.

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

Related transactions

Related communications documents

All 16 communications documents

Need help with the EDI 886?

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

Request a Demo Contact us