Customers · Customer Book
Put purchase history and credit beside the customer at the till.
Purchase history, returns and balances lose value when the counter cannot retrieve the customer record.
This is a capability inside Lightning Pharos, not a separate product.
Find the customer by phone and attach the transaction.
01 · What ships
The complete working surface.
The retail customer file, available at the counter.
- 01
Customer details, GSTIN, credit limit, phone lookup, and price-list assignment
- 02
Purchase history, return history, and payment-derived khata
- 03
Deterministic RFM segmentation from recorded transactions
- 04
A link to the CRM customer context
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
Find the customer by phone and attach the transaction.
- 02 / 03
Governed event
The transaction joins purchase history, khata and price-list context.
- 03 / 03
Connected result
Stores, loyalty, promotions and CRM read one customer history.
03 · What it needs
Ready inside every Pharos workspace.
No additional module is required before this capability can be switched on.
04 · Where it stops
The boundary is part of the product.
Phone and email are not globally unique, and the module does not yet provide contact-preference or consent management.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system