Order handling is where reselling either scales or stalls. A defined reseller order management workflow means any question about any order can be answered from a record rather than from memory.
One record per order
Every order needs a single row containing what was requested, for which target, when, at what price, and its current status. Spread across messages and mental notes, that information is effectively unavailable the moment volume rises.
Give every order a reference the customer can quote. Without one, each support conversation begins by establishing which order is being discussed, and that overhead grows directly with the number of customers.
The workflow
- Intake in a consistent format, whatever channel it arrives through.
- Validate the request against what is actually offered.
- Create the record and issue the reference immediately.
- Place the order through the supported route.
- Update status at defined points, not only when asked.
- Route exceptions to a named person with a documented path.
- Close the record with the outcome, including partial ones.
- Review the exception log monthly for patterns.
Recording partial and failed outcomes matters as much as successes. An operation that only records completions cannot see its own failure rate, and will keep offering whatever is quietly going wrong.
Exceptions need a path, not improvisation
Delays, partial delivery and cancellations are normal, and handling them differently each time produces inconsistent treatment between customers, which is what turns an operational issue into a reputational one.
Write down what happens in each case, who decides, and what the customer is told. Consistency here does more for trust than speed, because customers compare notes and notice when outcomes vary arbitrarily. The wider operation sits in the reseller workflow guide, and offer definition in service catalog planning.
Common questions
What should the record contain?
Request, target, date, price, reference, status history and outcome. That answers nearly every later question.
How often should status be updated?
At defined milestones. Updating continuously is unnecessary; updating only on request is where complaints come from.
Should customers see their own status?
Where possible. Self-service status removes a large share of routine contact.
How are disputes handled?
From the record. A dated history settles most disagreements immediately and without argument.
What should the exception log capture?
What happened, what was done, and what the customer was told. Patterns in that log usually point at a service worth reconsidering.
Should records be kept after completion?
Yes, for a reasonable period. Questions arrive weeks later, and a deleted record makes them impossible to answer. See contact.
Should orders be batched?
Batching placement can be efficient, but never batch the record-keeping. An order not written down when accepted is the one that goes missing.