How should a damaged-order replacement be approved?
Format: Article.
Before sending a replacement, get the right person's approval and check that it is ready to ship. Gather the customer's report. Match it to the item. Check the policy and any refund or replacement already arranged. Then check stock. A photo, a kind draft reply, or a request for help is not permission to send another item.
Keep the customer's need at the center of the review. Staff can say they have read the damage report without deciding who caused it. They can offer to check for a new item without saying one is held or on its way. A “remedy” below means the agreed fix, such as a new item or refund.
Assemble a replacement review packet
| Packet section | Evidence or decision needed |
|---|---|
| Original item | Order, line, variant, quantity, and parcel reference |
| Customer report | Their description, report time, and requested resolution |
| Damage evidence | Relevant photos or observations, with source and limits |
| Policy | Applicable version and any exception requiring approval |
| Remedy history | Related replacement, refund, return, or other service cases |
| Replacement proposal | Exact item and quantity, including any difference from the original |
| Stock check | Usable stock, location, source, and check time |
| Decision | Authorized approver, approved scope, unresolved conditions |
| Release check | Duplicate check, current readiness, and warehouse owner |
Ask for proof that helps answer the policy question. Leave out personal details that staff do not need. Never ask a customer to recreate an unsafe scene for a better photo. If an image cannot show the problem, say so. The care lead can decide what to ask for next under the store's rules.
Shopify describes processing a return, issuing a refund, and shipping an exchange as separate steps. [S01] Keep those states separate in your review too. This does not mean every damaged item must come back. Nor does it mean Shopify's exchange process fits every store's replacement policy. Check the app features and rules that apply to your store.
Hypothetical example: a cracked ceramic bowl
In this made-up case, the customer says one bowl in a set arrived cracked. Their photo shows a crack but not when it happened. Support saves what the customer said. Staff do not blame the carrier or the customer.
The care lead checks the order and policy. An earlier chat has a refund request for the same bowl. Staff do not know whether it went through. There is a matching bowl in stock. Support drafts a plan to send it, but holds that plan while staff check the refund. That check avoids granting two conflicting fixes for the same item.
The reviewer checks the proposed fix with staff and the customer. In this example, they choose one matching bowl, but only if no conflicting refund or replacement has gone through. Staff still need to check that point. Keep the packet on hold until they do. Having a bowl in stock does not clear the hold.
The customer draft says: “We have your damage report and are checking whether to send a new bowl. We need to check an earlier service request before we confirm the next step.” Staff can make the message warmer. They must not invent a shipment or a refund to do so.
Run the double-remedy check by item
Search cases by the original order and item, not just the customer's name. Check what each fix covers and how many units. A refund for shipping may not cover the damaged bowl. A request for a new bowl does not mean one was sent. Keep each record's state and source.
If records conflict, name a care owner to check them. Do not reject the customer or undo a refund by default. Give the reviewer the whole picture. A conflict is a reason to check, not proof that someone did something wrong.
For several damaged items, write down the choice for each one. Approval for one bowl should not release a whole set. If a substitute has a different size, finish, or use, ask for the required customer consent. A similar item code, or SKU, does not prove it is the same product.
Recheck at the warehouse handoff
The handoff should name the item, count, ship-to reference, and any conditions. Before release, check that the approval still applies. Has another team already arranged a new bowl? Is the stock check old? Is the address unclear? Send the packet back for review if any of those checks fails.
Keep “approved,” “released,” and “carrier received” separate in replies. A staff decision is not a tracking event. This guide does not issue refunds, send payments, change stock, or place replacement orders. Those actions need their own approved process and result check.
Core Agentic builds custom AI software to fit your support and shipping tools. A proposed review packet could gather the records for staff. Agree on access, policy rules, how to keep each customer's data separate, and what may go to cloud models. Test these limits before use. This is not a finished commerce product.
To explore a replacement review that gives staff a clear decision, Book a Demo.
Sources
These sources describe the named provider or framework. They do not establish a Core Agentic integration, customer result or certification.