Choosing self-ordering for a petrol-station store

Start with the order, not the screen

Picture the busiest fifteen minutes in the store. A customer wants a sandwich and coffee. Someone else is paying for fuel. A colleague is making food while another is dealing with a delivery. Where would a separate ordering point help, and where would it just create another queue?

A kiosk handles part of the journey. The business case depends on the whole journey: choosing, paying, preparing and collecting. Walk it through on your own shop floor before choosing hardware.

Write down what each store needs

• Map the food-to-go menu, modifiers, meal deals and payment methods. Include items that sell out during a shift.
• Check floor space, power, network access, customer reach and sightlines. The screen should be easy to find without blocking the shop.
• Decide where orders arrive and where customers collect them. Keep food ordering and fuel-payment requirements separate in the specification.
• Record who owns pricing, product images and changes to the menu. A chain needs a clear process for local exceptions.

Try a small, awkward order in the demo: a substitution, an unavailable item, a declined payment and a refund. A polished happy-path demo tells you less than those four tests.

Ask for a complete cost

Request hardware, software, installation, payment, support and replacement costs in the same proposal. Include any work needed on your POS. Ask what happens when you add another store or replace a damaged terminal.

Compare proposals over the same period and with the same assumptions. Our ROI calculator separates sales contribution from cash savings and running costs.

Give head office a practical test

Tapit supports browser-based management, role-based access, reporting and kiosk health monitoring. Test these with the people who will use them. Have a store manager change an item and a head-office colleague review access permissions. Ask the implementation team to demonstrate how changes reach the locations in your proposal.

Use a written acceptance checklist. It is easier to resolve a missing requirement before installation than during the first busy shift.

Choose a pilot you can learn from

Select stores that reflect the operating conditions you intend to serve. Agree on a baseline, a comparison method and a decision date. A single unusually busy or unusually quiet site can give a misleading picture.

Measure order completion, average basket, contribution after promotions, preparation time, refunds and support incidents. Include what staff say. They usually see the awkward bits first.