Web POS vs native device capabilities

Overview

• Web POS and MiniTill POS mobile use the same orders and payments, while Web KDS and Mobile KDS show the same kitchen orders.
• Web POS is useful for simple setups on an existing laptop/desktop where local printer/CDS/device integration is not required.
• Native POS is the hardware-focused client for local printer communication, CDS discovery/pairing, persistent device capabilities, and supported integrated terminal behaviour.
• Mobile KDS adds pairing, sound, screen-awake behaviour, and reconnect support for a dedicated kitchen device.
• Using the Web client is not a degraded data model; it simply has fewer device-local capabilities.

When to use this

• Start with Web POS/KDS for the simplest setup; choose native apps when the Store needs persistent dedicated devices or local hardware integration.

Step-by-step

1. List the Store's actual hardware requirements.
2. If orders/payment records only are needed, Web POS may be sufficient.
3. If CDS/local printer/integrated terminal capability is required, use native POS.
4. If kitchen sound/wake/recovery matters, use Mobile KDS.
5. Test the intended device path before buying/deploying additional hardware.

Common mistakes

• Do not tell a merchant they must buy tablets just to use MiniTill POS/KDS.
• Do not promise local CDS/printer discovery from Web POS.
• Do not create separate business/order data for Web and Native clients; they use the same server source of truth.

Troubleshooting

• If a hardware button/feature is missing only on Web POS, check whether it is intentionally native-only.
• If Web and Mobile show different order information, confirm the same Store is selected and refresh both screens.