VegaShelf label price audit work begins where a customer chooses an item, not at a spreadsheet. Two nearly identical detergent bottles sit beside a label for KSh 420. One is a smaller pack and the other is a refill. A cashier can scan the correct barcode while the customer has reasonably read the wrong label. The investigation must connect product, position, label and till record.
Use a fictional aisle with six products and record a photograph or sketch that avoids people and private information. This guide describes an operational rehearsal, not a rule about legal pricing obligations. Follow the business’s approved customer-resolution process for a real disagreement. Ask a colleague unfamiliar with the shelf to choose the product they believe the label describes, then compare that interpretation with the catalogue.
Shelf label price audit in four decisions
Use the four decisions below as a tabletop exercise. The case is fictional. Each decision pairs a new scenario with field notes drawn from a linked guide in our library. Read the scenario aloud first, and ask the next person to explain the result before consulting the notes.
1. Define the comparison properly
For each sample, capture the product reference, pack size, label location, displayed price and till result. Compare equivalent units before calling a difference an error. A carton price beside single bottles can look attractive while describing a different selling unit.
Record that ambiguity even if the carton amount itself is correct. Use a second label from another shelf position to test whether the same product has conflicting promises in different places. Shelf label price audit evidence should let a colleague reproduce the customer’s view, not merely confirm that a number exists somewhere in the pricing screen. For shelf label price audit, keep this starting assumption visible beside the result.
Field notes from our barcode label checks guide:
Separate product labels from shelf information
A product barcode identifies an item or unit within the agreed process. A shelf label may also show a price, location or promotional message. Treat those functions separately during barcode label checks. An accurate shelf description does not prove that the product sticker underneath it belongs to the same record.
Confirm the selling unit before printing
Write down whether staff sell a piece, packet, pair, carton or another unit. Confirm how the supplier’s packaging relates to that unit. Do not copy a carton label onto individual items without checking what the resulting scan means in your system. A successful scan can still select a quantity that the cashier did not intend.
Investigate repeated or conflicting matches
If a code selects an unexpected record, stop that label batch and record the observed result. Compare the printed characters with the intended reference. Check whether a different item has been given the same internal code or whether the wrong template was selected. Avoid fixing the problem by changing several records at once.
Review after the first trading period
Check the first day’s reported exceptions after introducing a label batch. Ask receiving staff whether application was straightforward and cashiers whether scanning produced consistent matches. Inspect a small sample on the shelf again. The goal is to discover practical problems that were not visible during printing.
2. Control the changeover
Suppose the approved price changes from KSh 420 to KSh 450 at opening tomorrow. Name who updates the catalogue, who replaces the shelf label and who checks the first scan. Avoid leaving old and new labels side by side without an explanation.
If the update is delayed, the supervisor needs to know which step is incomplete before customers reach the aisle. Keep the approval reference and effective time together. An instruction sent in a chat yesterday is not evidence that every shelf and till was changed at the intended moment today. This stage of shelf label price audit tests a different question from the final total.
Field notes from our retail quotation review guide:
Confirm quantities and selling units together
An accurate quantity with the wrong unit can still produce a serious misunderstanding. Ten boxes, ten pieces and ten metres describe different commitments. Record the selling unit beside every quantity and check how the system handles a pack containing several individual units. Do not assume that a supplier’s packaging description matches the unit used at your counter.
For example, imagine a customer requests six cartons and each carton contains twelve pieces. The quotation should make the offered basis clear before the team compares it with available stock. Retail quotation review should test the unit relationship using your actual products and supported configuration.
Explain delivery and collection responsibilities
Specify whether the customer will collect, the shop will arrange delivery or another party will handle transport. Include the relevant location and any agreed delivery charge. Separate a preferred date from a confirmed commitment. Staff should know what must happen before the business can promise a collection time or dispatch slot.
Keep amendments under one reference
Customers often change quantities, replace items or ask for a different delivery arrangement. Keep revisions connected so the team can identify the latest offer. Give each version a clear date or revision marker using the available process. An employee should not need to compare several screenshots to discover which one the customer accepted.
3. Retest promotion boundaries
Create a sample promotion valid for a defined period and product size. Test one qualifying product, one similar excluded product and a transaction after the promotion ends. Read the terms as a customer would. If two units qualify together, check a basket with one unit and another with three, using the agreed rule for the extra unit.
Do not infer eligibility from a colourful label alone. The shelf label price audit should record which offer actually applied and why. Ask whether a reserved order keeps its agreed price; that is a separate decision from changing today’s shelf price. Use shelf label price audit to expose this exception before relying on the ordinary successful path.
Field notes from our stock reservation expiry guide:
Identify the product and quantity precisely
Record the product reference, variant, selling unit and quantity. Similar goods on the same shelf are not necessarily interchangeable. A customer may have chosen a particular size, colour or configuration. If the reservation describes only a broad product family, the next shift may release or sell the wrong item while believing it has followed the instruction.
Handle partial collection clearly
A customer may collect some items while waiting for others. Record which quantities were fulfilled and which remain held. Do not close the whole reservation if part of the agreed arrangement is still active, and do not leave the original full quantity reserved after some goods have been released through the correct transaction.
Include reservations in shift handover
Highlight holds that need attention during the incoming shift. Give the reference, location, current status and next action. Keep the handover concise and point to the full record for detail. Rewriting the entire case in several notebooks can create conflicting versions when the customer changes the arrangement.
Review recurring causes of overdue holds
Look at a small sample of reservations that repeatedly need extension or clarification. The issue may be an unrealistic collection window, poor product descriptions, uncertain payment status or a handover gap. Treat the pattern as a question to investigate, not proof that customers or employees are behaving badly.
4. Close the exception visibly
A corrected label is not enough if a second obsolete label remains on an end display. Assign each exception a location and follow-up owner. After correction, repeat the scan with the physical item and compare the customer-facing description.
Keep a short record of the original difference and the action taken so recurring causes become visible. If several errors involve pack-size changes, review the update procedure instead of blaming the last cashier. End the rehearsal by asking someone who did not make the correction to choose the product and explain the price they expect to pay. The final shelf label price audit record should explain the outcome to someone who was not present.
Field notes from our reorder exception review guide:
Review recent demand in context
Compare the recent pattern with the circumstances of the period. A large one-off order, a promotion, a temporary closure or missing trading days may make an average misleading. Keep those events visible instead of treating every change as a permanent shift in demand.
Separate a price decision from a quantity decision
Supplier cost changes, selling prices and reorder quantities are related but different questions. A higher cost may require an authorised commercial review. It does not automatically justify buying an unusually large quantity or changing the counter price without approval.
Use the price change approval guide for the selling decision. In a reorder exception review, record the assumptions that affect the quantity and route separate price questions to the responsible person. This keeps the buyer’s explanation understandable when someone reviews the order later.
Record the decision and its reason
The outcome may be to order, wait, reduce a quantity, investigate a discrepancy or seek another authorised supply option. Record the approver, quantity basis and next action. A short explanation should connect the decision to the evidence rather than simply repeat approved or rejected.
Keep unresolved questions open under a named owner. Reorder exception review should not convert uncertainty into a blank field that disappears from attention. If the decision is temporary, record when it will be revisited and what information is expected before then.
Shelf label price audit test sheet
Before running the example, cover the expected results and ask a colleague to predict them. Use the disagreements to decide which rule needs explaining. These are fictional test cases; use your own approved references for the real procedure.
| Test condition | Expected evidence |
|---|---|
| Same product in two display locations | Both locations communicate the correct product size and approved offer. |
| Catalogue updated but label unchanged | The exception stays open until the physical customer-facing label is checked. |
| Three units in a two-unit promotion | The agreed treatment of the extra unit is visible on the test receipt. |
| Offer has ended | The new transaction uses the approved current rule rather than an obsolete label. |
| Independent colleague retests | The product, displayed promise and till outcome agree without coaching. |
Shelf label price audit: questions from the counter
Is checking the price list enough?
No. A price list cannot show whether the correct label is beside the correct product. Walk the shelf, identify the exact selling unit and scan a physical sample. Record each location where the item appears, including promotional displays. The customer encounters the whole presentation, not the price database in isolation.
Who should approve a correction?
Use the business’s existing pricing authority. The person finding a mismatch should preserve the evidence and escalate it, rather than inventing a new price to end the discussion. Customer resolution and permanent catalogue correction can require different actions; make both owners clear in the procedure.
How often should labels be checked?
Set a schedule based on how often products, pack sizes and offers change. Add targeted checks after an update and when a customer reports a discrepancy. A small well-chosen sample can reveal a process weakness, but do not present a sampled audit as proof that every shelf label was inspected.
Use shelf label price audit in your next demonstration
For a discussion about shelf label price audit, contact Vega POS on 0725345345. Bring one anonymised example, its starting position and the result your colleague expects. Ask for a demonstration using those details before assuming a particular feature or integration is available.
Other Kenyan business workflows
For a custom business portal, explore Zama Web Experts. If your team is working in another sector, these services provide different examples: Prim for salon bookings, sales and stock; TAS for chama records and contributions; JAAT for shop and product listings; Dereva for driver discovery. Use the service that fits your task; a link does not establish that the systems exchange data.