loading


Product

App-Only Vending Without a Selection Screen: Plan Arrival, Ordering and Recovery

Design the physical machine and mobile journey together when customers choose and pay entirely on their phones.

WEIMI INSIGHTS   /   MOBILE COMMERCE • MACHINE WORKFLOW

Removing the selection screen moves several customer tasks onto the phone. The cabinet still needs to identify itself, explain collection and support a failed mobile journey.

Design the physical machine and mobile journey together when customers choose and pay entirely on their phones.

ARRIVE

Make the correct physical machine easy to identify.

ORDER

Route the approved purchase to that machine and product.

RECOVER

Give customers a clear response to an uncertain outcome.

THE DECISION IN ONE LINE

An app interface does not replace the need for a defined machine-side workflow. Confirm the supported controller integration and test the complete purchase at the real cabinet.

01   /   BUYER NOTES

1. Make machine identity clear at the site

Decide how a customer selects the physical machine in the app. A displayed code or identifier may be part of the process, but its destination and mapping must be controlled. Customers should not accidentally order from a nearby or similarly named cabinet.

Put understandable identification and support information on the machine. Without a selection screen, the customer needs another way to confirm where they are and what to do next. Keep the information accurate when the cabinet moves or the operator changes.

Ask how the app handles a stale or incorrect machine reference. The system should not continue as though the customer is at the right location when the available information does not support that assumption. Define the recovery path before launch.

02   /   BUYER NOTES

2. Keep app availability aligned with the cabinet

Ask how the app receives product and stock information for the selected unit. A catalogue can display an attractive product while the physical position is empty or unavailable. Confirm the available interface and the rules for delayed or uncertain stock status.

Define what happens between selection and payment if availability changes. The app, payment service and controller need an agreed order flow. Do not assume that a general inventory API automatically reserves a product or prevents two customers from requesting the same last unit.

Keep product identifiers and machine positions controlled during refills. A correct mobile order can still deliver the wrong product if the physical mapping is wrong. Include the app catalogue in the normal stock-change and commissioning process.

03   /   BUYER NOTES

3. Route payment and dispensing through a confirmed state flow

Document the sequence from order creation through payment and the authorised machine command. Ask which party owns each decision and which statuses are available. A payment confirmation should not be treated as evidence that the item has already reached the customer.

Test retries and interrupted communication. If the phone loses connection after payment, the app needs a supported way to retrieve the result. Repeating a command without understanding its status can create a second issue, so agree duplicate handling with the integration teams.

Confirm what the machine reports about delivery and collection. Use accurate wording in the app based on the available signals. Where the outcome is uncertain, direct the customer to the defined support process rather than displaying an unsupported success message.

04   /   BUYER NOTES

4. Design collection without relying on a large screen

Make the pickup point visible on the cabinet and consistent with the app instructions. If several modules share one app interface, tell the customer which opening belongs to the order. Test the experience with someone who has not seen the design before.

Review what information remains available if the customer’s phone stops working. A flat battery or lost connection can occur after payment. The physical machine should still provide a practical support route and identifier so the customer is not left without a way to explain the situation.

Assess the intended users and venue before removing all local interaction. Some customers may be unable or unwilling to install an app or use mobile data. Decide whether the business needs an alternative purchase route and ask the supplier which configurations can support it.

05   /   BUYER NOTES

5. Commission the app and cabinet as one service

Use an agreed test environment for development, then complete the appropriate commissioning of the approved production arrangement. Include correct orders, unavailable stock, interrupted communication and a controlled dispensing failure. Compare app records with the machine’s actual outcome information.

Define support ownership across the app team, payment provider and equipment supplier. A customer sees one purchase even when three organisations provide the technology. Give the first support contact a clear escalation map and the references needed to investigate.

Send WEIMI your app workflow and intended screenless configuration. Request confirmation of supported interfaces, machine-side controls and recovery behaviour. Approve the complete customer journey rather than treating removal of a screen as a simple hardware cost reduction.

Three places the customer needs clear information

Before ordering

App: Correct machine and available products.

Cabinet: Matching identity and instructions.

During the purchase

App: Accurate payment and order status.

Cabinet: Supported physical progress or collection cues.

After a problem

App: Order reference and recovery guidance.

Cabinet: Visible support details if the phone flow is unavailable.

PRACTICAL ANSWERS

Questions about app-only vending

Can I remove the touchscreen if my app handles purchases?

Only within a supported configuration. Confirm which controls, services and customer information are still required at the machine.

Does an inventory API guarantee an item is reserved?

No. Reservation and concurrent-order behaviour need explicit interface support and an agreed workflow.

What happens if a phone disconnects after payment?

Use the defined status-recovery process. The app should retrieve the outcome without blindly repeating the dispense command.

YOUR NEXT STEP

Design the phone and cabinet journey together

Share your app order flow and machine-side requirements with WEIMI. Request an integration review that includes arrival, payment, collection and recovery.

Explore equipment →Discuss your requirements →

prev
Vending Management Software Demo: Test Tasks, Permissions and Real Data Boundaries
MDB vs DEX vs API: Which Interface Does Your Vending Project Need?
next
recommended for you
Get in touch with us
Customer service
detect