Owner and Customer Mobile Apps for Petrol Pumps

How do the apps fit with POS and ERP?

iPOS Web POS is the point-of-sale product. iPOS Infinity is the ERP system. The owner app and customer app provide separate mobile experiences around the selected business workflows. Do not make the mobile screen responsible for explaining a transaction that the station's own operating process has not defined.

Start with a map of the forecourt, service office, customer account process and management review. Ask the team to show which proposed product or app handles each responsibility. The Infinity overview provides a starting point for the wider operations discussion, while the exact forecourt equipment and integration scope need their own acceptance evidence.

Include the people who actually close shifts and answer customer questions in that rehearsal. Ask each person to identify the original record, the current issue and the next authorised action. This reveals a practical handoff problem sooner than a demonstration focused only on a successful mobile login. Retain the accepted sequence for training so the owner, station supervisor and customer-service team can follow one consistent explanation when a similar question arises.

What should the owner be able to investigate?

Give the owner a representative question about a shift, location or settlement difference. Ask how the selected app supplies the relevant period and operating context, which supporting information it exposes and what the supervisor must investigate at the station. A total alone cannot explain an unusual result.

Use the shift reconciliation checklist to connect the mobile question with nozzle or recorded-sale evidence, settlement categories and authorised adjustments. The demonstration should show the review path included in the proposal rather than suggesting that every possible forecourt detail automatically appears on a phone.

What does the customer relationship require?

Describe the fuel-customer journey the business wants to support. An ordinary visitor, an established account customer and a fleet customer can have different needs. List the information and requests relevant to the selected app scope, then identify who reviews or acts on each request.

If the business needs account references, transaction history or a particular billing interaction, make those explicit demonstration requirements. The customer's mobile experience should remain distinguishable from authority to approve credit, change a station record or settle a disputed amount. The fleet-credit guide helps the business define those responsibilities without assuming a specialised fleet feature from the existence of a customer app.

How can one disputed transaction test the design?

Use an illustrative account-customer query about a fuel transaction assigned to the wrong reference. Ask what the customer can identify through the selected app, how staff find the accepted station record and who is authorised to approve a correction. Then review how the owner sees the unresolved issue or confirms its outcome through the proposed management process.

The exercise links convenience with accountability. It also exposes gaps between an app request and an accepted business action. Retain the original transaction evidence and the approved resolution, rather than treating a customer-facing message as proof that the underlying record has already changed.

Which responsibilities should be compared?

Agree these criteria with the station team and review the observed results against the selected apps and their approved operating scope.

How do reliability and security enter the discussion?

Review the devices, connections and update timing used by the mobile experience. Separately inspect the supported forecourt and counter environment. A hybrid architecture can offer a useful way to place selected operational work locally, but its recovery and information exchange must be demonstrated for the proposed design.

Use the hybrid recovery guide to test an interruption and a clear return to accepted records. Review access changes, shared devices and support responsibilities. Reliable service comes from the complete operating model, including the people who monitor exceptions and the evidence they use to resolve them.

What should a petrol-pump app demonstration include?

Bring one shift pack, one customer-account example and a question the owner regularly asks from outside the station. Include an exception and an access restriction. Have station operations and accounts review the result together before approving the proposal.

Scope note: Confirm the selected owner and customer app functions, forecourt compatibility and POS or ERP connections; iPOS Web POS requires internet. Arrange a petrol-pump workflow demonstration with iPOS around your actual shifts and customer relationships.