How to Automate Hallpass

A food hall is a landlord that also runs the tills

Hallpass is a food hall operating system: the accounting and vendor management layer under a building where a dozen independent kitchens trade beneath one roof. The same software runs shopping malls and franchise groups, which have the same awkward shape.

The shape is this. The hall owns the building, the seating, the toilets and usually the tills. Each stall owns its food, its staff and the name above its counter. A customer buys a bao at one counter and a beer at another, pays, and walks off to find a table. The money has now arrived somewhere it does not belong, and it has to be split: this much to the stall, less rent, less the service charge, less the card fee.

So Hallpass sits between the registers and the vendors. It collects the deposits, works out what each stall is owed and what each stall owes, pays the difference, and publishes every vendor its own report so nobody has to be walked through a spreadsheet on a Monday morning.

The money arrives in one lump and leaves in twelve

The operator is usually the last person in the building to find anything out.

A card reader on stall four stopped talking at two on Saturday and nobody noticed, because the queue kept moving. The delivery apps pay that stall directly, so a third of its trade never appears in the hall's numbers at all, and the percentage rent is worked out on the part that does. Stall seven is two months behind on the service charge. Stall nine's lease renews in six weeks and the conversation has not started. Somebody's certificate of insurance expired in June.

Then there is the reconciliation itself: yesterday's totals against what the bank actually received, one stall at a time, in a spreadsheet that has been copied forward since the hall opened.

Every one of those is small on its own. Together they are why the operator is in the office on Sunday.

Hallpass

The deposit that did not arrive Yesterday's stall totals set against what the bank actually received, with any shortfall named the same week rather than at year end.

The trade that bypasses the till Delivery platform payouts read per stall and placed beside counter sales, so a percentage rent clause is worked out on the whole vendor.

Documents watched, not remembered Hygiene ratings, licences, insurance certificates and lease dates tracked per stall, each one named with its trading name and its date.

The remittance is calculated before anyone asks for it

Hallpass automates the split, and the split done by hand is where a hall quietly loses money.

Its accounting platform interfaces with the POS through an API and connects to the systems halls actually run, Toast and Square among them, gathering the day's transactions daily rather than at month end. It collects the deposits, calculates the remittance owed to each party, and distributes vendor payments net of rent and fees. Reports are generated automatically and made available to each vendor securely, so a stall can see its own numbers without an email thread. Around that sit the collections intermediary services, the contract compliance and the vendor management that make a multi-tenant building governable at all.

The common ingredient is the connected register. All of it is computed from transactions that came through a till Hallpass can see.

A stall's trade is wider than that till. Delivery aggregators pay the vendor directly, on their own schedule, into their own account. The bank is a separate login. So is the hygiene register, the alcohol licence, the insurer that issued the certificate, and the stall's own page announcing it is closed on Tuesdays in January.

A stall's real week includes sales the hall never sees

A hall's true week is the sum of several ledgers, and only one of them is inside the building.

Yesterday's totals from Hallpass set against what actually landed in the bank, so a short deposit becomes a Tuesday question rather than a March mystery. A register that stopped reporting on Saturday afternoon flagged while the receipts are still in the drawer and the day can still be reconstructed.

Each stall's delivery payouts read off the aggregator's own dashboard and set beside its counter sales, so the operator finally sees the whole vendor rather than the half that walked through the door. That one number changes what a percentage rent clause is actually worth.

Hygiene ratings and licence status checked on the public register for every trading name in the building, because an inspection result should not reach the landlord through a customer's review. Certificates of insurance watched for expiry, named by stall and by date. Lease and rent review dates lifted off the agreements onto a calendar with enough notice to negotiate.

Reading and comparing can run unattended overnight. Nothing that moves money, alters a remittance or lands in a vendor's inbox goes anywhere until somebody accountable for the number has read it.

The hall opened to sell food, not to reconcile deposits

Twelve stalls get paid on Friday whether or not anybody checked the numbers behind the payment. That is what makes the checking easy to skip, and expensive to have skipped.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the bank, the delivery platforms, the public licence register or Hallpass itself, reads what is on each screen, and sets the numbers side by side with the differences called out.

It runs on your schedule in your own private environment, and you can watch a run and stop it. Payments, statements and anything addressed to a vendor are prepared and held for a person.

Every workflow below states which sites it signs into.