A customer asking where an order is should be a routine support event. When the store has no delivery record, no supplier escalation rule, and no clear refund boundary, the same question can become a refund, a public complaint, or a chargeback within days.
This playbook turns post-purchase support into an operating system. It connects the promise shown on the product page to the supplier’s actual process, Shopify’s return settings, the response the customer receives, and the evidence retained if the payment is disputed. The goal is not to refuse every refund. It is to reach the fairest defensible resolution before uncertainty becomes expensive.
Use this as the parent guide. The supporting guides cover the Shopify return-policy workflow, the choice between refunds, exchanges, store credit, and reships, and the evidence required to prevent and answer Shopify chargebacks. This is operational guidance, not legal advice. Confirm the rules that apply to your business and markets.
Build support around one customer promise and one order record
The most common support failure is not a rude reply. It is a mismatch between systems. The product page says delivery takes 5 to 8 business days, the supplier dashboard shows 10 to 18, the confirmation email says only that the order is processing, and the support agent has no date for the next update. The customer receives four different versions of the purchase.
Create one truth set for every product and shipping lane. Record the supplier, fulfillment origin, processing range, transit range, tracking handoff, cancellation cutoff, return destination, defect procedure, and who pays each exception cost. Use sample orders and completed orders as evidence. Supplier catalog promises are inputs to verify, not copy to publish.
The order timeline should then live in one place your support team can read. At minimum, retain the order date, payment state, supplier order ID, fulfillment state, tracking number, carrier events, customer messages, concessions, refunds, and final resolution. A customer should never need to repeat the problem because your store changed channels.
| Record | Owner | Decision it supports |
|---|---|---|
| Published delivery range | Store owner | Whether the order is actually late |
| Supplier order and tracking | Operations | Whether to wait, trace, reship, or refund |
| Customer thread | Support | What was promised and whether the issue was resolved |
| Return or refund state | Support and finance | What money or inventory is still outstanding |
| Product-page snapshot | Marketing | Whether the item matched the description at purchase |
One order record prevents support, operations, and finance from making conflicting decisions.
Treat the return policy as an operating contract
A policy is useful only when the storefront, Shopify settings, supplier process, and support behavior can all honor it. Before choosing a return window, map what happens to the physical item. Can it go to your address, a 3PL, or the supplier? Does the supplier require authorization? Is the item worth recovering after international postage? Can it be inspected and resold? If no workable destination exists, do not promise a conventional return process and invent one after the first request.
Define eligibility, the start of the return window, required condition, excluded items, return-shipping responsibility, restocking fees, refund method, inspection timing, damaged-item evidence, and the handling of original shipping charges. Shopify can configure return windows, shipping fees, restocking fees, final-sale items, and market-specific rules. Its current return-rules documentation also notes that changes apply to future orders, not previous purchases.
Legal rights can override the commercial policy. For US orders, the FTC’s Mail, Internet, or Telephone Order Merchandise Rule governs shipment promises and delay choices. For many EU distance sales, consumers have a 14-day withdrawal right, subject to conditions and exceptions described by Your Europe. Get market-specific advice before using final-sale language or charging return costs.
Policy visibility also affects acquisition. Google Merchant Center can flag a store that lacks a clear, accessible, internally consistent return and refund policy. Google’s merchant guidance says the policy should explain requirements and timelines and remain consistent across the website and Merchant Center.
- Write the policy from the physical workflow, not from a competitor’s template.
- Separate change-of-mind returns from damaged, defective, wrong-item, and non-delivery claims.
- State when the window starts: order date, fulfillment date, or delivery date are not interchangeable.
- Keep a dated copy of the policy associated with each order when policy terms change.
- Display the same core rules on the product page, policy page, checkout context, and support macros.
Create a supplier resolution map before the first complaint
Dropshipping separates the seller from the parcel, but it does not transfer the customer obligation to the supplier. The customer bought from your store. If the parcel is late, damaged, incorrectly declared, or materially different from the listing, your support team must resolve the issue while pursuing the supplier separately.
For every supplier, document the evidence deadline, accepted file types, claim window, return address, refund method, reship conditions, and escalation contact. Some suppliers require an unedited unboxing video. Others accept carrier scans or photos. A requirement discovered after the customer discarded the packaging is not an operational process.
Decide whether each low-value item is returnable, returnless-refund eligible, or replacement-first. Returnless refunds can be rational when return postage, processing, and inspection exceed recoverable value. They should not be automatic for every claim. Use product cost, shipping, likely recovery, abuse risk, and customer evidence to choose the least wasteful fair outcome.
| Failure | Customer-facing action | Supplier-side action |
|---|---|---|
| Not yet fulfilled | Cancel if permitted and confirm refund | Stop supplier order before cutoff |
| Tracking stalled | Give a dated next update or trace result | Open carrier or supplier trace |
| Delivered but not found | Check address, carrier proof, household, and safe place | Request delivery evidence or carrier claim |
| Damaged or defective | Request proportionate evidence, then refund or replace | File claim within supplier deadline |
| Wrong item or variant | Replace or refund without blaming supplier | Document mapping or pick error |
| Not as described | Compare the received item with the listing at purchase | Audit sample, listing, and supplier batch |
Resolve the customer relationship first; recover supplier costs through a separate evidence track.
Triage tickets with a resolution ladder
A macro should accelerate judgment, not replace it. Triage each ticket by order state, policy eligibility, evidence strength, customer harm, supplier recoverability, contribution margin, and dispute risk. Then choose the lowest-cost resolution that fully closes the issue.
Start with facts: what was bought, what the store promised, where the parcel is, what the customer reports, and what evidence exists. Do not begin with whether the customer sounds angry. A calm customer with an undelivered order has the same underlying claim as an angry one.
Use a ladder rather than random goodwill. Information resolves uncertainty. A carrier trace resolves missing movement. A replacement resolves a verified defect when the customer still wants the product. An exchange preserves the sale when fit or variant is wrong. Store credit works only when the customer freely accepts it and expects to buy again. A refund closes the obligation when the store cannot deliver what it sold.
- Classify the order state: Unfulfilled, in transit, delivered, returned, refunded, or disputed.
- Compare promise with evidence: Use the listing, policy version, tracking, messages, and product evidence from the time of purchase.
- Check policy and legal minimums: Commercial rules cannot remove mandatory customer rights in the market where you sold.
- Choose the complete resolution: Information, trace, repair, replacement, exchange, credit, partial refund, or full refund.
- State the next date: Every open case needs an owner, next action, and date when the customer will hear from you.
- Record the root cause: Tag product, supplier, carrier, listing, checkout, support, or customer-abuse causes for weekly review.
Handle shipping delays before they become WISMO spikes
Where-is-my-order tickets usually signal an information gap before they signal a lost parcel. Send the order confirmation immediately, explain processing separately from transit, provide tracking when it becomes meaningful, and trigger a proactive update when the shipment misses a milestone. A tracking number with no carrier acceptance should not be presented as proof that the order is moving.
For US orders, a public shipping promise matters. The FTC requires a reasonable basis for the shipment time advertised. If the seller cannot ship within that time, or within 30 days when no time was stated, the seller generally needs to provide a compliant delay option or a prompt refund. A passive order-status page may support notice, but the FTC guide warns that it may not be enough if the customer does not visit it in time.
Build exception views instead of waiting for complaints. Review unfulfilled orders near the supplier cutoff, labels with no carrier scan, shipments with no movement, parcels beyond the published range, and failed delivery attempts. Each view needs a default action and escalation owner.
| Signal | Customer update | Internal action |
|---|---|---|
| Supplier missed processing range | Explain delay and give cancellation choice where required | Escalate or stop fulfillment |
| Label created, no acceptance | Say the carrier has not confirmed possession | Ask supplier for handoff proof |
| No movement in transit | Give trace date and next update | Open trace after carrier threshold |
| Past published delivery range | Offer the applicable wait, reship, or refund path | Review supplier and lane performance |
| Marked delivered, customer cannot find | Run a delivery-location checklist | Collect full carrier proof and claim options |
Prevent chargebacks by building evidence during the order
A chargeback response cannot recreate records that were never retained. Preserve the product description, price, policy version, checkout acceptance, order confirmation, customer communications, supplier record, tracking, delivery proof, return tracking, and refund record as the order progresses.
Evidence must answer the dispute reason. A return policy does not prove that a parcel was delivered. A tracking page does not prove that an item matched its description. Stripe’s dispute evidence guidance recommends concise, relevant evidence and full delivery-address proof for merchandise non-receipt cases. Shopify also states that the issuing bank decides outcomes and that the platform is not liable for chargebacks.
Prevention is broader than fraud screening. Use a recognizable billing descriptor, realistic shipping ranges, clear subscription and cancellation terms, delivery confirmation on high-value orders, fast support, and prompt delay notices. Review Shopify’s risk indicators before fulfillment and investigate high-risk orders rather than treating the risk label as an automatic verdict.
The detailed Shopify chargeback guide includes an evidence matrix for fraud, product-not-received, not-as-described, cancellation, and credit-not-processed disputes.
- Calendar the response deadline as soon as an inquiry or chargeback arrives.
- Write a one-paragraph factual case summary tied to the reason code.
- Include legible, relevant documents and explain what each one proves.
- Do not overwhelm the reviewer with unrelated policies or emotional argument.
- After closure, tag the root cause even when the dispute was won.
Run a weekly post-purchase control loop
Support data should change the store. A rising damaged-item rate is a supplier or packaging problem. Repeated size exchanges point to product-page information. Delivery complaints concentrated in one country reveal a shipping-lane issue. Fraud disputes after a specific campaign can indicate targeting, offer, or checkout-risk problems.
Review rates by order cohort, product, supplier, carrier, destination, and acquisition source. A blended refund rate hides the one SKU or lane causing most loss. Use both frequency and cost. Ten low-cost size exchanges may matter less than one unrecoverable high-ticket chargeback, but the repeated size issue can be fixed faster.
| Metric | Diagnostic question | Likely owner |
|---|---|---|
| First response time | Can customers reach a human before escalating? | Support |
| WISMO contacts per 100 orders | Are tracking and delivery expectations working? | Operations |
| Return and refund rate | Which products, claims, and cohorts create the cost? | Merchandising |
| Reship rate | Is the supplier or carrier failing repeatedly? | Supplier management |
| Disputes by reason | What evidence or promise is missing? | Payments and operations |
| Resolution cost per order | Is the policy funded by contribution margin? | Finance |
Review causes by cohort. Store-wide averages are useful alarms but weak diagnoses.
Primary sources to verify before changing policy
Platform features and legal rules change. Before publishing a policy or responding to a dispute, check Shopify returns and exchanges, Shopify chargebacks, Shopify fraud prevention, the FTC shipment rule guide, EU distance-sale return rights, and Google Merchant return-policy guidance.
Key takeaways
- Make the product-page promise, Shopify settings, supplier process, support reply, and evidence record agree.
- Separate change-of-mind returns from defects, wrong items, non-delivery, and not-as-described claims.
- Give every unresolved ticket an owner, next action, and date for the next customer update.
- Choose refunds, replacements, exchanges, credit, or traces using fairness, evidence, economics, and legal minimums.
- Preserve evidence during the order. A chargeback response cannot reconstruct missing tracking, policies, or conversations.
- Use support causes to improve products, suppliers, pages, shipping lanes, and acquisition campaigns each week.
Common questions
Who is responsible for a dropshipping return, the store or the supplier?
The customer bought from the store, so the store owns the customer-facing resolution. The supplier agreement determines whether the merchant can recover product, shipping, refund, or replacement costs afterward.
Should a dropshipping store require every item to be returned?
No universal rule works. Compare return postage, item value, inspection and resale potential, abuse risk, supplier requirements, and mandatory consumer rights. A documented returnless refund can be more economical for low-value items, while higher-value products may need tracked recovery.
How quickly should a Shopify store answer customer-service tickets?
Publish a response expectation you can keep and aim to answer routine email tickets within one business day. Urgent cancellation, fraud, failed-delivery, and dispute deadlines need faster queues. Resolution quality matters as much as first-response speed.
What should I do when a dropshipping supplier misses the delivery estimate?
Compare the order with the promise shown at purchase, contact the supplier, give the customer a factual revised update, and offer the cancellation or refund options required by your policy and applicable law. Do not invent a delivery date or leave the customer to chase the supplier.
What records help defend a Shopify chargeback?
Retain the listing and policy shown at purchase, order and payment details, customer communications, tracking and full delivery evidence, return tracking, refund records, and any relevant authorization or fraud indicators. Submit only evidence that addresses the dispute reason.