Stock · Stockroom
Know what you can sell before the customer asks.
A total stock number is not enough when batches expire, units move between stores or a count finds a variance.
This is a capability inside Lightning Pharos, not a separate product.
Count, dispatch or receive retail stock.
01 · What ships
The complete working surface.
What is on the shelf, at which location, right now.
- 01
Movement-derived on-hand quantity by retail location
- 02
Transfers with separate dispatch and receipt states
- 03
Batch, expiry, FEFO, and serial-unit tracking
- 04
Stock takes with counted-versus-system variance
- 05
Moving-average or FIFO valuation and reorder analytics
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
Count, dispatch or receive retail stock.
- 02 / 03
Governed event
The location ledger records quantity, actor and reason.
- 03 / 03
Connected result
The counter and managers see the same movement-derived on-hand, variance and reorder evidence.
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.
There is no explicit reserved or available-to-sell field, per-location reorder setting, or supplier-return workflow.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system