Every partner's numbers, from the POS, not from a form.
marql reads each franchisee's own systems and turns them into one scorecard per partner — revenue, growth, checklist completion, and the royalty their contract rate implies.
Partners · demo network
last 30 days
| partner | revenue | vs prior 30 | checklist | royalty est. |
|---|---|---|---|---|
| City Center4 units | 118 400 € | +6.2% | 92% | 5 920 €5.0% |
| Westside3 units | 74 900 € | −3.1% | 71% | 4 494 €6.0% |
| North Park2 units | 51 200 € | +1.4% | 100% | 2 304 €4.5% |
| Harbour2 units | not connected yetno verified revenue — no royalty is computed, and none is guessed | |||
| networkthree partners reporting | 244 500 € | 12 718 € | ||
royalty estimate = each unit's POS revenue × your rate for that partner
A partner connects once; the royalty estimate follows from the POS.
Each partner keeps their own POS and their own accountant. What has not been connected is named as not connected, never estimated.
Each partner connects their own systems
Read-only access to the POS the unit already runs, plus whatever accounting or export path the partner already uses. No system is replaced, and marql reads the partner's POS and accounting without changing them.
Revenue becomes the same number for both sides
Units, products and currencies are normalised into one model, so the franchisor and the partner are reading one figure rather than two that need reconciling.
Partner not connected — no revenue and no royalty is computed for them
The royalty estimate follows from it
Each unit's POS revenue is multiplied by your rate for that partner, giving a royalty estimate per unit and per partner, on the same basis for everyone.
The checklist is read the same way
The onboarding playbook you wrote is tracked per unit, so a partner's completion is a number rather than an impression — and a step every partner skips shows up as your problem, not theirs.
Today it is built by hand
A recruiting page that computes its own numbers.
Public pitch page · demo network
marql.one/franchise/your-network
786 store-days · data as of 15 Aug
- Avg. daily revenue per location
- ~1 240 €
- Average ticket
- 16.40 €
- Month-over-month growth
- +4.7%
- Active locations
- 9
- Avg. days to first revenue
- 34 days
computed from 786 store-days over 90 days
weighted across 9 locations
last 30 days vs the 30 before
currently connected
registration to first recorded sale
Interested in a location?
The form on the page writes straight into your pipeline.
Request the packverified means at least 14 store-days of data in the 90-day window · you choose which metrics the page shows, and whether it is public at all
The questions a network asks every month.
Who is growing, who owes what, who is following the model, and what a prospective partner is shown before they call you.
A scorecard per partner
Revenue, month-over-month growth, checklist completion and the per-unit breakdown, on the same basis for every partner in the network.
The monthly call starts from one page instead of four attachments.
Royalty estimates from the POS
Each unit's POS revenue multiplied by your rate for that partner: a royalty estimate per unit, on a basis both sides can read.
You and the partner start from the same figure before the invoice.
Checklist adoption, per step
The same onboarding tasks read across the whole network rather than per partner — drawn below.
You find out whether it is a partner problem or a playbook problem.
A verified pitch page
A public page for recruiting whose metrics are computed from connected locations, with the store-day count behind each one and a lead form underneath.
Prospective partners get numbers with a provenance instead of a brochure.
Partners see their own units
A franchisee gets a read-only portal scoped to their locations, with the network average and their rank beside them; the franchisor sees the network. Configured once, by role.
You can hand a partner real access without handing them the network.
One network, several countries
Parent and child organisations with money converted to the network's base currency, and network figures weighted by revenue rather than averaged.
A large market stops carrying the same weight as a small one.
Onboarding playbook · adoption by step
across every partner unit- Brand kit installed100%
- Staff trained92%
- Supplier contracts signed84%
- POS connected78%
- Local launch campaign46%
a step every partner skips is the franchisor's problem, not the partner's · the playbook is yours to write
Where marql stops and your franchise agreement starts.
This page is about numbers two parties have to agree on, which is exactly where a vague claim costs the most later.
Compliance here means the completion rate of the checklists you wrote.
It is not a hygiene, safety or brand audit, and it does not replace a visit — a fridge temperature is not in anyone's POS.
A partner who has not connected has no computed revenue and no computed royalty.
marql will not carry a self-reported figure into the same column as a verified one.
The royalty is an estimate, POS revenue × your rate; the invoice you send and the money you collect stay in your own billing.
"Verified" on the public page means at least 14 store-days of data inside the 90-day window.
Below that the figure appears without the badge rather than with a borrowed one.
marql reads a partner's POS and accounting without changing them.
With e:corg 2.0, e:corg creates an approved order or transfer as its own draft.
The partner scorecard and portal come as the Franchise Pack, which we set up with you; it runs in the classic workspace.
Both sides of the connect conversation.
That is the normal case for a network that grew by signing partners rather than opening units. Each partner connects what they already run and marql normalises products, categories, VAT and currency into one model — 151 connectors are live today, and anything else with a REST API or a scheduled CSV export is mapped without custom code.
Not their figures. A partner's portal is scoped to their own units — their revenue, their checklist, their royalty estimate — with the network average and their rank beside them. The franchisor sees the network. It is a role, configured once, not a permission argued about per report.
Your rate for that partner is applied to the revenue each unit's POS reported, which gives a royalty estimate per unit and per partner. Both sides read the same basis before anything is invoiced. Rates are per partner, so legacy contracts do not have to be flattened into one number.
No, and we would rather say so here than let you discover it later. It is the share of the onboarding checklist you wrote that a partner's units have actually completed, averaged across those units. It tells you who is following the model on the things software can see. Hygiene, presentation, equipment and everything else that needs a person in the room still needs a person in the room.
It is a page you can publish for recruiting new partners: average daily revenue per location, average ticket, month-over-month growth, active locations and average days from opening a location to its first recorded sale — each computed from connected data over the last 90 days, with the number of store-days behind it shown. The badge appears when there are at least 14 store-days in that window. You choose which metrics appear and whether the page is public at all, and the form on it writes into your pipeline.
Usually read-only API access to the POS, plus whatever accounting or export path they already use. No partner is asked to replace a system or change how they work day to day, and marql reads their POS and accounting without changing them.
Per location, on a graduated ladder: €200 a month for each of the first nine, €185 for locations 10 to 29 and €160 for 30 to 49. Each rate applies only to the locations inside its band, so a network of twenty units is €3,835 a month. From 50 we map the stack first and then quote. The calculator is on /pricing.
Ready to see
the euros it found?
The walkthrough is built around the POS and accounting you already run. Leave your details and pick a time.