Extend your setup · 5:09 · English

Customize your vehicle tuning database

Edit your account catalog, add vehicles and tuning stages, manage equipment, and review visibility and duplicate records.

Before you start

Pro or Max. Catalog edits change displayed information; they do not edit ECU files or change a vehicle.

Recorded in the Remapdb demonstration environment with example data. Use your own account details and review the saved result.

Explore the feature

Put it into practice

Check the vehicle hierarchy and availability.
Save your record and review the customer-facing result.
Follow duplicate notices and keep the intended record visible.

Open Customizations Read the guide

Follow at your own pace

Video transcript

Jump to a chapter or read the walkthrough step by step.

0:00 Your account, your catalog

Customizations controls your account’s catalog. On Pro and Max, the account owner can hide, edit, or add vehicles and equipment without changing the shared Remapdb database.

0:18 Find the right vehicle

The catalog follows vehicle type, manufacturer, model, generation, and engine. Search narrows the current table, and breadcrumbs keep the path clear. Default means shared data. Customized means you have overridden it. Added by you identifies your own records.

0:35 Visibility and availability

Visibility is an item’s own switch. Availability also depends on its parents. Hiding this generation makes its engines unavailable without changing their individual switches. Restoring the parent brings eligible children back. Individually hidden records stay hidden, and your widget’s category settings still apply.

0:56 Edit engine and tuning stages

The engine editor includes specifications, tuning stages, and equipment. Here, we update the example stage’s power and torque and save. Only overridden fields become account- specific; untouched fields keep shared values. Where offered, Reset returns a field to its current shared value.

1:16 See your changes in the widget

On the Apex Tuning website, the real widget shows our saved stage values. Customers receive your account’s effective catalog, including your changes.

1:26 Add a generation

A missing generation can be added under an existing model. Its name and years identify the new branch. After saving, it appears as Added by you. Models can be added from their parent list in the same way.

1:43 Enter engine specifications

An engine belongs beneath its generation. Here we enter the example specification: engine code, modification, compatible engine and fuel types, capacity, cylinders, and factory power and torque. The display name is generated from those details.

2:04 Add a tuning stage

Next, a tuning stage defines the offered power and torque. Its description can explain hardware requirements. At least one stage is required before the engine can be saved.

2:18 Select engine equipment

If equipment is missing, Add new creates it here. Enter its name and manufacturer, then save. The tool is selected for this engine and saved in your account’s reusable Tools catalog, where it can be edited later. The ECU selection identifies the engine control unit. The TCU links the relevant transmission control unit. Options describe additional tuning features, such as launch control. The work method records the access method, such as OBD.

2:55 Review and add the engine

Review brings the specifications, stage values, and all five equipment categories together. Check these details before saving the complete engine. Add engine saves the record. The new row then appears as Added by you.

3:10 Manage reusable equipment

In Options, select the table rows you want to change. These two checkboxes select two records. Choose Hide from Bulk actions. Both selected options become hidden together; their records remain in your catalog.

3:24 Follow duplicate notices

The orange dot flags duplicates. Hover for details, then open Vehicle catalog. Cars and L C V has a duplicate badge, so we open that category.

3:35 Follow the marked vehicle branch

We find B M W in the manufacturer list and open its marked row. Next, M three has the duplicate badge. We open that model, then follow the badge on F eighty to its engines.

3:51 Compare matching records

Here are the matching engines. Hover the duplicate badge to identify the other record. This can happen when a shared database update adds something you previously created. Both records need review.

4:03 What visitors see

Both visible, available records appear as separate choices. This can affect any vehicle dropdown, not just engines. Each choice opens its own data; duplicates are not automatically merged.

4:17 Keep the right record visible

Here we keep the shared engine and hide our duplicate. After refreshing, the widget has one matching choice. Hiding preserves the record, so the duplicate notice can remain until the underlying overlap is resolved.

4:31 Maintain your catalog

We no longer need the empty Workshop series generation. We select its row and open Delete. The confirmation names exactly what will be removed. Deletion is permanent. If this generation contained custom engines and stages, those would also be deleted, including engines linked to other generations. Shared records and reusable equipment remain. Here, the selected generation is empty. We confirm deletion. Workshop series disappears, while the other generations remain in the table.

Your next step

Put the walkthrough into practice

Start with the free widget, or compare plans for your website and application.

Start free See pricing