Sell (POS) · Till Stage
Bill a sale. See exactly what changed.
A receipt is only the front of the transaction. Stock, tax, tender and accounting status must remain explainable.
This is a capability inside Lightning Pharos, not a separate product.
Scan or search, set quantities, then charge.
01 · What ships
The complete working surface.
The register covers the cart, tender, receipt, and the ledger entry behind it.
- 01
Touch-first counter screen: scan or search, edit the cart, apply discounts, hold a bill
- 02
Split tender across cash, card, and UPI, with change and rounding handled
- 03
Returns referenced to the original bill
- 04
Every sale records the stock and tax consequences, then shows whether the accounting entry posted or needs recovery
- 05
Shift open and close with a cash-drawer count and a variance somebody explains
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Scan or search, set quantities, then charge.
- 02 / 03
Governed event
The completed sale records tender, receipt, stock and tax consequences.
- 03 / 03
Connected result
Pharos shows the accounting posting reference or a visible recovery state if posting is refused.
03 · What it needs
Connected by design.
Pharos requires these modules first because the workflow depends on their records. The dependency is enforced in the product.
04 · Where it stops
The boundary is part of the product.
There is no atomic exchange record. Payment-terminal and device-provider integrations are not claimed as verified.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system