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 · Catalogs and pricing

EDI 887 Coupon Notification

The X12 document a manufacturer uses to announce the issue of coupons and give distributors and clearinghouses what they need to process them.

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

What is an EDI 887?

The EDI 887 Coupon Notification is the ANSI X12 transaction set a manufacturer uses to notify a distributor, retail clearinghouse, manufacturer's agent or broker of the issue of coupons and to provide the information needed to process them. It describes each coupon, its value, its validity dates, the products it applies to and how it is distributed.

With the 887, clearinghouses and retailers know about a coupon before consumers present it, so redemptions can be validated. Redemption detail then flows back to the manufacturer and is reconciled with the 881.

How the EDI 887 worksDiagram of the EDI 887 Coupon Notification. Manufacturer sends it to distributor, retail clearinghouse, agent or broker. It usually starts the exchange. It is usually followed by 881 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and N1 (Party Identification). 3 optional loops are listed by their first segment.How the EDI 887 worksCoupon Notification: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 887SENDERManufacturerRECEIVERDistributor, retailclearinghouse, agentor broker997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY881Manufacturer CouponRedemption Detail997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code CNGS … GETransaction set 887ST … SEHEADINGBGNBeginning SegmentN1Party Identification+ 2 optional loops, starting with:G14G15DETAIL+ 1 optional loop, starting with:LINBlue 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 887. Your trading partner's implementation guide adds its own requirements.
How the EDI 887 worksDiagram of the EDI 887 Coupon Notification. Manufacturer sends it to distributor, retail clearinghouse, agent or broker. It usually starts the exchange. It is usually followed by 881 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and N1 (Party Identification). 3 optional loops are listed by their first segment.How the EDI 887 worksCoupon Notification: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 887SENDERManufacturerRECEIVERDistributor,retailclearinghouse,agent or broker997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY881Manufacturer Coupon Redemption Detail997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code CN (GS … GE)Transaction set 887 (ST … SE)HEADINGBGNBeginning SegmentN1Party Identification+ 2 optional loops, starting with:G14G15DETAIL+ 1 optional loop, starting with:LINBlue 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 887. Your trading partner'simplementation guide adds its own requirements.

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

  • Announcing a new coupon drop
  • Providing coupon values, dates and product coverage
  • Notifying changes or early expiry of a coupon

Where it fits in the document flow

This document 887 Coupon Notification
Usually followed by 881 Manufacturer Coupon Redemption Detail997 Functional Acknowledgment

Structure

Mandatory segments in the 887 (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
  • BGN
  • N1
  • G14
  • G15
  • LIN
  • G28
  • SE

Practical example

The 887 in practice

A personal care brand plans a newspaper insert coupon worth one dollar off its shampoo. Before the insert date it sends retailers and clearinghouses an 887 with the coupon identifier, face value, issue and expiry dates, the family code of eligible products and the distribution method. Clearinghouses set up validation so redemptions can be processed when stores submit them.

Implementation

Implementation considerations for the 887

  • Send notifications before the coupons reach consumers.
  • Keep coupon and family code data consistent with the 877.
  • Communicate early terminations quickly to prevent invalid redemptions.
  • Coordinate with the redemption detail process (881) for reconciliation.

How ECOM helps

Automate the 887 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 catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 887?

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

Request a Demo Contact us