Page is loading
Per-branch prices
Cheeseburger · In store · Dine-in
KadıköyOverride₺210
BeşiktaşRegional₺198
BebekTier₺206
AtaşehirMaster₺165
BakırköyMaster₺165
The coloured strip says where the price came from; you read the layer before the number.
Multi-branch

Branch Overrides

Override price, variant or availability at any branch — without touching the master menu. The master is protected; local control is yours.

Override matrixMaster protectionBulk applyInstant undo
4
Price sources: override, regional, tier and master
4
Channels: in store, your own app, marketplace, call centre
3
Service types: dine-in, takeaway, delivery
24/7
Support, around two hours to a reply
The layers

The most specific layer decides the price at a branch.

A product's price can come from four places. The panel says which one won with a coloured strip on the left of the row, so you see where a figure came from before you read it.

  1. OverrideA price typed in for this branchWinning layer
  2. RegionalThe store group's adjustment
  3. TierThe branch's tier adjustment
  4. MasterThe product's master price

Cheeseburger → ₺210 (Override)

An override of what?

A branch price is not a single number.

Which layer wins is what the ladder above answers. The real question comes a step later: what exactly is the override written on top of? Not the product — the product ON A CHANNEL, FOR A SERVICE TYPE, at a branch. The same burger's dine-in price and its delivery price are two separate records.

Where the price came from

Every row in the drawer carries a coloured strip on its left: override, regional, tier or master. You read the layer before you read the number.

Per-branch prices
Cheeseburger · In store · Dine-in
KadıköyOverride₺210
BeşiktaşRegional₺198
BebekTier₺206
AtaşehirMaster₺165
BakırköyMaster₺165
The coloured strip says where the price came from; you read the layer before the number.

Channel and service

Same branch, same product: a price in store, in your own app, on a marketplace and at the call centre; separate rows for dine-in, takeaway and delivery.

Dine-inTakeawayDelivery
In store₺210
Own app₺210
Marketplace₺239
Call centre₺225
Same branch, same product — a different price per channel. The delivery commission is written here.

This is exactly where a marketplace commission gets priced in — and it happens only on that channel, without touching what the guest in the dining room pays.

MargheritaSold out
Caesar saladOn sale
CheesecakeSold out
Turkish coffeeOn sale
Sold out

A branch takes an item off sale without touching the master.

When something runs out during the evening service, the branch closes it on its own list. The master catalogue does not change, the other branches are unaffected, and it opens again the next day. That is an override too — of availability rather than of price.

  • Availability, per branch
  • The master catalogue does not change
  • Flagged in the panel by the override indicator
Capabilities

Everything Branch Overrides ships with, end to end.

An override is four questions: where the price came from, which channel and service it was written for, whether the item is on sale, and how to undo it.

The four questions of an override

All four are answered in the same panel, on the same row.

Where the price came from

Every row carries a coloured strip on its left: override, regional, tier or master. You read the layer before the number.

Channel and service scope

An override is written on the product AS SOLD on a channel and for a service type, not on the product. Dine-in and delivery are separate rows.

Sold out, per branch

A branch can take an item off sale without touching the master catalogue, and put it back in the evening.

Reset to master

Any override reverts on one press and the value goes back to whatever the master says.

Get started

Let us set up your branch differences with you.

We talk through which branches price differently and why, build the layers together, and make them readable in the panel. The average business goes live in 14 days.

No brand lock-in — it runs on the hardware you already haveLive in 14 days on average, from a single site to a chain24/7 Turkish-language support, included on every planGİB compliant, KVKK compliant — no add-on module needed
Support hotline
24/7
Average setup time
14 days
Uptime guarantee
99.9%