Scale
From one shop to a franchise, without a rebuild
Franchise, marketplace, shop and staff form a clear hierarchy. A master catalogue pushes down to every branch, each branch keeps its own pricing, fleet and settings, and staff roles carry per-route permissions. Marketplace mode is on the Enterprise plan.
Locations
Locations
A location is stock, a pickup store and a team
Every location keeps its own stock count, can act as a pickup store and has its own staff. Starter includes 1 location, Growth 1 and Scale 3; extra locations are an add-on on Scale, up to 53 in total.
- Stock per location and a pickup store at each one, on every plan
- Per-location staff roles for staff and riders, on Scale
- Delivery zones per location, with orders routed to that location's staff, on Scale
- Extra locations as an add-on, on Scale, up to 53 in total
Structure
Structure
Franchise → Marketplace → Shop → Staff
A franchise sits above one or more marketplaces, each marketplace above its shops, each shop above its own staff. A master catalogue is built once at the top and pushed down to every branch beneath it.
- Franchise, marketplace, shop and staff — a clear four-level hierarchy
- Master catalogue built once, pushed to every branch
- Each level owns its own settings without breaking the level above
- A branch can still add its own products alongside the master catalogue
Per-branch control
Per-branch control
One catalogue, different prices and fleets
Inheriting the master catalogue does not mean inheriting the same price. Each branch sets its own pricing, runs its own delivery fleet, and can publish its own branded app (a paid add-on).
- Per-branch pricing on top of the shared catalogue
- Own delivery fleet per branch
- Own branded app per branch (paid add-on), from the same build pipeline
- Own settings per branch — slots and gateways; per-location delivery zones on Scale
Marketplace · Enterprise plan
Marketplace · Enterprise plan
A service area, and vendors who apply to join it
On the Enterprise plan, a marketplace draws a geo-polygon service area, then shops apply and are approved into it — with their own category sliders and banners once they are in.
- Geo-polygon marketplace service area
- Shops apply, then are reviewed and approved
- Marketplace-level staff, separate from any one shop’s staff
- Category sliders and banners at the marketplace level
Staff roles
Staff roles
A role for every job on the floor
Manager, junior product manager, delivery-guy manager, report analyst, picker and agent are built on Spatie roles with per-route permission checks, so a role sees only the screens and actions it should.
- Manager, junior product manager, delivery-guy manager, report analyst, picker, agent
- Built on Spatie roles with granular permissions
- Permission checks enforced per API route, not just per screen
- Roles apply at the shop, marketplace or franchise level as needed
Specification
Every detail, spelled out
Hierarchy & catalogue
- Levels
- Franchise, marketplace, shop, staff
- Master catalogue
- Built once, pushed to every branch
Locations
- Included
- Starter 1 · Growth 1 · Scale 3
- Extra locations
- Add-on on Scale, up to 53 in total
- Each location
- Its own stock, pickup store and staff
- Zones & routing
- Per-location delivery zones, orders routed to location staff, on Scale
Branch autonomy
- Pricing
- Per-branch, on top of the shared catalogue
- Delivery fleet
- Own fleet per branch
- Apps
- Own branded app per branch (paid add-on)
Marketplace & vendors (Enterprise)
- Service area
- Geo-polygon marketplace areas
- Vendor onboarding
- Apply, review, approve
Roles & permissions
- Roles
- Manager, junior product manager, delivery-guy manager, report analyst, picker, agent
- Permission model
- Spatie roles with per-route permission checks
FAQ
Questions about Multi-branch & franchise
Do all branches have to sell the same catalogue?
Can each branch run its own delivery fleet?
How does a shop join a marketplace?
How many locations can I run?
What roles come built in?
Are permissions checked on every action or just the menu?
Plan your branch rollout with us
We will map your hierarchy before the first branch goes live.
No card required · Live in a day · Support in Arabic and English