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 143 Product Service Notification

The X12 document used to transmit a mandatory or voluntary product recall, usually to servicing organizations.

Sent by
Manufacturer
Received by
Servicing organization, dealer or consumer
Standard
ANSI ASC X12

What is an EDI 143?

The EDI 143 Product Service Notification is the ANSI X12 transaction set used to transmit a mandatory or voluntary recall. While it could be sent to a consumer, it is more likely to be sent to a servicing organization, giving notice of the recall and the products affected.

Dealers and service centers need to know which products are affected, what work is required and how it will be reimbursed. The notification lets them identify affected products in their records and schedule the work, which is later claimed with the 142.

How the EDI 143 worksDiagram of the EDI 143 Product Service Notification. Manufacturer sends it to servicing organization, dealer or consumer. It usually starts the exchange. It is usually followed by 142 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required LIN loop with LIN (Item Identification). 3 optional loops are listed by their first segment.How the EDI 143 worksProduct Service Notification: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 143SENDERManufacturerRECEIVERServicing organization,dealer or consumer997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY142Product Service Claim997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code WAGS … GETransaction set 143ST … SEHEADINGBGNBeginning SegmentRequired loop N1 · repeats many timesN1Party IdentificationDETAILRequired loop LIN · repeats many timesLINItem Identification+ 3 optional loops, starting with:N1PRRSLNBlue 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 143. Your trading partner's implementation guide adds its own requirements.
How the EDI 143 worksDiagram of the EDI 143 Product Service Notification. Manufacturer sends it to servicing organization, dealer or consumer. It usually starts the exchange. It is usually followed by 142 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and the required N1 loop with N1 (Party Identification) and detail: the required LIN loop with LIN (Item Identification). 3 optional loops are listed by their first segment.How the EDI 143 worksProduct Service Notification: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 143SENDERManufacturerRECEIVERServicingorganization,dealer orconsumer997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY142Product Service Claim997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code WA (GS … GE)Transaction set 143 (ST … SE)HEADINGBGNBeginning SegmentRequired loop N1 · repeats manytimesN1Party IdentificationDETAILRequired loop LIN · repeatsmany timesLINItem Identification+ 3 optional loops, starting with:N1PRRSLNBlue 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 143. Your trading partner'simplementation guide adds its own requirements.

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

  • Notifying dealers of a safety recall
  • Announcing voluntary service campaigns
  • Listing affected serial numbers

Where it fits in the document flow

This document 143 Product Service Notification
Usually followed by 142 Product Service Claim997 Functional Acknowledgment

Structure

Mandatory segments in the 143 (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
  • LIN
  • PRR
  • N9
  • REP
  • PRT
  • ITA
  • SLN
  • SE

Practical example

The 143 in practice

An equipment manufacturer discovers a defective hydraulic hose on a range of loaders. It sends its dealers a 143 describing the recall, the affected serial number range, the replacement procedure and the reimbursement terms. Dealers check their customers' machines and schedule the repairs.

Implementation

Implementation considerations for the 143

  • Identify affected products precisely by serial range.
  • State the required work and reimbursement terms.
  • Follow regulatory requirements for mandatory recalls.
  • Track completion of recall work for each product.

How ECOM helps

Automate the 143 with ECOM

Industry

Manufacturing

Customer schedules, supplier connectivity and shipping integrated with the ERP for manufacturers.

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

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 communications documents

All 16 communications documents

Need help with the EDI 143?

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

Request a Demo Contact us