Fulfilment: deliver what you promised, every time
The sale is a promise. Fulfilment is whether you keep it.
The pain this fixes
Orders arrive and everything becomes manual chaos. Customers ask where their thing is, refunds pile up, and you cannot tell what is actually happening.
What you leave with
A mapped order journey, an SOP for each format, a support policy and the numbers that expose problems early.
Map the journey from payment to result
Write every step between “paid” and “got the outcome”. For each step, name the owner, the tool, the time limit and what happens when it fails. This is your fulfilment system; it does not need to be software.
- Payment confirmed → order recorded.
- Customer receives confirmation and next step.
- Work starts or item is picked/packed.
- Quality check before delivery.
- Delivery or access granted.
- Follow-up, support window and review request.
Digital products: access is the product
A digital buyer judges you on whether the file opens, the link works and the instructions are clear. Test the entire delivery on a phone and a desktop before selling.
- Instant download or account access with a backup link.
- License: what the buyer may and may not do with the file.
- Version updates and how buyers get them.
- Refund policy for digital goods, clearly stated before purchase.
- Email deliverability: use a real sending domain, not a free inbox.
Physical products and dropshipping: promises have transit times
Physical fulfilment is a logistics promise. Stockouts, customs, damaged items and late suppliers become your customer’s problem unless you plan for them. With dropshipping, you are still responsible for the promise even though someone else ships.
- Vet suppliers with a sample order and a timed test.
- Confirm stock, processing time, shipping zones and tracking.
- State realistic delivery windows, not the supplier’s best-case claim.
- Have a returns address and a damaged-item process.
- Never sell regulated, unsafe or IP-infringing products.
Services: boundaries are fulfilment
A service fails when scope, communication or capacity is unclear. A written scope, a kickoff checklist and a weekly update prevent most disputes.
- Kickoff: confirm outcome, access, decision-maker and deadline.
- Weekly update: done, next, blocked, decisions needed.
- Change control: new request = new scope and price.
- Capacity: how many clients can you serve without quality dropping?
- Handover: documentation the buyer can keep.
Use these words
Delay notification
Hi [name], your [order] is delayed by [reason]. The new delivery date is [date]. I’m sorry — you shouldn’t have to chase this. You can wait for the new date, or reply “refund” and I’ll return the payment. Either way, I’ll confirm when it ships/access is restored.
Refund decision
Thanks for telling me what went wrong. Based on [policy], this qualifies for [refund/replacement]. I’ve processed [action] and you’ll see it within [time]. If you’d rather try a fix first, I can [specific remedy] — but the refund is available either way.
Checklist
- Order journey mapped with owners and time limits.
- One SOP per format you sell.
- Support window and response time published.
- Returns/refund process tested.
- Capacity limit known before taking more orders.
Mistakes that cost money
- Selling more than you can deliver.
- Using a supplier’s shipping estimate without testing it.
- No returns address for physical goods.
- Letting scope grow without a change order.
- Hiding delays instead of communicating early.
Numbers to watch
On-time delivery
orders delivered within promise ÷ total orders
Defect/return rate
returns or complaints ÷ orders
Support time
minutes per order; automate the repeat questions
Refund rate
refunded orders ÷ paid orders
Your deliverable
A fulfilment map, one SOP, a support policy and a capacity limit.
Next stage
Traffic: earn attention without burning money