# Customer-Facing Displays for a Custom POS App

> Published: 2026-11-22
> Updated: 2026-11-22
> Author: Mathias Nielsen
> Canonical: https://finalpos.com/blog/customer-facing-display-pos

Swiveling a single tablet back and forth slows down your line and breaks cables. Learn how customer-facing displays actually sync cart state, handle tipping handoffs, and connect to a custom POS app.

Flipping a tablet around on a swivel stand is the fastest way to ruin a busy counter. A cashier rings up a latte and a croissant, spins the iPad toward the guest, and waits. Half the time the screen rotates upside down, the guest accidentally taps the back button into the main menu, or the USB cable connected to the card reader yanks out of the port. When you build a custom checkout app, a dedicated customer facing display POS setup fixes this physical bottleneck—if you understand how dual-screen hardware and state synchronization actually work at the counter.

Most teams building a browser checkout flow treat the customer view as an afterthought. You design a sharp cashier screen, test it on your laptop, and assume you can just open a second browser tab on an external monitor for the buyer.

Then you deploy to a store and hit the hardware wall. Operating systems restrict how single apps draw to secondary screens, and network drops leave your customer display stuck on the previous buyer's order. Connecting [POS hardware for custom apps](/blog/pos-hardware-for-custom-apps) requires specific architecture choices before you write a line of checkout UI.

## What customers expect to see on a second screen

A customer display app has one job during item entry: prove to the buyer that the cashier is ringing up the right items at the right prices. Buyers don't want to see SKU codes, inventory counts, or margin data. They want a clean, high-contrast list of line items, modifiers, and discounts updating within 100 milliseconds of a barcode scan.

As the transaction moves forward, the screen shifts from passive verification to active input:

* **Idle state:** A branded attract screen or promotional image when no cart is active.
* **Active cart:** Line items, explicit modifier pricing (like "+$0.75 Oat Milk"), subtotal, calculated tax, and a clear running total.
* **Interactive prompts:** Tip buttons, loyalty phone number entry, or email receipt capture.
* **Payment status:** Visual cues showing when to tap a card, when the transaction is authorizing, and when it's approved.
* **Post-sale reset:** An automatic timer (usually 3 to 5 seconds) that clears the screen back to idle so the next person in line doesn't stare at the previous buyer's receipt.

## Second screen on the same device vs. a separate tablet

**TL;DR:** Hardware with an attached secondary display uses direct USB or HDMI video output for zero-latency updates, while two separate tablets rely on local network or WebSocket messages that require connection management.

![Integrated dual-screen POS hardware showing the single-unit hinge connection for a secondary customer display](https://storage.googleapis.com/final-os-media/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/344e6cba7c1f6cc5-customer-facing-display-pos-section-2-en-us.png)
*Purpose-built registers with attached customer displays share local memory and power, avoiding wireless pairing drops.*


A POS dual screen setup takes one of two physical shapes: purpose-built register hardware where two screens share a single motherboard, or two independent devices (like two iPads) paired over a network.

### Attached displays on a single device

Commercial Android registers often attach a 10.1-inch customer display directly to the back of the main terminal via a proprietary USB or Pogo-pin connector. To the operating system, this is just an external monitor.

Writing a native Android app lets you use the `Presentation` API via `DisplayManager` to render a distinct view hierarchy onto that secondary display. Your cashier UI and customer UI share the exact same memory space and local state. When a cashier taps a product, the customer screen updates on the very next frame. Zero network latency, no IP address pairing, and only one power cord to plug into the wall.

Try running a browser-based web app on this same dual-screen hardware and you'll hit immediate friction. Standard web browsers don't automatically span two distinct layouts across two monitors without manual window dragging and kiosk-mode flags. Even with the Window Management API in Chromium browsers, keeping a full-screen window pinned to a secondary display across device reboots is fragile compared to a native app.

### Two separate devices over a network

The alternative is mounting an iPad or Android tablet facing the cashier and a second, cheaper tablet facing the customer. Because each tablet runs its own OS and app instance, they can't share local memory.

You have to build a pairing mechanism to make this work. The customer tablet runs in a locked listener mode while the cashier tablet broadcasts cart events. That gives you placement flexibility—you can mount the customer screen three feet away by the card reader. You pay for that flexibility in hardware maintenance: two batteries to charge, two OS update schedules to manage, and a wireless connection between them that can drop during the Friday lunch rush.

## How does a customer display stay in sync in real time?

When your two screens run on separate devices, you have to choose how they talk to each other. The simplest route for a web builder is routing every cart change through a cloud backend using WebSockets. The cashier taps an item after a [barcode scanner in your POS app](/blog/barcode-scanner-pos-app) reads a label, the tablet sends a payload to your cloud server, and the server pushes the updated cart down to the customer display.

Cloud sync works until the restaurant's internet hiccups. If the ISP drops packets for four seconds while a customer is tapping a tip button, the cashier has no idea if the tip registered. Even on a healthy connection, a 300-millisecond round trip to a cloud server feels sluggish when a cashier is rapid-firing five items onto a bill.

A production-grade second screen POS uses local peer-to-peer communication first, with cloud sync as a fallback. On iOS, native apps use Apple's Multipeer Connectivity framework. On Android or cross-platform setups, you run a local WebSocket server on the primary register and discover it via mDNS (Bonjour/Zeroconf) on the local LAN. That keeps latency under 20 milliseconds and lets the counter keep ringing sales when the external internet goes down.

Regardless of the transport layer, always send an idempotent full-cart snapshot rather than incremental "add item" deltas. If a customer display briefly disconnects and misses an "add item" message, deltas leave the customer total permanently out of sync with the cashier's screen. Sending the complete cart state object on every change guarantees the screen displays the exact truth the moment it reconnects.

## Handling tipping, payment, and receipt prompts

The hardest part of building a customer-facing display is managing the state handoff during checkout. During item entry, the cashier owns the state. The moment the cashier taps "Pay," control must lock on the cashier side and transfer to the customer screen.

![Customer tapping a smartphone directly on a customer-facing POS display with built-in NFC Tap on Glass](https://storage.googleapis.com/final-os-media/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/b9a414d3f4af4d40-customer-facing-display-pos-section-4-en-us.png)
*During checkout, state control locks on the cashier side while the customer display handles tip selection and NFC Tap on Glass.*


Your app needs a strict state machine for this handoff:

1. **Lock cashier cart:** Stop the cashier from adding items while the customer chooses a tip, but keep a prominent "Cancel / Return to Cart" override button on the cashier screen in case the buyer grabs a pack of gum at the last second.
2. **Present tip options:** Show preset percentages (calculated dynamically against pre-tax or post-tax rules depending on local norms), a custom dollar button, and a clear "No tip" option.
3. **Trigger payment hardware:** Once the tip is selected, update the final payment amount and wake the NFC reader. If your customer display has built-in NFC Tap on Glass, the screen itself shows the contactless wave symbol where the buyer taps their card or phone.
4. **Capture digital receipts:** After authorization, prompt for an email or phone number, then fire the reset timer immediately.

If you also route orders to the back of the house, kitchen tickets fire at this exact moment. Managing screen states across the counter and the kitchen shares a lot of architectural DNA, which we cover in our guide on [whether you should build a kitchen display system](/blog/build-kitchen-display-system).

## Accessibility, privacy, and counter ergonomics

A screen that looks great at eye level on your desktop monitor often fails when mounted at a 45-degree angle under harsh retail fluorescent lights. Customer displays need minimum 18-point typography for line items and 32-point or larger for the total. Use high-contrast dark text on a light background or crisp white on dark slate (#0F172A) so buyers with low vision can read the total from three feet away.

![Ergonomically angled customer-facing POS display mounted on a low accessible retail counter with bottom-aligned touch targets](https://storage.googleapis.com/final-os-media/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/ea1c879cbcba181f-customer-facing-display-pos-section-5-en-us.png)
*Mounting the customer screen at a 45-degree angle and keeping touch targets in the bottom half of the viewport ensures accessibility for all buyers.*


Physical height matters just as much. Tipping buttons placed at the very top edge of a high-mounted screen are unreachable for customers in wheelchairs. Keep interactive touch targets in the bottom half of the viewport, and make every button at least 48 by 48 pixels so hurried buyers don't mis-tap a 25% tip when aiming for 15%.

Watch buyer privacy at the counter, too. Never auto-populate a customer's home address, full phone number, or past purchase history on the customer-facing screen when the cashier attaches their profile to the order. Someone standing six inches behind them in a coffee shop queue can read that screen. Display only their first name or masked loyalty points (like "Sarah M. : 450 pts") and keep sensitive CRM details strictly on the cashier's view.

## Native customer displays in Final POS

Building dual-screen window management, local mDNS discovery, and payment state handoffs from scratch takes weeks away from designing your actual store workflow. We built Final POS so your custom checkout gets native dual-screen support without low-level device code.

Final is the world's most customizable POS, and Flow Studio is how you customize it. Most merchants start from a ready-made flow in the Flow Library and adjust it, or describe their workflow in Flow Studio so it generates the flow from their prompt. Every flow runs on real commerce rails, so hardware support for customer displays is already wired in.

When you run your flow inside the Final Station app (see our breakdown of [Native Station vs. Virtual and Hosted Stations](https://finalpos.com/help/native-vs-virtual-station) for how counter setups work), your checkout pairs automatically with our counter hardware. Our Final Register pairs with the Final Register CFD, a 10.1-inch HD customer display that connects via USB, supports plug-and-play setup, and includes built-in NFC Tap on Glass. At checkout, Final Pay customers [pick a preset, enter a custom tip, or choose No tip](https://finalpos.com/help/how-tipping-works-on-final) right on that customer-facing display, then tap their card directly on the glass.

You don't pay monthly software fees for multi-screen support. Final Station and Manage are included at $0 per month, with 1,000 free build credits per day (up to 5,000 a month) to customize your screens. With Final Pay, cash is always $0, and in-person card processing is a flat 1.99% + $0.10 CAD in Canada, 0.99% + €0.10 in Europe, and 2.49% + $0.10 in the US and worldwide.

Skip debugging WebSocket drops between two tablets or fighting browser window APIs. Open Flow Studio, customize your customer checkout prompts, and deploy your flow to a Station in minutes.

## FAQ

**Q: Do I need a customer-facing display?**
A: Most jurisdictions don't legally require a customer-facing display for standard retail or hospitality checkouts, unless you sell items by weight on an integrated scale. That said, adding a second screen cuts down on pricing disputes before payment and lifts tip averages because buyers aren't being watched by a cashier holding a swiveled tablet.

**Q: How does a customer display stay in sync?**
A: On all-in-one dual-screen hardware, the secondary display connects directly via USB or internal video cabling and shares the main app's local memory for instant updates. With two separate tablets, the POS pushes complete cart state snapshots over a local network connection or cloud WebSocket channel, so the display recovers immediately if Wi-Fi drops.

**Q: Can an iPad act as a customer display?**
A: Yes. An iPad works as a customer-facing display by running a dedicated listener view paired with your main register over the local network, or by connecting to an external USB-C monitor. In Final POS, you can deploy custom flows to any iOS, Android, macOS, or Windows screen, or plug in the 10.1-inch Final Register CFD with built-in NFC Tap on Glass.