Dropshipping Returns: Build a Workflow Before the First Request

A dropshipping return involves two relationships: the sale you made to the customer and the order you placed with the supplier. A supplier declining your claim does not make the customer’s request disappear.

Build a process that tracks those relationships separately. Your team needs to know what was promised, what happened to the item, what response is due, and whether any cost can be recovered. A copied refund policy is not an operating process.

This guide covers workflow design. It does not set a universal return deadline or replace the consumer rules that apply to your store and customers.

Start with the reason for the request

“Return” can mean several different problems. Ask enough to route the case without making the customer repeat the whole story.

What the customer reports	First fact to establish	Operational question
Wrong item or variant	What was ordered versus received	Was the error in the listing, mapping, or packing?
Damage or defect	Item condition and relevant evidence	Is a replacement suitable, and what does the supplier require?
Poor fit or change of mind	The request and applicable terms	Where can an authorized return go?
Parcel not received	Tracking and the delivery promise	Is this a shipment investigation rather than a physical return?

Do not force every case through the same form. A missing parcel cannot provide a photograph of a damaged product.

Your first reply should acknowledge the specific issue and explain the next step. Avoid promising supplier approval before you have it.

Keep the customer action and supplier claim separate

Zendrop describes two processes: the merchant handles the customer refund through the store, while Zendrop evaluates reimbursement to the merchant under its own terms. Zendrop refund responsibilities.

That distinction is a useful model for your case log even if you use another supplier. Keep separate fields for customer resolution and supplier recovery. “Refunded” is ambiguous if nobody knows which payment it refers to.

For an invented example, a customer receives the wrong $38 item. You resolve the sale, then submit a supplier claim for the product and delivery costs. Mark the customer action complete once it is actually processed, while leaving the supplier claim open until its outcome is known. Do not count an expected reimbursement as money already recovered.

The store metrics guide explains why unresolved costs should stay visible.

Verify the return destination

An address on a parcel label may not be an authorized return location. Confirm the destination before sending it to a customer.

Zendrop’s policy says it does not accept physical returns and that merchants handle the customer-facing process. Its separate apparel guidance notes that some US-sourced items may require a return. These documents are not a single universal routing rule: confirm the case-specific instruction before providing an address. Zendrop return policy, wrong-size guidance.

Record the approved address, contact, reference number, permitted carrier if specified, and who pays the postage. If the recipient has not agreed to receive the item, the return is not ready to send.

For a small store, arranging a valid return destination can be more valuable than buying an automated portal. A polished portal that sends goods to the wrong place makes the problem harder.

Collect evidence without creating needless friction

Ask for evidence that helps resolve the specific issue and is reasonably available. For a wrong variant, the order selection and item label may matter. For damage, the packaging and affected part may be useful. Follow the supplier’s current requirements without treating them as permission to ignore your own customer obligations.

Store the evidence with the case rather than scattering it across personal messages. Restrict access to staff who need it, and avoid duplicating full customer addresses in shared spreadsheets when an order reference will do.

A useful case record includes:

• Store order and supplier order references.
• Request date, reason, and owner.
• Relevant promise or policy version.
• Evidence received and any missing detail.
• Customer action, amount, and completion reference.
• Supplier claim status and recovered amount.
• Next follow-up date and final root cause.

If return details are spread across an inbox and several spreadsheets, CapitalOS is a useful option for bringing that work together. Its Returns module connects reasons, statuses, and refund information with SKUs, orders, and support tickets where those identifiers are available. That makes it a good fit for reviewing recurring product issues while keeping the related customer conversation within reach. You still need to match records correctly and confirm supplier reimbursement separately. See the Returns documentation.

Decide whether the item should come back

A physical return is not always the most useful resolution. Consider the applicable obligations, product condition, supplier instructions, postage, handling work, and whether the item can be used or resold safely.

Use a hypothetical low-value item to test your process. If postage and inspection exceed any recoverable value, a permitted refund without return may cost less. That is a case decision, not a blanket policy to copy onto every product.

Confirm the agreed resolution before instructing customers to dispose of goods; an unresolved evidence or return decision may still require the item.

Review the causes each week

Separate wrong-size ordering from wrong-size fulfillment. If customers choose a size based on an inaccurate chart, the fix is on the product page. If the correct selection repeatedly arrives wrong, inspect mapping and packing.

Track recurring issues by product, variant, and supplier route. A return app can help organize cases, but it will not correct a misleading description or a supplier’s packing error.

Before adding more products, run one paper exercise from customer request to financial close. If your team cannot name the return destination, decision owner, and place where recovery is recorded, finish those steps first.

Sources checked September 10, 2026. Examples are hypothetical. Check applicable consumer requirements separately; supplier reimbursement terms do not determine every obligation to a customer.