Defining a centre
Each revenue centre carries its own colour, menu, categories and price list.
The dining room, the terrace and the bar are different boundaries of the same business. Each revenue centre carries its own menu, categories, terminals and price list; it becomes its own line in the report and it narrows the scope of printer rules.
"Revenue centre" sounds like a label stuck to a table. It is not: it decides which menu a terminal shows, which price list it charges from, which printer a ticket lands on, and which line the money is written to in the report. Four separate subsystems ask it the same question.
Each carries its own colour, menu, categories and price list.
A device is bound to a centre and opens with that centre's menu.
A centre is a reporting dimension: the terrace and the bar do not share a line.
The routing ladder on the POS page shows this same boundary from the other end: choose a revenue centre on a printer rule and the rule's scope narrows to that centre.
A revenue centre is not only an operational boundary; it is a reporting dimension. The terrace's revenue and the bar's do not share a line, so you never have to ask separately which area brought in which share.
Three revenue centres, one day: the dining room, the terrace and the bar.
A revenue centre does work in four places: in its own definition, on the devices bound to it, in the report, and in the scope of printer rules.
One setting, answered by four separate systems.
Each revenue centre carries its own colour, menu, categories and price list.
A device is bound to a centre and opens with that centre's menu.
A centre is a reporting dimension: the terrace's revenue and the bar's do not share a line.
Choose a revenue centre on a printer rule and the rule's scope narrows to that centre.
We talk through which areas should be centres of their own, bind the terminals, and read the first report together. The average business goes live in 14 days.