ResourcesSolutions
Why UsFAQGet Started →

Customer-Facing POS Display for Retail Checkout

A customer-facing POS display is a second screen at a staffed checkout. It lets the shopper review items, quantities, prices and the total while the cashier controls the sale. In a T7 ERP demo, check what appears after a correction, what stays private and how the screen clears for the next shopper.

Product information updated 19 November 2026.

What is a customer-facing display at a checkout counter?

A customer-facing display is a view of the active basket for the person buying it. It is different from mirroring the cashier’s entire desktop: the shopper needs the bill lines and the amount due, not stock cost, staff controls or another customer’s account details. It is also different from a self-checkout kiosk, where the shopper scans or selects items. The useful test is not whether a second screen turns on. It is whether the shopper can spot an extra scan, see a corrected price and tell when the sale has actually finished. An item list, a payment prompt and a final confirmation serve different purposes. Test each state separately, and ask which optional fields can be enabled or masked during your intended rollout.

What should the shopper see, and what stays with the cashier?

Use this as a display policy for the demo. The supported layout and controls must be confirmed for your setup.

Checkout momentShopper view to testCashier responsibility
ScanningItem name, quantity, line amount and running totalResolve a wrong item or duplicate scan, then verify the corrected basket
AdjustmentUpdated line or total after an approved discount or removalApply the change with the right permissions and keep any reason code private
PaymentAmount due or a clear payment state; no success message while unconfirmedVerify the payment result before closing the sale or asking the shopper to retry
Next shopperNeutral view with no previous basket or identity detailsFinish, suspend or abandon the sale and make sure the correct basket is still open

What This Workflow Needs to Cover

Make corrections obvious on the shopper side

Stand where the shopper normally pays. Ask the cashier to adjust a quantity without explaining where to look. Check whether the corrected line and amount due are clear without having to read the cashier’s screen.

  • ✓ Readable item names and units for lookalike packs
  • ✓ Visible difference between a removed line and a price adjustment
  • ✓ Totals legible under the counter’s normal lighting

Choose which fields should stay private

Use entirely fictional customer records for a test. Decide whether the second screen should show any loyalty or store credit information, or whether staff should discuss it separately. Ask how optional fields are disabled or masked.

  • ✓ No unnecessary phone numbers or prior purchase details
  • ✓ No staff controls, cost prices or internal notes
  • ✓ No previous shopper’s personal fields on a suspended or idle screen

Customer display demo: correct a duplicate scan

Use a fictional basket with snack packs at ₹90 and a gift box at ₹120. These prices illustrate the test, not a price list or product guarantee.

  1. STEP 1

    Start with an overcount

    Scan two snack packs and one gift box so the displayed total is ₹300. The shopper should be able to identify the snack quantity from their side of the counter.

  2. STEP 2

    Remove the extra pack

    Correct the snack quantity from two to one. With no other adjustment, the new amount due is ₹210. Check that the line and total agree on both screens before starting payment.

  3. STEP 3

    Check an interrupted payment

    In a demo environment, interrupt confirmation while the cashier is waiting for payment on the ₹210 basket. Check how the display distinguishes pending from paid and who confirms the result before a retry.

  4. STEP 4

    Clear the screen for the next shopper

    Complete the sample sale, then start a fresh basket. Check the same clear-screen behaviour when a sale is abandoned or suspended, not only after a successful payment.

How do you test a second display before rollout?

Use the screen and counter layout you plan to deploy, not just a screenshot from a demo machine.

Match display and terminal

Write down the terminal model, software version, screen size, connection and mount. Ask which combination is supported and who configures it. Check the fallback if the display is disconnected during a sale.

Verify multi-counter pairing

Open different baskets on adjacent tills. Restart one display and verify it reconnects to its own counter, not the neighbouring lane. Record which station the team checks when a screen shows an unexpected bill.

Use the actual payment workflow

Test each payment prompt the store intends to show. If a payment code is in scope, confirm whether it is tied to the active amount and what happens after the basket changes.

When does a customer-facing display make sense?

Good fit when

  • ✓ Staffed retail counters where shoppers regularly check scanned quantities or prices
  • ✓ Teams that want shoppers to confirm the amount before paying
  • ✓ Stores with space for a readable screen that does not block counter traffic

Confirm before choosing

  • • A separate kiosk workflow if shoppers should scan and complete their own checkout
  • • A hardware and placement check before buying screens or mounts
  • • An explicit decision on what to show when the next shopper steps up

Frequently Asked Questions

Is a second screen the same as self-checkout?

No. A customer-facing display gives the shopper a view of a sale controlled by the cashier. Self-checkout gives the shopper an interface to operate the checkout, with a staff fallback where needed.

Can I use a screen the store already owns?

Bring the model, available inputs, resolution and connection details to the demo. Ask T7 which combinations are supported rather than assuming that a display that powers on will show the right basket.

Should the screen say paid as soon as a payment prompt appears?

No. A prompt shows how to pay. A paid state should be shown only after the applicable payment is confirmed. Ask how pending, failed and confirmed states differ on your setup.

Evaluate T7 ERP With Your Actual Workflow

Bring a sample invoice, product catalogue, branch structure, or process requirement to a scoped product walkthrough.

Request a Demo →