Multi-Accounting for Food Delivery Chains: Aggregator Dashboards
How restaurant chains and ghost kitchens manage dozens of delivery aggregator accounts without triggering antifraud flags. Proxies, roles, and setup.
Why food delivery chains run into the multi-accounting problem at all
A restaurant chain with 15 locations across three cities isn't one dashboard on Uber Eats or Glovo — it's at least 15. Add ghost kitchens, which often run 2–4 virtual brands out of a single physical kitchen under different names and menus, and each of those needs its own dashboard on every aggregator. A chain with 10 locations and 3 virtual brands per site is already 30 dashboards on a single aggregator, and most operators work with three or four: Uber Eats, DoorDash, Glovo, Wolt, plus regional players depending on the market.
All these dashboards get opened from one delivery manager's computer or a handful of laptops belonging to site managers. If they're all opened in the same browser without separation, the aggregator sees an identical device fingerprint across dozens of accounts that are physically located in different cities — and that's exactly the pattern antifraud systems on food marketplaces flag as suspicious, regardless of whether the business behind it is entirely legitimate.
Delivery platforms don't forbid chains from having many restaurant accounts — that's normal practice for franchises and ghost kitchens. What's forbidden is something else: inflating orders, generating fake reviews from sock-puppet customer accounts, dodging commission through grey schemes. Separating restaurant dashboards by location isn't a workaround — it matches the real structure of the business.
What a typical dashboard structure looks like
Take a ghost kitchen chain with 8 physical sites, each running 2–3 virtual brands across 3 aggregators.
| Level | Count | What it is |
|---|---|---|
| Physical sites | 8 | Actual kitchen addresses |
| Virtual brands | 2–3 per site | Separate menus, photos, names |
| Aggregators | 3 | Uber Eats, Glovo, Wolt |
| Total dashboards | ~60–72 | A separate profile for each |
Each dashboard needs to be tied to its own address, with a timezone that matches, and — where the aggregator checks this — an IP address that doesn't contradict the location's stated address. Opening a Lisbon kitchen's dashboard through a New York proxy is a reliable way to trigger an address verification request or a payout freeze.
Proxies: geo-match matters more than speed
For food delivery, the priority when picking a proxy isn't speed — it's geo-accuracy. You need a proxy from the same city (sometimes the same district) where the kitchen or restaurant physically operates, especially since some aggregators periodically cross-check login geolocation against the venue's registered address.
Practical recommendations:
- Residential proxies matched to the location's city. Each physical site gets its own proxy tied to the right city. For a chain with 8 sites in 3 cities, 3–8 proxies are usually enough, depending on how sensitive the aggregator is to shared IPs between neighboring dashboards in the same city.
- Don't cut corners by sharing proxies across cities. The temptation to use one cheap proxy for the whole network leads to dashboards from different cities logging in from the same IP — that's logically inconsistent for the business and reads as suspicious to antifraud systems.
- A stable IP for the dashboard's entire lifecycle. Rotating IPs mid-session while managing a menu or replying to reviews is a bad idea: some aggregators interpret a sudden geolocation jump as account compromise and temporarily lock access pending verification.
Choosing the right proxy type for a specific task without overspending is covered in detail in the piece on proxy types for multi-accounting. Setting up and checking proxies for each profile is easier with the built-in proxy manager, which shows check status and the exit IP right in the list.
Team roles: who sees which dashboard
A multi-site chain typically has three tiers of people working with aggregator dashboards:
- Chain manager — sees all locations, can adjust commission, payout settings, add new sites.
- Site manager — works only with their location's dashboards: updates menus, photos, replies to reviews, tracks rating.
- Finance — logs into dashboards only to reconcile payouts and commissions, doesn't touch operational settings.
If everyone shares one login tied to a shared inbox, there's no way to track who changed what, and when a site manager leaves, the chain either has to change the password everywhere or leave the former employee with access. The fix is a role-based model where every team member has their own login in the profile management system, and access to specific dashboards is granted precisely: a site manager gets only their own site's dashboards, finance gets view-only access with no menu editing rights.
When a site manager changes, the profile is simply handed over to the new employee without rebuilding it from scratch and without passing passwords around verbally. How to organize roles, limits, and profile handoff between employees is covered in detail in the article on team collaboration with profiles. Managing roles and per-member profile limits is handled through the team section.
- lev opened Airdrop zkSync 07
- artem closed FB · US · BM-14
- maya is watching artem
- lev transferred TikTok Shop 03
Everyday scenarios where this actually saves time
Launching a new virtual brand. A ghost kitchen decides to launch a fourth brand at an existing site. Instead of manually configuring a browser, the profile is created from a template: same proxy geo-match, same timezone, bookmarks already saved for each aggregator's menu management panel. That saves 15–20 minutes per dashboard versus setting things up from scratch.
Seasonal menu updates across all sites. When a seasonal menu changes across 8 sites × 3 brands × 3 aggregators at once, the manager opens the needed profiles one by one without losing track of which browser belongs to which dashboard — each profile in the list shows the site name, brand, and aggregator.
Checking how a customer in another city sees the restaurant. Before launching a promo, it's useful to log into the customer-facing app (not the restaurant dashboard) with an IP from the city where the promo is starting, and check how the restaurant shows up in search results, what delivery rating is displayed, whether the promo banner is visible. This requires a separate profile geo-matched to the customer's city — another example where separating profiles isn't about bypassing rules but about quality control.
Handing over management when opening a franchise. When a chain sells a franchise to a new site owner, some aggregator dashboards need to move to the new legal entity's account while preserving review history and rating. The profile with its dashboard gets transferred to another account as a whole — with saved cookies and settings, no need to log in again and risk a lockout for logging in from a new device with no history.
Common mistakes
One Chrome profile for all the chain's dashboards. The most common mistake among smaller chains: all site managers work in one browser on a shared laptop, switching between dashboards by logging out and back in. The aggregator sees an identical device fingerprint across 20+ different restaurant accounts — which is a formal trigger for manual review, even if the business is entirely legitimate.
Proxy doesn't match the site's address. Cutting corners on proxies leads to a Barcelona restaurant's dashboard logging in through a German proxy. When the address gets checked (and aggregators do this periodically, especially on fraud suspicion), a mismatch between login geolocation and the stated address is a reliable way to get payouts frozen for 3–7 days while it gets sorted out.
No single place to store 2FA for finance dashboards. Dashboards with access to payouts are usually protected by two-factor authentication. If 2FA codes live on a manager's personal phone, the chain risks losing access to payouts for several days after that person leaves, while the aggregator restores access through support. The fix is storing 2FA keys tied to the profile rather than the person, so access survives staff turnover. Encryption and 2FA storage are covered in detail in the article on profile security.
Mixing up brands at the same site. If several virtual brands live in identically named profiles like "Site 3", a manager will eventually update the wrong menu in the wrong dashboard. Naming profiles with a scheme like "City – Site – Brand – Aggregator" and grouping them accordingly is minimal but mandatory discipline. How to organize hundreds of profiles by groups, tags, and roles so a growing chain doesn't drown in chaos is covered in the article on organizing profile pools at scale.
The economics: how many profiles this costs
For the calculation, take a chain with 8 sites × 2.5 brands on average × 3 aggregators = 60 working dashboards, plus 5–10 utility profiles for checking search results and customer experience. That's roughly 70 profiles.
At that volume, the Base plan — 100 profiles for $44/month fits, with room to grow to 12–13 sites without upgrading. If the chain plans to scale past 25+ sites or add franchisees with separate access rights, it makes sense to look straight at the Team plan — 300 profiles for $79, which also provides more roles and limits for the team. Compare plans and estimate where the chain will land in profile count at its current growth rate on the pricing page. A detailed methodology for budgeting profiles, including proxies and team costs, is in the article on multi-accounting economics.
How the separation works in an antidetect browser
In GetAntik, each restaurant dashboard is an isolated browser profile: its own device fingerprint (OS, browser version, screen resolution, GPU parameters, canvas/WebGL noise), its own proxy geo-matched to the site's city, its own cookies and login history. Fingerprint settings can be viewed and adjusted in the profile editor when setting up a new site's dashboard.
Profile data is encrypted on the device with the account password — the server can't read it, which matters for chains whose dashboards hold payment details. Profiles sync across the manager's devices and can be handed off between employees when a site manager changes or a franchise launches. You can start with the free plan at 3 profiles to test the separation on a couple of pilot sites before rolling it out across the whole chain — download the app for macOS and Windows.
FAQ
Can we run multiple virtual brands out of one kitchen without risking an aggregator ban? Yes, this is standard practice for ghost kitchens and isn't explicitly forbidden by the main aggregators' rules. The risk doesn't come from having multiple brands — it comes from all the dashboards being opened with the same digital device fingerprint and proxy, which looks like one entity masquerading as several. That's exactly what antifraud catches.
Do we need a separate proxy per dashboard, or is one per site enough? Usually one stable proxy per physical site is enough, used for all brands and aggregators at that location — as long as the aggregator doesn't check for shared IPs between neighboring dashboards of the same brand on different platforms. For a more conservative approach, use a separate proxy for each brand-plus-aggregator pairing.
What do we do if an aggregator requests address verification for a site? This usually requires a lease or ownership document plus a match between recent login geolocations and the registered address. If the dashboard has always logged in through a proxy from the right city, that resolves most of the issue automatically — problems arise specifically when the proxy didn't match the address.
How quickly can we restore access if a site manager leaves without handing over passwords? If the dashboard profile lived in a shared profile management system rather than the employee's personal browser, access is simply reassigned to a new manager without contacting the aggregator's support. That's one of the main reasons chains move away from a shared laptop with passwords in a notes app toward isolated profiles with role-based access.