Platform
Beiond Franchise
Operations software for franchise networks
Head office owns the brand, the pricing and the catalogue. Each franchisee runs its own territory, its own crews and its own vehicles. Beiond Franchise keeps both halves honest — bookings, dispatch, payments and the monthly settlement between them.
The part nobody else has
It knows when the weather will ruin the job.
Field services fail on weather, and most software pretends otherwise. Beiond Franchise checks the forecast for the customer's actual location at the actual booked slot. If rain is likely, the booking only goes through when the customer confirms covered space — and a scheduled re-check can move an already-confirmed job if the forecast turns. The rule is enforced on the server, not suggested in the interface.
What it runs
Booking and dispatch
Availability by territory, automatic or manual assignment, blocked slots, coverage requests for postcodes nobody serves yet.
Live tracking
Crew and vehicle positions over WebSockets, plus a fleet map fed by vehicle telematics.
Payments and invoicing
Card, MB Way, instalments and recurring billing, with certified invoicing behind the same interface.
Head-office store
Catalogue, cart, checkout, shipping, orders and stock movements, owned centrally and sold across the network.
Memberships and referrals
Subscription plans, a referral scheme and a credit ledger that survives audit.
B2B fleet accounts
Corporate customers with their own vehicles, recurring schedules and consolidated invoices.
Day close
Crews close the day with photos and totals; the system produces the franchise-fee statement from it.
Fee settlement
A configurable head-office percentage, reconciled monthly, with receipt upload built into the flow.
White label
A second network is a config file, never a fork.
Brand identity, locale set, currency, timezone, payment methods, design tokens and the country-specific formats for postcodes, number plates, phone numbers and tax IDs all live in one validated configuration. Onboarding a different franchise network in a different country means a config, a seed pack and an asset set. We proved it by standing up a second brand in a second country and running the full test suite against it unchanged.
Scale
- 61
- Database tables
- 198
- API endpoints
- 140
- Test suites and specs
- 2
- Languages, enforced in CI
Built with — NestJS · PostgreSQL · Next.js · React Native · TypeScript end to end
Who it fits
Built for networks where head office and franchisee both need the truth.
Mobile services, home services, maintenance rounds, anything dispatched to a customer's address by crews who do not sit at a desk. If your franchisees are running on spreadsheets and WhatsApp, this is the shape of the replacement.