Managing slaves in a file service means two things: delivering each customer the file encrypted for their tool, never the plain read, and keeping the credits they pay you with in order, with a price list that suits resellers. A portal built for this knows who is a slave, decodes and re-encodes the file for each tool and takes payment in credits before you start working.
Who is a slave and why it matters
A slave tool is tied to your master tool and can only write files encrypted for it. If you deliver a plain read, the customer cannot use it and you lose time. The opposite case is a master customer, who rewrites the read with their own licence and can receive the plain file. For Magic Motorsport Flex TuningFile reads the slave list from your account and matches each customer by e-mail or name; for the other encrypted formats the customer is treated as a slave.
The right file for each tool
- KESS3: Boot/Bench or OBD decode and encode with your Alientech account.
- Autotuner: decode and encode with your Autotuner Cloud account.
- Flex: decrypt and encrypt with your Magic Motorsport account, with a master/slave check.
- Dimsport .TFP and .FPF: with a worker PC running your DSManager licence; the customer gets the Slave file.
In every case, if you are about to deliver what looks like a plain read to a customer who needs the encrypted file, the platform stops you.
The automated path
Where you save the most time is the file’s path, which on TuningFile can run on its own:
- The slave uploads the file read with their tool and pays in credits.
- The platform decodes the file with your tool account.
- Original and read go into a folder on your Google Drive, one per file service and ticket.
- AutoRemap, the WinOLS bot, prepares the modified file from your database.
- The file is encrypted again for the slave’s tool.
- The file reaches the customer, with an e-mail notice.
- The invoice was already issued when the customer bought the credits.
You can keep a manual check: choose which formats go out on their own, and incomplete files always wait for the technician. All on the automated A-to-Z workflow page.
Credits: price lists and groups
- Credit price list for every service and option.
- Customer groups with different price lists: for example workshops that resell pay fewer credits for the same job.
- Tiered packages: the more credits a customer buys, the less a credit costs; tiers are assigned per group too.
- Online purchase by card, PayPal or bank transfer, with an automatic invoice.
Manual top-ups, refunds and history
You can add or deduct credits by hand with a reason, and the customer sees it in their history. If you cancel a request, the credits go back to the customer automatically. The customer profile also shows the tools they declared at sign-up.
Flex slave expiries
For Magic Motorsport slaves you can set each one’s yearly expiry: the platform e-mails you at 30 and 7 days, and “Renewed” moves the date to the next year.
For the platform costs read what it costs to start a file service; for master versus slave see the master vs slave guide.
Want to see it under your brand? See the automated A-to-Z workflow or check the pricing and open your portal.
