How to Automate Revel Systems

The whole estate reports into a single console

Revel Systems is an iPad point of sale built for operators running more than one of something: quick service chains, franchise groups, coffee and juice brands, campus and stadium concessions, retail estates with a dozen shops. It is now part of Shift4, and its merchants still work where they always did, in the Management Console.

The console is the reason people choose it. Every establishment reports into it, so one screen carries yesterday across the whole estate: what each site took, what each site sold, who was rostered, and what the food cost against it.

That changes what the job is. A single-site owner walks the floor and knows. An operator with twenty sites has a browser tab instead, and almost everything they believe about Tuesday arrived through it.

Head office work multiplies by the number of sites

The work that fills a multi-site week is not hard work. It is one small task, repeated once per location.

A price goes up. It goes into Revel once, and then somebody has to confirm the delivery marketplaces carry the new price too, at every site, because those listings are managed store by store and none of them changed on their own. A new location opens, and the checklist behind it touches the bank, the marketplaces, the distributor account, the utilities and the local licensing body. Every site's deposit has to be matched against its takings. Every site's distributor account has its own login and its own invoices. A manager rings on Wednesday to mention the delivery tablet has been switched off since Sunday, which explains the numbers.

One site is an afternoon. Forty sites is a department, and in most operators it is two people and a spreadsheet of logins.

Revel Systems

A price change that actually landed Proof that the new price is live on every marketplace listing at every site, rather than on most of them and nobody knowing which.

The estate compared daily Each location's takings, discounts and voids ranked against the others, so the site that drifted shows up this week instead of this quarter.

Deposits that arrived Yesterday's takings at each location checked against what reached the bank, without a person opening forty statements to do it.

The Management Console reaches every establishment and nothing beyond

Inside the estate, Revel already does the repeating for you, and this is the part worth configuring properly before anything else.

The Enterprise Management System pushes changes out from head office to the establishments you choose, covering products, inventory, employees, reports and settings, so a menu change is made once rather than twenty times. Inventory is tracked at ingredient, prep and recipe level, so selling a burger takes the beef and the bun out of stock as well, and the Ingredient Inventory Log records what moved. The Product Mix report names the winners and the losers site by site. Shift Schedules and Timesheet Rules cover the rota, the overtime warnings and the payroll figures behind them.

All of that operates on establishments Revel knows about.

The delivery marketplaces do not report into it. Neither does the distributor whose portal holds this week's invoices, nor the bank where each deposit either landed or did not, nor the landlord's system, nor the council page where a licence renewal is either processed or stuck behind a query. Each of those has a login, per site, and the console has never seen any of them.

One check can run across every site at once

The size of the estate stops being the reason things go unchecked.

Every location's deposit checked against the bank the next morning, so a site that has not banked since Friday becomes a Monday conversation rather than a quarterly discovery. Every marketplace listing checked against the price head office pushed, so the store still selling the old combo at the old price is named instead of found by a customer.

Every distributor account opened, this week's invoices collected and filed against the right site, and the delivery that never shipped flagged before a kitchen runs out of it at lunchtime. Every site's discounts, voids and refunds ranked against the rest of the estate, so an outlier is visible while it is still one week of numbers and one conversation.

The site opening in March gets the same opening checklist run and reported rather than remembered, which is where most of the missed steps go.

Keep the money and the messages supervised. Reading forty portals can happen unattended. Changing a live listing, committing an order or writing to a franchisee should be drafted and approved by somebody who owns the relationship.

Repeating a task forty times is not a management decision

The check itself is easy. It is the fortieth repetition nobody has time for, which is why most of an estate only ever gets spot-checked.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the bank, the marketplace back office or the distributor portal for each site in turn, reads what is there, and sets it beside what the Management Console says, with the locations that disagree listed first.

It runs on your schedule in your own private environment, and you can watch a run and stop it mid-way. Anything that changes a live listing, commits money or goes to a franchisee is drafted and waits for a person.

The workflows below are already built, and each one lists the sites it visits and what it reads.