Requirements checklist
What to ask for when choosing software for laundry delivery services.
A checklist built from how laundry delivery services work, to print or save as a PDF and bring to any supplier meeting.
What the software should cover
Tick each one that matters to your business.
- Pickup booking and slots
- Rider rounds and handover codes
- Bag tagging and item count
- Partner laundry batches
- Plans, wallet and invoices
- Complaints and re-do tickets
Roles that need their own access
Who logs in, and what each person may see or change.
- For owners
- For dispatchers
- For riders
- For the tagging desk and plant coordinator
- For support agents
Reports to ask for
Ask to see each one with your own sample data.
- Pickups and drops by slot, rider and round
- Door counts against hub counts, by order
- Partner batches out, returned and short
- Plan usage, overage and renewals by subscriber
- Complaints by type, stage and rider
- Wallet balances and unpaid orders, oldest first
Systems it may need to connect to
Note which ones you already run.
- SMS
- Card and payment gateway
- Maps
- Accounting export
Questions for any vendor
Put these to every supplier you are comparing.
- Can a customer book without calling?
- How does a rider confirm the bag was collected?
- Can some orders go to a partner while others stay in-house?
- What happens when a returning batch is short?
- Can I run monthly plans with limits?
- Are riders tracked live on a map?
- Can customers pay by wallet or card?
- What does the subscriber import involve?
- Do we get a price list for this?
Where the work usually breaks today
Circle the ones you recognise. They set the order of the project.
- Counts at the door and the hub disagree
- Slots promise more than riders can carry
- Partner laundries return incomplete batches
- Subscription limits live in a spreadsheet
- Complaints have no home
Prefer to talk it through? See the laundry delivery services page.
