Open a module authorised by an owner or admin.
Product History includes supplier costs. An owner or admin grants it only to the appropriate device; an ungranted device receives a clear access message.
Product History
Follow the product record behind the shelf.
Carry a barcode into a read-only history of selling price, cost, receiving, sales and stock context. Source labels and missing-data states help the authorised colleague judge what the record can answer.
A demonstration first. A scoped subscription proposal before configuration.
Available
The question it answers
Keep a product question connected to its evidence.
A selling-price change can lead to questions about supplier cost, recent receipts, sales pace and stock. Product History gathers those recorded views around the scanned product without turning the handheld into an editing workflow.
Product HistoryAuthorised access
Harbour Oats 1 kg
Example product · VAT 0%
- Selling price
- £3.20
- Unit cost
- £1.74
- Margin
- 45.6%
- On hand
- 18
- Sold · 30 days
- 42
- Last received
- 9 Sep
- Selling price changed from £3.00POS · 8 Sep
- 24 units received at £1.74 eachIntakeBolt · 9 Sep
The workflow
See how the work fits together.
Identify the product once.
Scan directly or carry the barcode from Product Checker. Loading, not found and connection failure remain distinct states.
Review the headline facts.
See the available selling price, unit cost, margin, on-hand context, recent sales and last receipt before opening the supporting sections.
Follow history with its source.
Inspect recorded price and cost changes, receipts, sales periods, stock workings, movements and promotions. POS and IntakeBolt rows are labelled by source.
Keep gaps visible.
Unknown freshness, missing cost, unavailable stock and limited history are explained in words. A blank record is not presented as zero.
Connected handover
Connect shop-floor context to receiving and office review.
Receipt records connect the product back to receiving, while price and cost history give an authorised colleague context for the next review. The history itself does not write a movement or approve a change.
Fit and limits
Know what needs to be in place.
- Product History is read-only and requires a deliberate device grant because it exposes cost information.
- Price, cost, sales, stock and receipt sections depend on the source history available to the organisation.
- Recorded movements are a history view. This view does not change stock.
- Stock and sales functions require the relevant installation and data; unavailable or incomplete answers stay labelled.
Questions for a useful demo
- Which authorised colleagues should be permitted to see supplier cost and margin?
- How much POS sales, stock and price history is available?
- Which receiving and product questions should the demonstration follow?
Your next step
See how it fits your shop.
Tell us the part of your working day you want to improve. We will arrange a demo, check your systems and explain the proposed scope and costs.