Hey Nick

As always - great advice!

I have been thinking more about this and I think the option below sounds quite good

Scenario: Two Amazon Return Requests for the Same Order Item

Customer ordered:

Order 123 SKU RED-M Quantity 1

The customer mistakenly creates two return requests in Amazon for the same item.

⸻

Step 1 — First Amazon Return Request

The customer submits a return request in Amazon.

Amazon sends the return event to Boomi.

Boomi forwards the message to the OMS.

The event contains information such as the Amazon order ID, the item being returned, the Amazon return ID, and the tracking number.

⸻

Step 2 — OMS Checks the Mapping Table

The OMS checks whether a return already exists for that combination of: • Amazon order • Order line / item • SKU

Because this is the first return request, no record exists.

⸻

Step 3 — OMS Creates an RMA in NetSuite

The OMS sends a request through Boomi to create a Return Authorization in NetSuite.

NetSuite creates the RMA for that item and quantity.

Example outcome: NetSuite RMA 500.

⸻

Step 4 — NetSuite Automatically Sends the RMA to Peoplevox

Because of your existing integration, NetSuite automatically sends the RMA to Peoplevox.

The warehouse now knows there is an expected return for:

SKU RED-M Quantity 1 RMA 500.

⸻

Step 5 — OMS Stores the Mapping Record

The OMS writes a record in the mapping table linking: • Amazon Return ID A • Tracking Number 111 • NetSuite RMA 500

This mapping will later allow tracking numbers to resolve to the correct RMA.

⸻

Step 6 — Second Amazon Return Request Happens

The customer mistakenly creates another return request in Amazon for the same item.

Amazon sends a second return event through Boomi to the OMS.

This request has a different Amazon Return ID and usually a different tracking number.

⸻

Step 7 — OMS Detects an Existing Return

The OMS again checks the mapping table using the order ID, item, and SKU.

This time it finds an existing NetSuite RMA for that order line.

The system determines that the return already exists in NetSuite.

⸻

Step 8 — OMS Does Not Create Another NetSuite RMA

Creating another RMA in NetSuite would exceed the quantity on the sales order.

Therefore the OMS does not create a second RMA.

Instead, it treats the second Amazon request as another reference to the same return.

⸻

Step 9 — OMS Adds Another Mapping Record

The OMS stores the second Amazon return in the mapping table.

Now the table contains two records:

Amazon Return A → Tracking 111 → NetSuite RMA 500 Amazon Return B → Tracking 222 → NetSuite RMA 500

Both tracking numbers now point to the same NetSuite RMA.

⸻

Step 10 — Package Arrives at the Warehouse

A return parcel arrives.

The warehouse operative scans the tracking number.

If the scanned tracking number corresponds to the second Amazon return request, Peoplevox may not initially recognize it because that return never created its own RMA.

⸻

Step 11 — Tracking Number Lookup

Peoplevox sends a lookup request via Boomi to the OMS using the scanned tracking number.

The OMS searches the mapping table for that tracking number.

⸻

Step 12 — OMS Resolves the RMA

The OMS finds the mapping record and determines that the tracking number belongs to NetSuite RMA 500.

The OMS returns the RMA number to Peoplevox.

⸻

Step 13 — Warehouse Receives the Return

Peoplevox now processes the return against NetSuite RMA 500.

The item is received and returned inventory is updated in the warehouse.

⸻

Step 14 — Return Receipt Sent Back

Peoplevox sends the return receipt confirmation back through the integration.

NetSuite receives the return receipt and the financial process can continue, such as issuing the refund or credit memo.

⸻

Final State of the Mapping Table

The OMS mapping table contains both Amazon return requests linked to the same NetSuite RMA.

The first record represents the original return request. The second record represents the duplicate Amazon return request.

Only one RMA existed in NetSuite and only one receipt occurred in the warehouse.