Why uniform pricing is a strategy, not a default.
Many retailers run uniform pricing across branches because their POS does not support anything else. They call it brand consistency. Sometimes that is true. More often, they are leaving margin on the table at premium locations and losing volume at price-sensitive ones.
Real uniform pricing is a deliberate choice — same brand promise everywhere, premium positioning, customers who travel between branches. Default uniform pricing, where it just happened because the system would not let you do otherwise, is a missed opportunity. Decide which one you are.
The branch-tier model.
The cleanest multi-branch pricing model is tiers: Premium, Standard, Value. Each branch is assigned a tier, and each SKU has a price per tier. New SKUs default to a tier-set defined globally, with branch managers able to flag exceptions.
Three tiers covers 95% of cases without exploding into per-branch pricing chaos. A 12-branch chain typically has 2 premium (Paris central, Lyon central), 7 standard, and 3 value branches. The pricing matrix is 3 columns wide regardless of how many branches you add.
- Premium: high-rent locations, premium customer mix
- Standard: most branches, default pricing
- Value: suburbs or price-sensitive areas, lower margin acceptable
Per-branch price overrides.
Tiers cover 95%. The other 5% is per-branch overrides for local conditions: a competitor opened next door, this neighborhood has weird preferences, this branch is bleeding inventory on a SKU. You need the system to support per-branch override on top of the tier.
The override should be visible. A branch manager who sees that the global tier price is €42 but their branch override is €38 understands why their margin is lower. A hidden override is a lost data point. In Nonari overrides show up on the branch product page with a clear "tier price was X" indicator.
Promotional pricing across branches.
A promotion at one branch should not silently leak to all branches. Run a 20% off weekend at the Paris flagship and a customer at the Lyon branch quoting last week's ad will be unhappy. Promotions need branch scope from the start.
A correct system has promotions with branch-list and date-range. The Paris promo applies to Paris between Friday and Sunday, full stop. Cashiers at Lyon see no promo when they ring the same SKU. The receipt shows the standard price, no struck-through promo line. No customer confusion, no operational mess.
The cost basis stays the same.
Different selling prices across branches do not change the cost basis. WAC is global per SKU (or per branch if you isolate inventory). A shirt that costs €8 to produce costs €8 whether sold at €42 or €48. Margin differs by branch, cost does not.
This is where many retailers get confused — they think a higher selling price needs a higher cost. It does not. The premium branch has higher margin per unit, which is the whole point. The accounting is straightforward as long as you keep cost and price as separate concepts.
When to allow cashier price overrides.
Cashier price overrides are different from branch overrides. Branch override is a permanent or semi-permanent setting. Cashier override is on a single transaction. Both are useful, both can be abused. The rule of thumb: cashier override only with manager PIN, capped at 5% off the branch price, logged in the audit trail.
A cashier who can drop price by 20% on the spot is a cashier who is making business decisions you did not authorize. A cashier who can drop 5% with manager approval handles edge cases like price match without losing the customer. Set the cap and stick to it.
Reporting per branch with prices.
A multi-branch P&L by branch with average selling price column tells you which branches are pricing well. The Paris central branch with €45 average ticket and 35% gross margin is performing. The Marseille branch with €38 average ticket and 22% gross margin is under-pricing for the location.
Look at the branches at the extremes. The cheap branch may be losing margin needlessly. The expensive branch may be losing volume. Pricing strategy iterates with data, not with intuition. Your monthly branch comparison report is the input.
Communicating pricing to staff.
When pricing changes per branch, the staff at each branch needs to know without seeing the pricing matrix for other branches. Do not show the Lyon staff what Paris sells the same SKU for. It will leak to customers and create the perception of unfairness.
Branch staff sees only branch prices in the POS. The pricing matrix is admin-only. This is a permission-level boundary, not a UI choice. Configure permissions correctly the first time and you will not relitigate the leak conversation later.