--- title: "EDI 180 Return Merchandise Authorization | X12 | Stacksync" description: "EDI 180 is the X12 Return Merchandise Authorization and Notification, used when a return is requested, authorized or notified." canonical: https://www.stacksync.com/edi/x12/180-return-merchandise-authorization-and-notification last_modified: 2026-09-29 --- X12 transaction code # EDI 180 Return Merchandise Authorization and Notification (X12 180) > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md EDI 180 is the X12 Return Merchandise Authorization and Notification transaction set, used when a return is requested, authorized or notified. The document is bidirectional: a retailer or buyer typically sends the return request or return notification to the supplier, and the supplier sends back the authorization or disposition. Standard X12 Code 180 Partner references 5 [Book an EDI demo](https://www.stacksync.com/book-a-demo) [← All trading partners](https://www.stacksync.com/edi) At a glance ## EDI 180 at a glance What the 180 carries, who sends it to whom, when it goes out, and the segments trading partners list for it. **X12 180 Return Merchandise Authorization and Notification summary** | | | | --- | --- | | Document | X12 180 Return Merchandise Authorization and Notification | | Business record | Return authorization | | Who sends it to whom | The document is bidirectional: a retailer or buyer typically sends the return request or return notification to the supplier, and the supplier sends back the authorization or disposition. | | When it is sent | Merchandise is found defective, damaged, or incorrectly shipped, or a consumer returns product in-store, prompting the retailer to request authorization or notify the supplier of the return. | | Match on | Return authorization, original order and returned item | | Partner references | 5 trading partners in this directory | | Related documents | [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice), [X12 861 Receiving Advice/Acceptance Certificate](https://www.stacksync.com/edi/x12/861-receiving-advice-acceptance-certificate) | ### Key segments in an EDI 180 The business segments that appear in at least half of the 5 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send. | Segment | Name | Purpose | Partner references | | --- | --- | --- | --- | | BGN | Beginning Segment | To indicate the beginning of a transaction set. | 5 of 5 | | PRF | Purchase Order Reference | To provide reference to a specific purchase order. | 5 of 5 | | DTM | Date/Time Reference | To specify pertinent dates and times. | 5 of 5 | | BLI | Baseline Item Data | To specify basic item data: item identification, quantity, and price. | 5 of 5 | | N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 4 of 5 | | RDR | Return Disposition Reason | To indicate the disposition of the item, the reason for return by the returnee, the response to the reason for return, and whether the item was used. | 4 of 5 | | N1 | Name | To identify a party by type of organization, name, and code. | 3 of 5 | Stacksync connects EDI documents such as the X12 180 to your ERP, CRM and databases with two-way sync. Read the [EDI overview](https://www.stacksync.com/edi), check [pricing](https://www.stacksync.com/pricing) and [security](https://www.stacksync.com/security), or [book a demo](https://www.stacksync.com/book-a-demo) to walk through your partner guide. Implementation guide ## X12 180 mapping and validation X12 180 Return Merchandise Authorization and Notification is used when a return is requested, authorized or notified. Preserve return authorization, original order and returned item so the return authorization in your business system stays connected to the original document. Use the version and implementation guide agreed with your trading partner to confirm required fields and responses. **Map records and test the business result** | Document or decision | Record and matching IDs | What to test | | --- | --- | --- | | Match the business record | **return authorization** return authorization, original order and returned item | Define which combination of return authorization, original order and returned item identifies one business record, its lines and any later revision. | | Update the receiving system | **Processing the return authorization** ID assigned by the receiving system and processing result | Test a return quantity larger than the original shipment and require review. Keep authorization separate from physical receipt so stock is not increased early. | | Check the processing result | **Processing status for the return authorization** Original document reference and matching response | Reconcile the return authorization with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document. | ### How the related documents differ Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately. - [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice) **accounts-receivable or accounts-payable invoice:** a bill is ready for the buyer to process. - [X12 861 Receiving Advice/Acceptance Certificate](https://www.stacksync.com/edi/x12/861-receiving-advice-acceptance-certificate) **goods receipt or acceptance record:** received goods are counted or accepted. ### Implementation steps 1. #### Choose the starting event and owner Decide which application acts when a return is requested, authorized or notified. Name the operational owner of the return authorization and the team that resolves rejected or ambiguous messages. 2. #### Keep record IDs connected Map return authorization, original order and returned item. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier. 3. #### Test failures before launch Run the failure cases in the mapping table against realistic return authorization data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate. 4. #### Track every document to completion Record transport delivery and document validation separately from successful return authorization processing. Give unresolved errors an owner and check the receiving system before approving retries. ### Go-live checklist - An approved 180 sample and the agreed version and partner guide are available. - The mapping tests pass with realistic return authorization data. - Each submitted document can be traced through delivery, validation and processing in the receiving system. - Your team knows how to investigate and recover a rejected or timed-out return authorization without processing it twice. ### Related documents and resources - [X12 810 Invoice](https://www.stacksync.com/edi/x12/810-invoice) - [X12 861 Receiving Advice/Acceptance Certificate](https://www.stacksync.com/edi/x12/861-receiving-advice-acceptance-certificate) - [Field mapping workbook](https://www.stacksync.com/blog/two-way-sync-field-mapping-workbook) - [Production readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) **Sources.** Sources reviewed 2026-09-15. - [X12 transaction-set directory](https://x12.org/products/transaction-sets) - [RFC 4130: AS2 and message receipts](https://www.rfc-editor.org/info/rfc4130/) Document structure ## X12 180 Return Merchandise Authorization and Notification at the element level The X12 180 reference contains 22 segment entries and 75 data elements; 42 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields. Segments 22 Data elements 75 Mandatory elements 42 **Segments with elements marked mandatory in this reference** | Segment | Elements | Mandatory | | --- | --- | --- | | BGN | 5 | 3 | | PRF | 2 | 1 | | DTM | 4 | 1 | | N9 | 3 | 1 | | NTE | 1 | 1 | | N1 | 2 | 1 | | N3 | 2 | 1 | | PER | 7 | 1 | | BLI | 6 | 2 | | PID | 3 | 1 | Key identifiers in 180 - Transaction Set Purpose Code - Reference Identification - Date - Purchase Order Number - Date/Time Qualifier - Reference Identification Qualifier - Description - Entity Identifier Code ## Find your trading partner for X12 180 5 partners, 5 channels. Choose a channel to inspect its listed document reference and implementation context. - [Belk](https://www.stacksync.com/edi/belk) [Belk.com (via Rithum)](https://www.stacksync.com/edi/belk/belk-com-via-rithum/x12-180-return-merchandise-authorization-and-notification) - [Costco](https://www.stacksync.com/edi/costco) [Costco Dropship (via Commerce Hub)](https://www.stacksync.com/edi/costco/costco-dropship-via-commerce-hub/x12-180-return-merchandise-authorization-and-notification) - [Fanatics](https://www.stacksync.com/edi/fanatics) [Fanatics (Legacy ISA ID: SPSFANATICSP)](https://www.stacksync.com/edi/fanatics/fanatics-legacy-isa-id-spsfanaticsp/x12-180-return-merchandise-authorization-and-notification) - [HD Supply Holdings, Inc.](https://www.stacksync.com/edi/hd-supply-commerce-hub) [HD Supply (via Rithum (formerly CommerceHub))](https://www.stacksync.com/edi/hd-supply-commerce-hub/hd-supply-via-rithum-formerly-commercehub/x12-180-return-merchandise-authorization-and-notification) - [NEXCOM (Navy Exchange Service Command)](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) [NEXCOM Trans](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command/nexcom-trans/x12-180-return-merchandise-authorization-and-notification) Catalog breakdown ## Where X12 180 Return Merchandise Authorization and Notification appears in this catalog The largest groups of classified 180 catalog entries are in retail, building & hardware and e-commerce & marketplaces. ### By industry - retail 3 channels - building & hardware 1 channel - e-commerce & marketplaces 1 channel ### By network - Rithum 2 channels - CommerceHub 1 channel Partner entries with the most listed channels - [Belk](https://www.stacksync.com/edi/belk) - [Costco](https://www.stacksync.com/edi/costco) - [Fanatics](https://www.stacksync.com/edi/fanatics) - [HD Supply Holdings, Inc.](https://www.stacksync.com/edi/hd-supply-commerce-hub) - [NEXCOM (Navy Exchange Service Command)](https://www.stacksync.com/edi/nexcom-navy-exchange-service-command) FAQ ## EDI 180 questions ### What is an EDI 180? EDI 180 is the X12 Return Merchandise Authorization and Notification transaction set. Trading partners use it when a return is requested, authorized or notified. It carries the data for the return authorization, and your system matches it on return authorization, original order and returned item. ### Who sends an EDI 180 and who receives it? The document is bidirectional: a retailer or buyer typically sends the return request or return notification to the supplier, and the supplier sends back the authorization or disposition. Your trading partner agreement confirms the direction and version for your account. ### When is an EDI 180 sent? Merchandise is found defective, damaged, or incorrectly shipped, or a consumer returns product in-store, prompting the retailer to request authorization or notify the supplier of the return. Your partner guide sets any deadline or schedule for the document. ### What are the key segments in an EDI 180? Across 5 partner document references listed here, the business segments that appear most often include BGN (Beginning Segment), PRF (Purchase Order Reference), DTM (Date/Time Reference), BLI (Baseline Item Data), N9 (Reference Identification), RDR (Return Disposition Reason). Each partner guide sets which segments and elements your account must send. ### What is the difference between EDI 180 and EDI 810? The 180 carries the return authorization and is used when a return is requested, authorized or notified. The 810 carries the accounts-receivable or accounts-payable invoice and is used when a bill is ready for the buyer to process. ### What should I map for X12 180? Start with return authorization, original order and returned item and the target return authorization. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats. ### How should I test 180 error handling? Test a return quantity larger than the original shipment and require review. Keep authorization separate from physical receipt so stock is not increased early. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment. ### Which partners list X12 180? The directory on this page links 5 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires. ## Connect EDI to your business systems See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout. [Book an EDI demo](https://www.stacksync.com/book-a-demo) [Explore the EDI platform](https://www.stacksync.com/edi)