Retail pricing management software holds what each item sells for and why: the base price, the variations by location, channel and customer, the rules that generated it, the cost it was set against, and the history of every change. It rolls a change out to every place the price appears. With Pentoggle, a retailer can describe how they set and change prices and generate the starting application around it.
This page is about the everyday price. Temporary offers and discounts are Retail Promotion and Discount Management Software. What the price is applied to at the counter is Retail POS Software. The labels and shelf edges that display it are Retail Barcode and Label Software. What margin actually results is Retail Margin Management Software.
What you may charge, how prices must be displayed, what a price change commits you to, and what agreements about pricing are permitted, all differ by place and change over time. This page describes the workflow and states none of those requirements. Confirm what applies where you operate with a suitable adviser.
Most retailers already run an accounting system such as QuickBooks, Tally or Xero, and a POS that holds a price. Those stay where they are. What is often still managed outside them is the pricing decision: the trade price agreed with a contractor, the item whose cost rose in March and whose price did not, and the change that reached three stores out of four.
Key takeaways
- One price record with variations beats several price lists. Separate lists for stores, channels and customer groups drift apart, and the counter is where the drift is discovered.
- A price is set against a cost at a moment. When the cost moves and the price does not, margin erodes quietly, and the item that is still selling well is the one least likely to be noticed.
- A price change is a rollout, not an edit. Till, shelf edge, item label, website and any printed material all have to move together or the store is displaying two prices.
- Price history is worth keeping. Reproducing what an item cost the customer on a date, and why, answers disputes and supports analysis.
- A useful number is the count and value of items whose cost has risen since their price was last reviewed.
The spreadsheet is often not the problem
An owner who sets prices by knowing the goods, the customers and the competition, and changes them when something changes, is doing the job properly. In a store with a few hundred items and one decision-maker it works.
The trouble starts at identifiable points.
When the same item has several prices
The POS has one, the website has another, the trade price list has a third, and a customer who buys through two channels notices before you do.
When cost rises quietly
A supplier increases cost by a small amount on a routine invoice. The price stays. Repeated across many items over a year, the margin decline is real and no single event explains it.
When a change reaches some places and not others
The price is updated in the system on Monday. The shelf edge is changed on Thursday in two stores and not at all in a third. The customer is charged a price the shelf does not show.
When special prices live in memory
The contractor was given a discount two years ago by someone who has left. Nobody can say what it was, so it is re-negotiated at the counter each time.
What retail pricing management software holds
Base price per item
The standard selling price for each item and variant, with the date it was set and who set it.
Variations
Price by store, by channel, and by customer group or trade tier, held as differences from the base rather than as separate lists.
Pricing rules
Cost-plus, target margin, rounding conventions and price points, applied to generate a suggested price rather than to set it automatically.
Cost linkage
The cost the price was set against, and an alert when the current cost has moved beyond a threshold.
Approval
Who may change a price, up to what change, with approval above that and a record of the reason.
Scheduling
Changes dated to take effect, so a price rise can be prepared in advance and applied everywhere at once.
Rollout
The list of what must change when a price goes live: tills, shelf edges, item labels, the website and any other display.
History
Every price an item has carried, with dates, the cost at the time, and the reason for the change.
One record, many variations
The alternative to a single price record is several price lists, and they drift.
A store list, a website list, a trade list and a list for one large customer will be maintained by different people at different times. A change made in one is not made in the others, and the difference is found by a customer or at a reconciliation.
A single record with variations holds the base price once, and expresses each variation as a defined difference: this store is higher by an amount because of local costs, this channel carries a different price because of its own economics, this customer group receives a discount at an agreed level. When the base moves, the variations move with it unless they are set as fixed prices, which should be a deliberate choice rather than an accident.
The benefit at the counter is that the right price appears for the right customer at the right location without anyone remembering it. The benefit in the office is that the question "what does this item sell for" has an answer with a structure behind it.
Where a customer's price is contractual, it should be held on the customer record with a validity period, as described on Retail Billing Software, and honoured until it expires even when the base price moves.
Cost moves and prices do not
The quietest margin loss in retail is the price that was correct when it was set.
Supplier costs change, sometimes with notice and sometimes on an invoice nobody compared to the last one. The price on the shelf stays because nothing prompts it to move. The item continues to sell, which is exactly why nobody looks at it, and the margin it earns falls each time cost rises.
Linking the price to the cost it was set against turns this into a visible list. When the current cost has moved beyond a threshold from the cost at the time of pricing, the item appears for review. The review is a human decision, since raising a price is a commercial judgement about customers and competitors, not an arithmetic one, and it can only be made if the item is surfaced.
The same linkage supports rules where the store wants them. A target margin or a cost-plus rule can generate a suggested price when cost changes, with the buyer accepting or overriding it. Suggested rather than automatic is usually right in retail, because price points, competitor positions and customer expectations do not follow arithmetic.
It is worth reviewing in both directions. Costs fall as well as rise, and a store holding a price after a cost reduction has room it may prefer to use competitively rather than bank.
A change is a rollout
Changing a price in the system is the beginning of the work, not the end.
The price appears in several places, and they do not update themselves: the till, the shelf edge, the item label or ticket, the website, any marketplace listing, printed price lists given to trade customers, and any signage. A change that reaches some of these and not others produces the situation customers notice most, where the displayed price and the charged price differ.
Handling it as a rollout means the system produces the list. When a price change goes live, it generates the reprint list for labels and shelf edges by aisle so the store can be walked once, pushes the new price to the till, and flags the channels that need updating with what has changed.
Scheduling makes this manageable. A price change dated for Monday can have its labels printed on Sunday, so the physical and system changes happen together rather than days apart. Batching changes into a regular cycle, rather than making them one at a time, reduces the number of store walks and the number of chances to miss something.
Where displayed prices are subject to rules about what a customer must be charged, that is a matter for your adviser rather than for this page. Operationally, the goal is simply that the shelf and the till agree at all times.
Where pricing looks different by business type
- Grocery Store Software, where cost changes are frequent, margins are thin and shelf edges change weekly.
- Hardware Store Software, where trade and retail prices coexist and contractor accounts have negotiated levels.
- Jewelry Retail Software, where price may be derived from weight and prevailing material rates rather than set as a fixed figure.
- Electronics Retail Software, where competitor prices move quickly and manufacturer support affects what the store can charge.
- Multi-Store Retail Software, where store-level pricing differences have to be deliberate rather than accidental.
- D2C Brand Software, where the same product is priced across a website and several marketplaces with different fee structures.
Why retailers choose Pentoggle for pricing
One record with structured variations
Store, channel and customer prices as defined differences from a base, so a change moves everything it should.
Cost linked to price
An item's price held against the cost it was set at, with a review list when the gap moves.
Suggested, not automatic
Rules that propose a price and a person who decides it, because pricing is a commercial judgement.
Changes as scheduled rollouts
A date, a reprint list by aisle, and the channels flagged, so the shelf and the till agree.
Sits around your accounting and your POS
QuickBooks, Tally, Xero and comparable systems continue handling the books. Your POS continues charging. Pentoggle holds the price decision and the rollout behind them.
A useful number for pricing
The count and value of items whose cost has risen since their price was last reviewed.
It is a working list rather than a metric, and it is the closest thing pricing has to an exception report. Every item on it is earning less than it was designed to, and each needs a decision: raise the price, accept the lower margin for a competitive reason, or change supplier.
Read it by value rather than by count. A hundred small items with tiny cost increases matter less than five items carrying real volume.
Read the age of the list. Items that have been on it for months are decisions that were postponed rather than made, and the cumulative effect of postponing them is usually larger than any single price change would have been.
Ready to build retail pricing management software?
You know what you charge.
You may not be able to say which of your prices were set against a cost that has since gone up, or where the shelf and the till currently disagree.
Describe how you set prices, who may change them and where they appear to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.