Improve the reason record
Use a manageable set of reason categories and allow uncertainty when the explanation is unknown. Do not turn a courier note into a complete customer diagnosis without context. Compare the recorded reason with confirmation details and the advertised promise.
Separate refusal at delivery from a return after use if the business handles both. They involve different customer experiences and cost implications.
Investigate patterns
- Select mature dispatched cohorts.
- Compare meaningful product, region and acquisition segments.
- Review a sample of records and customer questions.
- Identify the strongest supported cause.
- Repair the promise, workflow or fulfillment issue that matches it.
- Evaluate contribution and delivery quality after the change.
Do not assume that a cheaper order-form lead is responsible for every delivery problem. Operations and expectations can also drive losses.
Reason-to-action table
| Evidence | Possible repair |
|---|---|
| Unexpected total cost | Clarify price and delivery conditions earlier. |
| Wrong variant or item | Improve order validation and fulfillment checks. |
| Unreachable customer | Review accurate contact and appropriate follow-up. |
| Delivery expectation mismatch | Align the promise with actual service conditions. |
Worked example: a marketing promise problem
Illustrative example: refusals repeatedly mention a size expectation different from the actual product. The ad image and product page do not show dimensions clearly. A targeted repair adds accurate scale and specifications rather than merely changing the audience.
If refusals decline, inspect whether contribution and suitable purchase volume also improve. The aim is informed demand, not a narrower report that hides unsuccessful orders.
Keep attribution modest
A before-and-after improvement can reflect inventory, seasonality or courier changes as well as the repair. Record those conditions and avoid declaring a clean causal lift from an uncontrolled comparison.
Should high-refusal regions always be excluded?
Investigate the cause first. A service or information problem may be repairable. A region decision should reflect reliable economics and operational capability.
What if reasons are incomplete?
Improve the record and sample relevant conversations. Label the remaining uncertainty rather than assigning every unknown to customer quality.
Put this into practice
Take the largest failure category and trace it back through ad, confirmation and delivery. Choose the repair that addresses the documented expectation or operational gap.
Related foundation: Meta Ads for e-commerce in Morocco: measure delivered orders. How these guides are prepared.
Related portfolio work: Etsy & Shopify. The worked examples in this guide are illustrative and are separate from the portfolio’s project evidence.
