CMS Variables

CMS Variables are name/value records that the backend reads from the CMS. Use this page for CMS Variables; deployment and runtime environment variables are documented in the repository ENVIRONMENT.md.

Fixed variables

Create the following names exactly as shown. Variable names are case-sensitive. Each name can have a localized variant as described below.

The seller variables are read independently for inventory and deals. Reusing the same value is fine, but each fixed name still needs its own CMS record.

Localized CMS Variables

Use uppercase, underscore-separated base names. A locale-specific value uses a lowercase locale suffix separated with a dot:

Use the base name in a template, for example {{SHOP_NAME}}. For a German page, the application uses SHOP_NAME.de when it exists; otherwise it falls back to SHOP_NAME. Do not use {{SHOP_NAME.de}} in a template.

This applies to CMS Variables used in page metadata, page-template slugs, inventory and deal seller data, and generated inventory metadata. A localized record with an empty value still overrides the default value.

The previous locale-prefix naming is deprecated. Rename the existing inventory metadata records as follows:

Use the same pattern for every other locale, for example .en.

Inventory metadata variables

These variables provide the call-to-action text when an inventory vehicle has no storage location. Use the generic name in generated metadata; add a locale suffix to the CMS record when the text differs by language.

Variables in templates and metadata

There is no closed list of names for template variables. The backend loads all CMS Variables when it renders:

• page metaTitle and metaDescription;
• page-template slugs, including generated inventory/product pages; and
• page titles and descriptions in /llms.txt.

Reference a CMS Variable with double braces, for example:

Variable name: SHOP_NAME
Variable value: Autohaus Beispiel

Page meta title: Fahrzeuge bei {{SHOP_NAME}}

The allowed name format is uppercase letters, digits, and underscores, with an optional lowercase locale suffix such as .de or .en. Examples are SHOP_NAME, SUPPORT_EMAIL, and SHOP_NAME.de. A missing variable is rendered as an empty string, so create every CMS Variable that a template or metadata field references.

Handlebars supports both {{VARIABLE}} and {{{VARIABLE}}}. Double braces HTML-escape the value; triple braces render the value unescaped. Use triple braces only for trusted CMS content that is intended to contain HTML. The inventory VEHICLE_BUY_* CTA variables use triple braces.

Built-in placeholders

The following placeholders are supplied by application code and must not be created as CMS Variable records:

These placeholders are different from CMS Variables: their values come from the page or deal being rendered.

Update existing CMS content to the uppercase syntax before deploying this change. Legacy placeholders are not expanded:

Page-template slug placeholders

Inventory-car, shop-product, and shop-collection templates use the application-supplied placeholders below. Do not create CMS Variable records for these names. Values are normalized into URL-safe slug segments before substitution.

Car-deal and generic-page templates use values supplied by their calling backend integration. The platform does not provide a data-source or automatic page-generation flow for those template types.

CMS Variables can also be used as path components. Reference the generic uppercase name in the template, such as {{SHOP_PATH}}. A CMS variable named SHOP_PATH.de is used for German pages; SHOP_PATH remains the fallback for other locales. The resolved value is normalized into a URL-safe path segment.

{{RANDOM_4_ID}} and {{RANDOM_7_ID}} are generated once when a sync slug is created. Reusing a stored slug does not generate a replacement identifier.

Example templates:

Inventory car: /{{LOCALIZED_PATHNAME}}/{{INVENTORY_ID}}/{{VEHICLE_SLUG}}
Shop product:  /{{LOCALIZED_PATHNAME}}/{{PRODUCT_SLUG}}-{{PRODUCT_ID}}
Shop collection: /{{LOCALIZED_PATHNAME}}/{{COLLECTION_HANDLE}}
Car deal:      /{{LOCALIZED_PATHNAME}}/{{VEHICLE_BRAND}}-{{VEHICLE_MODEL}}-{{DEAL_ID}}
Generic page:  /{{PAGE_TYPE}}/{{PUBLIC_NAME}}

The locale prefix remains automatic and is not part of the template. Prefer stable identifiers plus descriptive fields. Do not use mutable data such as price, mileage, stock, tags, or validity dates because those values would cause unnecessary URL changes.

Code inventory

The fixed names above are the complete set of literal CMS variable names used by the backend. The other variable reads use getAllVariables for localized template and metadata rendering. The AI/MCP variable operations require the same uppercase-and-underscore naming convention and do not introduce another required system variable.