Skip to content
EDI Costco Costco Dropship (via Commerce Hub) 180
X12 EDI

Costco X12 180 Return Merchandise Authorization and Notification

X12 180 (Return Merchandise Authorization and Notification) is the EDI transaction exchanged between Costco (Costco Dropship (via Commerce Hub)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
18
Loops
2
X12 180
All partners ↗
Book a demo ← All Costco Dropship (via Commerce Hub) transactions

Transaction context

Where 180 Return Merchandise Authorization and Notification fits on Costco Dropship (via Commerce Hub)

Costco channels
1 of 12

1 of Costco's 12 channels carries 180

Trading partners
5

partners across the Stacksync network trade 180

Channels
5

channels network-wide carry 180

Most common alongside 180

On CommerceHub, 180 runs on 1 channel.

The 180 carries the merchandise returns workflow between retailers and suppliers: a request for return authorization, the authorization or disposition decision, and notification that merchandise is being or has been returned, including consumer returns. Trading partners require it to replace fax and email RMA handling and to keep return credits, dispositions, and inbound return shipments matched to the original sale. 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 fires: 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.

Common 180 rejection causes
  • Ambiguous use-case designation: because one 180 can be a request, an authorization, or a notification, a missing or wrong purpose designation leaves the receiver unable to route the document.
  • Missing original purchase order reference (PRF segment), which breaks matching of the return to the original sale.
  • Missing or invalid return reason codes, delaying the supplier's disposition decision.
  • No 997 functional acknowledgment returned for the transaction, so the sender cannot confirm receipt and the return sits unresolved.

Specification summary

X12 180 Return Merchandise Authorization and Notification at the element level

The X12 180 specification defines 22 segments carrying 75 data elements, 42 of which are mandatory.

Segments
22
Data elements
75
Mandatory elements
42
Segments with mandatory elements
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
Full segment guideline — 18 segments 2 loops · X12 180 Return Merchandise Authorization and Notification
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BGN Beginning Segment 5 elements

To indicate the beginning of a transaction set

PRF Purchase Order Reference 2 elements

To provide reference to a specific purchase order

DTM Date/Time Reference 4 elements

To specify pertinent dates and times

N9 Reference Identification 3 elements

To transmit identifying information as specified by the Reference Identification Qualifier

TD5 Carrier Details (Routing Sequence/Transit Time) 1 element

To specify the carrier and sequence of routing and provide transit time information

NTE Note/Special Instruction 1 element

To transmit information in a free-form format, if necessary, for comment or special instruction

N1 Loop Repeat: 200
N1 Name 2 elements

To identify a party by type of organization, name, and code

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 4 elements

To specify the geographic place of the named party

PER Administrative Communications Contact 7 elements

To identify a person or office to whom administrative communications should be directed

BLI Loop
BLI Baseline Item Data 6 elements

To specify basic item data: item identification, quantity, and price

PID Product/Item Description 3 elements

To describe a product or process in coded or free-form format

RDR Return Disposition Reason 1 element

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

MEA Measurements 3 elements

To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Trading partners

5+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Browse the full directory

Costco Costco Dropship (via Commerce Hub) EDI 180 FAQ

Common questions about 180 Return Merchandise Authorization and Notification on the Costco Dropship (via Commerce Hub) channel.

What is X12 180 Return Merchandise Authorization and Notification?
X12 180 (Return Merchandise Authorization and Notification) is the EDI transaction set used to exchange return merchandise authorization and notification data. Costco's Costco Dropship (via Commerce Hub) channel requires it from trading partners.
Does Costco Costco Dropship (via Commerce Hub) require 180 for trading partners?
Yes, Costco (Costco Dropship (via Commerce Hub)) supports X12 180 Return Merchandise Authorization and Notification. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Costco 180 with Stacksync?
Most companies go live with Costco 180 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 180 on Costco Dropship (via Commerce Hub)?
On Costco Dropship (via Commerce Hub), X12 180 is typically exchanged alongside 850 Purchase Order, 856 Ship Notice Manifest, 846 Inventory Inquiry Advice, 860 Purchase Order Change Request Buyer Initiated. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.

Ready to automate your Costco EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a Costco EDI demo Tour the platform on your own