1. Choose one journey, not your whole business
Pick a journey you expect to handle regularly, such as a customer placing a collection order and collecting it at the counter. Define the starting point and the finishing point. For this journey, that might mean receiving the order through to handing it to the correct customer and making the records available for an end-of-day review.
Keep the first version narrow. Adding bookings, delivery and walk-in sales at the same time creates more handovers to investigate. Write down the information needed at each stage: an order reference, requested collection time, items, payment status and fulfilment status. Collect only the customer details needed to complete the service.
- Write the journey in one sentence from the customer's perspective.
- List each stage in the order it happens.
- Mark where a person or a different tool takes over.
2. Confirm what each tool will actually do
Choose tools against those stages rather than starting with a long product list. NeroPay offers card terminals and payment services, NeroPOS/ePOS software, NeroWeb online ordering and websites, NeroBooking booking software, and QR payment options. NeroWeb supports direct online ordering. These facts do not mean every product automatically shares every record.
Ask the team to confirm availability, supported devices and the specific integrations your proposed journey needs. Until a connection is confirmed, describe a manual handover instead. For example, a staff member might review an incoming order and enter the required details into a separate working list. That takes staff time, but it makes responsibility visible.
Check commercial terms before committing. With an eligible NeroPay card terminal, NeroPOS, NeroWeb and NeroBooking software can be included without an additional software subscription charge. Terminal costs, payment processing charges, eligibility and applicable terms still apply. For online ordering, payment processing and applicable delivery costs remain.
- Ask which information transfers, in which direction and at what point.
- Confirm how staff recognise a failed or delayed handover.
- Record the manual alternative for any unconfirmed connection.
3. Give every handover an owner and a clear record
A handover needs more than a destination. Name the person responsible for noticing new work, checking it and passing it on. In a small business, one person may cover several stages, but the responsibilities should still be separate. Assign a backup for breaks and busy periods.
Decide which record staff should consult for each question. The order record may describe what the customer requested, while the relevant payment record establishes the payment outcome. Do not treat an order arriving as proof that payment succeeded. Use a consistent reference in permitted records so staff can match the activity without copying unnecessary customer information.
- For each stage, write: owner, information needed and next action.
- Define when an item is ready to move forward.
- Choose where unresolved issues are recorded and who reviews them.
4. Rehearse the journey with a realistic example
Hypothetical example: a new café plans to accept collection orders through NeroWeb. The owner has not yet confirmed a connection to the café's other tools. For the rehearsal, the shift lead reviews the order, checks its payment status using the relevant payment record and adds the preparation details to a manual working list. The counter assistant uses the agreed reference when handing over the order.
First agree an appropriate testing method with the team; do not assume a test mode is available. Then rehearse both a straightforward order and an exception, such as an order whose payment outcome is unclear. Staff should know to investigate rather than mark it as paid or ask the customer to pay again without checking.
- Follow one order from receipt through preparation and collection.
- Check that the reference, items and collection time remain consistent.
- Practise pausing an unclear order and escalating it to the named owner.
- Confirm that no unresolved or duplicate task remains at the end.
5. Use a visible pass check before opening the workflow
Your success check should be observable: a team member who did not design the process can find the order, identify the payment outcome, explain its current stage and complete the next action using the written instructions. The finished journey should leave records that the owner can follow without reconstructing events from memory.
If that check fails, fix the unclear handover before widening the launch. Keep the first live scope manageable and review it after the first trading session. Ask staff where they repeated work, waited for information or needed the owner to interpret something. Change the instructions or confirm a technical requirement rather than relying on staff to remember a workaround.
- Keep a short issue list with an owner for each correction.
- Repeat any failed check after making a change.
- Expand to another journey only when the first is understandable and repeatable.
GOOD TO KNOW
Common questions
Do all my tools need to be integrated before launch?
No. A documented manual handover can work for a limited launch if someone owns it and checks it reliably. Confirm supported integrations before planning around automatic transfers.
What should I ask about a proposed connection?
Ask which records and fields move, whether updates travel both ways, how delays appear and who handles failures. Confirm support for your particular products and devices with the team.
Should I test a payment problem as well as a successful order?
Yes. Agree a suitable testing method first, then rehearse an unclear payment outcome. Staff should know where to check and who can resolve it before requesting another payment.