Vehicle and engine selection
Use catalog records to help visitors identify a vehicle variant. Check the entries relevant to your range before publishing.
For tuning box and piggyback module providers
Help visitors select their engine and review vehicle information before enquiring about a piggyback module. Use Remapdb for vehicle records, alongside the module-fitment and performance evidence you maintain on your own product pages.
Generic tuning reference gains are not proof of your module’s results or compatibility. Your business must supply and verify those product claims.
How Remapdb fits
A visitor needs to know which engine they have and whether your module is appropriate for it. Remapdb helps with the vehicle-selection and reference-information part. Your team remains responsible for matching a module to that vehicle, its installation requirements, and the results you advertise.
Use catalog records to help visitors identify a vehicle variant. Check the entries relevant to your range before publishing.
On Pro and Max, adjust catalog tuning values to reflect the information you are prepared to support. Keep your underlying test evidence and explain the applicable hardware and conditions on your product page.
Collect the selected engine and customer details through the widget, or connect vehicle records to your own product interface with the API.
Your setup
Review the engines you sell for in the demo. Decide how your own product identifiers and compatibility rules map to those records.
Keep generic reference tuning figures separate from measured results for your module. Use catalog editing where appropriate and describe test conditions in your own copy.
Confirm that the customer selects the intended engine and reaches the correct enquiry or product workflow. Your checkout and fulfilment remain in your existing system.
Before you choose
Remapdb does not provide a verified fitment catalog for your hardware or certify its performance. A displayed graph is based on stored values; it is not evidence that your module achieved those values on a dyno. Do not present general Stage 1 remap figures as measured piggyback results.
FAQ
Only make product claims you can substantiate independently. General tuning figures in the catalog do not demonstrate the performance of your specific module.
No. You supply and verify the mapping between your product and the vehicle. Remapdb supplies vehicle information that can be used in your interface.
Pro and Max include catalog editing in the app. Max also lets API v2 read your customized catalog. Editing displayed figures does not validate their accuracy.
The widget collects enquiries. Your product checkout, payment, inventory, and shipping are handled by your own ecommerce or sales system.
Explore the features
See how each feature works, what it includes, and which plan gives you access.
See how to change the displayed tuning values and vehicle visibility for your account on Pro and Max.
Explore customizationsAdd vehicle selection and an enquiry form alongside your own module information and evidence.
Explore widgetRetrieve vehicle records for an interface connected to the product and compatibility mappings you maintain.
Explore APIYour next step
Review the relevant engines and choose how to present your own supported module results alongside the vehicle data.
Generic tuning reference gains are not proof of your module’s results or compatibility. Your business must supply and verify those product claims.