# API
Source: https://docs.remapdb.com/api

Connect Remapdb to your backend or internal tools with clear setup, endpoint, and operations guidance.

Use this section to set up and run API access safely, including direct API requests, SDK workflows, and MCP-based AI tool connections.

Need endpoint-level request/response details? Open the [API reference](/api-reference/introduction).

Click the [**API**](https://app.remapdb.com/api) item in the main navigation.

## Use this section when

* You want to pull Remapdb data into your own backend.
* You want to automate workflows outside the Remapdb interface.
* You want to connect AI tools to Remapdb vehicle tuning data through API access.
* You need a clear setup path for credentials, endpoint usage, and daily request planning.

<Info>
  API access depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

<Warning>
  Never place API credentials in frontend code, browser storage, or public repositories. Keep them on your server or secure environment.
</Warning>

## What you can do from the API page

* Copy your `API key` and `API secret`.
* Click the **Generate new credentials** button when you need to rotate keys.
* Click the **API documentation** link for endpoint contracts.
* Open [API reference](/api-reference/introduction) for interactive endpoint docs.
* Use API access with MCP-based AI tools through [AI Integrations](/api/ai-integrations).
* Click the **PHP SDK** or **JavaScript SDK** link if you prefer SDK-based integration.

## Recommended order

* Start with [Credentials and authentication](/api/credentials-and-authentication).
* Connect [Remapdb AI Integrations](/api/ai-integrations) if you want MCP-based AI tools to use vehicle data through API access.
* Continue with [Best practices](/api/best-practices) before go-live.
* Check [Usage limits](/api/usage-limits) so traffic stays stable.
* If credentials are locked, open [Plan access](/api/plan-access).

## Success looks like

* Your integration authenticates successfully.
* Your requests return expected data in staging and production.
* You can monitor usage and rotate credentials without downtime.

## Pages in this section

<div>
  <Columns>
    <Card title="Credentials and authentication" href="/api/credentials-and-authentication">
      Copy, store, and rotate API credentials safely.
    </Card>

    <Card title="AI Integrations" href="/api/ai-integrations">
      Use API access to connect MCP-based AI tools to Remapdb vehicle tuning data.
    </Card>

    <Card title="Best practices" href="/api/best-practices">
      Use security, reliability, and rollout standards that prevent outages.
    </Card>

    <Card title="Plan access" href="/api/plan-access">
      Check which plans include API access and unlock credentials if needed.
    </Card>

    <Card title="Usage limits" href="/api/usage-limits">
      Plan daily request volume and avoid limit-related interruptions.
    </Card>

    <Card title="API reference" href="/api/api-reference">
      Browse interactive endpoint documentation.
    </Card>
  </Columns>
</div>


# Engine Details
Source: https://docs.remapdb.com/api-reference/engines/engine-details

/openapi.json get /engines/{engine_id}
Show engine metadata along with its performance and tuning information.



# Engines by Generation
Source: https://docs.remapdb.com/api-reference/engines/engines-by-generation

/openapi.json get /engines/generation/{generation_id}
Show all engines from specific generation.



# Generation Details
Source: https://docs.remapdb.com/api-reference/generations/generation-details

/openapi.json get /generations/{generation_id}
Show all generation metadata along with its corresponding engines.



# Generations by Model
Source: https://docs.remapdb.com/api-reference/generations/generations-by-model

/openapi.json get /generations/model/{model_id}
Show all generations from specific model.



# Introduction
Source: https://docs.remapdb.com/api-reference/introduction

Use the Remapdb Vehicle Tuning Database API to browse the vehicle hierarchy, retrieve detailed engine and generation metadata, validate API access, and build vehicle search and quoting workflows.

## Remapdb Vehicle Tuning Database API

The Remapdb REST API lets you programmatically access comprehensive vehicle details, including types, manufacturers, models, engines, ECU and TCU info, tuning tools, dyno charts, and available tuning or remap stages with their performance gains.

<Info>
  Need AI tools to search this data for you? API access also supports MCP-based setup through [AI Integrations](/api/ai-integrations).
</Info>

## Endpoints

* [`GET /subscription`](/api-reference/subscription/active-subscription): Check whether the authenticated API key has active API access.
* [`GET /types`](/api-reference/types/vehicle-types): List available vehicle types.
* [`GET /manufacturers/type/{type_id}`](/api-reference/manufacturers/manufacturers-by-type): List manufacturers for a vehicle type.
* [`GET /manufacturers/{manufacturer_id}`](/api-reference/manufacturers/manufacturer-details): Get manufacturer details.
* [`GET /models/manufacturer/{manufacturer_id}`](/api-reference/models/models-by-manufacturer): List models for a manufacturer.
* [`GET /models/{model_id}`](/api-reference/models/model-details): Get model details.
* [`GET /generations/model/{model_id}`](/api-reference/generations/generations-by-model): List generations for a model.
* [`GET /generations/{generation_id}`](/api-reference/generations/generation-details): Get generation details.
* [`GET /engines/generation/{generation_id}`](/api-reference/engines/engines-by-generation): List engines for a generation.
* [`GET /engines/{engine_id}`](/api-reference/engines/engine-details): Get engine details, including performance and tuning information.
* [`GET /search`](/api-reference/search/vehicle-search): Search across manufacturers, models, generations, and engines.

## Common Use Cases

* Build a vehicle selector flow: Start from `GET /types`, then drill down through manufacturers, models, generations, and engines.
* Validate API access before data calls: Use `GET /subscription` during app startup or before running batch jobs.
* Power quoting and lead forms: Use `/search` to quickly resolve vehicle entities and then fetch full metadata by ID.
* Render detailed vehicle pages: Fetch model, generation, and engine detail endpoints to display structured specs and tuning context.
* Support multilingual customer experiences: Send `Accept-Language` per request to localize returned data.

## Authentication

All endpoints require Bearer authentication.

Generate and manage your API key from your Remapdb account, then send:

```bash theme={null}
Authorization: Bearer <API_KEY>
```

Example:

```bash theme={null}
curl -X GET "https://api.remapdb.com/v1/types" \
  -H "Authorization: Bearer <API_KEY>"
```

## Base URL

`https://api.remapdb.com/v1`

## Language

All methods support language selection via the `Accept-Language` header.
If omitted, English (`en`) is used.

Example:

```bash theme={null}
curl "https://api.remapdb.com/v1/search?query=audi" \
  -H "Authorization: Bearer <API_KEY>" \
  -H "Accept-Language: nl"
```

## Rate Limits

Rate limits apply to all API methods and are tied to your API key and subscription plan.
Limits reset every hour.

## Response and Errors

The API returns `application/json` responses.

* Success responses return `2XX` codes.
* Error responses return `4XX` or `5XX` codes with an error object containing:
  * `code` (integer)
  * `message` (string)


# Manufacturer Details
Source: https://docs.remapdb.com/api-reference/manufacturers/manufacturer-details

/openapi.json get /manufacturers/{manufacturer_id}
Show all manufacturer metadata along with its corresponding models.



# Manufacturers by Type
Source: https://docs.remapdb.com/api-reference/manufacturers/manufacturers-by-type

/openapi.json get /manufacturers/type/{type_id}
Show all manufacturers from specific type.



# Model Details
Source: https://docs.remapdb.com/api-reference/models/model-details

/openapi.json get /models/{model_id}
Show all model metadata along with its corresponding generations.



# Models by Manufacturer
Source: https://docs.remapdb.com/api-reference/models/models-by-manufacturer

/openapi.json get /models/manufacturer/{manufacturer_id}
Show all models from specific manufacturer.



# Vehicle Search
Source: https://docs.remapdb.com/api-reference/search/vehicle-search

/openapi.json get /search
Searches through manufacturers, models, generations and engines.



# Active Subscription
Source: https://docs.remapdb.com/api-reference/subscription/active-subscription

/openapi.json get /subscription
This method allows you to check if the authenticated bearer token (`Authorization: Bearer <API_KEY>`) has access to Remapdb’s API.



# Vehicle Types
Source: https://docs.remapdb.com/api-reference/types/vehicle-types

/openapi.json get /types
Provides a list of all available vehicle types.



# AI Integrations
Source: https://docs.remapdb.com/api/ai-integrations

Connect AI tools to Remapdb vehicle tuning data through MCP.

Use Remapdb AI Integrations when you want an AI assistant to search and retrieve Remapdb vehicle data through structured MCP tools instead of copying data manually.

The hosted MCP endpoint is:

```text theme={null}
https://api.remapdb.com/mcp
```

<Info>
  **API access** is available on the **API** and **MAX** plans. It covers direct API usage and MCP-based AI tool connections.
</Info>

## What AI Integrations give your tool

With Remapdb AI Integrations connected, your assistant can:

* Search manufacturers, models, generations, and engines.
* Browse vehicle data step by step from vehicle type to engine.
* Retrieve engine metadata, OEM performance, tuning stages, ECUs, TCUs, tools, options, and work methods.
* Check the authenticated API key subscription and usage state.
* Request localized vehicle data by passing a supported language code.

This is useful for internal vehicle data questions, quote-flow prototypes, product catalog enrichment, integration work, and automotive app development.

## Requirements

* Node.js 20 or newer for the `npx` setup.
* A Remapdb API key from [API settings](https://app.remapdb.com/api).
* An active **API** or **MAX** plan with API access enabled for the subscription.

<Warning>
  Keep your API key out of source control. Store it in your MCP client config, shell environment, or secret manager.
</Warning>

## Recommended setup

Most coding agents and desktop AI tools ask you for a command to run. Use `npx` for that setup:

```bash theme={null}
npx -y @remapdb/mcp
```

Set this environment variable in the same MCP configuration:

```text theme={null}
REMAPDB_API_KEY=your_remapdb_api_key
```

The public npm package is maintained at [github/remapdb-mcp](https://github.com/BitMeshLtd/RemapDB-mcp). It connects your AI tool to the hosted Remapdb MCP endpoint securely with your API key.

## Setup examples

### Claude Code

Run this command:

```bash theme={null}
claude mcp add --env REMAPDB_API_KEY=your_remapdb_api_key --transport stdio remapdb -- npx -y @remapdb/mcp
```

Then start Claude Code and run:

```text theme={null}
/mcp
```

Use this to confirm `remapdb` is connected.

### Claude Desktop

Add this server to your Claude Desktop MCP configuration:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

Restart Claude Desktop after saving the file.

### Codex

Add this to your Codex MCP configuration:

```toml theme={null}
[mcp_servers.remapdb]
command = "npx"
args = ["-y", "@remapdb/mcp"]

[mcp_servers.remapdb.env]
REMAPDB_API_KEY = "your_remapdb_api_key"
```

### Cursor

Add this to your Cursor MCP configuration:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

Restart Cursor or reload MCP servers after saving the file.

### Windsurf

Add this to your Windsurf MCP configuration:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

Restart Windsurf or refresh the MCP configuration after saving.

### Gemini CLI

Add this to your Gemini CLI `settings.json`:

```json theme={null}
{
  "mcpServers": {
    "remapdb": {
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

In Gemini CLI, use `/mcp` to confirm the server is available.

### VS Code

Create or edit `.vscode/mcp.json` in your workspace:

```json theme={null}
{
  "servers": {
    "remapdb": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@remapdb/mcp"],
      "env": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

You can also add it through the **MCP: Add Server** command in the Command Palette.

### OpenCode

Add this to your OpenCode config:

```json theme={null}
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "remapdb": {
      "type": "local",
      "command": ["npx", "-y", "@remapdb/mcp"],
      "environment": {
        "REMAPDB_API_KEY": "your_remapdb_api_key"
      }
    }
  }
}
```

### Continue

Create a file such as `.continue/mcpServers/remapdb.yaml`:

```yaml theme={null}
name: Remapdb
version: 0.0.1
schema: v1
mcpServers:
  - name: Remapdb
    type: stdio
    command: npx
    args:
      - "-y"
      - "@remapdb/mcp"
    env:
      REMAPDB_API_KEY: your_remapdb_api_key
```

### Direct HTTP

Use direct HTTP only if your MCP client supports remote streamable HTTP MCP servers.

```text theme={null}
URL: https://api.remapdb.com/mcp
Authorization: Bearer your_remapdb_api_key
Mcp-Protocol-Version: 2025-03-26
```

## Test from a terminal

You can test that Node and the Remapdb MCP package start correctly:

```bash theme={null}
REMAPDB_API_KEY=your_remapdb_api_key npx -y @remapdb/mcp
```

If your npm version cannot infer the scoped package binary, use the explicit binary form:

```bash theme={null}
REMAPDB_API_KEY=your_remapdb_api_key npx -y --package @remapdb/mcp remapdb-mcp
```

## Available tools

| Tool                 | What it does                                                                                        |
| -------------------- | --------------------------------------------------------------------------------------------------- |
| `search_vehicles`    | Searches manufacturers, models, generations, and engines.                                           |
| `list_vehicle_types` | Lists available Remapdb vehicle types.                                                              |
| `list_manufacturers` | Lists manufacturers for a vehicle type.                                                             |
| `list_models`        | Lists models for a manufacturer.                                                                    |
| `list_generations`   | Lists generations for a model.                                                                      |
| `list_engines`       | Lists engines for a generation.                                                                     |
| `get_engine`         | Gets engine metadata, OEM performance, tuning stages, ECUs, TCUs, tools, options, and work methods. |
| `get_subscription`   | Shows API key scopes, call limit, and subscription access state.                                    |

Several tools accept an optional `language` argument. If it is not provided, Remapdb uses the request `Accept-Language` value where available, then falls back to the API default language.

Search and manufacturer listing support pagination with `cursor` and `limit`. `limit` must be between `1` and `100`.

## Example prompts

After AI Integrations are connected, try prompts like:

```text theme={null}
Search Remapdb for Audi A4 2.0 TDI engines.
```

```text theme={null}
Find the engine details and available remap stages for engine ID 123.
```

```text theme={null}
List vehicle types in Remapdb, then show manufacturers for the passenger car type.
```

```text theme={null}
Use Remapdb to compare available tuning data for BMW 320d generations.
```

```text theme={null}
Show me the tuning gains for BMW X7 G07 2018 M50i xDrive 530hp.
```

```text theme={null}
Find the closest matching engine for BMW X7 G07 M50i xDrive and summarize OEM power, stage gains, ECU, and available tuning methods.
```

```text theme={null}
Search for Volkswagen Golf GTI engines and show the available remap stages for the best match.
```

Your MCP client decides the exact tool calls.

## Troubleshooting

| Issue                  | What to check                                                                                                                         |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Missing API key        | Set `REMAPDB_API_KEY` in your MCP configuration or pass `--api-key` when testing from a terminal.                                     |
| Invalid API key        | Copy the API key again from [API settings](https://app.remapdb.com/api). If credentials were rotated, update every MCP client config. |
| API access unavailable | Confirm the subscription is active and on the **API** or **MAX** plan.                                                                |
| Not enough permissions | Confirm the API key includes the `vdb_read` scope.                                                                                    |
| Rate limit reached     | Wait for the limit window to reset or review API usage for the account.                                                               |
| Node cannot start      | Use an absolute `npx` path if your MCP client does not load `nvm`, `asdf`, or your shell profile.                                     |

## Related actions

* [Credentials and authentication](/api/credentials-and-authentication)
* [Plan access](/api/plan-access)
* [Usage limits](/api/usage-limits)


# API reference
Source: https://docs.remapdb.com/api/api-reference

Browse interactive Remapdb API endpoints, parameters, and responses.

<Columns>
  <Card title="API reference" icon="code" href="/api-reference/introduction">
    Use the interactive API reference to inspect endpoints, request parameters, and example responses.
  </Card>

  <Card title="AI Integrations" icon="bot" href="/api/ai-integrations">
    Use API access with MCP-based AI tools instead of calling REST endpoints directly.
  </Card>
</Columns>


# Best practices
Source: https://docs.remapdb.com/api/best-practices

Run Remapdb API integrations with strong security, clear monitoring, and safe rollout control.

Use this page as your production standard before you rely on API access for customer-facing flows, backend automation, or MCP-based AI tool connections.

## Security baseline

* Keep API credentials on server-side systems only.
* Restrict credential visibility to approved team members.
* Use separate credentials per environment.
* Keep a documented credential-rotation process.
* Store MCP client API keys as `REMAPDB_API_KEY` in approved config, environment, or secret storage.
* Rotate immediately after any suspected leak.

<Warning>
  If you suspect a key leak, rotate credentials first. Investigation comes after containment.
</Warning>

## Reliability baseline

* Set request timeouts for every API call.
* Retry only temporary failures.
* Use exponential backoff with jitter.
* Cap retry attempts to avoid retry storms.
* Show a graceful fallback in your UI when requests fail.

## Monitoring baseline

For each request, log:

* endpoint path and method
* response status
* response time
* retry count
* service and environment name

Do not log:

* API secrets
* full auth headers
* sensitive personal user data

## Safe rollout process

<Steps>
  <Step title="Validate in staging first">
    Test request/response behavior with your staging credentials and staging environment.
  </Step>

  <Step title="Release behind a controlled rollout">
    Start with a small share of traffic before full rollout.
  </Step>

  <Step title="Watch live metrics">
    Monitor error rate, response time, and retry volume in real time.
  </Step>

  <Step title="Keep rollback ready">
    Be able to disable or roll back quickly if error rates rise.
  </Step>
</Steps>

## Remapdb-specific checks

* After any plan change, confirm API access is still active.
* After any website/domain change, re-test widget-related API requests.
* After credential rotation, confirm every backend, worker, scheduled job, and MCP client loaded new credentials.

## Go-live checklist

* Credentials are stored securely on the backend.
* MCP clients are configured only in approved environments, if you use [AI Integrations](/api/ai-integrations).
* Staging validation is complete.
* Monitoring and alerts are active.
* Usage budget alerts are configured.
* Rollback procedure is tested.

## Related actions

* [Credentials and authentication](/api/credentials-and-authentication)
* [AI Integrations](/api/ai-integrations)
* [Usage limits](/api/usage-limits)


# Credentials and authentication
Source: https://docs.remapdb.com/api/credentials-and-authentication

Set up API credentials in Remapdb, store them safely, and rotate them without breaking your integration.

Use this page to connect your backend to Remapdb with a safe credential workflow.

## Where to find credentials

Click the [**API**](https://app.remapdb.com/api) item in the main navigation.

In the **Credentials** section, you will see:

* `API key`
* `API secret`
* **Copy** buttons
* **Generate new credentials** button

<Info>
  If credentials are disabled, your account does not currently have API access. Open [Plan access](/api/plan-access).
</Info>

## Set up credentials

<Steps>
  <Step title="Copy both credential values">
    Click the **Copy** button next to `API key`, then click the **Copy** button next to `API secret`.
  </Step>

  <Step title="Store credentials in your server environment">
    Save both values in secure server-side environment variables or your secret manager.
  </Step>

  <Step title="Connect your backend service">
    Configure your backend to read the stored credentials and use them for API requests.
  </Step>

  <Step title="Run one test request in staging">
    Confirm authentication works in staging before you send production traffic.
  </Step>
</Steps>

<Info>
  Your API key is also used for MCP-based AI tool setup. Set it as `REMAPDB_API_KEY` when you follow [AI Integrations](/api/ai-integrations).
</Info>

## Rotate credentials safely

Clicking the **Generate new credentials** button creates a new key and secret pair.

<Warning>
  Rotation is immediate. As soon as you generate new credentials, old credentials stop working.
</Warning>

Use this rotation order:

<Steps>
  <Step title="List every service that uses current credentials">
    Include web app backend, workers, scheduled jobs, and any integration scripts.
  </Step>

  <Step title="Generate the new credentials in Remapdb">
    Click the **Generate new credentials** button in the API page.
  </Step>

  <Step title="Update credentials in every environment">
    Replace old values in staging and production secret storage.
  </Step>

  <Step title="Reload services">
    Restart or redeploy services so they read the new values.
  </Step>

  <Step title="Run a smoke test">
    Confirm your key requests succeed and no authentication errors appear in logs.
  </Step>
</Steps>

## Common issues

* Credentials are disabled: open [Plan access](/api/plan-access).
* Requests started failing right after rotation: one or more services still use old credentials.
* Staging works but production fails: compare environment variables between both environments.

## Related actions

* [API](/api)
* [AI Integrations](/api/ai-integrations)
* [Usage limits](/api/usage-limits)


# Plan access
Source: https://docs.remapdb.com/api/plan-access

Check which plans include API access and unlock credentials when API controls are disabled.

Use this page when your API credentials are locked or hidden.

## Plans comparison

| Plan | API access |
| ---- | ---------- |
| Free | —          |
| Plus | —          |
| Pro  | —          |
| API  | ✓          |
| MAX  | ✓          |

If your current plan does not include API access, credential controls in the API page stay disabled.
API access also covers MCP-based AI tool setup through [AI Integrations](/api/ai-integrations).

<Info>
  For plan details, open [Billing](https://app.remapdb.com/settings/billing). For feature comparison, open [Feature availability by plan](/feature-availability-by-plan).
</Info>

## How to unlock API access

<Steps>
  <Step title="Open API settings">
    Click the [**API**](https://app.remapdb.com/api) item in the main navigation.
  </Step>

  <Step title="Start upgrade flow">
    If API controls are locked, click the **Upgrade plan** button shown on the page.
  </Step>

  <Step title="Choose an API-enabled plan">
    In billing, select **API** or **MAX** and complete the subscription change.
  </Step>

  <Step title="Return and verify">
    Go back to the API page and confirm credentials are now enabled.
  </Step>
</Steps>

You can also open billing directly:

* Click your name at the bottom of the main navigation.
* Click the [**Billing**](https://app.remapdb.com/settings/billing) item.

## What to verify after upgrade

* `API key` and `API secret` are visible.
* **Copy** buttons are enabled.
* **Generate new credentials** button is enabled.
* MCP-based AI tool setup can authenticate with `REMAPDB_API_KEY`, if you use [AI Integrations](/api/ai-integrations).
* A staging test request succeeds.

## If access is still locked

* Refresh the page after the subscription update.
* Confirm you are in the correct Remapdb account.
* Confirm subscription status is active in billing.
* Contact support if access is still blocked after these checks.

## Related actions

* [API](/api)
* [AI Integrations](/api/ai-integrations)
* [Credentials and authentication](/api/credentials-and-authentication)
* [Usage limits](/api/usage-limits)
* [Billing](https://app.remapdb.com/settings/billing)


# Usage limits
Source: https://docs.remapdb.com/api/usage-limits

Plan API traffic in Remapdb and keep request volume inside safe daily limits.

Use this page to prevent limit-related interruptions in API access workflows, including direct API requests and MCP-based AI tool connections.

## Current API rate limits

* Up to **120 requests per minute**

<Info>
  Use 120 requests/minute as your planning baseline unless support confirms a different account-specific limit.
</Info>

## What this means in daily operations

* 120/minute is about 2 requests/second on average.
* Short bursts can still happen, but sustained traffic should stay under budget.
* MCP-based AI tools can make several API-backed calls while searching or drilling into vehicle data.
* Contact support if your normal traffic now exceeds your current baseline.

## Plan your request budget

<Steps>
  <Step title="Estimate your normal traffic">
    Calculate how many API calls one user journey triggers, including backend services, workers, batch jobs, and MCP clients connected through [AI Integrations](/api/ai-integrations).
  </Step>

  <Step title="Add safety headroom">
    Reserve part of the budget for retries, support checks, and traffic spikes.
  </Step>

  <Step title="Set soft alerts">
    Add internal alerts around 70%, 85%, and 95% of daily capacity.
  </Step>

  <Step title="Reduce avoidable calls">
    Cache stable responses and remove duplicate polling.
  </Step>

  <Step title="Review usage every week">
    Compare forecast vs real usage and adjust before limits become incidents.
  </Step>
</Steps>

## If you are close to today’s limit

* Pause non-critical background jobs.
* Increase cache duration for low-change data.
* Investigate duplicate or noisy request sources.
* Keep only customer-critical API calls active.
* Contact support if your normal traffic now exceeds your current baseline.

<Warning>
  Do not wait for a hard-limit event in production. Use soft alerts and early traffic controls.
</Warning>

## Related actions

* [API](/api)
* [AI Integrations](/api/ai-integrations)
* [Best practices](/api/best-practices)
* [Plan access](/api/plan-access)


# Billing and plans
Source: https://docs.remapdb.com/billing

Understand billing in Remapdb, choose the right plan, and manage subscriptions, payments, and invoices with clear links to each billing task.

Use this section as your billing guide in Remapdb. It helps you choose a plan, subscribe, change plan, recover failed payments, and understand exactly when billing changes apply.

## How billing works in Remapdb

* You start billing actions in **Settings > Billing** in Remapdb.
* Remapdb shows your current plan, status, billing period, renew date, and current charge details.
* Payment method, billing address, invoice payment, and full invoice history are handled in the Stripe customer portal.
* Higher-cost paid-plan changes are applied immediately with proration, and any amount due is charged now.
* Lower-cost paid-plan changes and downgrade to Free are scheduled for period end.

<Info>
  For plan limits and feature access by tier, see [Feature availability by plan](/feature-availability-by-plan).
</Info>

## Open the right page for the right task

| Task                                                                | Page                                                                                  |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Compare plans and choose monthly or yearly billing                  | [Pricing plans](/billing/pricing-plans)                                               |
| Subscribe to a paid plan or change plan/cycle                       | [Subscribe or change plan](/billing/subscribe-or-change-plan)                         |
| Fix failed charges, past-due renewals, and invoice/payment warnings | [Payment failed: next steps](/billing/payment-failed-next-steps)                      |
| Update payment method, billing address, and invoice records         | [Billing invoices and payment methods](/billing/billing-invoices-and-payment-methods) |
| Understand status changes, scheduled updates, and downgrade timing  | [Billing subscription lifecycle](/billing/billing-subscription-lifecycle)             |

## Core billing tasks users ask most often

### Subscribe to a paid plan

* Go to [Pricing plans](/billing/pricing-plans) first to choose the plan and billing cycle.
* Then follow [Subscribe or change plan](/billing/subscribe-or-change-plan) for the full click-by-click flow.

### Update or change your plan

* Start in **Settings > Billing**.
* Click the **Update subscription** button.
* Follow [Subscribe or change plan](/billing/subscribe-or-change-plan) for the exact rules:
  * Higher-cost changes apply immediately with proration, and any amount due is charged now.
  * Lower-cost changes are scheduled for current period end.

### Cancel your paid plan (downgrade to Free)

* Open [Billing subscription lifecycle](/billing/billing-subscription-lifecycle) and follow the downgrade steps.
* Remapdb schedules downgrade at period end, so you keep current paid access until that date.

### Manage invoices, card, and billing address

* Open [Billing invoices and payment methods](/billing/billing-invoices-and-payment-methods).
* That page explains exactly which actions happen in Stripe and which billing data you can review directly in Remapdb.

## Where to check billing health quickly

* Open **Settings > Billing** and review:
  * **Status**
  * **Billing period**
  * **Renew date**
  * **Payment method** warnings
  * **Invoice history** due states
* If you see a warning banner at the top of the app, resolve it the same day using [Payment failed: next steps](/billing/payment-failed-next-steps).

## Before you make billing changes

* Confirm who in your team owns payment approval.
* Confirm your target plan covers your website count, quote volume, and API needs.
* Confirm your payment method is valid before starting plan updates.
* If a scheduled change already exists, click the **Cancel scheduled change** button before starting a new change.

## Pages in this section

<div>
  <Columns>
    <Card title="Pricing plans" href="/billing/pricing-plans">
      Compare plans, limits, and monthly versus yearly billing.
    </Card>

    <Card title="Subscribe or change plan" href="/billing/subscribe-or-change-plan">
      Subscribe, upgrade, downgrade between paid plans, or switch billing cycle.
    </Card>

    <Card title="Payment failed: next steps" href="/billing/payment-failed-next-steps">
      Fix payment issues before they affect your service.
    </Card>

    <Card title="Billing invoices and payment methods" href="/billing/billing-invoices-and-payment-methods">
      Manage card, billing address, and invoices through Stripe.
    </Card>

    <Card title="Billing subscription lifecycle" href="/billing/billing-subscription-lifecycle">
      Understand statuses, scheduled changes, downgrades, and timing.
    </Card>
  </Columns>
</div>


# Billing invoices and payment methods
Source: https://docs.remapdb.com/billing/billing-invoices-and-payment-methods

Manage payment method, billing address, and invoices in Remapdb, with clear guidance on what happens in Stripe customer portal.

Use this page to keep billing records healthy and avoid renewal failures.

## What Remapdb shows and what Stripe manages

In **Settings > Billing**, Remapdb shows a billing summary:

* Current payment method details
* Billing address summary
* Recent invoice history and due state

When you click a **Manage** button, Remapdb opens Stripe customer portal in a new tab. In Stripe, you can:

* Update payment method
* Update billing address and profile
* View and pay invoices

## Payment method section

In **Payment method**, Remapdb can show:

* Card or method type
* Last 4 digits
* Expiry date
* Warning badges like expired or expiring soon

To update:

1. Open **Settings > Billing**.
2. In **Payment method**, click the **Manage** button.
3. In Stripe, add or replace the default payment method.
4. Return to Remapdb and refresh the page.
5. Confirm the updated method details are visible.

## Billing address section

In **Billing address**, Remapdb shows your stored billing profile summary.

To update:

1. Open **Settings > Billing**.
2. In **Billing address**, click the **Manage** button.
3. In Stripe, update billing address and company billing details.
4. Save in Stripe.
5. Return to Remapdb and verify the updated summary.

## Invoice history section

In **Invoice history**, each row shows:

* Invoice date
* Total amount
* Status
* Open-invoice action

You may also see a due state when an invoice is still unpaid.

To pay a due invoice:

1. Open **Settings > Billing**.
2. In **Invoice history**, find the invoice marked due.
3. Click the invoice open icon.
4. Complete payment in Stripe.
5. Return to Remapdb and refresh to confirm the due state is cleared.

To open full invoice history:

1. In **Invoice history**, click the **View invoices** button.
2. Review full invoice list in Stripe portal.

## Monthly finance check

* Confirm payment method is valid and not close to expiry.
* Confirm billing address and company data are still correct.
* Confirm there are no due invoices.
* Store invoice documents in your accounting process.

## If you see warnings

If you see payment warnings in the top app banner or in billing status, follow [Payment failed: next steps](/billing/payment-failed-next-steps).

## Related actions

* [Billing and plans](/billing)
* [Payment failed: next steps](/billing/payment-failed-next-steps)
* [Billing subscription lifecycle](/billing/billing-subscription-lifecycle)


# Billing subscription lifecycle
Source: https://docs.remapdb.com/billing/billing-subscription-lifecycle

Understand how Remapdb applies billing changes, how cancellation timing works, and how subscription status affects feature access.

Use this page to understand billing timing in Remapdb: when changes apply now, when they are scheduled, and what happens when payment fails.

## How plan changes are applied

When you start a plan update from **Settings > Billing**, Remapdb uses one of these paths:

* Checkout flow in Stripe for accounts without a paid subscription.
* Immediate in-app change with proration, and any amount due charged now.
* Scheduled change at current period end.

The exact behavior depends on your current plan, target plan, billing cycle.

| Change type                    | Timing and charge behavior                                                   |
| ------------------------------ | ---------------------------------------------------------------------------- |
| Higher-cost paid-plan change   | Immediate. Proration is calculated, and any amount due is charged now.       |
| Lower-cost paid-plan change    | Scheduled for current period end. Current paid plan stays active until then. |
| Paid plan to Free              | Scheduled for current period end.                                            |
| Monthly to Yearly cycle switch | Immediate. Billing anchor resets to now and proration is applied.            |
| Yearly to Monthly cycle switch | Scheduled for current period end.                                            |

For the click-by-click change flow, see [Subscribe or change plan](/billing/subscribe-or-change-plan).

## Scheduled change guard

If a future change already exists, Remapdb blocks additional plan updates.

To continue:

1. Open **Settings > Billing**.
2. Click the **Cancel scheduled change** button.
3. Confirm the action.
4. Start your new plan update again.

## How cancellation works in Remapdb

In Remapdb, cancellation from a paid plan is handled as a scheduled downgrade to Free at period end.

1. Open **Settings > Billing**.
2. Click the **Update subscription** button.
3. In the pricing modal, click the **Downgrade** button.
4. Submit the required reason and optional feedback.
5. Confirm the downgrade scheduling action.

After scheduling:

* You keep paid access until the current period end date.
* Remapdb shows scheduled-change messaging in **Status** and **Renew date**.
* At period end, the account moves to Free behavior.

<Info>
  When you move to a lower plan or to Free, Remapdb keeps your existing paid-feature settings.\
  Some paid controls become unavailable while your plan does not include them, but their previous configuration stays saved.\
  If you upgrade again later, those saved settings become available again.
</Info>

## Cancel a scheduled downgrade

If you change your mind before period end:

1. Open **Settings > Billing**.
2. Click the **Cancel scheduled change** button.
3. Confirm the release action.
4. Verify your current paid plan remains active.

## Payment failure lifecycle impact

If payment issues are not resolved, Remapdb can move the subscription to a non-paying state. In that case, subscription will fall back to Free-tier behavior and paid features will be removed.

For recovery steps, see [Payment failed: next steps](/billing/payment-failed-next-steps).

<Info>
  Your available features follow your active plan. If your billing status changes, the features you can use may change too. See [Feature availability by plan](/feature-availability-by-plan).
</Info>

## What to verify after any billing event

* **Current plan**
* **Status**
* **Billing period**
* **Renew date**
* Payment and invoice state

## Related actions

* [Pricing plans](/billing/pricing-plans)
* [Subscribe or change plan](/billing/subscribe-or-change-plan)
* [Billing invoices and payment methods](/billing/billing-invoices-and-payment-methods)
* [Billing and plans](/billing)


# Payment failed: next steps
Source: https://docs.remapdb.com/billing/payment-failed-next-steps

Resolve payment incidents in Remapdb, including incomplete checkout, past-due renewals, unpaid invoices, and expired payment methods.

Use this page when billing warnings appear in Remapdb and you need to recover service quickly.

## Problem

You may see:

* Payment incomplete
* Payment past due
* Unpaid invoice warning
* Expired or expiring payment method warning

## Where you see it

* Top warning banner in the app
* **Status** in **Settings > Billing**
* **Invoice history** rows in **Settings > Billing**

## Why this happens

| Incident           | Most common reason                                  |
| ------------------ | --------------------------------------------------- |
| Payment incomplete | Checkout or payment authentication was not finished |
| Payment past due   | Renewal charge failed                               |
| Unpaid invoice     | Invoice is still open and unpaid                    |
| Card expired       | Saved payment method is no longer valid             |
| Card expiring soon | Saved payment method is close to expiry             |

## How to fix it

### Fast recovery path

1. Open **Settings > Billing**.
2. Check **Status**.
3. In **Payment method**, click the **Manage** button and confirm your default payment method is valid.
4. In **Invoice history**, open and pay any invoice marked due.
5. Refresh **Settings > Billing** and confirm warnings are cleared.

### Payment incomplete

1. Open **Settings > Billing**.
2. Click the **Update subscription** button.
3. Repeat the plan confirmation flow.
4. Complete payment authentication if requested.
5. Return to **Settings > Billing** and check status.

### Payment past due

1. In the warning banner, click **Update payment method**.
2. If the banner button is not shown, open **Settings > Billing** and click the **Manage** button in **Payment method**.
3. Update your default payment method in Stripe.
4. Return to Remapdb.
5. Pay any unpaid invoice shown in **Invoice history**.
6. Refresh the page and recheck status.

### Unpaid invoice warning

1. In the banner, click **View and pay invoice** when available.
2. If needed, open **Settings > Billing** and click the invoice open icon in **Invoice history**.
3. Complete invoice payment in Stripe.
4. Return to Remapdb and refresh.
5. Confirm the invoice is no longer due.

### Expired or expiring payment method

1. Open **Settings > Billing**.
2. In **Payment method**, click the **Manage** button.
3. Replace or update your default payment method in Stripe.
4. Return to Remapdb.
5. Confirm the new method details are shown.

<Warning>
  If payment issues remain unresolved, Remapdb can move the subscription to a non-paying state. In that case, subscription will fall back to Free-tier behavior and paid features will be removed.
</Warning>

## What to verify after recovery

* **Status** is no longer incomplete, past due, unpaid, or canceled.
* **Renew date** is present and correct.
* Payment method is valid and not near expiry.
* Latest due invoice is paid.
* Your expected paid features are available.

## If it still does not work

1. Capture the exact status text from **Settings > Billing**.
2. Capture the invoice ID for any unpaid invoice.
3. Capture the last 4 digits and expiry date of your current default payment method.
4. Open [Support request process](/support/support-request-process) and send these details to support.

## Related actions

* [Billing invoices and payment methods](/billing/billing-invoices-and-payment-methods)
* [Billing subscription lifecycle](/billing/billing-subscription-lifecycle)
* [Billing and plans](/billing)


# Pricing plans
Source: https://docs.remapdb.com/billing/pricing-plans

Compare Remapdb plans and billing cycles, then choose the right subscription for your website count, quote volume, and API needs.

Use this page to choose the right plan before you change billing. For the full subscribe/change flow, open [Subscribe or change plan](/billing/subscribe-or-change-plan).

## Where to compare plans in the app

1. Click your name at the bottom of the main navigation.
2. Click [**Billing**](https://app.remapdb.com/settings/billing).
3. Click the **Update subscription** button.
4. In the pricing modal, compare plans and use the **Monthly / Yearly** switch.

## Plan limits at a glance

| Plan | Best for                        | Website access | Quotes/day | API access |
| ---- | ------------------------------- | -------------- | ---------- | ---------- |
| Free | Evaluation and low-volume usage | 1              | 5          | —          |
| Plus | Single-site production usage    | 1              | Unlimited  | —          |
| Pro  | Multi-site production teams     | 5              | Unlimited  | —          |
| API  | Integration-first workflows     | 1              | 5          | ✓          |
| MAX  | Multi-site + advanced scale     | 10             | Unlimited  | ✓          |

API access includes API credentials, REST API usage, SDK workflows, and MCP-based AI tool connections through [AI Integrations](/api/ai-integrations).

## Key feature differences

| Area                                                                          | Free | Plus | Pro | API | MAX |
| ----------------------------------------------------------------------------- | ---- | ---- | --- | --- | --- |
| Link sharing / clean URLs                                                     | —    | ✓    | ✓   | —   | ✓   |
| Automatic SEO metadata                                                        | —    | —    | ✓   | —   | ✓   |
| Auto language detect                                                          | —    | ✓    | ✓   | —   | ✓   |
| Full branding controls                                                        | —    | ✓    | ✓   | —   | ✓   |
| Advanced quoting (dealers, pricing, custom messages, auto-reply, file upload) | —    | —    | ✓   | —   | ✓   |
| API access                                                                    | —    | —    | —   | ✓   | ✓   |

<Info>
  Plan limits and feature availability follow your active subscription state. For full details, see [Feature availability by plan](/feature-availability-by-plan).
</Info>

## What each pricing button means

| Button text                | Meaning                                |
| -------------------------- | -------------------------------------- |
| Current plan               | You are already on this plan and cycle |
| Choose plan                | Start plan-change flow for this plan   |
| Bill yearly / Bill monthly | Keep same plan, change cycle           |
| Downgrade                  | Schedule a move from paid plan to Free |

## How to choose the right plan

Use this decision order:

* Website access limit
* Quote capacity
* API access need
* Quoting and branding controls
* Billing cycle preference (monthly or yearly)

## Monthly or yearly: when to use each

Choose **Monthly** when:

* You are still testing demand or rollout.
* You expect plan changes in the near term.

Choose **Yearly** when:

* Your usage is stable.
* You want one annual payment cycle.

## How plan changes apply

* If your account does not have a subscription yet, Remapdb sends you to Stripe's checkout page.
* If you already have a paid subscription, Remapdb shows a confirmation flow inside the app.
* Higher-cost paid-plan changes apply immediately with proration, and any amount due is charged now.
* Lower-cost paid-plan changes are scheduled for period end.
* Downgrade to Free is scheduled for period end.

For exact steps and outcomes, see [Subscribe or change plan](/billing/subscribe-or-change-plan) and [Billing subscription lifecycle](/billing/billing-subscription-lifecycle).

## Before you confirm any plan change

* Confirm the selected plan matches your required website count.
* Confirm the selected plan includes API access if you need direct API usage, SDK workflows, or MCP-based AI tools.
* Confirm your payment method is valid.
* Confirm your finance owner approves the charge timing.
* If you already have a scheduled change, click the **Cancel scheduled change** button first.

## Related actions

* [Subscribe or change plan](/billing/subscribe-or-change-plan)
* [Billing subscription lifecycle](/billing/billing-subscription-lifecycle)
* [Billing invoices and payment methods](/billing/billing-invoices-and-payment-methods)
* [Feature availability by plan](/feature-availability-by-plan)
* [Billing and plans](/billing)


# Subscribe or change plan
Source: https://docs.remapdb.com/billing/subscribe-or-change-plan

Subscribe to a paid plan or change plan in Remapdb with clear timing for immediate prorated upgrades and scheduled downgrades.

Use this page when you want to subscribe to a paid plan, change from one paid plan to another, switch billing cycle, or move to Free.

## Before you start

* Confirm you can access **Settings > Billing**.
* Confirm you selected **Monthly** or **Yearly**.

## Start the plan change flow

1. Click your name at the bottom of the main navigation.
2. Click [**Billing**](https://app.remapdb.com/settings/billing).
3. Click the **Update subscription** button.
4. Set your billing cycle in the pricing modal.
5. Click the action button on your target plan:
   * **Choose plan** for a different paid plan
   * **Bill yearly** or **Bill monthly** for cycle change on the same plan

## If this is your first paid subscription

Remapdb sends you to Stripe Checkout.

1. Complete checkout details in Stripe:
   * Billing address
   * Payment method
   * Tax details when applicable
   * Promotion code when needed
2. Submit the payment in Stripe.
3. Wait for redirect back to Remapdb.
4. Open **Settings > Billing** and confirm the plan and cycle update.

## If you already have a paid subscription

Remapdb keeps you in the app and shows a confirmation flow.

1. Review the amount and timing in the confirmation modal.
2. Click the confirm action.
3. If Stripe requests authentication, complete it.
4. Return to **Settings > Billing** and confirm:
   * **Current plan**
   * **Status**
   * **Billing period**
   * **Renew date**

## How charges and timing work for paid-plan changes

| Change type                                 | What happens                                                                                                                          |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Move to a higher-cost paid plan             | The change is immediate. Remapdb calculates proration for the remaining time in your current period and charges the shown amount now. |
| Move to a lower-cost paid plan              | The change is scheduled for your current billing period end. You keep your current plan until that date.                              |
| Downgrade from paid plan to Free            | The downgrade is scheduled for your current billing period end.                                                                       |
| Change billing cycle from Monthly to Yearly | The change is immediate. Billing date resets to today and proration is applied in the confirmation amount.                            |
| Change billing cycle from Yearly to Monthly | The change is scheduled for your current billing period end.                                                                          |

In all immediate-change cases, the confirmation dialog shows the exact proration breakdown and total that will be charged today.

<Info>
  Changing to a lower plan or to Free does not erase your paid-feature setup. Remapdb keeps those settings saved, and they become available again if you upgrade later.
</Info>

## When change is blocked by scheduled change

If you already have a scheduled change (including scheduled downgrade), Remapdb blocks a new change until the existing schedule is removed.

1. Open **Settings > Billing**.
2. Click the **Cancel scheduled change** button.
3. Confirm the release action.
4. Click the **Update subscription** button again.
5. Repeat the plan change flow.

<Info>
  This guard prevents conflicting future billing instructions on the same subscription.
</Info>

## What success looks like

In **Settings > Billing**:

* **Current plan** shows your selected target plan.
* **Status** is not blocked by payment warnings.
* **Billing period** matches your selected cycle.
* **Renew date** is present.
* Charge details are visible in the plan summary.

Then validate features tied to your selected plan:

* Quoting controls
* Branding controls
* SEO and API controls when applicable

## Common failure patterns and fixes

### Billing page still shows old plan after checkout

1. Refresh the page.
2. Wait briefly for Remapdb's cache to clear.
3. Open **Settings > Billing** again.
4. If the payment is success but the status remains incomplete, contact support.

### Payment authentication interrupted

1. Start the upgrade again.
2. Complete the Stripe authentication step.
3. If the status remains incomplete, follow [Payment failed: next steps](/billing/payment-failed-next-steps).

### Schedule conflict message appears

1. Click the **Cancel scheduled change** button first.
2. Confirm the release.
3. Start the upgrade again.

## Related actions

* [Pricing plans](/billing/pricing-plans)
* [Billing subscription lifecycle](/billing/billing-subscription-lifecycle)
* [Payment failed: next steps](/billing/payment-failed-next-steps)
* [Billing and plans](/billing)


# Customisations
Source: https://docs.remapdb.com/customisations

Understand the Customisations area in Remapdb and follow the coming-soon database customisations flow.

Use this section to understand the **Customisations** page in Remapdb and register interest in the upcoming database customisations feature.

## What is available in this section

This section currently has one page:

* [Database customisations (coming soon)](/customisations/database-customisations-coming-soon): check current status, join the waiting list, and understand what capabilities are planned.

## What this category covers

* The current **coming soon** state of database customisations.
* How to join the waiting list from the **Customisations** page in the app.
* What changes are planned for future releases.

## Important scope note

* Database customisations are not live yet.

<Info>
  Customisations is currently in rollout preparation. Use this section as a status and onboarding point for the waiting list.
</Info>

## Page in this section

<div>
  <Columns>
    <Card title="Database customisations (coming soon)" href="/customisations/database-customisations-coming-soon">
      See what is available today, join the waiting list, and understand what is planned for future release.
    </Card>
  </Columns>
</div>


# Database customisations (coming soon)
Source: https://docs.remapdb.com/customisations/database-customisations-coming-soon

Understand what the Customisations page does today, how to join the waiting list, and what capabilities are planned.

Use this page if you opened **Customisations** in Remapdb and want to understand what is available now versus what is still coming soon.

## Current status

* Database customisations are not live yet.
* The current page is an interest page with a waiting list.
* You cannot edit vehicle database records from this page today.

## What you can do now

<Steps>
  <Step title="Open the page">
    Click the [**Customisations**](https://app.remapdb.com/crud) item in the main navigation.
  </Step>

  <Step title="Review the planned feature scope">
    On the page, review the capability summary shown under the coming-soon message.
  </Step>

  <Step title="Join the waiting list">
    Click the **Join the waiting list** button.
  </Step>

  <Step title="Confirm your status">
    After submission, check the confirmation state and joined date shown on the same page.
  </Step>
</Steps>

<Info>
  The waiting-list action is account-based and tied to your logged-in Remapdb account.
</Info>

## Planned capabilities shown in the app

The current coming-soon page describes these planned database customisation capabilities:

* Add or remove vehicles.
* Update tuning stage values (such as horsepower and torque).
* Edit engine parameters.
* Adjust tuning options and tools.
* Upload custom dyno charts.

## Planned direction

This feature area is designed for teams that need deeper control of vehicle data than the standard widget setup provides.

Planned direction includes broader custom data control, including adding custom entries and expanded data ownership workflows over time.

## Related actions

* [Customisations](/customisations)
* [Feature availability by plan](/feature-availability-by-plan)
* [Support](https://app.remapdb.com/support)


# Feature availability by plan
Source: https://docs.remapdb.com/feature-availability-by-plan

Understand exactly what each Remapdb plan includes, how to read the upgrade dialog, and which features unlock in your interface.

Use this page when:

* a setting is locked and you are not sure why
* you are comparing plans before upgrading
* you need to confirm what is included in your current subscription

## Check your plan and open the comparison dialog

<Steps>
  <Step title="Open Billing">
    Open [Billing in Remapdb](https://app.remapdb.com/settings/billing).\
    You can also click your name at the bottom of the main navigation, then click [**Billing**](https://app.remapdb.com/settings/billing).
  </Step>

  <Step title="Review your current subscription">
    In the **Current plan** area, check your plan name, status, billing cycle, and next renewal date.
  </Step>

  <Step title="Open the plan comparison dialog">
    Click the **Update subscription** button.
  </Step>

  <Step title="Compare monthly and yearly prices">
    Use the **Monthly / Yearly** switch at the top of the dialog to compare billing cycles.
  </Step>
</Steps>

## How to read the plan comparison dialog

* A check mark means the feature is included.
* A horizontal line means the feature is not included.
* Numeric values (for example website count, quotes per day) are hard limits.
* In the **Quotes per day** row, very high plan limits are shown as **Unlimited**.
* In the **Branding** section, colors are shown as one row.
* **Basic** means base color controls.
* **Full** means full color controls.

<Info>
  If a control is visible but disabled, check your [plan](https://app.remapdb.com/settings/billing) first, then compare feature access in this page.
</Info>

## Core plan limits

| Capability     | Free | Plus      | Pro       | API | MAX       |
| -------------- | ---- | --------- | --------- | --- | --------- |
| Website access | 1    | 1         | 5         | 1   | 10        |
| Quotes per day | 5    | Unlimited | Unlimited | 5   | Unlimited |
| API access     | —    | —         | —         | ✓   | ✓         |

What this means:

* **Website access** is the number of websites where you can run the widget or WordPress plugin.
* **Quotes per day** is the daily number of accepted quote submissions.
* **API access** controls whether you can use Remapdb API credentials, endpoints, SDK workflows, and MCP-based AI tool setup through [AI Integrations](/api/ai-integrations).

If your website is missing from allowed websites, follow [Code installation](/widget/installation/code-installation#website-address-rules-and-examples).
If you hit your quote cap, follow [Manage daily quote limit](/widget/quoting/manage-daily-quote-limit).

## Quoting feature availability

| Feature                      | Free | Plus | Pro | API | MAX |
| ---------------------------- | ---- | ---- | --- | --- | --- |
| VIN and Registration details | —    | ✓    | ✓   | —   | ✓   |
| Dealers                      | —    | —    | ✓   | —   | ✓   |
| Pricing                      | —    | —    | ✓   | —   | ✓   |
| Custom message               | —    | —    | ✓   | —   | ✓   |
| Auto-respond email           | —    | —    | ✓   | —   | ✓   |
| File upload                  | —    | —    | ✓   | —   | ✓   |

What each quoting feature does:

* **VIN and Registration details** lets customers submit VIN or registration data in the quote form.
* **Dealers** lets customers pick a dealer from your dealer network in the quote flow.
* **Pricing** shows service and option prices in the quote form and the estimated total.
* **Custom message** shows your own message under the form (for example notes, terms, or expectations).
* **Auto-respond email** sends an automatic confirmation email after a quote is submitted.
* **File upload** lets customers attach ECU reads, photos, logs, or supporting documents to quote requests.

For setup instructions, open [Quoting](/widget/quoting).

## Branding feature availability

| Feature                 | Free  | Plus | Pro  | API   | MAX  |
| ----------------------- | ----- | ---- | ---- | ----- | ---- |
| Colors                  | Basic | Full | Full | Basic | Full |
| Font                    | —     | ✓    | ✓    | —     | ✓    |
| Remove Remapdb branding | —     | ✓    | ✓    | —     | ✓    |
| Complete styling        | —     | ✓    | ✓    | —     | ✓    |

What each branding feature does:

* **Colors** controls widget colors for light and dark themes.
* **Font** lets you apply your brand font to the widget.
* **Remove Remapdb branding** lets you hide Remapdb logo/copyright for white-label presentation.
* **Complete styling** unlocks advanced custom CSS styling.

For detailed setup, open [Branding](/widget/branding).

## Vehicle information availability

| Feature            | Free    | Plus      | Pro       | API       | MAX       |
| ------------------ | ------- | --------- | --------- | --------- | --------- |
| Vehicle photos     | Branded | Unbranded | Unbranded | Unbranded | Unbranded |
| Vehicle logos      | ✓       | ✓         | ✓         | ✓         | ✓         |
| Dyno chart         | ✓       | ✓         | ✓         | ✓         | ✓         |
| All tuning stages  | ✓       | ✓         | ✓         | ✓         | ✓         |
| Engine information | ✓       | ✓         | ✓         | ✓         | ✓         |
| ECU information    | ✓       | ✓         | ✓         | ✓         | ✓         |
| Tuning options     | ✓       | ✓         | ✓         | ✓         | ✓         |
| Tuning tools       | ✓       | ✓         | ✓         | ✓         | ✓         |
| Work methods       | ✓       | ✓         | ✓         | ✓         | ✓         |

What each vehicle information feature does:

* **Vehicle photos** shows vehicle image assets; on Free these images are branded.
* **Vehicle logos** shows manufacturer logos in the widget.
* **Dyno chart** shows stock vs tuned power and torque graph.
* **All tuning stages** shows stage-based tuning data where available.
* **Engine information** shows key engine specs.
* **ECU information** shows ECU details where available.
* **Tuning options** shows available tuning options for the vehicle.
* **Tuning tools** shows supported tuning tools.
* **Work methods** shows supported connection methods such as OBD/Bench/BOOT where available.

## Support and services availability

| Feature                        | Free  | Plus        | Pro         | API         | MAX         |
| ------------------------------ | ----- | ----------- | ----------- | ----------- | ----------- |
| Support                        | Email | Email, Chat | Email, Chat | Email, Chat | Email, Chat |
| Free widget setup              | ✓     | ✓           | ✓           | ✓           | ✓           |
| Free WordPress plugin setup    | —     | ✓           | ✓           | —           | ✓           |
| Free styling setup             | —     | ✓           | ✓           | —           | ✓           |
| Custom auto-reply email domain | —     | —           | ✓           | —           | ✓           |

What each support feature does:

* **Support** defines which support channels are available in your plan.
* **Free widget setup** means the team can help place widget code correctly on your website.
* **Free WordPress plugin setup** means setup help for plugin installation/activation.
* **Free styling setup** means help with visual setup to match your website.
* **Custom auto-reply email domain** means support for sending quote auto-replies from your own domain.

For support flows, open [Support](/support).
For custom sender domain setup, open [Custom email domain setup information](/widget/quoting/custom-email-domain-setup-information).

## Customer experience availability

| Feature                  | Free | Plus | Pro | API | MAX |
| ------------------------ | ---- | ---- | --- | --- | --- |
| Performance units change | ✓    | ✓    | ✓   | ✓   | ✓   |
| Language change          | ✓    | ✓    | ✓   | ✓   | ✓   |
| Language auto-detect     | —    | ✓    | ✓   | —   | ✓   |

What each customer experience feature does:

* **Performance units change** lets website visitors switch between hp/Nm, hp/ft-lb, and kW/Nm.
* **Language change** lets website visitors switch widget language manually.
* **Language auto-detect** automatically picks language from visitor browser language.

For setup, open [Language and localization](/widget/settings/language-and-localization) and [Performance units](/widget/settings/torque-units).

## SEO feature availability

| Feature                   | Free | Plus | Pro | API | MAX |
| ------------------------- | ---- | ---- | --- | --- | --- |
| Share vehicle links (SEO) | —    | ✓    | ✓   | —   | ✓   |
| Automatic metadata        | —    | —    | ✓   | —   | ✓   |
| Automatic vehicle summary | —    | —    | ✓   | —   | ✓   |

What each SEO feature does:

* **Share vehicle links (SEO)** lets users share direct vehicle result links.
* **Automatic metadata** updates page title and description for better search visibility.
* **Automatic vehicle summary** shows a visible vehicle summary block for users and search engines.

For full guidance, open [SEO settings guide](/widget/settings/seo-settings-guide).

## API and customisations feature availability

| Feature                           | Free | Plus | Pro | API | MAX |
| --------------------------------- | ---- | ---- | --- | --- | --- |
| API access                        | —    | —    | —   | ✓   | ✓   |
| Database management (coming soon) | —    | —    | ✓   | —   | ✓   |

What each feature does:

* **API access** enables API credentials, direct API usage, SDK workflows, and MCP-based AI tool setup through [AI Integrations](/api/ai-integrations).
* **Database management (coming soon)** applies to the database customisations area. This feature is not live yet and is currently in coming-soon rollout.

For details, open [API](/api) and [Customisations](/customisations).
For API-specific eligibility details, open [Plan access](/api/plan-access).

## Advanced capabilities included in all plans

| Feature                      | Free | Plus | Pro | API | MAX |
| ---------------------------- | ---- | ---- | --- | --- | --- |
| Translations in 21 languages | ✓    | ✓    | ✓   | ✓   | ✓   |
| Responsive widget            | ✓    | ✓    | ✓   | ✓   | ✓   |
| Run everywhere               | ✓    | ✓    | ✓   | ✓   | ✓   |
| Unlimited usage on a website | ✓    | ✓    | ✓   | ✓   | ✓   |
| Daily database updates       | ✓    | ✓    | ✓   | ✓   | ✓   |
| WordPress plugin             | ✓    | ✓    | ✓   | ✓   | ✓   |

What these mean:

* **Translations in 21 languages** means the widget interface is available in every language listed in [Language and localization](/widget/settings/language-and-localization).
* **Responsive widget** means the widget adapts to desktop, tablet, and mobile screens.
* **Run everywhere** means broad website/platform compatibility, including WIX with minor limitations.
* **Unlimited usage on a website** means you can place the widget on as many pages as needed inside each allowed website.
* **Daily database updates** means vehicle data is refreshed continuously as part of daily updates.
* **WordPress plugin** means plugin-based installation is available in every plan.

## If a feature is still locked after upgrade

<Steps>
  <Step title="Refresh the page where the control is locked">
    Reload the page where you expect the feature, then check again.
  </Step>

  <Step title="Confirm the plan change in Billing">
    Open [Billing](https://app.remapdb.com/settings/billing) and confirm the new plan is active.
  </Step>

  <Step title="Check if the issue is a limit, not a missing feature">
    Verify website slots and daily quotes. Limits and feature flags are different.
  </Step>

  <Step title="Validate in the relevant section">
    Check the exact area again: [Installation](/widget/installation), [Quoting](/widget/quoting), [Branding](/widget/branding), [Settings](/widget/settings), or [API](/api).
  </Step>
</Steps>

## Related actions

* [Billing in Remapdb](https://app.remapdb.com/settings/billing)
* [Pricing plans](/billing/pricing-plans)
* [Subscribe or change plan](/billing/subscribe-or-change-plan)
* [Billing subscription lifecycle](/billing/billing-subscription-lifecycle)
* [AI Integrations](/api/ai-integrations)
* [Manage daily quote limit](/widget/quoting/manage-daily-quote-limit)
* [File upload](/widget/quoting/file-upload)
* [Code installation](/widget/installation/code-installation)
* [Plan access](/api/plan-access)


# Documentation
Source: https://docs.remapdb.com/index

Start here for the most important Remapdb documentation paths, from setup and widget installation to billing and support.

<div>
  <Columns>
    <Card title="Quick setup checklist" icon="rocket" href="/quick-setup-checklist">
      Launch your account with the minimum required steps for installation, configuration, and validation.
    </Card>

    <Card title="Installation" icon="plug" href="/widget/installation">
      Choose your installation method, configure allowed websites, and go live safely.
    </Card>

    <Card title="Widget settings" icon="sliders-horizontal" href="/widget/settings">
      Configure language, vehicle display options, performance units, and SEO behavior.
    </Card>

    <Card title="Widget quoting" icon="file-text" href="/widget/quoting">
      Set up lead forms, file uploads, service and pricing options, dealer routing, and quote automation.
    </Card>

    <Card title="Branding" icon="palette" href="/widget/branding">
      Match the widget to your brand using themes, typography, and advanced styling controls.
    </Card>

    <Card title="API" icon="code-xml" href="/api">
      Set up API access, connect MCP-based AI tools, review usage limits, and use integration guidance.
    </Card>
  </Columns>

  ### Account and operations

  <Columns>
    <Card title="Settings" icon="settings" href="/settings">
      Manage account profile, company information, appearance, security, email preferences, and billing settings.
    </Card>

    <Card title="Billing and plans" icon="credit-card" href="/billing">
      Understand plan features, upgrades, subscription lifecycle, invoices, and payment flows.
    </Card>

    <Card title="Support and troubleshooting" icon="life-buoy" href="/support">
      Get help quickly with support flows, status updates, and troubleshooting guides.
    </Card>

    <Card title="Customisations" icon="wrench" href="/customisations">
      Understand customisation scope and submit structured requests with clear requirements.
    </Card>
  </Columns>
</div>


# Quick setup checklist
Source: https://docs.remapdb.com/quick-setup-checklist

Use this launch checklist to confirm account, installation, settings, quoting, branding, and support readiness.

Use this page as your go-live checklist.
Keep it short and practical: if an item is not done, open the linked page, finish it, and come back here.

## How to use this checklist

* Work from top to bottom once.
* Treat every item as yes/no.
* Do not start campaigns until all required items are done.

## Account and plan

* Plan is active and correct for your rollout.\
  Check [Billing in Remapdb](https://app.remapdb.com/settings/billing).
* Website count and quote capacity match your expected traffic.\
  Check [Feature availability by plan](/feature-availability-by-plan).

## Installation readiness

* You decided your installation path: code or WordPress plugin.\
  Review [Installation](/widget/installation).
* Your website addresses are ready in the exact format.\
  Review [Code installation -> Website address rules and examples](/widget/installation/code-installation#website-address-rules-and-examples).

## Installation complete

* Your website is added in allowed websites.\
  Complete [Code installation -> Step 1: Add website in Remapdb](/widget/installation/code-installation#step-1-add-website-in-remapdb).
* The widget is installed.\
  Complete [Code installation](/widget/installation/code-installation) or [WordPress plugin installation](/widget/installation/wordpress-plugin-installation).
* The widget is visible on your live page.\
  Verify with [Installation checklist](/widget/installation/installation-checklist).

## Core widget settings

* Language is set correctly for your audience.\
  Complete [Language and localization](/widget/settings/language-and-localization).
* Vehicle data visibility is configured.\
  Complete [Vehicle data visibility](/widget/settings/vehicle-data-visibility).
* Performance units are set correctly.
  Complete [Performance units](/widget/settings/torque-units).
* SEO settings are configured if your plan includes SEO features.\
  Complete [SEO settings guide](/widget/settings/seo-settings-guide).

## Quoting setup

* Quote destination email and form inputs are set.\
  Complete [Email and inputs](/widget/quoting/email-and-inputs).
* File upload is configured, if your plan includes it and your team needs supporting files.
  Complete [File upload](/widget/quoting/file-upload).
* Services and estimated pricing are configured, if included in your plan.\
  Complete [Set services and pricing](/widget/quoting/set-services-and-pricing).
* Dealer cards, email addresses, and map locations are configured in **Manage dealers**, if you use dealers.\
  Complete [Set dealer network](/widget/quoting/set-dealer-network).
* Quote automation and auto-reply are configured, if included in your plan.\
  Complete [Set up quoting automation](/widget/quoting/set-up-quoting-automation).
* One real end-to-end test quote is submitted and received.

## Branding setup

* Theme and layout are configured.\
  Complete [Theme and layout](/widget/branding/theme-and-layout).
* Colors and typography are configured.\
  Complete [Colors and typography](/widget/branding/colors-and-typography).
* Custom CSS is applied only if needed.\
  Complete [Custom CSS styling](/widget/branding/custom-css-styling).

## API access setup

* API access is configured, if your team needs direct API requests, SDK workflows, or MCP-based AI tools.\
  Complete [API](/api) and [AI Integrations](/api/ai-integrations).
* API credentials are stored in approved backend, environment, MCP client, or secret storage only, if API access is used.

## Operations readiness

* Billing owner knows where to manage invoices, payment method, and plan changes.\
  Review [Billing and plans](/billing).
* Support owners know where to send users when issues happen.\
  Review [Support](/support).

## If something fails

* [Installation or visibility issues](/widget/installation/installation-troubleshooting)
* [Quoting failures or routing problems](/support/quoting-issues)


# Settings
Source: https://docs.remapdb.com/settings

Manage your account profile, company details, appearance, security, email preferences, billing, and account deletion.

Use this section to control how your Remapdb account works for you.

Click your name in the bottom-left main navigation, then click [Settings](https://app.remapdb.com/settings).

If you only need payment details, click your name in the bottom-left main navigation, then click [Billing](https://app.remapdb.com/settings/billing).

## Open settings pages in Remapdb

* [Account](https://app.remapdb.com/settings)
* [Company information](https://app.remapdb.com/settings/company)
* [Appearance](https://app.remapdb.com/settings/appearance)
* [Security](https://app.remapdb.com/settings/security)
* [Email preferences](https://app.remapdb.com/settings/notifications)
* [Billing](https://app.remapdb.com/settings/billing)

## What this section covers

* Your personal account details and login email.
* Your company profile details.
* App language and app theme.
* Password and account safety actions.
* Email communication preferences.
* Billing, invoices, and payment details.
* Permanent account deletion.

## Suggested order

* Start with [Account](/settings/account).
* Continue with [Company information](/settings/company-information).
* Update [Appearance](/settings/appearance) and [Security](/settings/security).
* Review [Email preferences](/settings/email-preferences).
* Finish with [Billing](/settings/billing).
* Use [Account deletion](/settings/account-deletion) only if you plan to permanently close the account.

## Pages in this section

<div>
  <Columns>
    <Card title="Account" href="/settings/account">
      Update personal information, change your login email, and open account deletion.
    </Card>

    <Card title="Company information" href="/settings/company-information">
      Manage your company name and business type.
    </Card>

    <Card title="Appearance" href="/settings/appearance">
      Set app language and app theme preferences.
    </Card>

    <Card title="Security" href="/settings/security">
      Change your password and handle common password issues.
    </Card>

    <Card title="Email preferences" href="/settings/email-preferences">
      Choose which product and update emails you want to receive.
    </Card>

    <Card title="Billing" href="/settings/billing">
      Review plan status, payment method, billing address, and invoices.
    </Card>

    <Card title="Account deletion" href="/settings/account-deletion">
      Permanently delete your account when you are fully ready.
    </Card>
  </Columns>
</div>

## Related actions

* [Billing and plans](/billing)
* [Feature availability by plan](/feature-availability-by-plan)


# Account
Source: https://docs.remapdb.com/settings/account

Update personal details, change your login email, and open the account deletion flow.

This page is for account owner identity and login-level changes.

Click your name at the bottom of the main navigation, click [**Settings**](https://app.remapdb.com/settings), then click [**Account**](https://app.remapdb.com/settings).

## Personal information

Use this area to keep your account owner details correct.

<Steps>
  <Step title="Open personal information">
    On **Settings > Account**, go to the **Personal information** section.
  </Step>

  <Step title="Update your details">
    Fill **First name**, **Last name**, **Phone number**, and (optional) **Time zone**.
  </Step>

  <Step title="Save">
    Click the **Save personal information** button.
  </Step>

  <Step title="Confirm">
    Refresh the page and confirm your saved values are still visible.
  </Step>
</Steps>

## Change your login email

Use this when your main login mailbox changes.

<Steps>
  <Step title="Open change email">
    On **Settings > Account**, go to the **Change email** section.
  </Step>

  <Step title="Enter the new address">
    Fill **New email** and **Confirm new email**.
  </Step>

  <Step title="Confirm with your password">
    Fill **Password**, then click the **Change email** button.
  </Step>

  <Step title="Approve from your new inbox">
    Open your new mailbox and click the confirmation link from Remapdb.
  </Step>
</Steps>

<Warning>
  Your login email does not change until you confirm from the new mailbox.
</Warning>

## Pending email-change request

If a request is already waiting for confirmation, you can:

* Click the **Resend confirmation email** button.
* Click the **Cancel email change** button.

If the request expires, start the flow again from **Change email**.

## Open account deletion

Click the **Delete account** button to open the deletion confirmation modal.

For the full irreversible process, open [Account deletion](/settings/account-deletion).

## Related actions

* [Security](/settings/security)
* [Billing](/settings/billing)
* [Account deletion](/settings/account-deletion)


# Account deletion
Source: https://docs.remapdb.com/settings/account-deletion



Use this page only when you are ready to permanently close your Remapdb account.

You can open the deletion flow from [**Settings**](https://app.remapdb.com/settings) on the [**Account**](https://app.remapdb.com/settings) page.

<Warning>
  Account deletion is permanent and cannot be undone.
</Warning>

## Before you delete your account

* Make sure your team no longer needs data in this account.
* Make sure no live customer workflow depends on your widget, WordPress plugin, or API access, including MCP-based AI tools.
* Make sure all account owners agree with permanent deletion.

## What you need

To confirm deletion, you must enter:

* Your exact account email
* Your current account password

## Delete your account

<Steps>
  <Step title="Open account page">
    Click your name at the bottom of the main navigation, click [**Settings**](https://app.remapdb.com/settings), then click [**Account**](https://app.remapdb.com/settings).
  </Step>

  <Step title="Open deletion modal">
    In the **Delete account** section, click the **Delete account** button.
  </Step>

  <Step title="Confirm credentials">
    In the modal, enter your **Email** and **Password**.
  </Step>

  <Step title="Delete">
    Click the **Delete account** button in the modal.
  </Step>
</Steps>

## What happens after deletion

* Access to your account stops.
* Embedded widget usage stops.
* WordPress plugin connection stops.
* API access from this account stops, including direct API requests and MCP-based AI tools.

If credentials are wrong, deletion is blocked until correct values are entered.

## Not sure yet?

If your goal is only to reduce cost or change plan level, use billing controls instead:

* [Billing](/settings/billing)
* [Billing and plans](/billing)

## Need help

* [Support request process](/support/support-request-process)


# Appearance
Source: https://docs.remapdb.com/settings/appearance

Set your app language and app theme for your Remapdb account interface.

Use this page to control how the Remapdb app looks for your own account session.

Click your name at the bottom of the main navigation, click [**Settings**](https://app.remapdb.com/settings), then click [**Appearance**](https://app.remapdb.com/settings/appearance).

## Change app language

<Steps>
  <Step title="Open appearance">
    Go to **Settings > Appearance**.
  </Step>

  <Step title="Pick language">
    Open the **Language** dropdown and select your preferred language.
  </Step>

  <Step title="Save">
    Click the **Save appearance** button.
  </Step>
</Steps>

After saving, the app interface reloads with the selected language.

## Change app theme

Use the **Theme** dropdown to select:

* **Light**
* **Dark**
* **Auto** (follows your system mode)

Theme change applies immediately after selection.

<Info>
  This page controls the Remapdb app interface only. It does not change your live widget branding. For widget design, open [Theme and layout](/widget/branding/theme-and-layout).
</Info>

## Related actions

* [Theme and layout](/widget/branding/theme-and-layout)
* [Colors and typography](/widget/branding/colors-and-typography)


# Billing
Source: https://docs.remapdb.com/settings/billing

Review your current plan, payment method, billing address, invoice history, and billing support options.

Use this page for day-to-day billing checks and billing profile updates.

You can open billing in two ways:

* Click your name in the bottom-left main navigation, then click [**Billing**](https://app.remapdb.com/settings/billing).
* Click your name in the bottom-left main navigation, click [**Settings**](https://app.remapdb.com/settings), then click [**Billing**](https://app.remapdb.com/settings/billing).

## Current plan

The **Current plan** section shows:

* Plan name
* Plan status
* Billing period
* Renewal date
* Current charge breakdown

You can also:

* Click the **Update subscription** button to open plan update options.
* Click the **Cancel subscription** button to start the subscription cancellation procedure.
* Click the **Cancel scheduled change** button when a future plan change is already scheduled.

Plan-change timing:

* Higher-cost paid-plan changes apply immediately with proration, and any amount due is charged now.
* Lower-cost paid-plan changes and downgrade to Free are scheduled for period end.

For full plan decisions, open [Billing and plans](/billing).

## Payment method

If your account has an active billing profile, this section shows your saved payment method.

* Click the **Manage** button to open the Stripe billing portal in a new tab.
* Update card details there, then return to Remapdb.

## Billing address

This section shows your current billing address and tax-related billing profile details.

* Click the **Manage** button to open the Stripe billing portal in a new tab.
* Update company and billing address details there.

## Invoice history

This section lists recent invoices with date, amount, and status.

* Click the invoice open icon to open a specific invoice.
* Click the **View invoices** button for full invoice history in the Stripe portal.

## Help and support

If you have billing issues:

* Click the support button in the **Help and support** section.
* Or open [Support request process](/support/support-request-process).

<Info>
  Some billing actions depend on your current plan and feature access. See [Feature availability by plan](/feature-availability-by-plan).
</Info>

## Related actions

* [Billing and plans](/billing)
* [Payment failed: next steps](/billing/payment-failed-next-steps)
* [Account deletion](/settings/account-deletion)


# Company information
Source: https://docs.remapdb.com/settings/company-information

Update your company name and business type used in your Remapdb account profile.

Use this page to keep your business identity details correct.

Click your name at the bottom of the main navigation, click [**Settings**](https://app.remapdb.com/settings), then click [**Company information**](https://app.remapdb.com/settings/company).

## What you can update

* **Company name**
* **Business type**

## Update company information

<Steps>
  <Step title="Open company information">
    Go to **Settings > Company information**.
  </Step>

  <Step title="Set the company name">
    Fill the **Company name** field. You can leave it empty if you do not want to show one here.
  </Step>

  <Step title="Select business type">
    Open the **Business type** dropdown and pick the option that best matches your business.
  </Step>

  <Step title="Save">
    Click the **Save company information** button.
  </Step>
</Steps>

## Related actions

* [Billing](/settings/billing)
* [Account](/settings/account)


# Email preferences
Source: https://docs.remapdb.com/settings/email-preferences

Choose which update and summary emails you want to receive from Remapdb.

Use this page to control non-critical communication emails.

Click your name at the bottom of the main navigation, click [**Settings**](https://app.remapdb.com/settings), then click [**Email preferences**](https://app.remapdb.com/settings/notifications).

## How saving works

Each toggle saves immediately when you switch it on or off. There is no Save button on this page.

## Available email categories

* **Database update emails**: New vehicles, ECU data, tools, and specs.
* **Promotional emails**: Occasional offers and recommendations.
* **New features and announcements**: Product updates and releases.
* **Quotes summary**: Quote activity summary.
* **Widget usage summary**: Widget activity summary.
* **API usage summary**: API usage summary.
* **Feedback and surveys**: Product feedback requests.

## Update your preferences

<Steps>
  <Step title="Open email preferences">
    Go to **Settings > Email preferences**.
  </Step>

  <Step title="Switch categories on or off">
    Use each category toggle based on what your team wants to receive.
  </Step>

  <Step title="Verify">
    Refresh the page once and confirm your toggle states remain as expected.
  </Step>
</Steps>

<Info>
  Disabling these toggles does not block critical account, security, or billing emails.
</Info>

## If a toggle does not save

* Toggle it once more and wait a second.
* Refresh the page and check again.
* If it still fails, open [Support request process](/support/support-request-process).

## Related actions

* [Settings](/settings)
* [Account](/settings/account)


# Security
Source: https://docs.remapdb.com/settings/security

Change your account password and resolve common password update issues.

Use this page to update your Remapdb account password.

Click your name at the bottom of the main navigation, click [**Settings**](https://app.remapdb.com/settings), then click [**Security**](https://app.remapdb.com/settings/security).

## Change password

<Steps>
  <Step title="Open security">
    Go to **Settings > Security**.
  </Step>

  <Step title="Enter your current password">
    Fill the **Current password** field.
  </Step>

  <Step title="Enter your new password">
    Fill **New password** and **Confirm new password**.
  </Step>

  <Step title="Save">
    Click the **Change password** button.
  </Step>
</Steps>

Password change applies immediately after successful save.

## Password rules

* You must enter your current password.
* New and confirmation passwords must match.
* Your new password must be at least **6 characters**.

## If you forgot your current password

* Click the **Forgot password?** link under the current password field.
* Complete the reset flow from your mailbox.
* Return to [**Settings > Security**](https://app.remapdb.com/settings/security) if you still need to set a different password.

## Common issues

| Issue                           | What to check                                                        | How to fix                                                                                                                    |
| ------------------------------- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Current password is rejected    | You may be entering your new password in the current password field. | Enter your current password in **Current password**, then try again.                                                          |
| New password confirmation fails | **New password** and **Confirm new password** are not identical.     | Click the **view password** icon in both fields to show plain text, compare both values, fix any mismatch, then submit again. |
| Form shows validation error     | One required field is empty, or the new password is too short.       | Fill all required fields and make sure the new password has at least **6 characters**.                                        |

## Related actions

* [Account](/settings/account)
* [Support request process](/support/support-request-process)


# Support
Source: https://docs.remapdb.com/support

Get help in Remapdb with the right support flow, clear troubleshooting order, and faster ticket resolution.

Use this section when you need help from the Remapdb team or you want to solve an issue quickly on your own.

## What this section covers

* How to pick the right support option in the app.
* How to submit a request that gets resolved faster.
* How to troubleshoot common widget, quoting, and API access issues before escalation.

## Support options in Remapdb

| Support option                      | Where to click                                                                                                     | Best for                                                                                                           | Plan requirement        |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | ----------------------- |
| General support request             | Open [Support](https://app.remapdb.com/support), then click the button with the support email address              | Bugs, account-specific issues, API access questions, unclear behavior                                              | None                    |
| Live chat support                   | Open [Support](https://app.remapdb.com/support), then click **Live chat support**                                  | Real-time help for active blockers                                                                                 | Feature access required |
| Widget code installation help       | Open [Support](https://app.remapdb.com/support), then in **Widget code installation** click **Request help**       | Script installation and placement help                                                                             | None                    |
| WordPress plugin installation help  | Open [Support](https://app.remapdb.com/support), then in **WordPress plugin installation** click **Request help**  | WordPress plugin setup help                                                                                        | Feature access required |
| Widget styling help                 | Open [Support](https://app.remapdb.com/support), then in **Widget complete custom styling** click **Request help** | Advanced widget styling help. Full flow: [Widget styling request process](/support/widget-styling-request-process) | Feature access required |
| Custom auto-reply email domain help | Open [Support](https://app.remapdb.com/support), then in **Custom auto-reply email domain** click **Request help** | Sender-domain setup guidance                                                                                       | Feature access required |

<Info>
  If a support action is disabled, check your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan) first.
</Info>

## Use this order when you need help

<Steps>
  <Step title="Start with the matching help page">
    Open the article for your exact issue first, so you can solve common setup mistakes without waiting for support.
  </Step>

  <Step title="Check current support availability">
    Open [Service status](/support/service-status) to see whether support is currently online and what response timing to expect.
  </Step>

  <Step title="Submit the most specific support flow">
    Open [Support request process](/support/support-request-process) and choose the form that matches your case.
  </Step>

  <Step title="Share complete evidence in the first message">
    Include the live page URL, widget ID, exact error text, screenshot, and the time of the latest failed test.
    If you are not sure where to find these, open [Support request process](/support/support-request-process#how-to-find-details-for-support-requests).
  </Step>
</Steps>

## Pages in this section

<div>
  <Columns>
    <Card title="Help center" href="/support/help-center">
      Find the right guide quickly and move through docs in the right order.
    </Card>

    <Card title="Support request process" href="/support/support-request-process">
      Learn the exact request forms, required fields, and what happens after submit.
    </Card>

    <Card title="Widget styling request process" href="/support/widget-styling-request-process">
      Submit complete styling requests with the right details so support can implement changes faster.
    </Card>

    <Card title="Service status" href="/support/service-status">
      Understand what the support status banner means and what to do next.
    </Card>

    <Card title="Widget not visible" href="/support/widget-not-visible">
      Fix missing widget output with a practical, code-accurate checklist.
    </Card>

    <Card title="Quoting issues" href="/support/quoting-issues">
      Fix quote form availability, validation, file upload, captcha, and delivery issues.
    </Card>
  </Columns>
</div>


# Help center
Source: https://docs.remapdb.com/support/help-center

Use the Remapdb help center efficiently and open the right guide for your exact task.

This page helps you find the correct guide quickly, without jumping between unrelated articles.

## Start from your goal

| If you want to...                             | Start here                                      |
| --------------------------------------------- | ----------------------------------------------- |
| Launch quickly and avoid missed setup steps   | [Quick setup checklist](/quick-setup-checklist) |
| Install with code or WordPress                | [Installation](/widget/installation)            |
| Configure widget behavior and SEO             | [Settings](/widget/settings)                    |
| Configure quote flow and automation           | [Quoting](/widget/quoting)                      |
| Set up API access and integrations            | [API](/api)                                     |
| Connect MCP-based AI tools through API access | [AI Integrations](/api/ai-integrations)         |
| Get direct help from the team                 | [Support](/support)                             |

## Fast way to find the right article

<Steps>
  <Step title="Open the section overview first">
    Start from the section root page (for example, Installation or Quoting) to see what each sub-page is for.
  </Step>

  <Step title="Open one task page at a time">
    Follow one guide fully, validate the result, then continue to the next related guide.
  </Step>

  <Step title="Use troubleshooting only when needed">
    If the expected result does not appear, open the matching troubleshooting page instead of guessing.
  </Step>
</Steps>

## When to switch from docs to support

Open [Support](https://app.remapdb.com/support) when:

* You followed the relevant guide and the issue still happens.
* You need account-specific help.
* You need assisted setup (for example WordPress installation, styling, or custom sender domain setup).

Then follow [Support request process](/support/support-request-process) so your first message includes everything the team needs.

## Related actions

* [Support](/support)
* [Support request process](/support/support-request-process)
* [Service status](/support/service-status)


# Quoting issues
Source: https://docs.remapdb.com/support/quoting-issues

Fix quote form problems in Remapdb, including unavailable quotes, validation failures, and missing quote emails.

Use this page when the quote form does not open, does not submit, or submits but your team does not receive the quote.

## Typical symptoms

* **Request a quote** does not open the form.
* The form opens but submission fails.
* You see validation, captcha, or checksum errors.
* File upload does not appear or an uploaded file is rejected.
* Dealer selector does not appear, or the selected dealer does not receive the quote email.
* You see a message that quotes are unavailable.
* The quote is submitted but your team does not receive it.

## Step-by-step fix

<Steps>
  <Step title="Step 1: Check quote availability and daily limit">
    Open the live widget, then click **Request a quote**.

    If quotes are unavailable, open [Manage daily quote limit](/widget/quoting/manage-daily-quote-limit) and check your current usage.
  </Step>

  <Step title="Step 2: Verify quote form setup">
    Open the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation, then open [Email and inputs](/widget/quoting/email-and-inputs).

    Confirm recipient email, visible fields, and required fields are configured as expected.
  </Step>

  <Step title="Step 3: Verify file upload setup when files are involved">
    Open [File upload](/widget/quoting/file-upload).

    Confirm your plan includes file upload, the **File upload** setting is turned on, and the test file is below the shown file limit.
  </Step>

  <Step title="Step 4: Verify services and options setup">
    Open [Set services and pricing](/widget/quoting/set-services-and-pricing).

    Confirm the service list is configured correctly for the vehicle types you use.
  </Step>

  <Step title="Step 5: Verify dealer setup when dealer routing is involved">
    Open [Set dealer network](/widget/quoting/set-dealer-network).

    Confirm **Enable dealers** is on, at least one dealer card is saved in **Manage dealers**, and the selected dealer email is correct.
  </Step>

  <Step title="Step 6: Retry submit with fresh form data">
    Re-select vehicle details, fill the form again, then submit.

    This avoids stale form state and mismatched validation data.
  </Step>

  <Step title="Step 7: Check captcha and browser blockers">
    If you see captcha errors, disable strict blocking extensions for the page and try again.
  </Step>

  <Step title="Step 8: Verify post-submit email flow">
    Open [Set up quoting automation](/widget/quoting/set-up-quoting-automation) and confirm sender/automation settings are correct.
  </Step>
</Steps>

## Common quote messages and what they mean

| Message                                                                                                  | Meaning                                                                              | What to do                                                                                                         |
| -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| `reCAPTCHA verification failed. Please try again.`                                                       | Captcha token was missing/invalid/expired                                            | Reload page and submit again; check blockers                                                                       |
| `Checksum verification failed.`                                                                          | Form data is out of sync with current vehicle selection                              | Re-select vehicle and submit again                                                                                 |
| `Thank you for your interest! Quotes are currently unavailable at this time. Please try again tomorrow.` | Daily quote limit has been reached                                                   | Check [Manage daily quote limit](/widget/quoting/manage-daily-quote-limit)                                         |
| `File uploads are not available for this widget.`                                                        | File upload is not included, not enabled, or no longer available for the widget plan | Check [File upload](/widget/quoting/file-upload) and [Feature availability by plan](/feature-availability-by-plan) |
| `You can upload up to ... files.`                                                                        | The selected files exceed the current file count limit                               | Remove extra files and submit again                                                                                |
| `File is too large. Max size is ...`                                                                     | One selected file exceeds the current size limit                                     | Upload a smaller file                                                                                              |
| `Fix the errors on the page to continue.`                                                                | One or more required fields are invalid                                              | Correct highlighted fields and resubmit                                                                            |

<Info>
  Quote capacity depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## If the issue continues

Include these details in your support request:

* Live page URL (copy from the browser address bar on the exact page used for the test).
* Widget ID (open **Installation**, then in **2. Install widget code** copy the `data-widget` value).
* Vehicle combination used in the test (vehicle type, brand, model, generation, engine).
* Exact error message shown (copy exactly as displayed).
* File name and file size, if the issue involves file upload.
* Selected dealer name and dealer email, if the issue involves dealer routing.
* Time of the failed submit (include your timezone).
* Screenshot of the form state.

Then open [Support request process](/support/support-request-process).

## Related actions

* [Quoting](/widget/quoting)
* [Manage daily quote limit](/widget/quoting/manage-daily-quote-limit)
* [Email and inputs](/widget/quoting/email-and-inputs)
* [File upload](/widget/quoting/file-upload)
* [Set dealer network](/widget/quoting/set-dealer-network)
* [Support request process](/support/support-request-process)


# Service status
Source: https://docs.remapdb.com/support/service-status

Understand the support status banner in Remapdb and decide the right next action.

This page explains what the status information on the Remapdb support page means.

## What this status shows

* Current support team availability.
* Working hours text in your timezone.
* Usual response-time expectation.

## What this status does not show

* It is not a full infrastructure uptime dashboard.
  For infrastructure status, check <a href="https://status.remapdb.com">Remapdb Infrastructure Status ↗</a> page.
* It does not confirm that your widget or account configuration is correct.

## Status messages and next action

| Status shown on the support page     | What it means                    | What to do next                                                         |
| ------------------------------------ | -------------------------------- | ----------------------------------------------------------------------- |
| **Need Support? We're Online!**      | Support team is currently online | Submit your request now from [Support](https://app.remapdb.com/support) |
| **Support is currently unavailable** | Team is outside support hours    | Submit your request anyway; it will be handled in business hours        |

## Recommended workflow

<Steps>
  <Step title="Check status first">
    Open [Support](https://app.remapdb.com/support) and review current availability.
  </Step>

  <Step title="Run the matching troubleshooting page">
    Open [Widget not visible](/support/widget-not-visible) or [Quoting issues](/support/quoting-issues) based on your problem.
  </Step>

  <Step title="Escalate with full evidence">
    If the issue remains, submit a request with URL, widget ID, error text, screenshot, and test time.
    If needed, use [Support request process](/support/support-request-process#how-to-find-details-for-support-requests) to collect each detail.
  </Step>
</Steps>

## Related actions

* [Support](/support)
* [Support request process](/support/support-request-process)
* [Help center](/support/help-center)
* <a href="https://status.remapdb.com">Remapdb Infrastructure Status ↗</a>


# Support request process
Source: https://docs.remapdb.com/support/support-request-process

Submit support requests in Remapdb with the correct form, required details, and faster resolution.

Use this page to submit support requests correctly and avoid back-and-forth.

## Open the support page

* Open [Support](https://app.remapdb.com/support).
* Choose the support flow that matches your issue.

## Request forms available in Remapdb

| Form                                | Where to click                                                | Required fields                            | Plan requirement        |
| ----------------------------------- | ------------------------------------------------------------- | ------------------------------------------ | ----------------------- |
| General support request             | Click the button with the support email address               | Category, Subject, Description, Captcha    | None                    |
| Widget code installation help       | In **Widget code installation**, click **Request help**       | Website URL, Captcha                       | None                    |
| WordPress plugin installation help  | In **WordPress plugin installation**, click **Request help**  | Website URL, Captcha                       | Feature access required |
| Widget complete custom styling help | In **Widget complete custom styling**, click **Request help** | Website URL, Captcha                       | Feature access required |
| Custom auto-reply email domain help | In **Custom auto-reply email domain**, click **Request help** | Business email address, From name, Captcha | Feature access required |

For the full styling-specific guide, open [Widget styling request process](/support/widget-styling-request-process).

<Info>
  If a request form is disabled, check your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## What happens after you submit

<Steps>
  <Step title="Your request is validated">
    Remapdb validates required fields and verifies captcha before creating the request.
  </Step>

  <Step title="Request details are stored">
    The request is saved with technical context such as request metadata.
  </Step>

  <Step title="Attachments are linked">
    If you attached files in the general support form, they are linked to the request.
  </Step>

  <Step title="You see confirmation immediately">
    You see a success message that confirms your request was received.
  </Step>

  <Step title="Support replies by email">
    The team replies to your request email. Usual response time is 1 to 3 business days.
  </Step>
</Steps>

## File attachments

* File attachments are available in the general support request form.
* Maximum file size is 20MB per file.
* You can attach images by directly pasting them into the description field while you are typing, or by using the upload button in the attachments section.
* If upload fails, submit the request without files, then include clear text details and re-send files in follow-up.

## Information to include in your first message

* Live page URL where the issue happens.
* Widget ID.
* Exact issue description: expected result and actual result.
* Exact error text and code, if shown.
* Screenshot or short video.
* Time of the latest failed test and your timezone.

## How to find details for support requests

Use this checklist when a form asks for URL, widget ID, or technical evidence.

### Live page URL

* Open the exact page where the issue happens.
* Copy the full address from your browser address bar.
* Use the published/live URL, not an editor-preview URL.

### Widget ID

* Open the [**Installation**](https://app.remapdb.com/widget/install) item in the main navigation.
* In the **Code** tab, open **2. Install widget code**.
* Find the `data-widget="..."` value in the embed script. That value is your widget ID.
* If needed, use [Code installation](/widget/installation/code-installation) for the full example.

### Exact error text and code

* Reproduce the issue once.
* Copy the full message exactly as shown on screen.
* If an error code is shown (for example `0032` or `9017`), include the code with the message.

### Time of latest failed test

* Right after reproducing the issue, note the exact date and time.
* Include your timezone (for example `UTC+2`).

### Screenshots or short video

* Capture the full page state where the issue is visible.
* Include the browser address bar in at least one screenshot.
* If possible, include the exact error message in the capture.

### Vehicle combination used in test (for quoting/widget issues)

* Note the exact selection used:
  * vehicle type
  * brand
  * model
  * generation
  * engine

### Endpoint path and method (for API issues)

* Include the request path (for example `/api/widget/seo`).
* Include the request method (`GET` or `POST`).
* If available, copy this from your integration logs or browser/network logs.
* For MCP-based AI tool issues, include the MCP client name and the prompt or tool call that failed.

## Related actions

* [Support](/support)
* [AI Integrations](/api/ai-integrations)
* [Service status](/support/service-status)
* [Widget styling request process](/support/widget-styling-request-process)
* [Widget not visible](/support/widget-not-visible)
* [Quoting issues](/support/quoting-issues)


# Widget not visible
Source: https://docs.remapdb.com/support/widget-not-visible

Fix cases where the Remapdb widget does not appear on your website.

Use this page when the widget does not show on your live page or shows an error in the widget area.

<Warning>
  If your website is missing in Allowed websites, the widget will not load.
</Warning>

## Step-by-step fix

<Steps>
  <Step title="Step 1: Check Allowed websites first">
    Open the [**Installation**](https://app.remapdb.com/widget/install) page in Remapdb, then check **Add allowed websites**.

    Make sure the website in your browser address bar is added exactly.

    If you need help with website format, open [Code installation](/widget/installation/code-installation#website-address-rules-and-examples).
  </Step>

  <Step title="Step 2: Confirm your plan website limit">
    If your plan website limit is full, newly added websites can stay listed but inactive.

    Open [Billing](https://app.remapdb.com/settings/billing) to check your current plan, and open [Feature availability by plan](/feature-availability-by-plan) for limits.
  </Step>

  <Step title="Step 3: Confirm code is installed on the live page">
    Check the live page source and confirm both are present:

    * Widget container element.
    * The Remapdb embed script with the correct widget ID.
  </Step>

  <Step title="Step 4: Test the published website, not editor preview">
    If you use a website builder, open the published website URL and test there.
  </Step>

  <Step title="Step 5: Check subscription health">
    If subscription is not operational, the widget can be blocked even when code and website are correct.

    Open [Billing](https://app.remapdb.com/settings/billing) and confirm subscription is active.
  </Step>

  <Step title="Step 6: Clear cache and test again">
    Clear website cache/CDN cache, then reload with hard refresh (`Ctrl/Cmd + Shift + R`).
  </Step>
</Steps>

## Most common widget error codes

| Error code | Meaning                         | Primary action                       |
| ---------- | ------------------------------- | ------------------------------------ |
| `0030`     | Widget ID not found             | Verify widget ID in embed code       |
| `0031`     | Website context missing         | Re-check embed setup                 |
| `0032`     | Website is not allowed          | Add this website in Allowed websites |
| `0036`     | Subscription is not operational | Fix subscription status in Billing   |

There are other less common error codes that may be displayed in the widget area.
If you see an error code that is not listed above, please contact support for assistance. Make sure to include the error code in your support request.

## Other common issues

| Issue                                                 | Primary action                                        |
| ----------------------------------------------------- | ----------------------------------------------------- |
| Widget is displayed but does not open                 | Re-check your widget configuration                    |
| Widget is displayed but styling is incorrect          | Check your branding settings and custom CSS           |
| Widget is displayed but some features are not working | Check your subscription plan for feature availability |

## If it still does not work

Send this in your support request:

* Live page URL (copy from the browser address bar on the page where the issue happens).
* Widget ID (open **Installation**, then in **2. Install widget code** copy the `data-widget` value).
* Full error text and code (copy exactly as shown).
* Screenshot of browser console/network errors.
* Time of the latest failed test (include your timezone).

If needed, use [Support request process](/support/support-request-process#how-to-find-details-for-support-requests) for a full “how to find each detail” checklist.

Then open [Support request process](/support/support-request-process).

## Related actions

* [Installation troubleshooting](/widget/installation/installation-troubleshooting)
* [Code installation](/widget/installation/code-installation)
* [Support request process](/support/support-request-process)


# Widget styling request process
Source: https://docs.remapdb.com/support/widget-styling-request-process

Submit a widget styling support request in Remapdb with the correct steps, required fields, and clear implementation details.

Use this page when you want the Remapdb support team to help with advanced widget styling.

## Before you start

* Confirm the style change cannot be done with your current branding settings.
* Prepare the exact website URL where the widget is live:
  * Open the live page where the widget is shown.
  * Copy the full URL from your browser address bar.
  * Use the published URL, not an editor preview URL.
* Prepare short, clear styling instructions (what to change and how it should look).

<Info>
  This request action depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan). If the action is disabled, your current plan does not include styling support.
</Info>

## Open the request form

You can open the same request form in two ways:

<Steps>
  <Step title="Open from Support">
    Click the [**Support**](https://app.remapdb.com/support) item in the main navigation, then click the **Request help** button in **Widget complete custom styling**.
  </Step>

  <Step title="Open from Branding">
    Click the [**Branding**](https://app.remapdb.com/widget/branding) item in the main navigation, scroll to the help section, then click the **Help me with styling** button.
  </Step>
</Steps>

## Fill and submit the form

<Steps>
  <Step title="Enter website URL">
    In **Website URL**, enter the exact live page URL where you want style changes applied.
    Copy this URL directly from your browser address bar.
  </Step>

  <Step title="Enter details (optional but recommended)">
    In **Details**, describe what should change. Add links or references if you have brand examples.
  </Step>

  <Step title="Complete captcha">
    Complete the captcha check in the form.
  </Step>

  <Step title="Submit">
    Click the **Request help** button.
  </Step>
</Steps>

## Field requirements

### Website URL

* Required.
* Must be a valid website address.

Examples:

* `example.com`
* `https://example.com`
* `https://shop.example.co.uk`

### Details

* Optional.

## How to write useful details

A good request usually includes:

* What should change (colors, fonts, spacing, buttons, inputs).
* Where it should change (specific pages or sections).
* Visual references (brand guide, website section, screenshot).
* Any constraints (deadline, legal text, accessibility requirement).

Example:

```bash theme={null}
Please align the widget with our site style.

Website URL
https://example.com

Changes
- Primary button color: #0B6E4F
- Input corners: 6px
- Keep high contrast in light and dark mode

Scope
Homepage and service pages only
```

## What happens after submission

* You receive an in-app confirmation.
* A request ID is created.
* Support follows up to your account email.
* Usual response target shown in the interface is 1 to 3 business days.

## If the form does not submit

* Check that **Website URL** is filled with a valid website address.
* Check that captcha is completed.
* If the action is disabled, check [Feature availability by plan](/feature-availability-by-plan) and your [Billing](https://app.remapdb.com/settings/billing).

## Related actions

* [Support](/support)
* [Support request process](/support/support-request-process)
* [Custom CSS styling](/widget/branding/custom-css-styling)
* [Customisations](/customisations)


# Branding
Source: https://docs.remapdb.com/widget/branding

Style your widget to match your website using theme, fonts, colors, sizes, and optional custom CSS.

Use this section to control how the widget looks on your website.

This section is for people who manage design and user experience in your company.

Click the [**Branding**](https://app.remapdb.com/widget/branding) item in the main navigation.

## What you can control in Branding

* Copyright notice visibility.
* Primary font.
* Theme mode (Light, Dark, Auto).
* Colors and sizes in the visual customizer.
* Advanced styling with custom CSS.

## Recommended setup order

<Steps>
  <Step title="Open Theme and layout first and set copyright notice and theme behavior." />

  <Step title="Set typography and color system in Colors and typography." />

  <Step title="Add Custom CSS only for edge cases that cannot be solved with built-in controls." />

  <Step title="Verify the result on your live website on desktop and mobile." />
</Steps>

<Info>
  Some Branding controls depend on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Pages in this section

<div>
  <Columns>
    <Card title="Theme and layout" href="/widget/branding/theme-and-layout">
      Control copyright notice visibility, choose light/dark/auto theme, and manage layout sizing behavior.
    </Card>

    <Card title="Colors and typography" href="/widget/branding/colors-and-typography">
      Set your primary font and tune widget colors and sizes in the visual customizer.
    </Card>

    <Card title="Custom CSS styling" href="/widget/branding/custom-css-styling">
      Add advanced styling rules when built-in Branding controls are not enough.
    </Card>
  </Columns>
</div>


# AI widget styling context
Source: https://docs.remapdb.com/widget/branding/ai-widget-styling-context

Context to give an AI assistant when generating Remapdb widget custom CSS.

Use this page when you want an external AI assistant, such as ChatGPT, Claude, Cursor, or Codex, to help generate custom CSS for the Remapdb widget.

Remapdb does not require a special AI assistant for styling. Your assistant only needs this styling context, the goal you want to achieve, and any brand colors or website examples you want it to follow.

## Copy this prompt

```text theme={null}
Read this Remapdb widget styling context:
https://docs.remapdb.com/widget/branding/ai-widget-styling-context

Generate only valid CSS for the Remapdb Custom CSS field.
Do not include <style> tags.
Prefer Remapdb CSS variables over deep selectors.
Use :root for light theme variables.
Use [data-bs-theme="dark"] for dark theme variables.
Use RGB channel values, not hex, for variables documented as RGB channels, for example --rdb-primary-color: 202, 0, 0;.
Keep selectors scoped to the widget iframe structure and avoid changing layout unless I ask for it.

Goal:
[describe the style you want]

Brand colors:
[add hex colors, fonts, or website URL]
```

## How widget styling is applied

The Remapdb widget is rendered inside an iframe. Custom CSS is injected into that iframe, after the default widget CSS and after the UI-based customizer variables.

The order is:

```text theme={null}
default widget theme CSS
customizer variables
custom CSS
```

This means Custom CSS can override values set in the UI customizer. When possible, ask the AI assistant to change `--rdb-*` variables first, then use selectors only for details that variables cannot cover.

## Theme model

Light theme variables go in `:root`.

```css theme={null}
:root {
  --rdb-widget-bg-2: #ffffff;
  --rdb-title-color: #17181c;
  --rdb-button-solid-bg: #17181c;
  --rdb-button-solid-color: #ffffff;
}
```

Dark theme variables go in `[data-bs-theme="dark"]`.

```css theme={null}
[data-bs-theme="dark"] {
  --rdb-widget-bg-2: #17181c;
  --rdb-title-color: #ffffff;
  --rdb-button-solid-bg: #ffffff;
  --rdb-button-solid-color: #17181c;
}
```

If the widget is set to **Auto**, Remapdb can switch the iframe theme based on the parent website theme. In that case, include both `:root` and `[data-bs-theme="dark"]` values.

## Recommended variables

Use these variables before targeting element classes:

```css theme={null}
:root {
  --rdb-widget-bg-2: #ffffff;
  --rdb-widget-bg-1: #f7f8fa;
  --car-specs-rdb-car-specs-bg-2: #ffffff;
  --rdb-title-color: #17181c;
  --rdb-table-color-1: #17181c;
  --rdb-table-color-2: #525b75;
  --rdb-form-control-bg: #ffffff;
  --rdb-form-control-color: #17181c;
  --rdb-form-control-border-color: #cbd0dd;
  --rdb-form-label-color: #525b75;
  --rdb-dropdown-bg: #ffffff;
  --rdb-dropdown-link-color: #17181c;
  --rdb-chip-bg: #eff2f6;
  --rdb-chip-color: #17181c;
  --rdb-button-solid-bg: #31374a;
  --rdb-button-solid-color: #ffffff;
  --rdb-button-outline-color: #31374a;
  --rdb-button-outline-border-color: #31374a;
  --rdb-modal-bg: #ffffff;
  --rdb-modal-color: #17181c;
  --rdb-border-radius: 0.125rem;
  --rdb-border-width: 1px;
}
```

See [CSS variable reference](/widget/branding/css-variable-reference) for the larger variable list.

## RGB channel variables

Some Remapdb variables are inserted into CSS like `rgb(var(--name))` or `rgba(var(--name), 0.25)`. These variables must contain only RGB channels, not a hex color.

Correct:

```css theme={null}
:root {
  --rdb-primary-color: 202, 0, 0;
}
```

Incorrect:

```css theme={null}
:root {
  --rdb-primary-color: #ca0000;
}
```

If you want to use a hex color, set the final component variable instead:

```css theme={null}
:root {
  --rdb-button-solid-bg: #ca0000;
  --rdb-button-outline-color: #ca0000;
  --rdb-form-control-focus-border-color: #ca0000;
}
```

Common RGB-channel variables:

```css theme={null}
--rdb-primary-color
--rdb-br-primary
--utility-white
--gray-900
--dark-gray-800
```

Do not override derived aliases such as `--rdb-text-primary` unless you understand where they are used. Prefer changing `--rdb-primary-color` as RGB channels, or set final component variables such as `--rdb-title-color` and `--rdb-button-solid-bg`.

## Main widget structure

The initial widget view contains:

```html theme={null}
<div class="container-fluid" data-iframe-size>
  <div id="quoting-success">...</div>
  <div id="vehicle-quote"></div>

  <div id="vehicle-form-content">
    <div id="rdb-alert-info" class="alert alert-info">...</div>

    <div id="vehicle-form" class="row">
      <select id="vehicle-type" class="form-select component-size">...</select>
      <select id="brand" class="form-select component-size">...</select>
      <select id="model" class="form-select component-size">...</select>
      <select id="generation" class="form-select component-size">...</select>
      <select id="engine" class="form-select component-size">...</select>
      <button id="show-remap" class="btn btn-secondary component-size">View remap</button>
      <div id="rdb-alert-danger" class="alert alert-danger">...</div>
    </div>

    <div class="border-disclaimer2 text-disclaimer2">Powered by remapdb.com</div>
  </div>

  <div id="vehicle-content-placeholder" class="bg-widget-content-1 placeholder-glow">...</div>
  <div id="vehicle-content" class="bg-widget-content-1">...</div>
</div>
```

The vehicle details content is loaded dynamically after a vehicle is selected and **View remap** is clicked.

## Quote form structure

When quoting is enabled, the quote panel contains:

```html theme={null}
<div id="quote-title" class="bg-modal">
  <div class="modal-title text-modal">Request a quote</div>
  <button class="btn btn-link close-quote">...</button>
</div>

<form id="quote-form">
  <input id="quote-name" class="form-control component-size">
  <input id="quote-email" class="form-control component-size">
  <input id="quote-phone" class="form-control component-size">
  <input id="quote-location" class="form-control component-size">
  <input id="quote-reg" class="form-control component-size">
  <input id="quote-vin" class="form-control component-size">
  <select id="quote-service" class="form-select component-size">...</select>
  <select id="quote-dealer" class="form-select component-size">...</select>
  <textarea id="quote-text" class="form-control component-size"></textarea>
  <div id="quote-files">...</div>
  <button id="quote-submit" class="btn component-size">...</button>
</form>
```

Optional quoting features may add pricing, services, options, dealer map controls, file upload, and custom message areas.

## Useful selectors

Prefer variables first. Use selectors only for targeted adjustments.

```css theme={null}
/* Vehicle selector row */
#vehicle-form .form-select {}
#show-remap {}

/* Vehicle result area */
#vehicle-content {}
.text-title {}
.text-table-1 {}
.bg-widget-content-1 {}
.bg-car-spec2 {}
.brand-logo {}

/* Disclaimer */
.text-disclaimer2 {}
.border-disclaimer2 {}

/* Quote panel */
#vehicle-quote {}
#quote-title {}
#quote-form .form-control {}
#quote-form .form-select {}
#quote-submit {}
.quote-container {}
.quote-file-dropzone {}
.quote-custom-message {}

/* Feedback and placeholders */
#rdb-alert-info {}
#rdb-alert-danger {}
#quoting-success {}
#vehicle-content-placeholder {}
```

## CSS rules for AI assistants

Ask the assistant to follow these rules:

* Output CSS only.
* Do not include `<style>` tags.
* Prefer `--rdb-*` variables over raw Bootstrap class overrides.
* Use `202, 0, 0` format, not `#ca0000`, for RGB-channel variables such as `--rdb-primary-color`.
* Include both light and dark theme values when the widget can use Auto theme.
* Avoid global website selectors. The CSS runs inside the widget iframe, but broad rules still make future maintenance harder.
* Avoid `@import`, external `url(...)`, fixed positioning, very large `z-index`, and layout resets.
* Avoid hiding required controls, validation messages, quote fields, or the View remap button.
* Avoid changing IDs or relying on generated option IDs.
* Test on desktop and mobile after saving.

## Example: dark premium style

```css theme={null}
:root {
  --rdb-widget-bg-2: #0f1115;
  --rdb-widget-bg-1: #171a21;
  --car-specs-rdb-car-specs-bg-2: #0f1115;
  --rdb-title-color: #f8fafc;
  --rdb-table-color-1: #f8fafc;
  --rdb-table-color-2: #cbd5e1;
  --rdb-form-control-bg: #111827;
  --rdb-form-control-color: #f8fafc;
  --rdb-form-control-border-color: #374151;
  --rdb-dropdown-bg: #111827;
  --rdb-dropdown-link-color: #f8fafc;
  --rdb-chip-bg: #242936;
  --rdb-chip-color: #f8fafc;
  --rdb-button-solid-bg: #d6b25e;
  --rdb-button-solid-color: #111111;
  --rdb-button-solid-hover-bg: #e8c772;
  --rdb-modal-bg: #0f1115;
  --rdb-modal-color: #f8fafc;
  --rdb-border-radius: 0.25rem;
}

[data-bs-theme="dark"] {
  --rdb-widget-bg-2: #0f1115;
  --rdb-widget-bg-1: #171a21;
  --car-specs-rdb-car-specs-bg-2: #0f1115;
  --rdb-title-color: #f8fafc;
  --rdb-table-color-1: #f8fafc;
  --rdb-table-color-2: #cbd5e1;
  --rdb-form-control-bg: #111827;
  --rdb-form-control-color: #f8fafc;
  --rdb-form-control-border-color: #374151;
  --rdb-dropdown-bg: #111827;
  --rdb-dropdown-link-color: #f8fafc;
  --rdb-chip-bg: #242936;
  --rdb-chip-color: #f8fafc;
  --rdb-button-solid-bg: #d6b25e;
  --rdb-button-solid-color: #111111;
  --rdb-button-solid-hover-bg: #e8c772;
  --rdb-modal-bg: #0f1115;
  --rdb-modal-color: #f8fafc;
}

#show-remap,
#quote-submit {
  text-transform: uppercase;
  font-weight: 800;
}
```

## More references

* [Custom CSS styling](/widget/branding/custom-css-styling)
* [CSS variable reference](/widget/branding/css-variable-reference)
* [Widget HTML and selectors](/widget/branding/widget-html-and-selectors)


# Colors and typography
Source: https://docs.remapdb.com/widget/branding/colors-and-typography

Set your primary font and customize widget colors and sizes for a consistent brand look.

Use this page to match widget typography and color style to your website design.

Click the [**Branding**](https://app.remapdb.com/widget/branding) item in the main navigation.

## Primary font

In the **Fonts** section, the **Primary Font** dropdown controls the main widget font.

What to expect:

* Fonts are provided from Google Fonts.
* Changing **Primary Font** updates widget text style.
* If custom fonts are not available on your account, this control can be disabled.

### Change the primary font

1. In **Fonts**, open **Primary Font**.
2. Click the font you want.
3. Wait for save confirmation and preview refresh.
4. Check readability for headings, labels, and buttons.

## Colors and sizes customizer

The **Customize colors and sizes ...** row opens a side panel for visual styling.

Important: this side panel follows your main **Theme** setting from the Branding page.

* If **Theme** is set to **Light**, the side panel works in Light only.
* If **Theme** is set to **Dark**, the side panel works in Dark only.
* If **Theme** is set to **Auto**, the side panel supports both Light and Dark color values.
* In **Auto**, a **Light theme / Dark theme** switch is available at the top of the side panel so you can review both sets.
* In **Light** or **Dark**, that top switch is hidden because the widget is locked to one mode.

There is no separate standalone preview mode setting in this panel.

In this side panel, you can:

* Adjust color values for key widget areas.
* Adjust size-related values where available.
* Save your styling changes.

<Steps>
  <Step title="Click the Customize colors and sizes ... row." />

  <Step title="Check your main Theme setting first (Light, Dark, or Auto), because it controls what color values are shown in the side panel." />

  <Step title="Open one variable group at a time and adjust values gradually." />

  <Step title="Check key UI areas after each change: text, buttons, forms, dropdowns, and chart." />

  <Step title="Click the Save button in the side panel." />

  <Step title="Recheck the result on a live page, not only in preview." />
</Steps>

## If some styling controls are limited

If you see limited controls or upgrade prompts in the customizer, this means your current access includes only part of the styling set.

<Info>
  Styling depth depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Good practice

* Start with text contrast and readability first.
* Keep one consistent button style across all widget states.
* Test both desktop and mobile before finalizing.
* Apply small changes in batches so issues are easy to track.

## Related actions

* [Branding](/widget/branding)
* [Theme and layout](/widget/branding/theme-and-layout)
* [Custom CSS styling](/widget/branding/custom-css-styling)


# CSS variable reference
Source: https://docs.remapdb.com/widget/branding/css-variable-reference

Remapdb widget CSS variables available for branding and custom CSS.

The widget theme is built around CSS variables. Use variables before overriding individual Bootstrap or utility classes.

Light theme values should be placed in `:root`. Dark theme values should be placed in `[data-bs-theme="dark"]`.

## Important: RGB channel variables

Some variables are used inside CSS functions such as `rgb(var(--rdb-primary-color))` or `rgba(var(--rdb-primary-color), 0.25)`. These variables must contain only RGB channels.

Correct:

```css theme={null}
:root {
  --rdb-primary-color: 202, 0, 0;
}
```

Incorrect:

```css theme={null}
:root {
  --rdb-primary-color: #ca0000;
}
```

If an AI assistant outputs `--rdb-primary-color: #ca0000;`, replace it with:

```css theme={null}
--rdb-primary-color: 202, 0, 0;
```

For most component variables, hex colors are fine:

```css theme={null}
:root {
  --rdb-button-solid-bg: #ca0000;
  --rdb-button-outline-color: #ca0000;
  --rdb-form-control-focus-border-color: #ca0000;
}
```

## Variables exposed in the UI customizer

These variables are part of the widget customizer allowlist.

### Free customizer variables

```css theme={null}
--rdb-widget-bg-2
--rdb-widget-bg-1
--car-specs-rdb-car-specs-bg-2
--rdb-button-solid-color
--rdb-button-solid-bg
--rdb-button-outline-color
--rdb-modal-bg
--rdb-button-solid-hover-color
--rdb-button-solid-active-color
--rdb-button-solid-disabled-color
--rdb-button-solid-active-bg
--rdb-button-solid-disabled-bg
--rdb-button-outline-hover-color
--rdb-button-outline-active-color
--rdb-button-outline-disabled-color
--rdb-button-outline-border-color
--rdb-button-outline-hover-border-color
--rdb-button-outline-active-border-color
--rdb-button-outline-disabled-border-color
--rdb-button-solid-hover-bg
--rdb-button-outline-hover-bg
--rdb-disclaimer1-color
--rdb-disclaimer1-border-color
--rdb-logo1-bg
--rdb-disclaimer2-color
--rdb-disclaimer2-border-color
--rdb-logo2-bg
```

### Full customizer variables

```css theme={null}
--rdb-widget-bg-2
--rdb-widget-bg-1
--car-specs-rdb-car-specs-bg-2
--rdb-button-solid-color
--rdb-button-solid-bg
--rdb-button-link-color
--rdb-table-color-1
--rdb-title-color
--rdb-form-control-color
--rdb-form-control-placeholder-color
--rdb-form-control-disabled-color
--rdb-form-label-color
--rdb-form-validation-text-color
--rdb-form-control-bg
--rdb-form-control-disabled-bg
--rdb-form-control-border-color
--rdb-form-control-hover-border-color
--rdb-form-check-border-color
--rdb-chip-color
--rdb-chip-bg
--rdb-chart-color-2
--rdb-chart-border-color-1
--rdb-chart-border-color-2
--rdb-chart-axis-color
--rdb-chart-border-color-3
--rdb-dropdown-link-color
--rdb-dropdown-header-color
--rdb-dropdown-bg
--rdb-dropdown-link-hover-bg
--rdb-dropdown-link-active-bg
--rdb-border-radius
--rdb-border-width
--rdb-button-link-active-color
--rdb-button-link-hover-bg
--rdb-button-solid-hover-color
--rdb-button-solid-active-color
--rdb-button-solid-disabled-color
--rdb-button-solid-active-bg
--rdb-button-solid-disabled-bg
--rdb-button-outline-color
--rdb-button-outline-hover-color
--rdb-button-outline-active-color
--rdb-button-outline-disabled-color
--rdb-button-outline-border-color
--rdb-button-outline-hover-border-color
--rdb-button-outline-active-border-color
--rdb-button-outline-disabled-border-color
--rdb-button-solid-hover-bg
--rdb-button-outline-hover-bg
--rdb-form-control-focus-color
--rdb-form-control-focus-bg
--rdb-form-check-bg
--rdb-dropdown-border-color
--rdb-form-control-focus-border-color
--rdb-form-control-focus-shadow-out
--rdb-form-control-disabled-border-color
--rdb-form-check-bg-checked
--rdb-form-check-hover-bg-checked
--rdb-form-check-focus-shadow-out
--rdb-form-check-hover-bg
--rdb-dropdown-link-hover-color
--rdb-dropdown-link-active-color
--rdb-modal-color
--rdb-table-color-2
--rdb-modal-bg
--rdb-disclaimer1-color
--rdb-disclaimer1-border-color
--rdb-logo1-bg
--rdb-disclaimer2-color
--rdb-disclaimer2-border-color
--rdb-logo2-bg
```

## Useful variable groups

### Backgrounds

```css theme={null}
--rdb-widget-bg-1
--rdb-widget-bg-2
--car-specs-rdb-car-specs-bg-2
--rdb-bg-lightest
--rdb-bg-lighter
--rdb-bg-light
--rdb-bg-semi-light
--rdb-bg-mid-light
--rdb-bg-darker
--rdb-bg-darkest
--rdb-modal-bg
--rdb-dropdown-bg
--rdb-success-card-bg
```

### Text

```css theme={null}
--rdb-title-color
--rdb-table-color-1
--rdb-table-color-2
--rdb-text-primary
--rdb-text-darker
--rdb-text-mid-dark
--rdb-text-mid
--rdb-text-lightest
--rdb-modal-color
--rdb-form-label-color
--rdb-form-validation-text-color
--rdb-disclaimer1-color
--rdb-disclaimer2-color
```

### Buttons

```css theme={null}
--rdb-button-solid-bg
--rdb-button-solid-color
--rdb-button-solid-border-color
--rdb-button-solid-hover-bg
--rdb-button-solid-hover-color
--rdb-button-solid-active-bg
--rdb-button-solid-active-color
--rdb-button-solid-disabled-bg
--rdb-button-solid-disabled-color
--rdb-button-outline-bg
--rdb-button-outline-color
--rdb-button-outline-border-color
--rdb-button-outline-hover-bg
--rdb-button-outline-hover-color
--rdb-button-outline-hover-border-color
--rdb-button-link-bg
--rdb-button-link-color
--rdb-button-link-hover-bg
--rdb-button-link-hover-color
```

### Forms and dropdowns

```css theme={null}
--rdb-form-control-bg
--rdb-form-control-color
--rdb-form-control-placeholder-color
--rdb-form-control-border-color
--rdb-form-control-hover-border-color
--rdb-form-control-focus-bg
--rdb-form-control-focus-color
--rdb-form-control-focus-border-color
--rdb-form-control-disabled-bg
--rdb-form-control-disabled-color
--rdb-form-control-disabled-border-color
--rdb-form-check-bg
--rdb-form-check-bg-checked
--rdb-form-check-border-color
--rdb-dropdown-bg
--rdb-dropdown-color
--rdb-dropdown-border-color
--rdb-dropdown-link-color
--rdb-dropdown-link-hover-bg
--rdb-dropdown-link-hover-color
--rdb-dropdown-link-active-bg
--rdb-dropdown-link-active-color
```

### Chips, charts, alerts, and sizing

```css theme={null}
--rdb-chip-bg
--rdb-chip-color
--rdb-chart-color-2
--rdb-chart-border-color-1
--rdb-chart-border-color-2
--rdb-chart-border-color-3
--rdb-chart-axis-color
--rdb-alert-success-bg
--rdb-alert-success-color
--rdb-alert-info-bg
--rdb-alert-info-color
--rdb-alert-warning-bg
--rdb-alert-warning-color
--rdb-alert-danger-bg
--rdb-alert-danger-color
--rdb-font-size
--rdb-border-radius
--rdb-border-width
```

## Full internal `--rdb-*` variable list

These variables are extracted from the current widget CSS. Some are lower-level implementation variables, so prefer the customizer variables above when possible.

```css theme={null}
--rdb-alert-danger-bg
--rdb-alert-danger-border-color
--rdb-alert-danger-color
--rdb-alert-danger-link-color
--rdb-alert-info-bg
--rdb-alert-info-border-color
--rdb-alert-info-color
--rdb-alert-info-link-color
--rdb-alert-offset
--rdb-alert-success-bg
--rdb-alert-success-border-color
--rdb-alert-success-color
--rdb-alert-success-link-color
--rdb-alert-warning-bg
--rdb-alert-warning-border-color
--rdb-alert-warning-color
--rdb-alert-warning-link-color
--rdb-bg-danger-light
--rdb-bg-danger-lighter
--rdb-bg-darker
--rdb-bg-darkest
--rdb-bg-info
--rdb-bg-light
--rdb-bg-lighter
--rdb-bg-lightest
--rdb-bg-mid-light
--rdb-bg-semi-light
--rdb-bg-success
--rdb-bg-warning
--rdb-border-radius
--rdb-border-width
--rdb-br-danger
--rdb-br-dark
--rdb-br-info
--rdb-br-light
--rdb-br-mid-light
--rdb-br-primary
--rdb-br-success
--rdb-br-warning
--rdb-button-link-active-bg
--rdb-button-link-active-border-color
--rdb-button-link-active-color
--rdb-button-link-bg
--rdb-button-link-border-color
--rdb-button-link-color
--rdb-button-link-danger-active-color
--rdb-button-link-danger-color
--rdb-button-link-danger-disabled-color
--rdb-button-link-danger-hover-color
--rdb-button-link-disabled-bg
--rdb-button-link-disabled-border-color
--rdb-button-link-disabled-color
--rdb-button-link-hover-bg
--rdb-button-link-hover-border-color
--rdb-button-link-hover-color
--rdb-button-link-success-active-color
--rdb-button-link-success-color
--rdb-button-link-success-disabled-color
--rdb-button-link-success-hover-color
--rdb-button-outline-active-bg
--rdb-button-outline-active-border-color
--rdb-button-outline-active-color
--rdb-button-outline-bg
--rdb-button-outline-border-color
--rdb-button-outline-color
--rdb-button-outline-disabled-border-color
--rdb-button-outline-disabled-color
--rdb-button-outline-hover-bg
--rdb-button-outline-hover-border-color
--rdb-button-outline-hover-color
--rdb-button-solid-active-bg
--rdb-button-solid-active-border-color
--rdb-button-solid-active-color
--rdb-button-solid-bg
--rdb-button-solid-border-color
--rdb-button-solid-color
--rdb-button-solid-disabled-bg
--rdb-button-solid-disabled-border-color
--rdb-button-solid-disabled-color
--rdb-button-solid-hover-bg
--rdb-button-solid-hover-border-color
--rdb-button-solid-hover-color
--rdb-chart-axis-color
--rdb-chart-border-color-1
--rdb-chart-border-color-1-rgb
--rdb-chart-border-color-2
--rdb-chart-border-color-3
--rdb-chart-color-2
--rdb-chip-bg
--rdb-chip-color
--rdb-disclaimer1-border-color
--rdb-disclaimer1-color
--rdb-disclaimer2-border-color
--rdb-disclaimer2-color
--rdb-dropdown-bg
--rdb-dropdown-border-color
--rdb-dropdown-color
--rdb-dropdown-divider-bg
--rdb-dropdown-header-color
--rdb-dropdown-link-active-bg
--rdb-dropdown-link-active-color
--rdb-dropdown-link-color
--rdb-dropdown-link-danger-color
--rdb-dropdown-link-danger-hover-color
--rdb-dropdown-link-disabled-color
--rdb-dropdown-link-hover-bg
--rdb-dropdown-link-hover-color
--rdb-font-size
--rdb-form-check-bg
--rdb-form-check-bg-checked
--rdb-form-check-border-color
--rdb-form-check-color
--rdb-form-check-focus-shadow-out
--rdb-form-check-hover-bg
--rdb-form-check-hover-bg-checked
--rdb-form-control-bg
--rdb-form-control-border-color
--rdb-form-control-color
--rdb-form-control-disabled-bg
--rdb-form-control-disabled-border-color
--rdb-form-control-disabled-color
--rdb-form-control-error-border-color
--rdb-form-control-error-focus-shadow-out
--rdb-form-control-focus-bg
--rdb-form-control-focus-border-color
--rdb-form-control-focus-color
--rdb-form-control-focus-shadow-in
--rdb-form-control-focus-shadow-out
--rdb-form-control-hover-border-color
--rdb-form-control-placeholder-color
--rdb-form-label-color
--rdb-form-radio-bg-checked
--rdb-form-section-color
--rdb-form-validation-error-color
--rdb-form-validation-text-color
--rdb-logo1-bg
--rdb-logo2-bg
--rdb-modal-bg
--rdb-modal-color
--rdb-offcanvas-footer-height
--rdb-offcanvas-header-height
--rdb-placeholder-bg
--rdb-primary-color
--rdb-success-card-bg
--rdb-success-card-color-1
--rdb-success-card-color-2
--rdb-table-color-1
--rdb-table-color-2
--rdb-text-danger-dark
--rdb-text-danger-light
--rdb-text-darker
--rdb-text-lightest
--rdb-text-mid
--rdb-text-mid-dark
--rdb-text-primary
--rdb-text-success-dark
--rdb-text-success-light
--rdb-title-color
--rdb-tooltip-bg
--rdb-tooltip-color
--rdb-widget-bg-1
--rdb-widget-bg-2
```

## Notes for AI assistants

* Prefer variables that describe the result, such as `--rdb-button-solid-bg`, over low-level aliases such as `--rdb-bg-darker`.
* Some variables expect RGB channel lists because they are used in `rgb(var(...))`, for example `--rdb-primary-color: 202, 0, 0;`.
* Most color variables accept hex, RGB, RGBA, HSL, or another CSS variable.
* Sizing variables should use CSS units such as `px`, `rem`, or `%`.


# Custom CSS styling
Source: https://docs.remapdb.com/widget/branding/custom-css-styling

Apply advanced CSS safely when built-in Branding controls are not enough.

Use this section when you need styling changes that are not possible through standard Branding controls.

Click the [**Branding**](https://app.remapdb.com/widget/branding) item in the main navigation.

## Where to edit custom CSS

* Go to the **Advanced** section.
* Use the **Custom CSS** field.

## Before you add CSS

* First try built-in controls in **Theme**, **Fonts**, and **Customize colors and sizes ...**.
* Use custom CSS only for edge cases.
* Keep rules scoped to the widget so website-wide styles are not affected.
* Prefer Remapdb CSS variables when changing colors, radius, borders, buttons, form controls, chips, charts, and quote panel styling.

## Add and save custom CSS

1. In **Advanced**, add your CSS in the **Custom CSS** field.
2. Click the **Save** button.
3. Check the widget preview.
4. Open a live page and verify the result.

## Validation rules you should know

* Do not add `<style>` tags.
* Very unsafe or invalid CSS can be removed during sanitization.

## Safe example

```css theme={null}
:root {
  --rdb-button-solid-bg: #17181c;
  --rdb-button-solid-color: #ffffff;
  --rdb-border-radius: 0.5rem;
}

#show-remap,
#quote-submit {
  font-weight: 800;
}
```

## Get help from an AI assistant

You can use your own AI assistant to generate CSS for the Custom CSS field.

Give the assistant this page first:

[AI widget styling context](/widget/branding/ai-widget-styling-context)

Then describe the style you want. For example:

```text theme={null}
Read the Remapdb widget styling context and generate CSS only.
Do not include <style> tags.
Make the widget match a dark luxury automotive website with black backgrounds, graphite form controls, white text, and subtle gold buttons.
Use Remapdb CSS variables where possible.
```

## Common mistakes

* Using very broad selectors that affect too many elements.
* Applying many `!important` rules and making future changes hard.
* Changing structural layout classes and breaking mobile rendering.
* Skipping live-page testing after save.

## Need help with styling

In **Advanced**, click the **Help me with styling** button when it is available.

<Info>
  Styling assistance availability depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Related actions

* [Branding](/widget/branding)
* [Theme and layout](/widget/branding/theme-and-layout)
* [Colors and typography](/widget/branding/colors-and-typography)
* [AI widget styling context](/widget/branding/ai-widget-styling-context)
* [CSS variable reference](/widget/branding/css-variable-reference)
* [Widget HTML and selectors](/widget/branding/widget-html-and-selectors)


# Theme and layout
Source: https://docs.remapdb.com/widget/branding/theme-and-layout

Set copyright visibility, choose widget theme mode, and control layout sizing behavior.

Use this page to set the base visual behavior of your widget before deeper styling.

Click the [**Branding**](https://app.remapdb.com/widget/branding) item in the main navigation.

## Before you start

* Make sure you are editing the correct widget.
* Open a live page where this widget is installed, so you can verify changes after each edit.

<Info>
  If a control is disabled, check your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Copyright notice

In the **Copyright notice** section, the **Show copyright notice** switch controls whether the widget shows the Remapdb logo and copyright details.

What to expect:

* The switch is on by default.
* If branding removal access is available, you can turn it on or off.
* If branding removal access is not available, the switch remains on.

### Change the copyright notice setting

1. Go to the **Copyright notice** section.
2. Turn the **Show copyright notice** switch on or off.
3. Wait for save confirmation and preview refresh.

## Theme mode

In the **Theme** dropdown, choose how the widget theme behaves:

| Theme option | What it does                                                                  |
| ------------ | ----------------------------------------------------------------------------- |
| Light        | Always uses light widget theme                                                |
| Dark         | Always uses dark widget theme                                                 |
| Auto         | Uses automatic mode and follows your website theme (light/dark) in real time. |

### Change theme mode

1. Open the **Theme** dropdown.
2. Click **Light**, **Dark**, or **Auto**.
3. Wait for save confirmation and preview refresh.

## Auto mode behavior

When **Theme** is set to **Auto**, the widget automatically follows your website theme.

What this means:

* No additional sync toggle is required.
* Theme updates follow your website light/dark state.
* Best for a consistent page + widget look.

<Info>
  For custom theme switchers, use the programmatic integration guide:
  [Sync widget theme with website](/widget/branding/theme-sync-with-website)
</Info>

## Colors and sizes panel

The **Customize colors and sizes ...** row opens a side panel where you can adjust visual variables and sizing.

Theme dependency:

* When **Theme** is **Light**, the side panel uses Light styling values.
* When **Theme** is **Dark**, the side panel uses Dark styling values.
* When **Theme** is **Auto**, the side panel works with both Light and Dark color values.
* When **Theme** is **Auto**, a **Light theme / Dark theme** switch appears at the top of the side panel.
* When **Theme** is **Light** or **Dark**, that side-panel switch is hidden.

1. Click the **Customize colors and sizes ...** row.
2. In the side panel, adjust values you need.
3. Click the **Save** button.

## Verify on live website

* Open the live widget page.
* Confirm theme matches your expected look.
* Confirm text remains readable in all key areas.
* Confirm spacing and controls look correct on desktop and mobile.

## Related actions

* [Branding](/widget/branding)
* [Sync widget theme with website](/widget/branding/theme-sync-with-website)
* [Colors and typography](/widget/branding/colors-and-typography)
* [Custom CSS styling](/widget/branding/custom-css-styling)


# Sync widget theme with your website
Source: https://docs.remapdb.com/widget/branding/theme-sync-with-website

Control widget light or dark theme from your website theme state and switcher.

Use this page when you want your website to control widget theme in real time.

## How it works

Website sync requires this widget setting:

* **Theme** = **Auto**

In Auto mode:

* Remapdb detects your website theme.
* It sends the resolved theme (`light` or `dark`) to the widget.
* Widget applies it without reloading.

## Automatic theme detection

Remapdb resolves your website theme using this priority:

1. `data-bs-theme` on `<html>`
2. `data-bs-theme` on `<body>`
3. Computed `color-scheme` on page root
4. Explicit theme classes (`dark`, `light`, `theme-dark`, `theme-light`, etc.)
5. Rendered page background luminance
6. `prefers-color-scheme` media query fallback

## Programmatic control from your theme switcher

### Option A: API call

```js theme={null}
window.RDBWidget?.setTheme('dark'); // light | dark | auto
```

Target a specific widget:

```js theme={null}
window.RDBWidget?.setTheme('dark', { widgetId: 'YOUR_WIDGET_ID' });
```

### Option B: Custom event

```js theme={null}
window.dispatchEvent(new CustomEvent('rdb-theme', {
  detail: { theme: 'dark' } // light | dark | auto
}));
```

## Typical integration with a website theme switcher

```js theme={null}
const applyTheme = (nextTheme) => {
  document.documentElement.setAttribute('data-bs-theme', nextTheme);
  window.RDBWidget?.setTheme(nextTheme);
};

themeToggleButton.addEventListener('click', () => {
  const current = document.documentElement.getAttribute('data-bs-theme') === 'dark' ? 'dark' : 'light';
  const next = current === 'dark' ? 'light' : 'dark';
  applyTheme(next);
});
```

## Debug checklist

* Ensure widget setting is **Theme = Auto**.
* Confirm your page actually exposes a theme signal (`data-bs-theme`, classes, or clear light/dark surface styles).
* Enable debug logs in widget settings and inspect browser console.
* If using custom switchers, always call `window.RDBWidget.setTheme(...)` after your site theme changes.

## Related pages

* [Theme and layout](/widget/branding/theme-and-layout)
* [Tracking events](/widget/tracking/tracking-events)


# Widget HTML and selectors
Source: https://docs.remapdb.com/widget/branding/widget-html-and-selectors

Current Remapdb widget iframe structure and useful selectors for custom CSS.

The Remapdb widget renders inside an iframe. Custom CSS is also injected inside that iframe.

Use this page as context for AI assistants that need to understand the widget structure before generating CSS.

<Warning>
  Prefer [CSS variables](/widget/branding/css-variable-reference) before selector overrides. Selector-based CSS is more likely to need updates after future widget changes.
</Warning>

## Initial selector form

The first visible view is the vehicle selector form.

```html theme={null}
<div class="container-fluid p-0 position-relative" data-iframe-size>
  <div id="quoting-success" class="d-none">...</div>
  <div id="vehicle-quote"></div>

  <div id="vehicle-form-content" class="p-4">
    <div id="rdb-alert-info" class="alert alert-info d-none">...</div>

    <div id="vehicle-form" class="row g-2">
      <select id="vehicle-type" class="form-select component-size">...</select>
      <select id="brand" class="form-select component-size">...</select>
      <select id="model" class="form-select component-size">...</select>
      <select id="generation" class="form-select component-size">...</select>
      <select id="engine" class="form-select component-size">...</select>
      <button id="show-remap" class="btn btn-secondary component-size">View remap</button>
      <div id="rdb-alert-danger" class="d-none">...</div>
    </div>
  </div>

  <div id="vehicle-content-placeholder" class="bg-widget-content-1 placeholder-glow d-none">...</div>
  <div id="vehicle-content" class="bg-widget-content-1 d-none">...</div>
</div>
```

Useful selectors:

```css theme={null}
#vehicle-form-content {}
#vehicle-form {}
#vehicle-form .form-select {}
#vehicle-type {}
#brand {}
#model {}
#generation {}
#engine {}
#show-remap {}
#rdb-alert-info {}
#rdb-alert-danger {}
#vehicle-content-placeholder {}
#vehicle-content {}
```

## Vehicle result area

After the visitor clicks **View remap**, Remapdb loads vehicle details and performance data into `#vehicle-content`.

Common classes in the result area:

```css theme={null}
.bg-widget-content-1 {}
.bg-car-spec2 {}
.brand-logo {}
.text-title {}
.text-table-1 {}
.form-section {}
.form-section-label {}
.text-disclaimer2 {}
.border-disclaimer2 {}
.placeholder {}
.text-placeholder {}
```

Common data attributes used by JavaScript:

```css theme={null}
[data-torque] {}
[data-torque-unit] {}
[data-stage] {}
```

The dyno chart reads chart colors from variables such as:

```css theme={null}
--rdb-chart-color-2
--rdb-chart-border-color-1
--rdb-chart-border-color-2
--rdb-chart-border-color-3
--rdb-chart-axis-color
```

## Quote panel

The quote panel is injected into `#vehicle-quote`.

```html theme={null}
<div id="quote-title" class="p-4 bg-modal">
  <div class="modal-title text-modal">Request a quote</div>
  <button class="btn btn-link close-quote">...</button>
</div>

<div class="quote-container">
  <form id="quote-form">
    <div class="form-control-parent">
      <label class="form-label" for="quote-name">Name</label>
      <input id="quote-name" class="form-control component-size">
      <div class="form-text">...</div>
      <div class="invalid-feedback">...</div>
    </div>

    <input id="quote-email" class="form-control component-size">
    <input id="quote-phone" class="form-control component-size">
    <input id="quote-location" class="form-control component-size">
    <input id="quote-reg" class="form-control component-size">
    <input id="quote-vin" class="form-control component-size">
    <select id="quote-service" class="form-select component-size">...</select>
    <select id="quote-dealer" class="form-select component-size">...</select>
    <textarea id="quote-text" class="form-control component-size"></textarea>
    <div id="quote-files">...</div>
    <button id="quote-submit" class="btn component-size">...</button>
  </form>
</div>
```

Useful quote selectors:

```css theme={null}
#vehicle-quote {}
#quote-title {}
#quote-form {}
#quote-form .form-control {}
#quote-form .form-select {}
#quote-name {}
#quote-email {}
#quote-phone {}
#quote-location {}
#quote-reg {}
#quote-vin {}
#quote-service {}
#quote-dealer {}
#quote-text {}
#quote-files {}
#quote-submit {}
.quote-container {}
.quote-custom-message {}
.quote-file-dropzone {}
.quote-more-options {}
.close-quote {}
```

## Dealer map and pricing selectors

These elements appear only when the related quoting features are enabled.

```css theme={null}
#quote-dealers-map {}
#quote-dealers-map-toggle {}
#quote-dealers-map-panel {}
#quote-dealer-details {}
#price-estimate-container {}
#price-estimate {}
#price-estimate-tooltip {}
```

## Safe selector patterns

Use focused selectors:

```css theme={null}
#vehicle-form .form-select {
  border-radius: 0.5rem;
}

#show-remap,
#quote-submit {
  font-weight: 800;
}

#quote-form .form-label {
  text-transform: uppercase;
  letter-spacing: 0.04em;
}
```

Avoid broad selector resets:

```css theme={null}
/* Avoid */
* {
  box-sizing: content-box;
}

/* Avoid */
.row {
  display: block;
}

/* Avoid */
.form-control {
  height: 80px;
}
```

## Class list snapshot

This is a compact list of useful classes currently present in the widget and quote form templates.

```text theme={null}
alert
alert-danger
alert-info
bg-car-spec2
bg-modal
bg-success-card
bg-widget-content-1
border-disclaimer2
brand-logo
btn
btn-icon
btn-link
btn-secondary
btn-sm
btn-w-icon-text
close-quote
component-size
container-fluid
form-check
form-check-component
form-check-input
form-check-label
form-control
form-control-parent
form-counter
form-element-counter
form-label
form-section
form-section-label
form-select
form-text
invalid-feedback
invalid-feedback-text
modal-title
placeholder
placeholder-glow
quote-container
quote-custom-message
quote-dealers-map
quote-file-dropzone
quote-file-input
quote-more-options
text-disclaimer2
text-modal
text-placeholder
text-success-card-1
text-success-card-2
text-table-1
text-title
```

## ID list snapshot

```text theme={null}
brand
engine
generation
model
price-estimate
price-estimate-container
price-estimate-tooltip
q-logo-container
q-logo-name-container
q-logo-name-container2
quote-controls
quote-dealer
quote-dealer-details
quote-dealers-map
quote-dealers-map-panel
quote-dealers-map-toggle
quote-email
quote-file-dropzone
quote-file-list
quote-files
quote-location
quote-name
quote-overlay
quote-phone
quote-phone-intl
quote-reg
quote-service
quote-submit
quote-text
quote-title
quote-vin
quoting-full-name
quoting-success
rdb-alert-danger
rdb-alert-info
show-remap
vehicle-content
vehicle-content-placeholder
vehicle-form
vehicle-form-content
vehicle-quote
vehicle-type
```


# Installation
Source: https://docs.remapdb.com/widget/installation

Install your Remapdb widget with clear steps and launch safely.

Use this section to move from setup to live widget with a clear, low-risk path.

## Use this section when

* You are installing Remapdb for the first time.
* You are adding a new website or replacing an old one.
* You need a clean checklist before launch.

<Warning>
  Before you install, add your website in **Installation -> Add allowed websites**.\
  If this is missing or wrong, the widget will not load on your live page.
</Warning>

## Success looks like

* The widget loads on the live page.
* Vehicle selection works and results load.
* A test quote is submitted successfully.

## Pages in this section

<div>
  <Columns>
    <Card title="Code installation" href="/widget/installation/code-installation">
      Install the widget with embed code on non-WordPress websites.
    </Card>

    <Card title="WordPress plugin installation" href="/widget/installation/wordpress-plugin-installation">
      Install and connect the official WordPress plugin.
    </Card>

    <Card title="Temporary WordPress access" href="/widget/installation/temporary-wordpress-access">
      Share temporary access safely when support helps with setup.
    </Card>

    <Card title="Website address rules" href="/widget/installation/code-installation#website-address-rules-and-examples">
      Add websites in the correct format so loading checks pass.
    </Card>

    <Card title="Installation checklist" href="/widget/installation/installation-checklist">
      Confirm launch readiness before and after go-live.
    </Card>

    <Card title="Installation troubleshooting" href="/widget/installation/installation-troubleshooting">
      Fix loading, access, or embed issues on live pages.
    </Card>
  </Columns>
</div>


# Code installation
Source: https://docs.remapdb.com/widget/installation/code-installation

Install the Remapdb embed code correctly and validate the widget on your live website.

<Warning>
  Always configure allowed websites first. The code can be present on the page, but the widget will still fail to render if the website is not allowed.
</Warning>

## Step 1: Add website in Remapdb

<Steps>
  <Step title="Open Add allowed websites">
    In `Installation`, find **1. Add allowed websites**.
  </Step>

  <Step title="Enter the exact website">
    Paste/type the exact website where the widget will run.
  </Step>

  <Step title="Save">
    Click **Save**.
  </Step>

  <Step title="Add additional websites if needed">
    If your widget is used on multiple websites, click **Add website** and save each one separately.
  </Step>
</Steps>

## Step 2: Install widget code

<Steps>
  <Step title="Open the Code tab">
    In `Installation`, stay on the **Code** tab.
  </Step>

  <Step title="Copy widget code">
    In **2. Install widget code**, click **Copy code**.
  </Step>

  <Step title="Paste into your page">
    Paste the snippet into the exact page section where the widget should appear.
  </Step>

  <Step title="Keep snippet parts together">
    Keep the wrapper `<div>` and the `<script>` in the same block. Do not separate them.
  </Step>

  <Step title="Publish">
    Save and publish/deploy your page.
  </Step>
</Steps>

The generated snippet contains:

```html theme={null}
<div class="rdb-widget" style="min-height:179px"></div>
<script async src=".../assets/widget/js/embed.js" data-widget="YOUR_WIDGET_ID" data-component-size="lg"></script>
```

## Placement rules that matter

* Use one widget instance per webpage.
* Do not remove the `data-widget` attribute.
* Do not change the script URL unless instructed by Remapdb support.
* If your CMS strips `<script>` tags, place the snippet in a code/HTML block that allows scripts.

## Verify in the live page

* Open the live public page in an incognito/private browser window.
* Confirm the widget area is visible where you placed the code.
* Select vehicle type, brand, model, generation, and engine.
* Confirm performance results load correctly.
* Submit a test quote and confirm it reaches your configured quote destination.

## Website address rules and examples

Enter the website name from the browser address bar.

Example website address:

```text theme={null}
https://shop.example.com/remap/audi-a4?source=ad
        ^^^^^^^^^^^^^^^^
        website to add
```

In this example, the value you add in **Add allowed websites** is:

```bash theme={null}
shop.example.com
```

Use these rules exactly when adding allowed websites:

* Enter only the website name, for example `example.com` or `shop.example.com`.
* Do not include page paths like `/pricing` or `/remap/audi-a4`.
* Do not include query strings like `?utm_source=...`.
* If you use multiple website variants (for example `example.com` and `shop.example.com`), add each one separately.
* The saved value must exactly match the website where the widget is running.

Good inputs:

```bash theme={null}
example.com
shop.example.com
remap.example.co.uk
```

Do not use:

```bash theme={null}
https://example.com/page
example.com/pricing
example
127.0.0.1
example_com
```

<Info>
  If your widget page is `https://tuning.example.com/chiptuning/audi-a4`, add exactly `tuning.example.com` in **Add allowed websites**.
</Info>

## Plan limits and active websites

The number of websites you can keep active depends on your plan:

| Plan | Active websites |
| ---- | --------------- |
| Free | 1 website       |
| Plus | 1 website       |
| Pro  | 5 websites      |
| API  | 1 website       |
| MAX  | 10 websites     |

<Info>
  If you move to a lower [plan](https://app.remapdb.com/settings/billing), websites above the new limit can still appear in your list, but only the allowed number will stay active until you upgrade or remove extras.
</Info>

## If it does not load

* Recheck **Add allowed websites** and confirm the saved website exactly matches the website shown in your browser address bar.
* Confirm your page, website builder, security settings, or optimization plugins are not blocking the widget script.
* Verify the copied snippet belongs to the same Remapdb account and widget you are configuring.
* Continue with [Installation troubleshooting](/widget/installation/installation-troubleshooting).


# Installation checklist
Source: https://docs.remapdb.com/widget/installation/installation-checklist

Use this short checklist to install the Remapdb widget correctly and confirm it works on your live website.

Use this page as a final yes/no checklist.

If any item is not done, open the linked help page, complete the steps there, then come back and continue.

## Shared checklist (everyone)

* Website is added in allowed websites.\
  Use [Code installation -> Step 1: Add website in Remapdb](/widget/installation/code-installation#step-1-add-website-in-remapdb).
* Live page is published (not only preview/editor).
* Widget is visible on the live page.
* Vehicle selection works and results load.
* Test quote is submitted and received.

## Checklist for code installation

* Code installation is completed.\
  Use [Code installation -> Step 2: Install widget code](/widget/installation/code-installation#step-2-install-widget-code).
* Code placement rules are followed.\
  Use [Code installation -> Placement rules that matter](/widget/installation/code-installation#placement-rules-that-matter).

## Checklist for WordPress plugin installation

* WordPress plugin is installed and activated.\
  Use [WordPress plugin installation](/widget/installation/wordpress-plugin-installation).
* Plugin is connected to your Remapdb account.\
  Use [WordPress plugin installation -> Connect the plugin to your Remapdb account](/widget/installation/wordpress-plugin-installation#connect-the-plugin-to-your-remapdb-account).
* Shortcode `[remapdb]` is added on the target page.\
  Use [WordPress plugin installation -> Add the widget to a page with shortcode](/widget/installation/wordpress-plugin-installation#add-the-widget-to-a-page-with-shortcode).

## If any checklist item fails

1. Open [Installation troubleshooting](/widget/installation/installation-troubleshooting).
2. Fix the problem.
3. Return here and re-run this checklist.


# Installation troubleshooting
Source: https://docs.remapdb.com/widget/installation/installation-troubleshooting

Use this short guide to fix widget installation problems for both code install and WordPress plugin install.

Use this page when the widget is blank, missing, or not working on your live page.

If you have not run the full setup flow yet, start with [Installation checklist](/widget/installation/installation-checklist).

## Quick checks first

1. Open the live public page URL (not preview mode).
2. Confirm your website is added in Remapdb.
   * In Remapdb, click the [**Installation**](https://app.remapdb.com/widget/install) item in the main navigation.
   * In **Add allowed websites**, confirm the exact live website is listed.
3. Reload the page with a hard refresh (`Ctrl/Cmd + Shift + R`).

## If you installed with code

1. Open the page source or page builder HTML area.
2. Confirm the widget container exists (`<div class="rdb-widget">`).
3. Confirm the embed script exists on the same page (`embed.js`).
4. Confirm you only have one widget snippet on that page.
5. Save, publish, and test again.

## If you installed with WordPress plugin

1. In WordPress admin, click the **Plugins** item in the main navigation.
2. Click the **Installed Plugins** link.
3. Confirm Remapdb plugin status is active.
4. Click the **Pages** item in the main navigation.
5. Click the **Edit** link for the target page.
6. Confirm shortcode `[remapdb]` is present.
7. Click the **Update** button.
8. Open the live page and test again.

## If it works on one URL but fails on another

1. Check the exact website in the browser address bar.
2. Add that exact website in **Add allowed websites**.
3. Repeat for each different website or subdomain you use.

## If changes are not visible

1. In WordPress, click the **Plugins** item in the main navigation.
2. Click the **Installed Plugins** link and check if you use a speed/cache plugin.
3. If yes, click the **Settings** link for that plugin.
4. Click the **Clear cache** button or the **Purge cache** button.
5. If you also use hosting/CDN cache, clear it there.
6. Reload with a hard refresh and test again.

## Still blocked?

1. Open [https://app.remapdb.com/support](https://app.remapdb.com/support) or email [support@remapdb.com](mailto:support@remapdb.com).
2. Send:
   * Live page URL
   * Screenshot of **Add allowed websites**
   * Short note: code install or WordPress install
   * Screenshot of what you see on the live page

After support fixes the issue, go back to [Installation checklist](/widget/installation/installation-checklist) and run all checklist items again.

<Info>
  Need full setup steps?\
  Use [Code installation](/widget/installation/code-installation) for code setup and [WordPress plugin installation](/widget/installation/wordpress-plugin-installation) for plugin setup.
</Info>


# Temporary WordPress access
Source: https://docs.remapdb.com/widget/installation/temporary-wordpress-access

Share temporary WordPress access securely when Remapdb support helps with plugin installation.

Use this only when support requests temporary access for installation or troubleshooting.

## Before you share temporary credentials

Before asking for WordPress help, make sure your [website is already added](/widget/installation/code-installation#step-1-add-website-in-remapdb) in Remapdb:

<Warning>
  If this is missing, the widget can fail to load even when plugin setup is correct.
</Warning>

## Create a temporary WordPress admin user

<Steps>
  <Step title="Open Users in WordPress">
    In WordPress admin, open **Users** from the main navigation.
  </Step>

  <Step title="Click Add user">
    Click the **Add user** button near the top of the page.
  </Step>

  <Step title="Fill user details">
    Complete the fields:

    * **Username**
    * **Email**
    * **Password** (use **Generate password**)
  </Step>

  <Step title="Set role to Administrator">
    In the **Role** dropdown, choose **Administrator**.
  </Step>

  <Step title="Create the user">
    Click the **Add User** button.
  </Step>
</Steps>

## Send this information to Remapdb support

Share these details through official Remapdb [support channels](https://app.remapdb.com/support):

1. Website URL where you want the widget to appear.
2. Temporary WordPress username.
3. Temporary WordPress password.

Support channels:

1. Email support.
2. Live chat (if included in your current plan).

## Important: what you should do yourself

The WordPress plugin installation flow is straightforward and is best done by you, because during setup you must enter your own Remapdb username and password.

<Warning>
  Security notice: Remapdb support will never ask for your personal Remapdb login credentials (email and password). Never share your personal account login details with anyone.
</Warning>

Remapdb support can help with:

1. Installing the plugin on your WordPress website.
2. Troubleshooting connection issues with the Remapdb app.
3. Reviewing screenshots and guiding you step by step.

## After support completes the work

For security, remove temporary access immediately:

1. Open **Users**.
2. Select the temporary user with the checkbox.
3. In **Bulk actions**, choose **Delete**.
4. Click **Apply**.

If you prefer to keep the user for a short time, change the password right away and remove access later.

<Warning>
  Never share your main owner/admin credentials. Always use a temporary user and remove it after support is done.
</Warning>


# WordPress plugin installation
Source: https://docs.remapdb.com/widget/installation/wordpress-plugin-installation

Install the official Remapdb WordPress plugin and connect it to your widget safely.

## Before you start

Confirm you have WordPress admin access.

* Open your WordPress admin login page and sign in (for example: `https://www.yourwebsite.com/wp-admin`).
* Click the **Users** item in the main navigation.
* Click the **Plugins** item in the main navigation.
* If you can open both pages and you can see the **Add user** button, your access is usually correct.
* If you cannot open these pages, ask the website owner to give you **Administrator** role.

## Method 1: Install from the plugin .zip file

<Steps>
  <Step title="Open the official plugin page">
    Open the official Remapdb WordPress plugin page: [https://wordpress.org/plugins/remapdb/](https://wordpress.org/plugins/remapdb/).
  </Step>

  <Step title="Download the official plugin zip">
    A new tab opens the official Remapdb WordPress plugin page. Click the **Download** button to get the plugin `.zip` file.
  </Step>

  <Step title="Open WordPress plugin upload">
    In WordPress admin, click the **Plugins** item in the main navigation, then click the **Add plugin** link.
  </Step>

  <Step title="Upload the zip file">
    Click the **Upload plugin** button near the top of the page, choose the downloaded plugin zip, and install it.\
    Do not unzip/unarchive the file before uploading.
  </Step>

  <Step title="Activate the plugin">
    After installation finishes, click the **Activate** button.
  </Step>
</Steps>

After successful activation, the Remapdb plugin appears in the main WordPress navigation.

## Method 2: Install directly from WordPress plugin search

<Steps>
  <Step title="Open Add Plugin page">
    In WordPress admin, click the **Plugins** item in the main navigation, then click the **Add plugin** link.
  </Step>

  <Step title="Search for the plugin">
    In the plugin search box, type **remapdb**.
  </Step>

  <Step title="Install the official plugin">
    Find the official Remapdb plugin and click the **Install now** button.
  </Step>

  <Step title="Activate the plugin">
    When installation completes, click the **Activate** button.
  </Step>
</Steps>

After successful activation, the Remapdb plugin appears in the main WordPress navigation.

## Connect the plugin to your Remapdb account

1. In WordPress admin, click the **Remapdb** item in the main navigation.
2. Click the **Settings** tab.
3. Click the **Connect remapdb** button.
4. Follow the on-screen instructions to complete connection.

The connection step should be done by you, because you must enter your own Remapdb account credentials.

## Add the widget to a page with shortcode

After the plugin is connected, place the widget on the page where you want it to appear.

Use this shortcode:

```bash theme={null}
[remapdb]
```

Most websites add this inside a **Shortcode** block.

### Block editor (Gutenberg)

1. Open the page in WordPress editor.
2. Click the **Add block** button.
3. Search for and select the **Shortcode** block.
4. Paste `[remapdb]` in the block.
5. Click the **Update** button or click the **Publish** button.

### Elementor

1. Open the page in Elementor editor.
2. Click the **Widgets** tab.
3. Search for **Shortcode**.
4. Drag and drop the **Shortcode** widget to the desired location on the page.
5. Paste `[remapdb]` in the shortcode text area.
6. Click the **Apply** button to apply the changes or click the **Update** button if you are editing an existing page.

### Classic editor

1. Open the page in WordPress editor.
2. Paste `[remapdb]` in the content where the widget should appear.
3. Click the **Update** button or click the **Publish** button.

## Verify on live website

1. Open the live page URL.
2. Confirm the widget loads and accepts vehicle selections.
3. Submit a test quote and verify email delivery.

## Common issues

1. Domain not added in allowed websites.
   * In Remapdb, click the [**Installation**](https://app.remapdb.com/widget/install) item in the main navigation.
   * In **Add allowed websites**, make sure the exact website is saved.
   * If needed, follow [Add website in Remapdb](/widget/installation/code-installation#step-1-add-website-in-remapdb).
   * Open your live page again and test.
2. Plugin is active, but shortcode/block is missing from the page.
   * In WordPress, click the **Pages** item in the main navigation.
   * Click the **Edit** link on the page where the widget should appear.
   * Add a **Shortcode** block.
   * Paste `[remapdb]`.
   * Click the **Update** button.
   * Reload the live page and test.
3. An old saved version of the page is still loading.
   * In WordPress, click the **Plugins** item in the main navigation.
   * Click the **Installed Plugins** link and check if you use a speed/cache plugin.
   * If you use one, click the **Settings** link for that plugin, then click the **Clear cache** button or the **Purge cache** button.
   * If you do not use one, skip this step and continue.
   * If your hosting panel or CDN also has cache, clear it there too.
   * Reload the page with a hard refresh (`Ctrl/Cmd + Shift + R`) and test again.
4. Theme or page builder removes shortcode output.
   * Click the **Edit** link on the same page and move `[remapdb]` to a simple content area first.
   * Test with a basic **Shortcode** block instead of advanced theme blocks.
   * If it works in a simple block, keep it there or ask your theme support how to allow shortcode rendering in your current block type.

## Need help from support

If you have any issue, click the **Support** tab in the plugin and click the **Open Remapdb Support** button to see official support channels.

You can also contact us directly:

1. Support page: [https://app.remapdb.com/support](https://app.remapdb.com/support)
2. Support email: [support@remapdb.com](mailto:support@remapdb.com)

When contacting support, describe the issue clearly and include screenshots when possible.


# Quoting
Source: https://docs.remapdb.com/widget/quoting

Set up your full quote flow in Remapdb, from form fields and services to dealer routing and email automation.

Use this section to configure how visitors request quotes and how your team receives and follows up on those requests.

Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation.

## What this section includes

* Daily quote capacity and limit handling.
* Quote form fields and recipient email.
* File uploads for quote requests.
* Services, options, and optional estimated pricing.
* Optional dealer routing.
* Customer auto-reply email setup.
* Custom sender-domain setup details for auto-reply emails.

## Recommended setup order

* Set your quote inbox in [Email and inputs](/widget/quoting/email-and-inputs).
* Turn on supporting file collection in [File upload](/widget/quoting/file-upload), if your plan includes it.
* Configure services and options in [Set services and pricing](/widget/quoting/set-services-and-pricing).
* Configure dealer routing in [Set dealer network](/widget/quoting/set-dealer-network) (if needed).
* Configure customer emails in [Set up quoting automation](/widget/quoting/set-up-quoting-automation).
* If needed, prepare sender-domain setup in [Custom email domain setup information](/widget/quoting/custom-email-domain-setup-information).
* Track quote usage in [Manage daily quote limit](/widget/quoting/manage-daily-quote-limit).

## Quote email flow at a glance

After a successful quote submission:

* Your team inbox receives the quote.
* Uploaded files are linked in quote emails (if file upload is enabled).
* The selected dealer can also receive the quote (if dealer routing is enabled).
* The visitor can receive an automatic confirmation email (if auto-reply is enabled).

<Info>
  Some quoting controls depend on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

<Warning>
  If the quote destination email is not set correctly, quote requests can be missed.
</Warning>

## Pages in this section

<div>
  <Columns>
    <Card title="Manage daily quote limit" href="/widget/quoting/manage-daily-quote-limit">
      Track your daily quote usage and avoid missed leads.
    </Card>

    <Card title="Email and inputs" href="/widget/quoting/email-and-inputs">
      Configure quote inbox, visible inputs, and custom message.
    </Card>

    <Card title="File upload" href="/widget/quoting/file-upload">
      Let visitors attach ECU reads, photos, logs, or supporting documents to quote requests.
    </Card>

    <Card title="Set services and pricing" href="/widget/quoting/set-services-and-pricing">
      Manage services, options, and optional estimated pricing.
    </Card>

    <Card title="Set dealer network" href="/widget/quoting/set-dealer-network">
      Route requests to the right branch or partner inbox.
    </Card>

    <Card title="Set up quoting automation" href="/widget/quoting/set-up-quoting-automation">
      Send automatic customer confirmation emails with dynamic content.
    </Card>

    <Card title="Custom email domain setup information" href="/widget/quoting/custom-email-domain-setup-information">
      Prepare sender-domain details for custom auto-reply delivery setup.
    </Card>
  </Columns>
</div>


# Custom email domain setup information
Source: https://docs.remapdb.com/widget/quoting/custom-email-domain-setup-information

Request custom sender-domain setup for quote auto-reply emails and prepare the exact details support needs.

Use this page when you want quote auto-reply emails to be sent from your business email identity instead of the default `remapdb.com` sender domain.

## What this changes

After setup is completed, your customer auto-reply emails can show your business sender identity (for example `quotes@yourdomain.com`) and your sender name.

This makes your emails look more branded and trusted for your customers.

## Where to start in the interface

You can open the same request flow from two places:

* Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation, go to the automation area, then click the **Help me use my domain** button.
* Click the [**Support**](https://app.remapdb.com/support) item in the main navigation, find **Custom auto-reply email domain**, then click the **Request help** button.

Both paths open the same support request form.

## Before you submit

* Make sure auto-reply is already configured in [Set up quoting automation](/widget/quoting/set-up-quoting-automation).
* Decide which business email address you want to use as the sender.
* Decide which sender name customers should see.
* Make sure you can update your DNS records when support sends verification instructions.

<Info>
  Custom sender-domain setup depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan). If the action is not available, your current plan does not include this feature.
</Info>

## Submit the request

<Steps>
  <Step title="Open the request form">
    Click the **Help me use my domain** button in Quoting, or click the **Request help** button in the **Custom auto-reply email domain** support card.
  </Step>

  <Step title="Enter business email address">
    In **Business email address**, enter the mailbox you want to use for auto-replies.
  </Step>

  <Step title="Enter from name">
    In **From name**, enter the sender name customers should see.
  </Step>

  <Step title="Add details (optional)">
    In **Details**, add useful context such as DNS provider, technical contact, and go-live date.
  </Step>

  <Step title="Complete captcha and submit">
    Complete the captcha check, then click the **Request help** button.
  </Step>
</Steps>

## Field requirements

### Business email address

* Required.
* Must be a valid email address format.

### From name

* Required.
* Maximum 120 characters.
* Must not include special header-unsafe characters such as `<`, `>`, `:`, `"`, `\`, or line breaks.

### Details

* Optional.

## What happens after you submit

* Your request is saved and assigned a request ID.
* Your request is routed to the support team.
* You see a confirmation message in the interface.
* Support follows up to your account/request email (usual response target is 1 to 3 business days).

## What support needs from you

* Business sender email address.
* Sender name.
* DNS provider name (for example Cloudflare, GoDaddy, cPanel).
* Person who can apply DNS changes.
* Target launch date (if you have one).

## Validate the setup after support confirms completion

* Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation and confirm **Send auto-reply email** is turned on.
* Submit one real test quote from a live page where your widget is installed.
* Open the received auto-reply and confirm the sender address and sender name are correct.
* Reply to the message and confirm the reply reaches your quote inbox.

## Example request text

```text theme={null}
Business email address
quotes@yourdomain.com

From name
Your Brand Performance

Details
Please set up our custom sender domain for quote auto-replies.
Our DNS is managed in Cloudflare. We can apply records within 1 business day.
Target launch date: 2026-05-01.
```

<Warning>
  Do not announce the new sender address in customer campaigns until you complete a full live test and confirm delivery.
</Warning>

## Related actions

* [Set up quoting automation](/widget/quoting/set-up-quoting-automation)
* [Quoting](/widget/quoting)
* [Support request process](/support/support-request-process)


# Email and inputs
Source: https://docs.remapdb.com/widget/quoting/email-and-inputs

Choose which fields your visitors fill in, where quotes are sent, and how quote form settings connect to file upload and custom message.

This page controls what your visitors see in the quote form and what information your team receives.

Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation.

## Step 1: Set where quotes are sent

In the **Email to receive quotes** section:

1. Enter the team mailbox that should receive quote requests.
2. Click the **Save** button.
3. Submit one test quote from the live widget and confirm your mailbox receives it.

Use a shared team mailbox when possible, not one personal inbox.

## Step 2: Choose which inputs are visible

In the **Visible inputs** section, turn each switch on or off based on what you want to collect.

| Input in quote form    | What your visitor can provide  |
| ---------------------- | ------------------------------ |
| Location               | City and country               |
| Registration number    | Vehicle registration number    |
| VIN number             | Vehicle VIN                    |
| Options                | Extra service options          |
| Additional information | Free-text details and requests |

The following inputs are always required by default:

* Name.
* Email address.
* Phone.

## Step 3: Set the custom message section

In the **Custom message** section:

1. Turn on the **Enable custom message** switch.
2. Add your message text.
3. Click the **Save** button.

What this section is for:

* Add short business notes under the form.
* Add disclaimer text.
* Add response expectations (for example expected response time).
* Add special instructions for visitors before they submit.

Where visitors see it:

* At the bottom of the quote form in the widget.

<Info>
  If **Enable custom message** is disabled or not available on your [plan](https://app.remapdb.com/settings/billing), the custom message will not appear in the widget.
</Info>

## Step 4: Configure file upload when needed

The **File upload** section controls whether visitors can attach files to quote requests.

Use it when your team needs supporting files such as ECU reads, photos, logs, or documents before preparing a quote.

For full setup, limits, and email behavior, open [File upload](/widget/quoting/file-upload).

<Info>
  File upload is available on the **Pro** and **MAX** plans. If **File upload** is disabled, check [Feature availability by plan](/feature-availability-by-plan).
</Info>

## Step 5: Verify on your live website

1. Open a real page where the widget is installed.
2. Open the quote form.
3. Confirm only the intended inputs are visible.
4. If file upload is enabled, attach a small test file and wait until it finishes uploading.
5. Submit a test quote and confirm your team receives the expected details.

## Important dependencies

* **Registration number** and **VIN number** depend on your plan feature access.
* **Options** appear only when you have active options in services setup.
* **Dealer selector** appears only after **Enable dealers** is on and at least one dealer is saved in **Manage dealers**.
* **File upload** appears only when your plan includes file upload and the **File upload** setting is turned on.

For dealer setup, see [Set dealer network](/widget/quoting/set-dealer-network).
For services and options setup, see [Set services and pricing](/widget/quoting/set-services-and-pricing).
For file upload setup, see [File upload](/widget/quoting/file-upload).

## Related actions

* [File upload](/widget/quoting/file-upload)
* [Set services and pricing](/widget/quoting/set-services-and-pricing)
* [Set dealer network](/widget/quoting/set-dealer-network)
* [Set up quoting automation](/widget/quoting/set-up-quoting-automation)
* [Manage daily quote limit](/widget/quoting/manage-daily-quote-limit)


# File upload
Source: https://docs.remapdb.com/widget/quoting/file-upload

Let visitors attach ECU reads, photos, logs, or supporting documents to quote requests.

Use this page when you want customers to send files with quote requests.

Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation, then open the **File upload** section.

## What file upload does

When file upload is enabled, the quote form shows a **Files** upload area near the bottom of the form.

Visitors can attach supporting files such as:

* ECU read files
* Vehicle photos
* Diagnostic logs
* Supporting documents
* Other files your team needs before preparing a quote

After the quote is submitted, uploaded files are linked in quote emails so your team can download them.

<Info>
  File upload is available on the **Pro** and **MAX** plans.
</Info>

## Turn on file upload

<Steps>
  <Step title="Open Quoting">
    Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation.
  </Step>

  <Step title="Find File upload">
    Scroll to the **File upload** section.
  </Step>

  <Step title="Enable the setting">
    Turn on the **File upload** switch.
  </Step>

  <Step title="Check the live widget">
    Open a live page where the widget is installed, select a vehicle, and open the quote form.
  </Step>
</Steps>

## What visitors see

When the setting is active, visitors see a **Files** field in the quote form.

They can:

* Drag files into the upload area.
* Click **browse** to select files from their device.
* Remove a selected file before submitting the quote.

The quote submit button can stay disabled while files are still uploading. Wait until uploads finish before submitting a test quote.

## File limits

The live upload area shows the current limit, for example:

```text theme={null}
Up to 4 file(s), 10 MB each.
```

Your exact file count can depend on the active upload configuration.
The default size limit is **10 MB per file** unless Remapdb has configured a different limit for your environment.

If a visitor selects too many files, only the allowed number is processed.
If a file is too large, the form shows a size error and the file is not attached.

## What your team receives

Uploaded files are added to quote emails as download links.

Your team receives the file links in the main quote email. If dealer routing is enabled and the visitor selects a dealer, the selected dealer can also receive the quote email with the same file links.

The quote email also includes a file security notice:

* Remapdb does not scan uploaded files for viruses.
* Scan files before opening them.
* Uploaded file links are not permanent storage. Download and store files you need for customer work in your own workflow.

<Warning>
  Only open files you trust and scan uploaded files before using them. Treat customer uploads like any other external attachment.
</Warning>

## If the setting is disabled

If **File upload** is disabled or does not save:

1. Open [Feature availability by plan](/feature-availability-by-plan).
2. Confirm your account is on **Pro** or **MAX**.
3. Open [Billing](https://app.remapdb.com/settings/billing) and confirm your subscription is active.
4. Reload **Quoting** and check the setting again.

When you move to a lower plan, Remapdb can keep the saved setting, but the live widget will not show file upload until your plan includes the feature again.

## Verify end-to-end

<Steps>
  <Step title="Open a live widget page">
    Use a real published page where the widget is installed.
  </Step>

  <Step title="Open the quote form">
    Select a vehicle, then click **Request a quote**.
  </Step>

  <Step title="Attach a small test file">
    Use a harmless test file below the size limit.
  </Step>

  <Step title="Submit the quote">
    Wait until the upload finishes, then submit the quote.
  </Step>

  <Step title="Check the received email">
    Confirm the quote email includes the uploaded file link and the file security notice.
  </Step>
</Steps>

## Related actions

* [Email and inputs](/widget/quoting/email-and-inputs)
* [Set services and pricing](/widget/quoting/set-services-and-pricing)
* [Set up quoting automation](/widget/quoting/set-up-quoting-automation)
* [Quoting issues](/support/quoting-issues)
* [Feature availability by plan](/feature-availability-by-plan)


# Manage daily quote limit
Source: https://docs.remapdb.com/widget/quoting/manage-daily-quote-limit

Track your daily quote capacity, understand what counts, and avoid missed leads.

This page helps you monitor your daily quote capacity and prevent lost requests.

Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation.

## Check your current usage

In the top usage block, review:

* Quotes received today.
* Your daily quote limit.
* The progress bar.
* The exceeded attempts count.

The exceeded attempts count shows how many quote tries happened after your daily limit was reached.\
This helps you understand how many potential customers wanted to submit a quote but could not. If this number keeps growing, it is a clear signal to increase quote capacity before your next campaign.

## What counts toward your daily limit

Counted:

* Quotes that are successfully submitted and accepted.

Not counted:

* Opening the quote form.
* Validation errors (for example missing required fields).
* Failed reCAPTCHA checks.
* Failed integrity checks.

Still tracked separately:

* Attempts made after the daily limit is already reached (these increase the exceeded attempts count).

## What your visitors see when the limit is reached

When the limit is reached:

* New quote requests are blocked.
* The visitor sees that quotes are not available right now.
* Quoting becomes available again after the next daily reset.

<Warning>
  When the daily limit is reached, new leads cannot submit quotes. If this happens often, [review your plan](https://app.remapdb.com/settings/billing) before active campaigns.
</Warning>

## Reset time

Your quote usage resets every day at **00:00 UTC**.

This means:

* Unused quotes do not carry over.
* A new day starts from zero accepted quotes.

## If you hit the limit often

* Check the exceeded attempts number each day.
* If exceeded attempts appear regularly, [review your current plan](https://app.remapdb.com/settings/billing).
* If needed, click your name at the bottom of the main navigation, then click [**Billing**](https://app.remapdb.com/settings/billing), and move to a plan with higher quote capacity.

<Info>
  Daily quote capacity depends on your [subscription plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Related actions

* [Quoting](/widget/quoting)
* [Email and inputs](/widget/quoting/email-and-inputs)
* [Billing and plans](/billing)
* [Feature availability by plan](/feature-availability-by-plan)


# Set dealer network
Source: https://docs.remapdb.com/widget/quoting/set-dealer-network

Add, edit, and manage dealers so quote requests can be routed to the dealer selected by the visitor.

Use this page when you want visitors to choose a dealer in the quote form, and you want the selected dealer to receive the quote request.

Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation.

## Step 1: Turn on dealers

In the **Dealers** section:

1. Turn on the **Enable dealers** switch.
2. Click the **Manage dealers...** row.

The **Manage dealers** side panel opens.

## Step 2: Understand the Manage dealers panel

The **Manage dealers** panel shows your saved dealers as cards.

Each dealer card can show:

* Dealer name.
* Dealer email.
* Dealer phone, if saved.
* Dealer address, if saved.
* Map status: **Shown on dealers map** when latitude and longitude are saved, or **No map location** when no valid coordinates are saved.

Each card has two actions:

* **Edit dealer**: opens the same dealer details panel used by **Add dealer**, with the dealer fields prefilled.
* **Delete dealer**: opens a confirmation dialog before the dealer is removed.

The list panel also has:

* **Add dealer**: opens a dealer details panel for a new dealer.
* **Close**: closes the side panel.

If no dealers are saved yet, the panel shows **No dealers added** and the **Add dealer** button.

## Step 3: Add a dealer

In the **Manage dealers** panel:

<Steps>
  <Step title="Click Add dealer">
    The **Add dealer** panel replaces the dealer card list in the same side panel.
  </Step>

  <Step title="Enter the required details">
    Fill in **Name** and **Email**. These are required.
  </Step>

  <Step title="Enter optional contact and address details">
    Add **Phone**, **Address**, **Address 2**, **City**, **State / Region**, **ZIP / Postal code**, and **Country** when you want visitors to see more dealer context in the quote form or dealer map.
  </Step>

  <Step title="Set the map location, if needed">
    Use **Find on map** or enter **Latitude** and **Longitude** manually.
  </Step>

  <Step title="Click Save">
    Remapdb saves the dealer, returns to the **Manage dealers** card list, and refreshes the quote preview.
  </Step>
</Steps>

Use clear dealer names your visitors understand, such as branch name, city, region, or partner name.

## Dealer details fields

| Field             | Required | What it controls                                                                                     |
| ----------------- | -------- | ---------------------------------------------------------------------------------------------------- |
| Name              | Yes      | The dealer name shown in the dealer list and quote form. Dealer names must be unique for the widget. |
| Email             | Yes      | The inbox that receives the dealer copy of a quote when that dealer is selected.                     |
| Phone             | No       | Shown as dealer contact information where dealer details are displayed.                              |
| Address           | No       | Main street address. Used for display and map search.                                                |
| Address 2         | No       | Additional address line.                                                                             |
| City              | No       | City used for display and map search.                                                                |
| State / Region    | No       | Region or state used for display and map search.                                                     |
| ZIP / Postal code | No       | Postal code used for display and map search.                                                         |
| Country           | No       | Searchable country dropdown used for display and map grouping.                                       |
| Latitude          | No       | Map coordinate. Must be saved together with longitude to show the dealer on a map.                   |
| Longitude         | No       | Map coordinate. Must be saved together with latitude to show the dealer on a map.                    |

## Map location behavior

Dealer routing works without a map location. Name and email are enough to route quote emails.

Add a map location when you also want the dealer to appear on dealer maps.

You can set the map location in two ways:

* Click **Find on map**. Remapdb tries to find the location from the address fields, then opens a map picker.
* Enter **Latitude** and **Longitude** manually.

In the map picker:

* Click the map or drag the marker to adjust the exact dealer position.
* Click **Use this location** to copy the selected coordinates into the dealer form.
* Click **Cancel** to leave the existing coordinates unchanged.

After valid latitude and longitude are saved, the dealer card shows **Shown on dealers map**.
If one coordinate is missing, invalid, or outside the accepted range, the dealer cannot be saved with that map location.

Accepted coordinate ranges are:

* Latitude: `-90` to `90`
* Longitude: `-180` to `180`

## Standalone dealers map code

When dealer access is included in your plan and **Enable dealers** is on, the **Dealers** section can also show a **Dealers map** code block.

Copy this code only if you want to place a standalone dealer locator map on your website.

Important behavior:

* The standalone dealers map uses the same saved dealer records from **Manage dealers**.
* The map shows only dealers with valid saved latitude and longitude.
* A dealer without coordinates can still be selected in the quote form and can still receive quote emails.
* If no saved dealer has a valid map location, the standalone dealers map has no dealer locations to show.

## Step 4: Edit a dealer

In the **Manage dealers** panel:

<Steps>
  <Step title="Click the edit icon on the dealer card">
    The **Edit dealer** panel replaces the dealer card list in the same side panel.
  </Step>

  <Step title="Update the dealer details">
    The form is the same as **Add dealer**, but the saved values are already filled in.
  </Step>

  <Step title="Click Save">
    Remapdb updates the dealer, returns to the **Manage dealers** card list, and refreshes the quote preview.
  </Step>
</Steps>

Click **Cancel** or the close icon in the **Add dealer** or **Edit dealer** panel to return to the **Manage dealers** list without saving changes.

## Step 5: Delete a dealer

In the **Manage dealers** panel:

<Steps>
  <Step title="Click the delete icon on the dealer card">
    A confirmation dialog opens.
  </Step>

  <Step title="Confirm Delete dealer">
    Remapdb removes the dealer and refreshes the **Manage dealers** list.
  </Step>
</Steps>

Deleting a dealer removes it from future quote selection. It does not change quote emails that were already sent.

## Step 6: Verify in the live widget

1. Open a live page where your widget is installed.
2. Open the quote form.
3. Confirm the dealer selector is visible.
4. Select a dealer.
5. Confirm the selected dealer details appear if contact or address details were saved.
6. If at least one dealer has saved map coordinates, click **View dealers map** and confirm mapped dealers appear.
7. Submit a test quote with a selected dealer.

## How quote emails are sent to dealers

When **Enable dealers** is on and a visitor selects a dealer in the quote form:

* Your main quote inbox still receives the quote.
* The selected dealer also receives the quote.
* The selected dealer name and address are included in the quote details when available.

If no dealer is selected, or if **Enable dealers** is off:

* Only your main quote inbox receives the quote.

## If the dealer selector is not visible

1. Confirm **Enable dealers** is turned on in **Quoting**.
2. Confirm at least one dealer card is saved in **Manage dealers**.
3. Confirm your plan includes dealer selection feature access.
4. Reload the live widget page and test again.

<Info>
  Dealer selection in the quote form depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## If a dealer does not appear on the map

1. Open **Manage dealers...**.
2. Check the dealer card status.
3. If it says **No map location**, click the edit icon.
4. Use **Find on map** or enter valid **Latitude** and **Longitude** values manually.
5. Click **Save**.
6. Confirm the dealer card now says **Shown on dealers map**.

Dealers without coordinates can still receive selected dealer quote emails. They only stay off the map.

## Related actions

* [Email and inputs](/widget/quoting/email-and-inputs)
* [Set services and pricing](/widget/quoting/set-services-and-pricing)
* [Set up quoting automation](/widget/quoting/set-up-quoting-automation)
* [Quoting issues](/support/quoting-issues)


# Set services and pricing
Source: https://docs.remapdb.com/widget/quoting/set-services-and-pricing

Configure services, options, and estimated prices so visitors see the right choices in the quote form.

This page controls what people can select in the quote form and whether they see an estimated total price.

Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation.
In **Quoting**, open the **Services and pricing** section.

## What you configure on this page

* Which services are available in the quote form.
* Which options (per vehicle category) are available in the quote form.
* Whether visitors see estimated prices.
* Which currency is used for price display.

## Step 1: Decide if visitors should see prices

In the **Services and pricing** section:

1. Turn on the **Enable pricing** switch if you want visitors to see estimated totals.
2. Leave the **Enable pricing** switch off if you want to collect requests without showing prices.

Why this matters:

* When pricing is on, the widget shows estimated totals in the quote flow.
* When pricing is off, visitors can still submit requests, but no price estimate is shown.

## Step 2: Choose the currency (when pricing is on)

1. Turn on the **Enable pricing** switch.
2. Open the **Currency** dropdown.
3. Select your currency.

## Step 3: Configure services and options

Important: in this area, there is a control called **Manage services and pricing...**.\
When you click this row, a side panel opens. In that side panel, you can manage services, options, and prices for each vehicle category.

<Steps>
  <Step title="Click the Manage services and pricing... row." />

  <Step title="Open each vehicle type tab you use." />

  <Step title="Turn on only the services you offer." />

  <Step title="Turn on only the options you offer." />

  <Step title="Enter prices for the active items." />

  <Step title="Click the Save services and pricing button." />
</Steps>

### What on/off changes for your visitors

After you click the **Save services and pricing** button and reload the live page:

* If a service is **on**, visitors can select it in the quote form.
* If a service is **off**, visitors cannot see or select it in the quote form.
* If an option is **on**, visitors can add it to their quote.
* If an option is **off**, visitors cannot see or add it.

This works per vehicle category tab in the side panel.\
For example, turning on a service in one category does not automatically turn it on in all other categories.

## Important behavior about prices

To edit price values directly in the panel:

1. Turn on the **Enable pricing** switch first.
2. If pricing is off, price inputs stay read-only.

If a price input is left empty, Remapdb treats that item as **0.00**.
This is reflected in the quoting form when that item is selected.

This is useful when you want two different setups:

* You may keep services active for requests.
* You may keep pricing hidden if you do not want public estimates.

## How estimated price is calculated

When pricing is enabled, Remapdb adds:

* Selected service price.
* Plus selected option prices.

Example:

* Service: Stage 1 = 450.
* Option: EGR off = 50.
* Option: DPF off = 50.
* Estimated total shown to visitor = 550.

## Why it is called estimated price

The price shown in the quote form is an initial estimate, not a final invoice amount.

This helps visitors understand a likely cost range before they submit a request, but the final offered price can be different after your team reviews the vehicle.

Common reasons the final offered price can change:

* Vehicle condition found during inspection.
* ECU/TCU compatibility details confirmed during review.
* Extra work needed for the specific vehicle setup.
* Additional customer requirements discussed after the request.

Use this expectation in your communication:

* The quote form shows an estimated price.
* Final price is confirmed after review by your tuning team.

## Verify in the live widget

<Steps>
  <Step title="Open a live page where your widget is installed." />

  <Step title="Open the quote form." />

  <Step title="Check that only your intended services and options are visible." />

  <Step title="Select service and options and confirm the estimate updates correctly." />

  <Step title="Submit one test quote and confirm selected items are included in the received email." />
</Steps>

<Info>
  Pricing visibility and some quoting controls depend on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Related actions

* [Email and inputs](/widget/quoting/email-and-inputs)
* [Set dealer network](/widget/quoting/set-dealer-network)
* [Set up quoting automation](/widget/quoting/set-up-quoting-automation)
* [Feature availability by plan](/feature-availability-by-plan)


# Set up quoting automation
Source: https://docs.remapdb.com/widget/quoting/set-up-quoting-automation

Configure automatic customer confirmation emails, sender behavior, and template variables for your quote flow.

Use this page to control the automatic email sent to visitors after they submit a quote, and how sender details are shown.

Click the [**Quoting**](https://app.remapdb.com/widget/quoting) item in the main navigation, then open the **Automation** section.

## Step 1: Turn on auto-reply

In **Automation**:

1. Turn on the **Send auto-reply email** switch.

## Step 2: Set the email subject

1. In **Email subject**, enter your subject line.
2. Click the **Save** button.

## Step 3: Set the email template

1. In **Email template**, write your message.
2. Add variables where you want dynamic values.
3. Click the **Save** button.

Supported variables:

* `{{name}}` — visitor name.
* `{{vehicle_brand}}` — selected brand.
* `{{vehicle_model}}` — selected model.
* `{{vehicle_generation}}` — selected generation.
* `{{vehicle_engine}}` — selected engine.
* `{{contact_email}}` — your quote recipient email from **Email to receive quotes**.

Pricing variables (only when pricing is enabled and available on your plan):

* `{{price_breakdown}}`
* `{{total_price}}`

## Step 4: Set sender name

1. In **From name**, enter the name you want people to see.
2. Click the **Save** button.

The **Send from** value is shown as read-only in the standard setup.

## Step 5: Test end-to-end

<Steps>
  <Step title="Open a live page where your widget is installed." />

  <Step title="Submit a test quote with a real inbox you can access." />

  <Step title="Check team inbox delivery." />

  <Step title="Check dealer inbox delivery (if dealer routing is enabled)." />

  <Step title="Check customer auto-reply delivery." />

  <Step title="Confirm template variables are replaced correctly." />
</Steps>

## What happens after a quote is submitted

A successful quote can trigger up to three emails:

* Quote email to your team mailbox (set in **Email to receive quotes**).
* Quote email to the selected dealer (if dealer routing is enabled and a dealer is selected).
* Auto-reply email to the visitor (if **Send auto-reply email** is turned on).

If [File upload](/widget/quoting/file-upload) is enabled and the visitor attaches files, file links are included in quote emails.

## Who receives what, and where replies go

### Team quote email

* Sent to your **Email to receive quotes** address.
* If your team replies to this email, the reply goes to the visitor email from the form.

### Dealer quote email

* Sent to the selected dealer email saved in **Manage dealers** (when dealer routing is active).
* If the dealer replies, the reply goes to the visitor email from the form.

### Customer auto-reply email

* Sent to the visitor who submitted the quote.
* If the visitor replies, the reply goes to your **Email to receive quotes** address.

This keeps quote conversations in your sales/support inbox.

## Use your own sender domain

If you want to send from your own domain:

1. Click the **Help me use my domain** button in **Automation**.
2. Follow the Remapdb support setup process.
3. Complete domain verification and sender setup with support.

<Info>
  Custom sender domain setup depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Reset buttons

If needed, you can restore defaults:

* Click the reset icon next to **Email subject** to restore the default subject.
* Click the reset icon next to **Email template** to restore the default template.

## How this works with pricing

* If pricing is enabled, pricing details can be included in customer auto-replies.
* If pricing is disabled, quote automation still works, but pricing details are not included.

## Example template

```text theme={null}
Hi {{name}},

Thank you for your quote request for:
{{vehicle_brand}} {{vehicle_model}} {{vehicle_generation}} - {{vehicle_engine}}.

Our team will review your request and contact you shortly.
If you have questions, contact us at {{contact_email}}.
```

## Good practices

* Keep **From name** stable so customers recognize your messages.
* Use the same sender name across all quote emails.
* After changes, submit a real test quote and check inbox and spam folders.

<Info>
  Auto-reply availability and pricing variables depend on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

## Related actions

* [Email and inputs](/widget/quoting/email-and-inputs)
* [Set services and pricing](/widget/quoting/set-services-and-pricing)
* [Custom email domain setup information](/widget/quoting/custom-email-domain-setup-information)
* [Support request process](/support/support-request-process)


# Settings
Source: https://docs.remapdb.com/widget/settings

Configure language, vehicle visibility, performance units, URL behavior, and SEO output in your live widget.

Use this section to configure how your live Remapdb widget looks, behaves, and is discovered.

## Use this section when

* You want to adjust language and vehicle data visibility.
* You need to control units and presentation behavior in the live widget.
* You want better URL sharing and SEO output for search and social links.

<Info>
  Some controls are plan-gated. If a control is disabled, check your current plan and [feature access](/feature-availability-by-plan) first.
</Info>

## Success looks like

* The widget shows the right language and visible vehicle data.
* Visitors see the right unit and content behavior.
* Shared links and SEO output match selected vehicle content correctly.

## Pages in this section

<div>
  <Columns>
    <Card title="Language and localization" href="/widget/settings/language-and-localization">
      Set language behavior for visitors and multilingual usage.
    </Card>

    <Card title="Vehicle data visibility" href="/widget/settings/vehicle-data-visibility">
      Control which vehicle categories and data blocks appear.
    </Card>

    <Card title="Performance units" href="/widget/settings/torque-units">
      Choose hp/Nm, hp/ft-lb, or kW/Nm as the default performance display.
    </Card>

    <Card title="SEO settings guide" href="/widget/settings/seo-settings-guide">
      Configure metadata, summary content, and URL behavior for search and sharing.
    </Card>
  </Columns>
</div>


# Language and localization
Source: https://docs.remapdb.com/widget/settings/language-and-localization

Choose the widget language your visitors see and control automatic language detection.

Use this page to control which language your widget opens in.

## Where to change this

1. Click the [**Settings**](https://app.remapdb.com/widget/settings) item in the Widget section of the main navigation.
2. Go to the **Language** section.

## What each setting means

### Default language

This is the main language your widget uses.

Use this when you want one consistent language for most visitors.

### Detect automatically

When this is enabled, Remapdb tries to show the widget in each visitor's browser language.

Simple example:

* Your default language is English.
* A visitor's browser language is German.
* The widget opens in German if German is supported in your widget setup.

If Remapdb cannot use the visitor language, it falls back to your **Default language**.

<Info>
  If your [plan](https://app.remapdb.com/settings/billing) does not include automatic detection, the **Detect automatically** toggle is unavailable.
</Info>

## Supported widget languages

The embedded widget is available in 21 languages:

* Bulgarian
* Simplified Chinese
* Croatian
* Danish
* Dutch
* English
* Estonian
* Finnish
* French
* German
* Hungarian
* Italian
* Latvian
* Lithuanian
* Norwegian Bokmål
* Norwegian Nynorsk
* Portuguese
* Russian
* Spanish
* Swedish
* Turkish

Hungarian appears as **Magyar** in the widget language selector.

<Note>
  Vehicle names and technical vehicle data use English when the vehicle database does not have content in the selected widget language.
</Note>

## How Remapdb chooses the language

1. If **Detect automatically** is enabled, Remapdb tries the visitor browser language.
2. If browser language is within the supported languages, Remapdb uses it.
3. If not, Remapdb uses your **Default language**.

## Step-by-step setup

1. In **Default language**, choose the language you want as your baseline.
2. In **Detect automatically**, enable or disable the toggle based on your preference.
3. Wait for save confirmation.
4. Open the live page and test once.

## Quick testing checklist

* Open the live widget page and confirm text appears in your expected default language.
* If **Detect automatically** is enabled, test with a browser that uses a different language.

## Common mistakes

1. Testing only in preview instead of a live embedded page.
2. You test with a browser language that is not supported.


# SEO settings guide
Source: https://docs.remapdb.com/widget/settings/seo-settings-guide

Set up page titles, social previews, visible summary text, and shareable links so more people can find your website and contact your tuning business.

This guide explains every SEO setting in Remapdb in plain language.

You will learn what each setting does, why it matters for visibility and traffic, and how to set it correctly so more people can discover your website, open your widget pages, and contact you for tuning services.

## Who this guide is for

Use this guide if you manage a Remapdb widget and you want better search visibility, better shared links, and clearer page content for visitors.

## Before you configure SEO

1. Open page [Code installation](/widget/installation/code-installation).
2. Complete **Step 1: Save website in Remapdb** so your website is in **Allowed websites**.
3. Confirm your widget is already live on your real website page.

<Warning>
  If your website is missing in **Allowed websites**, the widget may not load, and SEO updates cannot run on your live page.
</Warning>

## Where to configure these settings

1. Click the [**Settings**](https://app.remapdb.com/widget/settings) item in the Widget section of the main navigation.
2. Go to section **SEO**.

## How these settings support visibility, traffic, and leads

* Better titles and descriptions make your pages clearer in search results, which can improve click-through rate.
* Better social previews make shared links look more trustworthy, which can increase link clicks.
* Visible vehicle summary text helps visitors understand gains faster, which can increase quote or contact intent.
* Cleaner shareable links make it easier for people to revisit and share the same vehicle page.

## If a setting is disabled

Some SEO controls depend on your plan.

* **Page title mode**, **Page title**, **Page description**, and **Title separator** need **Automatic metadata** access.
* **Summary container ID**, and **Summary template** need **Automatic vehicle summary** access.

If a control is disabled in the interface, open page [Feature availability by plan](/feature-availability-by-plan) and confirm your current plan access.

## What each SEO setting does

### What users can see vs what only search engines/bots read

This is important: not all SEO settings are visible as page text.

Some settings are mostly for search engines, social crawlers, and bots.\
Some settings are visible to normal visitors on your website.

Quick rule:

* If it is meta tags or structured data, visitors usually do not see it in page text.
* If it is summary content, visitors do see it on the page.
* If it is URL behavior, visitors see it in the address bar and shared links.

What meta tags are and where they are:

* Meta tags are small information labels in the page `<head>` section (the top metadata area of the HTML document).
* They are not shown as normal visible text in the page body.
* Search engines and social crawlers read them to understand what your page is about.
* Normal users usually see their effect indirectly, for example in Google snippets or social link previews.

Simple examples in page code:

```html theme={null}
<head>
  <title>Stage 2 tuning for Audi A3 2.0 TDI 150HP</title>
  <meta name="description" content="From 150 HP to Stage 2 190 HP...">
  <meta property="og:title" content="Stage 2 tuning for Audi A3 2.0 TDI 150HP">
  <meta property="og:description" content="From 150 HP to Stage 2 190 HP...">
</head>
```

In this example:

* Visitors see the `<title>` in the browser tab.
* Visitors usually do not see `<meta ...>` lines directly on the page.
* Bots use those meta lines for search and social preview understanding.

Below, each category explains exactly what is visible to visitors and what is mostly for bots.

### Search visibility settings

Visibility in this category:

* **Automatic metadata**, **Page title mode**, and **Title separator** are control settings. Users do not see them as page text.
* **Page title** appears in the browser tab and can appear in search results.
* **Page description** is mainly a meta tag in the page `<head>`, used mostly by search engines.

Simple code example from this category:

```html theme={null}
<head>
  <title>Stage 2 tuning for Audi A3 2.0 TDI 150HP | Remapdb</title>
  <meta name="description" content="From 150 HP to Stage 2 190 HP...">
</head>
```

#### Automatic metadata

Turn this on when you want Remapdb to update your page title and page description based on the selected vehicle.

In simple terms, this setting makes each vehicle page feel like a specific landing page instead of a generic widget page. When a visitor switches from one vehicle to another, Remapdb updates the SEO text to match that exact selection. This helps search engines and users understand what is on the page without guessing.

Why this helps:

* Search engines can understand each vehicle page better.
* Search result snippets become more specific.
* Better snippets usually bring more relevant clicks from people already searching for tuning.

#### Page title mode

This setting controls how Remapdb combines SEO title text with your existing page title.

Options:

* **Append to existing title**: keeps your current page title first, then adds vehicle SEO text.
* **Prepend to existing title**: puts vehicle SEO text first, then adds your current page title.
* **Replace existing title**: uses only the Remapdb SEO title.

Why this helps:

* You can balance brand visibility and vehicle-specific keywords.
* You can decide whether brand-first or vehicle-first wording works better for your audience.

#### Page title

This is the title template Remapdb uses for search engines and browser tabs.

What is a page title: it is the main headline search engines usually show for your page, and it is also the text people see in their browser tab. This is often the first text a potential customer sees before they click your page.

Example page title template:

`Stage ${best_stage} tuning for ${vehicleName}`

Example output for one vehicle:

`Stage 2 tuning for Audi A3 2.0 TDI 150HP`

Why this helps:

* A clear vehicle title can improve click-through rate from search results.
* Better click-through means more qualified visitors landing on your pages.

#### Page description

This is the description template shown under the title in many search results.

What is a page description: it is the short summary under your page title in search results. It gives visitors context before they click, so they can quickly decide if your service is relevant for their vehicle.

Example page description template:

`Best available result for ${vehicleName}: Stage ${best_stage} with ${power_best} ${power_unit} and ${torque_best} ${torque_unit} (OEM ${power_oem} ${power_unit} / ${torque_oem} ${torque_unit}).`

Example output for one vehicle:

`Best available result for Audi A3 2.0 TDI 150HP: Stage 2 with 190 HP and 410 Nm (OEM 150 HP / 320 Nm).`

Important clarification: `${best_stage}`, `${power_best}`, and `${torque_best}` always represent one single stage only, the highest available stage for that vehicle. They do not list all stages.

Why this helps:

* A clear description can attract people who are ready to compare tuning options.
* Better description quality can increase visits from relevant users.

#### Title separator

This is the short separator text between your existing title and generated SEO title.

This is mostly a readability setting. It does not add content value by itself, but it keeps your title clean when your base website title and dynamic Remapdb title are combined.

Example separators: `|` or `-`.

Why this helps:

* Keeps page titles readable.
* Makes brand and vehicle text easy to scan.

### Social sharing and search understanding

Visibility in this category:

* **Social sharing metadata** is not visible as body text. It is mostly for social crawlers and bots.
* **Structured data** is not visible as body text. It is a hidden JSON-LD script for bots.
* Visitors mostly see the result indirectly when links render richer previews.

Simple code examples from this category:

```html theme={null}
<head>
  <meta property="og:title" content="Stage 2 tuning for Audi A3 2.0 TDI 150HP">
  <meta property="og:description" content="From 150 HP to Stage 2 190 HP...">
  <meta property="og:image" content="https://.../audi-a3.jpg">
  <script type="application/ld+json">{ ... }</script>
</head>
```

#### Social sharing metadata

Turn this on to improve how links look when shared in places like Facebook, LinkedIn, and messaging apps.

When this is on, Remapdb sends structured share-preview data for your current vehicle page, such as:

* a social title (`og:title`)
* a social description (`og:description`)
* a preview image (`og:image`)
* the page link (`og:url`)

This is why shared links can show a proper preview card instead of a plain URL. Better preview cards are easier to trust and usually attract more clicks from people who are already interested in tuning.

Why this helps:

* Shared links look more complete and professional.
* Better previews usually get more clicks when your pages are shared.

#### Structured data

Turn this on to add hidden machine-readable vehicle data for search engines.

What structured data is: a hidden block of information in a standard format that search engines read to understand page meaning. Visitors do not see it in the page body, but search engines use it as extra context.

Remapdb outputs this in JSON-LD format. Simple example:

```json theme={null}
{
  "@context": "https://schema.org",
  "@type": "Thing",
  "name": "Audi A3 2.0 TDI 150HP",
  "description": "OEM 150 HP / 320 Nm to Stage 2 190 HP / 410 Nm"
}
```

This helps search engines understand that your page is about a specific vehicle and a specific tuning result, not only generic content.

Why this helps:

* Search engines understand your page context more clearly.
* Clearer understanding can improve how your content is categorized and surfaced over time.

<Info>
  Structured data improves understanding, not instant rankings. It is a long-term quality signal.
</Info>

### On-page SEO content

Visibility in this category:

* **Automatic vehicle summary** creates visible text in the page body.
* **Summary container ID** is a technical placement setting (users do not see the ID itself).
* **Summary template** is visible output text and can be read by both users and search engines.

Simple page-body example from this category:

```html theme={null}
<div id="rdb-ss">
  Audi A3 2.0 TDI 150HP: OEM 150 HP / 320 Nm to Stage 2 190 HP / 410 Nm.
</div>
```

#### Automatic vehicle summary

Turn this on to show visible, readable vehicle summary text on your page.

This summary appears in your page content (outside the widget) in the location you control with **Summary container ID**. It updates when the selected vehicle changes, so visitors and search engines can both read vehicle-specific text directly on your page.

Why this helps:

* Search engines rely on visible page text, not only hidden tags.
* Visitors immediately see useful tuning details without extra clicks.

#### Summary container ID

This is the target page element ID where summary text is injected.

Example page element:

```html theme={null}
<div id="rdb-ss"></div>
```

Why this helps:

* It lets you choose exactly where summary text appears in your page layout.

How to control this:

* Use **Automatic vehicle summary** to turn summary text on or off.
* Use **Summary container ID** to define where the text appears.
* Use **Summary template** to control the wording users see.

#### Summary template

This controls the actual sentence shown in the summary container.

This template uses dynamic values, so one template can work for many vehicles. As visitors switch vehicles, Remapdb replaces the variable placeholders with real values and updates the sentence automatically.

Why this helps:

* You can keep wording aligned with your service style.
* You can highlight OEM vs tuned results in a simple, trustworthy sentence.

### Link structure settings

Visibility in this category:

* **Clean vehicle URLs** and **Query parameter** are visible in the browser address bar.
* They are visible to users, and also parsed by bots and analytics systems.
* These settings control how shared links look and how vehicle state is restored when someone opens the link.

Simple URL examples from this category:

* Query style: `https://yourwebsite.com/?catalog=cars/audi/a3/...`
* Clean style: `https://yourwebsite.com/catalog/cars/audi/a3/...`

#### Clean vehicle URLs

This chooses URL style for selected vehicles.

* Off: URL uses query style (example `?catalog=...`).
* On: URL uses path style (example `/catalog/...`).

Why this helps:

* Path-style links are often easier to read and share.
* Clear links improve trust when users copy and send them.

Better example comparison:

* Query style: `https://yourwebsite.com/?catalog=cars/audi/a3/8p/20-tdi-150hp-320nm`
* Clean style: `https://yourwebsite.com/catalog/cars/audi/a3/8p/20-tdi-150hp-320nm`

The second version is easier for people to read, easier to share in messages, and easier to understand at a glance.

<Warning>
  If you turn on **Clean vehicle URLs**, your website must route those path URLs to the page that contains your Remapdb widget. If routing is missing, users can get a 404 page.
</Warning>

Simple server examples (replace `/tuning` with the page URL where your widget is embedded):

If your **Query parameter** is the default `catalog`, clean URLs like:

`/catalog/cars/audi/a3/...`

should be routed to:

`/tuning?catalog=cars/audi/a3/...`

**Apache (`.htaccess`)**

```apache theme={null}
RewriteEngine On

# Keep existing files/folders working normally
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

# /catalog/... -> /tuning?catalog=...
RewriteRule ^catalog/(.*)$ /tuning?catalog=$1 [L,QSA]
```

**Nginx**

```nginx theme={null}
# /catalog/... -> /tuning?catalog=...
location ~ ^/catalog/(.+)$ {
    rewrite ^/catalog/(.+)$ /tuning?catalog=$1&$args last;
}
```

Notes:

* Keep your normal website URLs unchanged.
* Replace `catalog` in the rules if you changed the **Query parameter** (for example `vehicle` or `rdb`).
* Keep `/catalog/` (or your custom key) as the path prefix when **Clean vehicle URLs** is enabled.
* After adding rules, open one clean URL and confirm it loads the page with your Remapdb widget (not a 404 page).

#### Query parameter

This is the key used in your vehicle URL.

Default example key: `catalog`.

Why this helps:

* You can keep URL structure clean and consistent with your website.
* You can avoid conflicts with existing website parameters.

What a query parameter is: in a URL, it is the key name before `=`.\
Example URL: `https://yourwebsite.com/?catalog=cars/audi/a3/...`\
In this example, `catalog` is the query parameter key.

How it works in Remapdb:

* Remapdb writes the selected vehicle path into this key.
* Remapdb reads this key when someone opens the link, so the same vehicle can be preselected.

Why changing it can be important:

* Some websites already use specific URL keys for other features.
* If your site or server already uses `catalog` for another purpose, you can change it to avoid collisions.
* This helps prevent front-end and server-side conflicts, including broken routing, unexpected behavior, or URL parsing errors.

Practical examples:

* Default: `https://yourwebsite.com/?catalog=cars/audi/a3/...`
* Custom key: `https://yourwebsite.com/?vehicle=cars/audi/a3/...`
* Another custom key: `https://yourwebsite.com/?rdb=cars/audi/a3/...`

## Template values you can use

You can use these values in **Page title**, **Page description**, and **Summary template**.

What these values do: they act as placeholders in your text templates. Remapdb replaces each placeholder with real vehicle data. This is what makes one template work dynamically for many vehicle pages.

Why this helps dynamic content:

* You write template text once.
* Remapdb automatically updates it per selected vehicle.
* Your page stays specific and relevant without manual rewriting.

| Value            | Meaning                                                 |
| ---------------- | ------------------------------------------------------- |
| `${vehicleName}` | Full vehicle name                                       |
| `${power_oem}`   | Original power in the selected unit                     |
| `${torque_oem}`  | Original torque in the selected unit                    |
| `${best_stage}`  | Single highest available tuning stage number            |
| `${power_best}`  | Power from that single best stage in the selected unit  |
| `${torque_best}` | Torque from that single best stage in the selected unit |
| `${power_unit}`  | Selected power label: hp or kW                          |
| `${torque_unit}` | Selected torque label: Nm or ft-lb                      |

The values follow the default selected under [Performance units](/widget/settings/torque-units). For example, the **kW** mode produces kW power values and Nm torque values in visible summaries, metadata, social previews, and structured data.

<Note>
  The older `${hp_oem}`, `${nm_oem}`, `${hp_best}`, and `${nm_best}` placeholders remain supported for existing templates. Use the unit-aware placeholders above for new or updated templates.
</Note>

Example template:

`Remap for ${vehicleName}: best result is Stage ${best_stage} (${power_best} ${power_unit} / ${torque_best} ${torque_unit}), compared with OEM ${power_oem} ${power_unit} / ${torque_oem} ${torque_unit}.`

Example output for one vehicle:

`Remap for Audi A3 2.0 TDI 150HP: best result is Stage 2 (190 HP / 410 Nm), compared with OEM 150 HP / 320 Nm.`

## Field limits and save rules

| Setting              | Rule                              |
| -------------------- | --------------------------------- |
| Page title           | Required, up to 70 characters     |
| Page description     | Required, up to 160 characters    |
| Title separator      | Required, up to 5 characters      |
| Summary container ID | Required, up to 20 characters     |
| Summary template     | Required, up to 300 characters    |
| Query parameter      | Letters only, up to 30 characters |

Save behavior in this section:

* Toggles and dropdowns save right after you change them.
* Text fields save when you click the **Save** button in that field block.

## Recommended setup order

1. Turn on **Automatic metadata**.
2. Set **Page title mode**.
3. Write **Page title**, **Page description**, and **Title separator**.
4. Turn on **Social sharing metadata**.
5. Turn on **Structured data**.
6. Turn on **Automatic vehicle summary**.
7. Set **Summary container ID** and **Summary template**.
8. Decide if you want **Clean vehicle URLs** on or off.
9. Set **Query parameter**.

## How to verify everything on your live website

1. Open your real widget page on your website.
2. Select a vehicle in the widget.
3. Check browser tab title and page description.
4. Check that summary text appears in your target summary container.
5. Copy the page link and open it in a new tab.
6. Confirm the same vehicle state is loaded.
7. Share the link in your preferred social channel and check preview quality.

## Common issues and quick fixes

### Page title or description did not change

* Confirm **Automatic metadata** is turned on.
* Confirm you clicked the **Save** button for title and description fields.
* Refresh the page and test again on the live website.

### Summary text is not visible

* Confirm **Automatic vehicle summary** is turned on.
* Confirm your page contains an element with the exact **Summary container ID**.
* Confirm you clicked the **Save** button after editing the summary fields.

### Shared link preview still shows old data

* Re-share the link after selecting a vehicle again.
* Some platforms cache previews for a while, so changes can appear with delay.

### URL style does not work when clean URLs are on

* Confirm your website routes that path to the page where widget code is installed.
* If not, turn off **Clean vehicle URLs** until routing is ready.

### Query parameter does not save

* Use letters only.
* Keep it short and do not use spaces, numbers, or symbols.

## Related actions

* [Code installation](/widget/installation/code-installation)
* [WordPress plugin installation](/widget/installation/wordpress-plugin-installation)
* [Installation checklist](/widget/installation/installation-checklist)
* [Installation troubleshooting](/widget/installation/installation-troubleshooting)


# Performance units
Source: https://docs.remapdb.com/widget/settings/torque-units

Choose the default power and torque units visitors see first in your widget.

Use this setting to control how power and torque values are shown when the widget first loads.

<Info>
  The selected mode also applies to the dyno chart, visible vehicle summary, metadata, social sharing output, and structured data.
</Info>

## Where to change this

1. Click the [**Settings**](https://app.remapdb.com/widget/settings) item in the Widget section of the main navigation.
2. Open the **Performance units** section.

## Available options

| Setting                 | Power | Torque |
| ----------------------- | ----- | ------ |
| **Nm** (Newton-meters)  | hp    | Nm     |
| **ft-lb** (foot-pounds) | hp    | ft-lb  |
| **kW** (kilowatts)      | kW    | Nm     |

## What this changes in the widget

When you change this setting:

1. Power and torque values open in the selected default combination.
2. Performance labels and chart values follow the same units.
3. SEO output uses the selected units, including visible summaries and structured data.
4. Visitors can still switch units inside the widget if they prefer another format.

In short: this controls the **starting unit**, not a permanent lock.

## Step-by-step setup

1. In **Performance units**, choose **Nm**, **ft-lb**, or **kW**.
2. Save your changes.
3. Open your widget preview and check one vehicle.
4. Open a live page and confirm the same result.

## Quick testing checklist

* Widget opens with the performance units you selected.
* Power and torque labels match the selected mode.
* Power values switch between hp and kW when expected.
* SEO summary and metadata use the same unit labels and converted values.
* Manual unit switch in the widget still works.

## Good practice

* Choose the unit most of your visitors already expect to see.
* Keep your widget, SEO templates, sales text, and screenshots in the same units.


# Vehicle data visibility
Source: https://docs.remapdb.com/widget/settings/vehicle-data-visibility

Choose which vehicle categories and detail blocks visitors can see in your widget.

Use this page to control what visitors can browse and what they see in the vehicle result view.

## Where to change this

1. Click the [**Settings**](https://app.remapdb.com/widget/settings) item in the Widget section of the main navigation.
2. Open the **Details** section.

## What these settings do in the widget

### Visible vehicle types

This setting controls which top-level vehicle categories people can choose in the widget.

Available categories:

* Car & LCV
* Truck
* Agriculture
* Motorcycle
* Machinery
* Marine

If a category is enabled, visitors can select it.\
If a category is disabled, visitors will not see it in the widget.

### Vehicle details

These settings control the blocks shown in the vehicle details area:

* **Show dyno chart**: shows or hides the performance chart.
* **Show vehicle logo**: shows or hides the brand logo.
* **Show vehicle image**: shows or hides the vehicle image.

When you disable any of these, that block is removed from the widget view.

<Info>
  If your [plan](https://app.remapdb.com/settings/billing) does not include some visual options, related toggles may be unavailable.
</Info>

## Step-by-step setup

1. In **Visible vehicle types**, enable only categories you actually service.
2. In **Vehicle details**, choose what should be visible to visitors.
3. Save your changes.
4. Test the widget in preview.
5. Test again on a live page.

## Quick testing checklist

* Every enabled category is visible and selectable in the widget.
* Disabled categories are not shown.
* Dyno chart visibility matches your setting.
* Vehicle logo visibility matches your setting.
* Vehicle image visibility matches your setting.

## Common mistakes

1. Enabling categories you do not service.
2. Disabling a category, then expecting it to still appear in the widget.
3. Testing only in preview and skipping a live page test.


# Tracking
Source: https://docs.remapdb.com/widget/tracking

Understand when to use Remapdb tracking events and where they fit in your widget setup.

Use this section only if you need custom analytics or custom website behavior tied to widget actions.

Most customers do not need manual tracking setup to use the widget successfully.

## Who should use this section

* Developer teams integrating Remapdb with GTM, GA4, Meta Pixel, or internal analytics.
* Teams that want custom behavior on their website when users select vehicles in the widget.

## When to use Tracking

Use this section when you need to:

* Send widget selection data to your analytics tools.
* Trigger website behavior when users interact with the widget.
* Build custom reporting based on vehicle selections and tuning-stage data.

## When you can skip Tracking

You can skip this section if you only need:

* Normal widget installation and launch.
* Standard quoting flow.
* Standard SEO setup from the widget settings.

## What this section includes

* Event flow between widget iframe and website page.
* What each event means.
* Security checks you must implement.
* A safe listener example for analytics tools.
* Control widget theme programmatically from your own website

## Pages in this section

<div>
  <Columns>
    <Card title="Tracking events" href="/widget/tracking/tracking-events">
      Event reference for custom analytics and custom website integrations.
    </Card>
  </Columns>
</div>


# Tracking events
Source: https://docs.remapdb.com/widget/tracking/tracking-events

Developer reference for Remapdb widget events used in custom analytics and custom website behavior.

This page is for advanced integrations.

If you only need standard widget setup, you do not need to implement these events manually.

## How event communication works

Remapdb widget communicates with your website using events.

Event name format:

* `rdb-eventName`

Why this matters:

* It helps prevent cross-talk when multiple widgets exist on one page.
* Your listener should always filter by event name and origin.

## Events emitted from the widget

### `rdb-queryKey`

The widget sends the query key name it uses (default is usually `catalog`).

Important detail:

* Use this key when building custom URL rules on your website side.

### `rdb-seoConfig`

The widget sends SEO configuration flags and templates.

Important detail:

* This allows parent-page SEO updates (title, description, OG, JSON-LD) to stay aligned with widget settings.

### `rdb-vehicleMeta`

The widget sends current selected vehicle metadata and gains.

Important detail:

* This is the main event for analytics integrations.

Typical payload fields include:

* Vehicle type, brand, model, generation, engine.
* Vehicle name and language.
* Engine fuel type.
* Gains for different stages.
* Language
* Stages
* URL path.

Listener Example:

```js theme={null}
window.addEventListener("message", (event) => {
  if (event.origin !== "https://app.remapdb.com") return;

  const evt = event?.data?.event || "";
  if (!evt.endsWith("-vehicleMeta")) return;

  const meta = event?.data?.meta;
  if (!meta) return;

  window.dataLayer?.push({
    event: "remapdb_vehicle_selected",
    vehicle: meta.vehicleName,
    type: meta.type,
    brand: meta.brand,
    model: meta.model,
    generation: meta.generation,
    image: meta.image,
    engine: meta.engine,
    fuelType: meta.fuelType,
    gains: meta?.gains,
    language: meta.language,
    stages: meta?.stages,
    urlPath: meta.urlPath,
  });
});
```

### `rdb-updateUrlPath`

The widget asks your website to update the browser URL with the current vehicle path.

Important detail:

* Applied only when link sharing is enabled.

### `rdb-requestCurrentURL`

The widget asks for the current full page URL.

### `rdb-switchLanguage`

The widget asks your website to reload iframe with a selected language.

Important detail:

* Applied only when link sharing is enabled.

## Programmatic theme control

If your website has a light/dark switch, you can notify the widget by firing this event from your website page:

### `rdb-theme`

```js theme={null}
window.dispatchEvent(new CustomEvent("rdb-theme", {
  detail: { theme: "dark" } // light | dark | auto
}));
```

Important detail:

* This is consumed by widget runtime. It is not emitted by the widget.
* Use it when your website changes theme via custom theme switcher.

<Info>
  For custom theme switchers, use the programmatic integration guide:
  [Sync widget theme with website](/widget/branding/theme-sync-with-website)
</Info>

## Implementation safeguards

* Always verify `event.origin`.
* Filter only Remapdb namespaced events.
* Ignore events without expected payload fields.
* Add tracking listeners in your own website code or tag manager.
* You do not need to edit Remapdb widget files.

## Troubleshooting

* Confirm the widget is loaded and interactive first.
* Open browser developer tools and inspect `message` events.
* Confirm your origin check matches your real app domain.
* Confirm your listener loads after widget initialization.

## Related actions

* [Tracking](/widget/tracking)
* [Sync widget theme with website](/widget/branding/theme-sync-with-website)
* [Code installation](/widget/installation/code-installation)
* [WordPress plugin installation](/widget/installation/wordpress-plugin-installation)