Different services needed more than different names
Merchant delivery starts at a known collection point, while errands may involve purchasing or service confirmation. One undifferentiated order could not describe both clearly.
Turn the service promise into operating rules
We defined the initial service scope, pricing, acceptance, cancellation and completion criteria, sharing identity and task structures while keeping service differences explicit.
Build a traceable route from request to completion
Customer entry, merchant access, dispatch and rider tasks retain pricing evidence, collection details and completion records. Exceptions needing agreement remain visible to support.
Make the new service operable
The team can configure coverage, assign tasks and follow fulfilment. Rule documentation and permissions help add further service types while preserving a clear customer experience.