Price Lists and Schemes for Supermarkets
Apply dated price lists and promotional rules to eligible transactions.
Does this function belong in your operation?
Use when prices vary by customer group, channel, quantity or promotion.
A price or commercial offer changes.
Buy-two offers, member prices and end-of-week markdowns are set by item and date. They switch on at the till without hand edits. Expired offers drop off by themselves.
Bring the records the workflow depends on.
- Item prices
- Customer eligibility
- Validity and combination rules
Outputs to check
- Effective-dated pricing register
- Offer eligibility and application record
- Discount-exception report
Follow the price lists and schemes workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
Decide how exceptions are handled.
These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.
Can this work independently?
Pricing can be maintained independently, but quoting or billing must use the approved selection rules for consistent application. Customer groups and item codes provide eligibility. The price module does not establish stock availability, contractual acceptance or whether a promotion is legally permitted.
Systems and records it connects with
- Invoice management: Issued invoice references, line amounts and outstanding balances.
- Point of sale billing: Counter sales, tender records and authorised returns.
- Credit control: Customer limits, current exposure and authorised order releases.
- Dealer portal: Partner identities, submitted orders and permitted account information.
Configure, test and introduce the workflow.
- Hand over price sheets, scheme letters and the discount habits of the counter. A note groups them into lists.
- Decide who sits on which list and how far each role may go. Bills that pick the right rate come back. Try them. Staff raise sample bills from several lists. Corrections return as an adjusted set of lists.
- Billing clerks and sales staff practise approvals. A reference sheet for the counter follows. The next offer is entered with its dates. A review after it ends checks what each party paid.
Check the result before rollout.
Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.
- Expired offers stop applying.
- Eligibility rules select the intended buyers.
- Old transactions retain their original rates.
How the business operates.
A supermarket lives or dies between the delivery bay and the checkout lane, where a warm chiller or a wrong shelf label ends in a till dispute. Fresh lettuce, coriander and bananas turn in days. Packaged goods carry dates that cannot be missed. Prices change weekly.
The records that hold the operation together.
- Item master and labels. Keep every product with its barcode, unit, department, supplier and tax setting, and print shelf-edge labels and weighing-scale labels from the one record. No aisle strip disagrees with the till.
- Lane billing. Scan or weigh at the lane, apply offers, split payment across cash, card and vouchers, and park a basket when a shopper walks back for a forgotten carton of milk.
- Weighed and loose items. Price produce, deli and bakery lines by weight through price lookup codes, with a scale label or a lane scale, and keep the net weight printed on the bill.
- Batch and expiry. Receive chilled, dairy, bakery and packaged lines by batch with a date, then list what falls due by department. Markdown stickers are planned before the oldest stock reaches the front.
Operational bottlenecks to check
Shelf expiry dates are checked by eye
Dairy shelves get a glance each morning. A short-dated carton of yoghurt that should have gone to markdown last week is found by a customer holding it at the lane, not by staff.
Shelf price and till price disagree
A multi-buy offer ends on Sunday. The endcap ticket stays up until Tuesday. The customer points to the shelf edge, the cashier points to the screen, and the manager approves a discount just to clear the queue behind them.
How work flows across this business
This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.
1. Item set-up
A new product is added with barcode, department, pack size, tax setting, supplier and shelf location, and the shelf-edge label prints from that same record. The till reads that record too.
2. Purchase order
Buyers raise orders to suppliers, distributors and local producers from sales and stock levels, and each order goes out by email or messaging with the agreed case rate. The delivery day is printed on it.
3. Receiving
Cartons are counted against the delivery note, short or damaged cases are noted, and chilled goods are probed with a thermometer before the driver leaves. Perishable batches go in with their dates.
4. Shelf and promotion
Stock moves from the backroom to the shelf with the oldest batch forward. Price changes and multi-buy offers start and end on their set dates, and shelf labels for the affected bays are reprinted that same day.
5. Checkout
Cashiers scan and weigh, apply offers, take cash, card or vouchers and add loyalty points at the belt. At shift end, the cashier counts the drawer and the card terminal batch is settled before the lane closes.
6. Markdown and wastage
Items nearing their date are marked down by department with a coloured sticker. What cannot be sold is written off with a reason, and the loss is read against that department’s sales.
Industry reports to connect with
- Sales by department, product group and hour of the day
- Batches due to expire this week, by department
- Wastage by reason, department and week
- Deliveries received against orders, with short supply
Questions before implementation.
When should supermarkets consider price lists and schemes?
Use when prices vary by customer group, channel, quantity or promotion. A price or commercial offer changes.
What should we bring to the requirements discussion?
Bring anonymised examples of Item prices; Customer eligibility; Validity and combination rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.
Does this replace our existing business software?
The starting point is your current system and the gap you need to close. Apply dated price lists and promotional rules to eligible transactions. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
Commercial policy and permitted promotional terms must be approved by your business.
How are scope, price and rollout decided?
The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Expired offers stop applying. Use this check when reviewing the first working version.
Related functions for supermarkets.
Discuss price lists and schemes for your business.
Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.
What happens after you share your requirements
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- Review the scope and commercial terms before deciding whether to proceed.
Start with your requirements
Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.
Share your requirements