972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Shipping and logistics

RETANN Announcement for returns

The UN/EDIFACT message a party uses to announce goods it wants to return and the reasons, such as repair, end of lease or damage.

Sent by
Customer or holder of the goods
Received by
Supplier, lessor or manufacturer
Standard
UN/EDIFACT · Batch message
X12 equivalent
No direct equivalent

What is the EDIFACT RETANN message?

RETANN is the UN/EDIFACT announcement for returns message. The directory defines it as a message by which a party announces to another party details of goods for return for specified reasons, such as returns for repair, returns at the end of a leasing period or returns because of damage.

The announcement lets the supplier decide whether and how the goods should come back before anything ships. The supplier answers with an instruction for returns (RETINS), and the return itself is then announced with a despatch advice.

How the EDIFACT RETANN message worksDiagram of the UN/EDIFACT RETANN Announcement for returns message. Customer or holder of the goods sends it to supplier, lessor or manufacturer. It usually starts the exchange. It is usually followed by RETINS. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG11 loop with LIN (Line item) and UNS (Section control). 18 conditional segment groups are listed by their trigger segment.How the EDIFACT RETANN message worksAnnouncement for returns: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeRETANNSENDERCustomer or holder ofthe goodsRECEIVERSupplier, lessor ormanufacturerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYRETINSInstruction for returns2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage RETANNUNH … UNTSTART OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG11 · repeats up to 9,999LINLine itemUNSSection control+ 18 conditional groups, starting with:DOCRFFNADTODTDTEQDALCTAXQTYDGSHANPACBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for RETANN. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT RETANN message worksDiagram of the UN/EDIFACT RETANN Announcement for returns message. Customer or holder of the goods sends it to supplier, lessor or manufacturer. It usually starts the exchange. It is usually followed by RETINS. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and body and segment groups: the required SG11 loop with LIN (Line item) and UNS (Section control). 18 conditional segment groups are listed by their trigger segment.How the EDIFACT RETANNmessage worksAnnouncement for returns: who sends it, whereit fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeRETANNSENDERCustomer orholder of thegoodsRECEIVERSupplier, lessoror manufacturerCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYRETINSInstruction for returns2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message RETANN (UNH … UNT)START OF MESSAGEBGMBeginning of messageBODY AND SEGMENT GROUPSMandatory group SG11 · repeats upto 9,999LINLine itemUNSSection control+ 18 conditional groups, starting with:DOCRFFNADTODTDTEQDALCTAXQTYDGSHANPACBlue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for RETANN.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends RETANN, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around RETANN and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.

Expand diagram Download SVG

When it is used

  • Announcing damaged or defective goods for return
  • Announcing returns at the end of a lease
  • Requesting return of unsold or overstocked goods

Where it fits in the message flow

This message RETANN Announcement for returns
Usually followed by RETINS Instruction for returns

Structure

Mandatory segments in RETANN (directory D.21A)

In UN/EDIFACT directory D.21A, the RETANN message has 74 segment positions arranged in 24 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.

  • UNH
  • BGM
  • SG11 (LIN)
  • UNS
  • UNT

Practical example

RETANN in practice

An electronics retailer has 40 faulty units of a router model returned by customers. It sends the manufacturer a RETANN listing the product, serial numbers, quantities and fault reasons. The manufacturer replies with a RETINS authorizing the return to its repair center, and the retailer ships the units with a DESADV.

Implementation

Implementation considerations for RETANN

  • Use return reason codes agreed with the supplier.
  • Include serial or batch numbers where the supplier tracks them.
  • Wait for return instructions before shipping.
  • Link the return to credit notes or repairs that follow.

How ECOM helps

Automate RETANN with ECOM

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Industry

Consumer Goods

Retail, distributor, marketplace and direct-channel integration for consumer brands.

Solution

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related shipping and logistics messages

Need help with RETANN?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us