EDIFACT message guide · Shipping and logistics
RETINS Instruction for returns
The UN/EDIFACT message a party uses to say whether, and how, goods announced for return should be returned.
- Sent by
- Supplier, lessor or manufacturer
- Received by
- Customer or holder of the goods
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT RETINS message?
RETINS is the UN/EDIFACT instruction for returns message. The directory defines it as a message by which a party informs another party whether and how goods shall be returned. It usually answers an announcement for returns (RETANN).
The instruction can authorize the return and give an authorization number, a destination such as a repair center, the transport arrangements and the timing, or it can refuse the return or tell the customer to dispose of the goods locally. Clear instructions prevent unauthorized returns arriving at the wrong place.
How to read this diagram: the top row shows who sends RETINS, 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 RETINS 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.
When it is used
- Authorizing a return and giving the destination
- Refusing a return
- Instructing local disposal or scrapping
Where it fits in the message flow
Structure
Mandatory segments in RETINS (directory D.21A)
In UN/EDIFACT directory D.21A, the RETINS message has 65 segment positions arranged in 21 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)
- UNT
Practical example
RETINS in practice
A manufacturer receives a RETANN for 40 faulty routers. It sends the retailer a RETINS authorizing the return of 35 units to its repair center with a return authorization number and a collection date, and instructing local recycling of five units with cosmetic damage only. The retailer ships the 35 units with a despatch advice quoting the authorization.
Implementation
Implementation considerations for RETINS
- Give a return authorization reference for every accepted return.
- Specify destination, transport and timing.
- Answer each announced line, including refusals.
- Connect authorizations to credit and repair processes.
How ECOM helps
Automate RETINS 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
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 RETINS?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.