Separate replacement from refund and return
A replacement is a new shipment, not a refund and not a return. The note should say which remedy the customer chose and who approved it. Mixing the three creates duplicate credits and lost stock. Write the distinction at the top of the record.
Record the original order and the item that failed. Include the SKU, the quantity, and the specific defect or loss. A note that says wrong item cannot support a replacement. The warehouse needs the detail to send the right product.
Decide whether the customer must return the original item before a replacement ships. This is a policy decision, not a desk preference. Record the policy and any exception. The note should state whether a return label was issued.
Keep the replacement value within the desk's written limit. A high-value replacement needs an owner's approval before the order is created. Record the approver and the time. A limit that exists only in training is not a control.
Capture the original order and the failed item
Start from the order record rather than the customer's description alone. Confirm the purchase date, the shipping address, and the item on file. Compare that record with the photo or message the customer sent. The comparison is the evidence for the replacement.
Ask for a photo when the defect is visible and the policy allows it. Give the customer a clear reason for the request. Do not demand a photo for a missing parcel that was never delivered. Match the evidence request to the actual failure.
Check whether the item is still in stock before promising a replacement. A promise made without a stock check becomes a second failure. If stock is unavailable, offer the approved alternative or escalate. Record the choice the customer made.
Note any prior replacement on the same order. A second replacement can signal a recurring defect or a misuse pattern. Escalate the pattern rather than processing another shipment automatically. The history belongs in the note.
State the decision owner and the limit
Write the name of the person who approved the replacement. A queue that says approved without a name cannot be audited. Include the role and the time of approval. The owner should be reachable if the warehouse asks a question.
Separate the decision to replace from the decision to expedite. An expedited shipment may cost more and needs its own approval. Record the service level and who authorized it. Do not let urgency quietly expand the desk's authority.
Give the desk a clear stop rule for suspected fraud. Repeated replacements to different addresses or names should pause for review. Record the signal and the reviewer. The stop rule protects the customer relationship as well as the margin.
Tell the customer what was approved and what happens next. State the item, the address, and the expected ship date. Avoid promising a delivery date the warehouse has not confirmed. The message should match the record exactly.
Give the note a status and a follow-up date
Use a small status set such as requested, approved, shipped, delivered, and closed. Each status should have a next action and a time limit. A note that only says open does not tell the team what to do. Sort the queue by the next due action.
Set a follow-up date for the warehouse confirmation. A replacement that was approved but never shipped is invisible without one. Check the date on the next shift. Record the result of the check.
Record the tracking number when the replacement ships. Link it to the original order and the case. The customer should not have to explain the history again. A linked record also prevents a duplicate replacement.
Close the note only when the customer has the item or an agreed alternative. Delivery confirmation is the preferred evidence. If the customer cannot be reached, record the attempts and the final disposition. The queue should distinguish resolved from simply quiet.
Review replacements for repeat causes
Review replacements weekly by product, reason, and destination. A product with repeated defects may need a quality check. A destination with repeated losses may need a carrier review. Group the cases before choosing a fix.
Compare the replacement rate with the return rate and the refund rate. A rising replacement rate with stable returns may mean the desk is choosing the easiest remedy. Report the three measures together. A single measure can hide a shift in behavior.
Ask the warehouse and the customer team what the note misses. They see the packing problem and the customer's real complaint. Use one example in the next review. A small field can remove a long email thread.
Update the note template when the policy or the system changes. Remove fields that no one uses and add the one fact that keeps causing delays. Record the effective date. A template that grows without review becomes a form to skip.
For the next step, compare this workflow with Design a refund decision lane for an outsourced support team and Reconcile Partial Shipments With Outsourced Order Support. For access and oversight, use the authoritative planning reference alongside your own policy.
