Run many locations
as one.

That depends on your plan, and it is a question for our sales team rather than one this page can answer. The sample screens show a group of 24 with 22 trading — a number chosen to illustrate the layout. It is not a limit, a minimum or a recommendation, and we would rather you did not read a ceiling, or the absence of one, off a screenshot. What we can be useful about is what changes as a group grows. The dashboard is a summary at estate scale, so a single weak site is easy to miss inside a group total until you open the per-outlet view. The menu matrix gets wider, and each override you grant adds a row someone has to keep track of. Role design stops being an afterthought somewhere around the point where regional managers appear. None of that is a hard boundary; it is the work that scales alongside the estate. Ask sales what your plan covers for outlets, terminals and users in your region, and get the answer confirmed before you build a rollout plan on it.

Head office edits the master item — the design uses a Classic Burger at a $14.00 global base price, with recipe, image and brand locked and availability set centrally. You choose who receives it, all branches or named outlets, and publish. Each outlet then reads as Inherited, meaning it is carrying the global value, or Override, meaning someone was permitted to set a local one: Riverside at $15.50 for local market demand while Downtown and Uptown stay at $14.00. Only fields you have permitted can be overridden per outlet, and the central dashboard records the change details — field, from and to values, who changed it, the timestamp and the approval status — with a revert-to-global action next to it. On the word the design uses for the sync, immediate: a publish is a push, not teleportation. It travels over your outlets' network connections to terminals that have to be reachable to receive it. A site on a poor line, a terminal switched off overnight or a station mid-service picks the change up when it next connects, which is why there is a pending-updates counter on the dashboard at all — if every push landed the moment you pressed publish, there would be nothing to count. Treat the per-outlet sync status as the thing that tells you a change arrived, and if a price change has a hard start time, publish it with enough margin to check the outlets read Synced. One more plain point. Central control works while outlets are actually running the shared configuration, and every override you grant is a standing exception that someone has to own and revisit. The system records that Riverside is at $15.50; it does not record whether that is still the right answer six months later. A group that accumulates local prices nobody remembers approving has lost the thing the global menu was for. The audit log makes overrides visible — deciding which ones still earn their place is a review a person has to actually do.

We would rather describe the steps than quote you a number of days, and if you have seen a phrase like days, not weeks on a draft of this page, treat it as marketing copy rather than a commitment. What the rollout does is make the setup repeatable. Step one, identity and configuration: the new location's metadata and system hooks. Step two, menu sync, so the site inherits your global menu and pricing rules instead of having them typed in from scratch. Step three, kitchen hardware, with KDS and POS stations provisioned remotely. A status view tracks each stage — location identity complete, menu integration synced, kitchen provisioning in progress, staff training pending approval — so you can see where a site has got to rather than asking around. What that removes is re-keying and guesswork, and inheriting a menu you have already tested is genuinely faster than building one. What it does not remove is the part that belongs to you: whether your item data, prices and tax setup are clean enough to be worth inheriting, whether the hardware and network are physically installed at the site, whether the line is live, and whether you have staff hired and trained. Note that the sample rollout is stalled at 65% with staff training still pending approval — that is the realistic shape of it. Those factors set the pace and they vary from site to site, so ask our sales or onboarding team for a schedule based on your own data, hardware and staffing rather than planning an opening around a figure on a web page.

They control what a user can do in the system, which is worth having and is not the same thing. Corporate carries full visibility and editing rights across every outlet, billing and system-wide configuration. Regional restricts a user to assigned outlets — a geography or a concept within the group — with the inventory and performance views for those sites. Franchise is narrower again: a single outlet's operations, local staff and shift scheduling. Set up well, that means a regional manager cannot edit a price in a region they do not run, one franchisee cannot read another's numbers, and system-wide configuration stays with the people who should be touching it. What permissions do not do is prevent theft, fraud or collusion. Somebody acting entirely within their rights can still discount for friends, void a paid order and keep the cash, ring an item under a cheaper code, or approve a supplier they have an interest in. Two people whose rights are deliberately separated can defeat that separation by agreeing to. Access control narrows who could do a thing, and the audit log records who did — that makes a pattern findable afterwards and it is a genuine deterrent, but it is not a lock. The controls that actually catch this are procedural and human: someone independent reviewing voids, comps and cash variance, counts checked against what was recorded, and keeping the person who approves separate from the person who benefits. Vertex can give you the evidence those reviews run on. It cannot perform them for you.

No, and we would be cautious about any platform that says it does. Vertex applies the configuration you set up, per outlet: the tax rates and codes your business uses and how they map to your revenue and expense categories, whether prices are handled tax-inclusive or tax-exclusive, and which local values a site is permitted to carry. It applies that consistently and records who changed what. It does not decide what the configuration ought to be. A group trading in more than one region has different obligations at each location — different tax treatment and rates, different rules on receipts and how long records must be kept, different employment law around scheduling, breaks and pay, and, if you franchise, disclosure and franchise regulation that is specific to the jurisdiction and has nothing to do with your POS. You will not find a rate, a threshold, a filing deadline, a retention period or a required document format stated anywhere on this page, because all of those are jurisdiction-dependent and they change over time. Nor does Vertex monitor those changes on your behalf: if a rate or a rule at one of your locations moves, someone updates that outlet's configuration. Determining the correct treatment at each location, keeping every outlet's configuration current, and filing what is due remains yours to settle with your accountant, and for franchising and employment questions with your legal adviser. Central configuration makes it easier to apply a decision consistently once it has been made. Making the decision is not something software takes off you.