Building a Sub-Dealer Network for Your Chiptuning Business: Master Portal + Sub-Tuners + Cross-Portal File Routing

The natural growth pattern for a chiptuning workshop has three stages. Stage one: you tune customer cars yourself, one at a time, and bill direct. Stage two: you hire a second tuner, split the workload, and the business has two engineers but one brand. Stage three: other workshops in nearby towns send you their files because their own engineers can’t tune ECU families outside their training. You become a master tuner with a network of sub-dealers.

Stage three is where the operational model breaks down in most chiptuning portals. The portal was built assuming one company, one set of customers, one engineer pool. A master-with-sub-dealers model needs two layers of attribution (the master who delivers the file, the sub-dealer whose customer originated it), wholesale-tier pricing (sub-dealers pay less than retail), a shared file library (so a sub-dealer asking for a Bosch EDC17 tune on a Vauxhall Astra gets served from the master’s existing files instantly), and clean handover when a sub-dealer escalates to the master.

This post lays out how the master/sub-dealer model actually works in production, what the cross-portal routing looks like, and the operational pitfalls — billing, attribution, branding — that catch out workshops trying to bolt this onto a portal that wasn’t designed for it.

What a “sub-dealer network” actually is

A master tuner runs their own portal — branded as their workshop, customer-facing, with their own price list. A sub-dealer is a smaller workshop in another town that:

• Doesn’t have the technical depth to tune every ECU family their customers ask for
• Doesn’t want to commit to a £699 portal licence + admin overhead
• Has end-customers (vehicle owners) who pay them directly for tuning work
• Sends some-or-all of their files to the master to actually tune, then re-sells the result

In a healthy network this is a win for everyone:

• The master gets predictable wholesale revenue from 5-20 sub-dealers, often £3,000-£8,000/month, on files that take 15-45 minutes each.
• The sub-dealer keeps their customer relationship and brand visibility, doesn’t have to learn every ECU family, doesn’t carry the IT overhead.
• The customer gets the tune faster than the sub-dealer could deliver it alone, with the sub-dealer still as their single point of contact.

The whole arrangement only works if the technical pipeline between master and sub-dealer is invisible from the customer’s perspective.

The five routing strategies

When a sub-dealer submits a file to a master, the master needs to choose how the work is allocated. Five patterns cover essentially all real-world workflows:

Strategy 1 — All work to the master (default)

Every file from the sub-dealer flows to the master’s queue. The master’s engineers tune all of it. The sub-dealer’s portal is purely a customer-intake front-end.

Best for: new sub-dealers who can’t tune anything themselves yet.

Strategy 2 — Sub-dealer handles common stuff, master handles tricky stuff

The sub-dealer’s own engineers handle Stage 1 on common ECU families (EDC17, MED17). Anything outside their training — exotic ECUs, BDM/boot-mode files, specific delete jobs, performance dyno targets — auto-routes to the master. The router can match by ECU family, by modification type, by vehicle make, or by a custom rule.

Best for: experienced sub-dealers who want to keep margin on simple work.

Strategy 3 — Master only sees escalations

The sub-dealer’s engineers handle everything by default. The master only sees a request when the sub-dealer explicitly escalates it (“I can’t read this ECU”, “Customer is unhappy with my tune, can you check”). Escalation is a single button on the sub-dealer’s request detail page.

Best for: mature sub-dealers with a technical team; master is the safety net.

Strategy 4 — Capacity-based load balancing

When the sub-dealer’s queue is over a threshold (e.g. > 4 open requests), new files auto-route to the master. The master takes the overflow. When the sub-dealer’s queue drains, they resume handling their own files.

Best for: sub-dealers with seasonal demand (e.g. summer track-day workshops).

Strategy 5 — Pure brokerage

The master tunes 100% of every sub-dealer’s files. Sub-dealers never see the tuning tooling; their portal is essentially a customer-facing storefront. The master’s brand is invisible to end-customers.

Best for: master operators running a wholesale-only business; sub-dealers who don’t have tuning engineers at all.

A real network typically uses different strategies per sub-dealer — Strategy 1 for the new ones, Strategy 3 for the experienced ones, Strategy 4 during busy months.

Attribution: the trap

The single most common bug in master/sub-dealer setups is customer attribution loss. A file arrives at the master’s queue and shows the sub-dealer’s name as the customer, not the actual end-customer (the vehicle owner). Three things break:

1. The master can’t address the customer by name in the conversation thread (“Hi Daniel, the tuned file is ready” → “Hi Sub-Dealer Workshop, the tuned file is ready” — wrong)
2. The completion certificate goes out with the wrong name
3. The master’s CRM thinks every sub-dealer is one customer with 500 vehicles

Correct behaviour: when a file forwards from sub-dealer to master, both identities are preserved. The master sees:

End-customer: Daniel Baltac (BD68 KZX, Audi A4 2.0 TDI)
Source: Workshop X (sub-dealer)
Wholesale: Yes — billed at £20/credit (not £40 retail)

The conversation thread, the certificate, the completion email all use the end-customer name. The internal routing knows the sub-dealer is the source for billing purposes, but the customer-facing surface is the end-customer.

This sounds obvious. It is not how most portals work by default. Files forwarded from sub-dealer to master commonly lose the end-customer identity entirely and surface as “request from Workshop X”.

Wholesale pricing tiers

Sub-dealers expect to pay less than retail per credit. A typical structure:

The sub-dealer’s portal displays retail pricing to end-customers (£40/credit, framed as “£40 per ECU service”). The sub-dealer’s wallet balance with the master is in wholesale credits (£20-each). The margin (£20-25 per file, depending on tier) is the sub-dealer’s revenue without lifting a soldering iron.

For this to work cleanly, the master’s portal needs:

• Per-sub-dealer pricing-tier configuration
• A wallet balance per sub-dealer (so the master is paid before tuning happens)
• A top-up flow on the sub-dealer’s side that adds credits to that wallet
• Auto-deduction on each file submitted (so the wallet drains as the sub-dealer earns)

The wallet model prevents the worst sub-dealer failure mode: a sub-dealer who racks up £2,000 of files and disappears. Pre-paid wallet = no debtor risk.

Top-up methods that actually fit small workshops

Sub-dealers running 5-50 files a month don’t want to manage manual bank transfers or PayPal invoices. Two methods cover the realistic spectrum:

Method A — Stripe card top-up. Standard checkout flow, instant credit. Works for sub-dealers with healthy cash flow.

Method B — UK monthly finance (Payment Assist or similar). Spread a £500-£2,500 top-up over 3-12 months at low APR. Useful for sub-dealers building inventory of credits during a slow season. The credit lands in the wallet immediately; the sub-dealer pays the finance provider on a schedule.

Allowing both is most flexible. Forcing one (especially the manual bank-transfer-only model) is a recurring complaint in chiptuning network communities.

The sub-dealer dashboard — what they actually see

A sub-dealer’s portal looks almost identical to the master’s, with three deliberate differences:

1. No view of other sub-dealers’ work. Each sub-dealer sees only their own requests. The master is the only party with visibility across the whole network.
2. Wholesale pricing on file submissions. When the sub-dealer submits a file, they see the wholesale price they will pay. End-customer pricing is configured separately, in their own retail front-end.
3. A “Forward to master” pill on every request once they submit. If they want to handle it themselves (Strategy 2/3), they don’t click forward. If they want the master to handle it, one click escalates.

The end-customer’s view is the sub-dealer’s brand only — no mention of a master, no “Powered by” footer, no leak of the wholesale tier. The end-customer never knows there’s a network behind their tune. That’s the entire point.

Avoiding the “wholesale leak”

Three places where a master/sub-dealer setup leaks the master’s identity to the end-customer:

• Conversation thread. When an engineer at the master replies in the chat, the message must appear under the sub-dealer’s brand (engineer name = sub-dealer’s tuning engineer, not the master’s). The master’s actual engineer name is internal only.
• Email sender. Completion emails go from the sub-dealer’s mail-from address, not the master’s. SPF/DKIM configured per sub-dealer.
• Certificate PDF. The branded certificate uses the sub-dealer’s logo, not the master’s. If the master ships a certificate with their own logo, the leak is on the customer’s wall within 24 hours.

This is the white-label discipline applied to a network: every customer-facing artefact must be brand-neutral to the master and 100% in the sub-dealer’s brand. The technical routing happens invisibly underneath.

Shared file library — the multiplier

The killer feature of a master/sub-dealer network isn’t routing. It’s the shared library.

When a sub-dealer submits a file with SW number 03L906022KP_4945 (a common Audi/VW 2.0 TDI EDC17C46 calibration), and the master has previously tuned that exact SW+HW combination for another sub-dealer’s customer, the master’s library already contains a tuned version. The new request can be served from the library in 30 seconds — no actual tuning work, no vendor decrypt cost.

The economics: the master charges the sub-dealer the wholesale rate (£20/credit, say) regardless of whether the work is fresh or from library. On the 30% of files that match library, the master’s margin is essentially 100%. The sub-dealer doesn’t care — they got their file in 30 seconds instead of 30 minutes.

Workshops with mature libraries (5,000+ historical files indexed by SW + HW + SHA) report 35-55% library match rates on incoming requests. That’s the difference between a tuning business and a tuning platform.

When the network gets big — operational shape

At 5-8 sub-dealers, the master’s two-engineer team handles everything fine. Around 12-15 sub-dealers, the master’s engineer queue starts overflowing during peak hours (Friday afternoons before weekend track days are a real bottleneck).

Three operational moves help:

1. Capacity-based routing (Strategy 4) on the high-volume sub-dealers, so their files flow back to the sub-dealer’s own engineers during the master’s busy hours.
2. Engineer specialisation tags. The master’s two diesel engineers don’t take petrol work; the petrol engineer doesn’t take Audi BDM jobs. Routing matches by specialisation.
3. A second master tier. Some networks run a “lead engineer” master + 2-3 “second-tier master” workshops. Tricky escalations from sub-dealers flow up the chain. Master-of-masters routing is the same five strategies applied recursively.

This is operationally complex enough that most portals don’t model it. The ones that do (TunerSuite’s multi-technician feature is built around exactly this pattern) treat the master/sub-dealer link as a first-class entity, not a hack on top of a single-tenant model.

What this looks like in TunerSuite

A workshop running TunerSuite v2.8.140+ as a master portal:

• Sub-dealers run their own TunerSuite installs, each licensed for £699 one-time, fully white-labelled.
• The master enables “Network sharing” in their settings; each sub-dealer enables “Forward to master” in theirs.
• Files submitted to a sub-dealer’s portal can auto-forward or manual-forward to the master, with all five routing strategies configurable per sub-dealer.
• End-customer attribution is preserved end-to-end — the master sees who actually owns the car.
• Per-sub-dealer pricing tiers, per-sub-dealer wallet, per-sub-dealer top-up methods (Stripe + UK monthly finance).
• Shared library cross-references against the master’s full file history, with SHA + SW+HW + ECU-family match strategies.
• AI Match auto-delivers from library when a matching file exists; the sub-dealer’s customer gets the tuned file in under a minute.
• Cross-portal billing summary shows the sub-dealer their wallet balance, recent debits, and runway estimate.

The entire network model is bundled into the £699 TunerSuite licence — there is no separate “network edition” pricing tier. A workshop running one portal today can scale to 15 sub-dealers without paying anything else.

FAQ

Do sub-dealers see other sub-dealers’ work?
No. Each sub-dealer’s portal is isolated. Only the master has cross-network visibility. Sub-dealers can’t see each other’s customers, files, pricing, or volumes.

Can a sub-dealer be promoted to a master themselves?
Yes. If a sub-dealer eventually scales their own engineer team and wants to take on their own sub-dealers, their portal flips to master mode with one setting change. Their existing customers continue uninterrupted; new sub-dealers slot in underneath them.

Who owns the tuned files in a network?
The end-customer owns the file they pay for. The sub-dealer who took the customer’s payment delivers it to them. The master who tuned it owns the indexed entry in the shared library for future matching — but cannot share that customer’s specific file with another sub-dealer without explicit permission (and most networks never do).

What’s the legal model for the master/sub-dealer relationship?
A simple wholesale supply agreement. The master sells tuning capacity to the sub-dealer at a wholesale rate; the sub-dealer resells to end-customers at their own retail price. No employer/employee relationship, no franchise law issues. A one-page agreement on letterhead covers most jurisdictions.

Can I run a master/sub-dealer model on a SaaS portal?
Some SaaS portals offer “wholesale” pricing tiers but most do not model the dual-attribution and per-sub-dealer billing properly. The most reliable path is to run your own portal (self-hosted gives you the database, the customisation, the data, and zero per-sub-dealer fees) and add sub-dealers under it.

Next step

If you’re a workshop owner at stage 2 of the growth path (one workshop, multiple engineers, fully loaded), the master/sub-dealer model is the natural way to add revenue without adding fixed costs. The TunerSuite £699 one-time licence covers the full network model — no per-sub-dealer fees and no cut of what you charge them. You pay £49.99/month for the master; each sub-dealer node is a line on the same invoice.

If you’re already running a network on a portal that wasn’t designed for it (single-tenant SaaS, custom WooCommerce setup, file submissions over email), the migration is straightforward and there’s a guide to migrating from MyTuningPortal that covers the most common starting point.

For the operational side of how engineers and customers actually communicate inside the network, see the live chat workflow guide. For the brand-safety side, see white-label.