Your customers and dealers read the ECU with their Alientech tool and upload the file to your portal. The request keeps the tool, the vehicle and the requested options together.
The portal is built around the tools already on your bench, Alientech among them.
Four-step upload: vehicle, tuning options, file and submission, so a request arrives complete.
The reading device the customer used stays attached to the request.
Vehicle data from a 67,000+ vehicle database, filtered by ECU and reading device.
The tuner opens the work queue with vehicle and customer history already attached.
File status reaches the customer by SMS and email as it changes.
Credit packages, invoices and PDF receipts run in the same customer account.
What the customer picks on the request
The customer picks Alientech from the reading device list, then the reading type: Full Read, ID Only or Virtual Read.
Each file can be up to 64 MB. Server scripts and executables are refused; other file types are accepted.
The file is recognised on upload
After the upload the portal analyses the file and proposes the ECU behind it: either an exact match or a ranked list of candidates the customer chooses from.
When the file is too small, carries too little signal or matches conflicting signatures, the request is marked for manual verification instead of carrying a guessed ECU.
Master and slave dealers
If your dealers work as slaves to your master file service, open a customer account for each of them and put them in a customer group: their own files and invoices, the group’s price and a slave credit wallet. A dealer sees only the files, vehicles and invoices of their own account.
Questions
Does the portal read or write the ECU?
No. Reading and writing stay in the Alientech software. The portal carries the file, the vehicle context and the payment.
Can the tuner see which tool made the read?
Yes. The reading device the customer used stays attached to the request.
Can dealers have their own prices?
Yes. Each customer group applies a percentage or a fixed amount to the price list, so dealers in the same group share one price.
Does the customer pick KESS3 or K-TAG separately?
No. The reading device list has one Alientech entry; the reading type (Full Read, ID Only or Virtual Read) and the note on the request carry the rest.
Does the portal guess the ECU from the file?
It proposes one only on an exact match or as a ranked list of candidates. Anything less certain is marked for manual verification.
