A multi-store retailer is a single business with several places to sell, and the tension in running it is the same at three stores as at three hundred. Central buying earns better terms and consistent range; the store manager knows what sells on their street. Head office wants every store the same; each store's building, staff and customers are not. The result the owner reads is the sum of stores, and the sum hides which store is carrying which. With Pentoggle, a multi-store retailer can describe how their chain actually runs, centrally and store by store, and generate the starting application around it.
This page is for the chain of company-owned stores, in any category. The workflow of seeing one item across every location is Retail Multi-Store Inventory Software, and moving stock between locations is Retail Stock Transfer Software; this page is the business those workflows serve. Outlets owned by others under a brand are Franchise Retail Software. One building of many departments is Department Store Software.
Most chains already run an accounting system, a POS at each store, and supplier portals or ordering methods. Those stay where they are. What is often still managed outside them is the chain as a set of stores: the allocation of a delivery across locations, the transfer that left one store and arrived at another, each store's margin after the costs that belong to it, the price change that reached most stores, and the comparison that is fair.
Key takeaways
- Central purchasing earns terms and consistency; allocation is where it succeeds or fails. The same delivery split equally across stores that sell differently is the origin of dead stock in one and stockouts in another.
- Store P&L is only honest with shared costs attributed on a stated basis. Head office, warehouse, delivery and marketing costs spread as an average make every store's margin wrong in a different direction.
- Comparison between stores has to be on rates. Sales per hour open, margin per unit of space, shrink as a share of sales, labour as a share of sales. Totals reward the biggest store and tell nobody anything.
- The manager who runs their store differently is sometimes the problem and sometimes the finding. The record should show the difference and its result, not suppress it.
- A useful number is store margin after attributed costs per unit of space, read alongside the spread between the best and worst store on each rate.
How a multi-store retailer makes money
A chain earns what each store earns, less the cost of running the centre, and it exists because the centre adds more than it costs. Central purchasing earns better prices, terms and supplier support than any single store could, and it gives every store the same range at the same cost. Shared services, warehouse, delivery, marketing, systems, finance, cost less per store than each store providing its own. A brand across locations earns recognition that a single store cannot.
Against that, each store is its own trading unit with its own sales, margin, labour and local costs, and the chain's result is the sum of stores after the centre is paid for. A store that earns well on the shelf and poorly after its share of the centre is a real finding; so is a store that looks weak on totals and strong on rates because it is small.
The store manager is where the chain's economics meet the street. A good manager adapts range, staffing and presentation to their customers within the chain's rules, and their store outperforms. A manager who departs from the rules quietly, on pricing, on promotions, on range, on process, produces a store that cannot be compared to the others and a chain that is not quite one business. The difference between the two is whether the departure is recorded as a local exception with a reason and a result, or hidden.
Growth in a chain is adding stores, and each new store is a bet that the model transfers. The chain's data on what makes its existing stores work, by rate, is the basis for that bet.
The cost rhythm that runs against it
Stock is bought centrally, ahead, in quantities for the chain, and delivered to a warehouse or directly to stores. Allocation across stores is a decision made at every delivery, and a decision made by formula rather than by each store's sales and cover produces imbalance that transfers then have to correct. Transfers between stores cost handling and transport and carry the risk of stock lost between two locations.
Each store runs its own day: deliveries received, shelves filled, counts done, staff rostered, cash closed, all to a chain standard that has to be maintained by people head office does not see. Local costs arrive at the store; central costs arrive at the centre and have to be attributed.
Pricing and promotions are set centrally and have to land in every store on the same date, with labels and tills updated everywhere, and local exceptions, where allowed, recorded. Standards are audited by area managers who cover several stores and see each one occasionally.
Set against a result that is the sum of stores after the centre, this rhythm means the chain needs allocation from each store's data, transfers recorded on both sides, store P&L with attributed costs on a stated basis, pricing and promotions rolled out with confirmation per store, standards audited with evidence, and comparison on rates with local exceptions visible.
Where the record usually breaks
Each store's POS records its own sales. The breaks are between the stores and the centre.
When allocation is an average
A delivery of a hundred units goes twenty to each of five stores. One store sells forty a week and another sells five. In a fortnight the first is out and the second has two months of cover, and a transfer is arranged to fix a problem the allocation created.
When store P&L is the till
Head office knows each store's sales. Each store's margin after its labour, its local costs and its share of the warehouse, delivery and marketing is a spreadsheet built at the year end, if at all, and the store that is losing money is subsidised by the ones that are not without anyone deciding to.
When comparison is a league table of totals
The biggest store is always top. The small store in a good location with the best margin per unit of space is always mid-table. Managers learn that the ranking is about size and stop reading it.
When a store is quietly different
One manager runs a promotion the chain did not set, or stocks a local line, or prices a category differently. Sales are up. Whether it is a finding the chain should adopt or a departure it should stop is unknown, because the difference was never recorded as an exception.
What multi-store retail software holds
Central purchasing for the chain
Orders placed centrally against the chain's needs, with the allocation across stores planned from each store's sales velocity and cover, and supplier terms earned at chain volume.
Allocation and transfers
Incoming stock allocated by store from data rather than by average, delivered to the warehouse or direct, and transfers between stores recorded as dispatch and receipt on each side.
Store-level P&L
Each store's sales, cost of goods, margin, labour, local costs and attributed central costs on a stated basis, so the store's result is honest and comparable.
Pricing and promotions across stores
Central prices and offers rolled out to every store with confirmation per location, local exceptions recorded with a reason and an approver, and end dates enforced everywhere.
Standards across locations
Store audits with evidence and actions per store, so the chain standard is a record area managers and store managers share.
Local exceptions
Where a store departs from the chain's range, pricing, promotion or process, the exception held with its reason, its approver and its result, so a finding can be adopted and a departure stopped.
Comparison on rates
Sales per hour open, margin per unit of space, shrink, labour and expenses as a share of sales, by store, so stores of different sizes are compared fairly.
The head office view
Stores on rates with the spread between best and worst, allocation and transfer activity, store P&L, open standards actions and local exceptions, on a phone.
Workflows this business depends on
- Retail Multi-Store Inventory Software, because one item across every store is the view allocation, transfers and customer service all rest on.
- Retail Stock Transfer Software, because stock moves between stores constantly and a transfer recorded on one side only is stock lost between two locations.
- Retail Replenishment Software, because replenishment is per store against that store's velocity, and the order may be to the warehouse rather than to a supplier.
- Retail Margin Management Software, because the same item's margin differs by store through local pricing, shrink and markdowns, and store P&L needs it.
- Retail Expense Management Software, because comparing the same cost lines across stores is the main reason to record store expenses consistently.
- Retail Pricing Management Software, because store-level price differences have to be deliberate, recorded and confirmed, not accidental.
- Retail Store Audit Software, because the chain standard is maintained by people head office rarely sees, and the audit with evidence is how it is known.
- Retail Employee Scheduling Software, because people work across locations, and labour as a share of sales by store is one of the rates the chain compares.
Why multi-store retailers choose Pentoggle
Allocation from each store's data
Incoming stock split by velocity and cover rather than by average, so transfers correct less and stores hold what they sell.
Store P&L with costs where they belong
Attributed central costs on a stated basis, so the store that is losing money is known rather than subsidised.
Comparison that is fair
Rates, not totals, by store, so the small store with the best margin per unit of space is seen for what it is.
Local exceptions as records
A store's departure from the chain held with its reason and its result, so findings are adopted and drift is stopped.
Sits around your accounting, your store POS and your suppliers
Your accounting system continues handling the books, with cost attribution set with your accountant. Each store's POS continues at its counters. Suppliers continue taking central orders their way. Pentoggle holds the chain as a set of stores between them.
A useful number for a multi-store retailer
Store margin after attributed costs per unit of space, read alongside the spread between the best and worst store on each rate.
The first is each store's contribution on a basis that stores of different sizes can share. After the centre is paid for, on the space it occupies, it is the number that says which stores earn their existence and which are carried.
The second is the chain's consistency. A narrow spread on shrink, labour and margin means the model transfers between locations; a wide spread means something is different between stores, and the stores at each end are where to look. The local exceptions record is often where the explanation sits.
Read allocation accuracy beneath both: how much transfer activity was needed to correct the initial allocation. A chain that allocates well transfers less.
Ready to build multi-store retail software?
You know what the chain sold last month and what each store took.
You may not be able to say which store is losing money after its share of the centre, which store's manager is doing something the others should copy, or how much of your transfer activity is correcting your own allocation.
Describe your stores, your central buying and how head office and store managers work together to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.