Checkout · transaction control

Every checkout leaves an operating record.

Build the exact cart, park it when the line changes, use supported tenders, deliver a receipt, inspect the transaction, and begin a qualified return without losing the sale's operating context.

Transaction 8421 · one operating record

The sale keeps item, customer, employee, tender, receipt, and qualified return context under one transaction identity.

  1. 01

    Build

    Exact items, variants, modifiers, quantities, customer, tax, discount, and tip.

  2. 02

    Tender

    Supported tenders—including split tender when it is part of the merchant's payment setup—remain attached to the cart.

  3. 03

    Receipt

    Print, screen, email, or configured SMS receipt delivery records the handoff.

  4. 04

    Inspect

    Transaction detail preserves the employee, line items, totals, and payment references.

  5. 05

    Return

    A qualified partial or full refund begins from the original transaction record.

Operating thread

Keep the sale connected after tender.

Cart, tender, receipt, transaction detail, and qualified return remain one buyer-visible operating story.

  1. 01

    Build

  2. 02

    Tender

  3. 03

    Receipt

  4. 04

    Inspect

  5. 05

    Return

See the real product

See the register and the record it creates.

Use genuine product captures to evaluate the operating record behind the claim.

LiftedPOS Sales screen with product search, cart, customer, totals, and tender controls
Real product proof · LiftedPOS Sales screen with product search, cart, customer, totals, and tender controls
Inspect full-resolution screen
LiftedPOS Transactions screen for inspecting recorded sales and returns
Real product proof · LiftedPOS Transactions screen for inspecting recorded sales and returns
Inspect full-resolution screen

Branded customer handoff

Let the receipt keep working after checkout.

Carry your configured merchant identity into supported receipt surfaces with your configured logo, custom footer, and supported digital brand-color treatment. Add a validated Google review URL as a QR code on fresh and reprinted receipts, giving customers a direct path back to your business.

01Your identity

Keep the business name, configured logo, and custom footer recognizable.

02A direct review path

The validated destination gives customers a convenient route to leave their own feedback; review volume and search outcomes remain earned results.

03Find it again

Reprint the transaction receipt while retaining the validated review QR.

Printed receipts use a monochrome treatment. Reprint confirmation applies specifically to the review QR. Email and SMS delivery require the corresponding merchant communications setup.

YOUR BUSINESS SUPPORTED RECEIPT SURFACE
Sale record
Transaction
Customer handoff
Receipt
Return path
History

VALIDATED REVIEW DESTINATION

YOUR CUSTOM FOOTER
Illustrative field composition—not a fictional merchant receipt or application screen.

Build the exact sale in front of you.

Search products and categories, use exact barcode lookup, choose configurable variants and modifiers, change quantity, and attach the customer. Weighted checkout applies only to products already configured for weight pricing. Tax, permission-aware discounts, and tips remain visible before tender.

Keep tender attached to the cart.

Cash, rewards wallet, and configured card paths stay with the transaction. Split tender, when included in the merchant's payment setup, and restaurant split checks are available only where the merchant's device, payment, and rollout setup supports them. A sale can be parked and resumed without rebuilding the cart.

Give the customer a receipt and the operator a record.

Receipt choices include print, on-screen display, email, and configured SMS delivery. Authorized tenant settings can carry the merchant logo, primary brand color, and custom receipt footer into the customer-facing receipt. A validated HTTP(S) Google review URL can add a review QR to fresh and reprinted receipts; it gives the customer a path to the merchant's review page without claiming that a review or reputation result is guaranteed. Transaction detail retains employee attribution, customer, line items, totals, tender references, and supported export context.

Start a return from the original transaction.

LiftedPOS supports qualified partial and full refund control from transaction detail. The configured payment processor, gateway, MID, terminal, batch state, stored references, and rollout determine how a particular card return or void can proceed.

Configuration and responsibility boundary

POS transaction control is not a processor promise.

LiftedPOS preserves the sale record and can initiate a qualified partial or full refund. A particular card return, open-batch void, or token-backed refund depends on the configured payment processor, gateway, MID, terminal, original references, settlement state, and verified rollout. Refund approval is not guaranteed.

Inspect it

Follow one seeded sale all the way through.

Use the demo for product context, then confirm deployment-dependent behavior during a scoped rollout review.

  1. 01

    Open Sales in a seeded retail store and search or scan an exact product.

  2. 02

    Attach a customer, adjust the cart, and inspect the available tender and receipt controls.

  3. 03

    Park and resume the cart before completing a safe demo transaction.

  4. 04

    Open Transactions and inspect the recorded employee, items, totals, receipt, and qualified return controls.

Ring a seeded checkout

Workflow FAQ

Know what checkout can do in your configuration.

Can LiftedPOS park a sale and resume it later?

Yes. A cashier can park the current cart and resume the recorded sale without rebuilding its item and customer context.

Does LiftedPOS support split tender?

LiftedPOS can split a sale across supported tenders when that option is included in the merchant's payment setup, and it includes restaurant split-check controls. Availability depends on the configured tenders, device path, payment setup, and rollout.

How can LiftedPOS deliver receipts?

Receipt choices include print, on-screen display, email, and configured SMS delivery. Authorized tenant settings can add the merchant logo, primary color, custom footer, and a validated Google review URL rendered as a receipt QR. The enabled path depends on station, branding, communications, and merchant configuration.

Can frontline staff use LiftedPOS in Spanish?

LiftedPOS includes English and Español selection for supported navigation plus portions of the register and restaurant sale screen. During rollout, we verify the bilingual path your frontline team will use and confirm exactly where Spanish applies.

Can a cashier issue a partial or full refund?

LiftedPOS exposes qualified partial and full refund control from the original transaction. A card return or void still depends on the configured payment processor, gateway, MID, terminal, references, batch state, and rollout.

Public station terms

Know the price. Plan the way your team will use it.

Software is $100/month for the first station and $50/month for each additional station. A standard station is $499.99 to purchase or $39.99/month to lease. Cancel anytime with no long-term software contract. Leased equipment must be returned after cancellation or it is billed at the full purchase price. Payment terminals, processing, and separately scoped rollout work are separate from station pricing.

See the capability inside a working store.

Run it with safe demo data, then map the locations, roles, devices, and configuration your operation needs.