/ 4 min read / returned goods / repair record / SKU mapping
Returned Goods Come Back Under New SKU
Returned goods under a new SKU need a link to original shipment, claim, and repair record.
What to check in the order file
Returned Goods Come Back Under New SKU starts when a buyer notices returned goods coming back under a new SKU code. The order may still look normal, but returned goods under new SKU changes what another person will need to prove later.
For returned goods under new SKU, the first pass should stay close to the documents. Compare original invoice, return authorization, repair note, new SKU, packing list, photos, and broker message.
A supplier may use a new SKU for repaired goods because the packaging or component changed. The buyer needs one plain sentence: whether the returned goods can be tied to the original transaction and claim.
The control question is narrow: can the buyer connect the new SKU to the old claim without reopening email?
When returned goods under new SKU affects value, beneficiary, carton count, origin wording, product description, freight charge, or claim credit, attach the buyer's decision to the commercial file.
Store the note near the return and repair folder.
The next reviewer should see why returned goods under new SKU was accepted, held, or sent back for correction.
Make the decision before the next handoff
Returned goods under a new SKU need a link to original shipment, claim, and repair record. Another member of the team should be able to verify the answer from the file before claim acceptance, credit, replacement, or file closure. Make this result visible in the returned goods sku decision record.
Open the customer or warehouse evidence, SKU and batch link, receiving record, counterparty response, warranty term, and proposed credit or replacement together. Mark the first changed field and retain the earlier version beside the file the order owner plans to use. The comparison should show who supplied the revision, when it arrived, and which order step depends on it. Attach the evidence to the repair record version that now controls the order.
Familiar commercial explanations can hide a real mismatch. Ask which company, file, quantity, model, payment, or shipment the answer covers, and record when the answer applies only to this order. Carry the result into the SKU mapping instruction used by the next team.
Assign the file to customer service, quality, and the person negotiating the vendor remedy. The owner does not need every chat message, but does need the final record, vendor answer, purchasing team decision, and next checkpoint. Link the answer to the returned goods checkpoint for this order.
The unresolved risk is that the order owner may lose the link between the reported problem and the supplier shipment that should answer for it. State whether the exception covers one shipment, one payment, one model, or the wider supplier relationship. A one-order decision should not silently become standing approval. State the remaining limit in the returned goods sku note before the file is closed.
Use the checklist as a closing test: keep the earlier file version, name the changed field, tie the decision to po or invoice, and assign the next owner. Record who completed each step and keep the evidence beside the file it supports instead of leaving a general note that the vendor was checked. Keep the supporting file beside the SKU mapping entry in the order folder.
Give the exception an end point, such as receipt of a corrected record, payment confirmation, inspection, broker acceptance, warehouse receipt, or claim settlement. Put that result in the returned goods note for the current PO.
Close the record for the next order
Public guidance can frame the returned goods check, but it cannot establish the facts of this order. The importer's PO, invoice, beneficiary record, packing list, product evidence, broker reply, and shipment file remain the deciding records. Use the repair record record to show who accepted the result and on what date.
If the issue returns, begin with the prior note. It should show which file to request first and which assumption caused the earlier delay. Keep the supporting file beside the returned goods sku entry in the order folder.
Save the revision path visible. The folder should show which version was rejected, which version controls, and whether anyone outside sourcing still holds an obsolete copy. State the remaining limit in the returned goods note before the file is closed.
Record one of three outcomes: approve, approve with a stated condition, or hold. Name the evidence supporting that outcome and the event that would force the importer to reconsider it. The next reviewer should find the answer under repair record without reopening the whole case.
Send the controlling document to every team that will act on it. Approval is incomplete when finance, logistics, the warehouse, or the broker continues from an older version. Use the SKU mapping record to show who accepted the result and on what date.
When the same exception affects several orders, add the field to the supplier baseline. Repeated problems belong in onboarding, PO wording, inspection scope, payment decision, or broker instructions. Record the outcome with the returned goods sku evidence before handoff.
Working checklist
- Keep the earlier document version.
- Name the changed field.
- Tie the decision to PO or invoice.
- Assign the next owner.
- Store proof beside the final file.