Skip to content
X12 EDI

Costco X12 180 Return Merchandise Authorization and Notification

Plan X12 180 Return Merchandise Authorization and Notification for Costco Dropship (via Commerce Hub). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
18
Loops
2
X12 180
Partner references ↗

Implementation guide

Costco Dropship (via Commerce Hub): 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.

This document is listed for Costco Dropship (via Commerce Hub). Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat 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.

The document reference includes 18 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

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 Costco 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.

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 list 180

Trading partners
5

partner references list 180

Channels
5

channel entries list 180

The directory associates CommerceHub and 180 with 1 channel.

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
Segment reference — 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)

Related references

Other transactions in Costco Dropship (via Commerce Hub)

Other EDI documents listed on this channel.

Costco Dropship (via Commerce Hub) EDI 180 questions

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 used for?

180 is used when a return is requested, authorized or notified. It carries information for the return authorization. Match it to your business system using return authorization, original order and returned item.

Is 180 required for Costco Dropship (via Commerce Hub)?

180 is listed for Costco Dropship (via Commerce Hub). Confirm the required version and direction for your business unit and account with the partner.

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.

How does 180 relate to other EDI messages?

Keep 180 business processing separate from transport receipt and technical validation. Agree which preceding record, response or reconciliation completes the return authorization workflow; confirm any required companion messages with your partner.

Connect Costco 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.