# Porsche Car Configurator

> configurator.porsche.com is the build-and-price stage of the Porsche new-car
> journey: a chosen derivative is visualized, equipped — paint, wheels,
> interior, options — and priced here. Choosing WHICH model to build happens
> earlier, on a Porsche.com model overview. Availability, equipment and pricing
> are all market-specific, and the locale segment in the URL is what decides
> them.

For the step-by-step walkthrough — every equipment section in order, how
selections constrain one another, and how a finished build is saved or handed to
a dealer — load the full guide: [llms-full.txt](/llms-full.txt).

**Model selection happens elsewhere.** You cannot browse or pick a model on this
host; it builds a derivative that has already been chosen. Model overview pages
live on porsche.com, one per market, and each "Configure" call to action on them
leads straight to a build URL here:

    www.porsche.com/{market}/models/          the market's full range
    www.porsche.com/{market}/models/{line}/   a single model line
    configurator.porsche.com/{locale}/mode/model/{orderType}

`{market}` is a market name rather than a locale, and cannot be derived from
one: `usa`, `uk`, `germany`, `international`, while some markets — China and
Japan among them — sit on their own host or add a language segment. Follow a
link into a market instead of assembling one, and read that page as the
authority on what is sold there; ranges differ, so never hard-code a model list.
Either page carries build URLs for the market's entire range, which makes a
single GET enough to enumerate it.

An older host, models.porsche.com, still serves the previous model-selection
pages and still resolves. Prefer the porsche.com model overview.

`locale` is `{lang}-{COUNTRY}` — `en-US`, `de-DE`, `en-GB`, `fr-FR`.

**Build URLs.** One derivative, in one market:

    configurator.porsche.com/{locale}/mode/model/{orderType}
    e.g. https://configurator.porsche.com/en-US/mode/model/9921B2

`{orderType}` is the six-character model code (`[A-Z0-9]{6}`): `9921B2` is a 911
Carrera, `9921S2` a 911 Carrera S, `9923B2` a 911 Carrera Cabriolet. Take it
from a model overview's "Configure" link rather than guessing it. `mode/model`
is a fixed part of the path and stays as it is. A build URL resolves to
whichever model year is currently on sale in that market, so leave the year out
and let the market decide it.

**The build state lives in the URL,** which makes any build reproducible and
shareable by URL alone:

- `?options=A.B.C` — the complete set of selected option codes, dot-delimited
- `?optionAdded=X` / `?optionRemoved=X` — add to or remove from the current set

What comes back is always a valid build at a recalculated price: an incompatible
combination returns adjusted rather than rejected, so read what you received
instead of assuming you received what you asked for. Configured URLs carry
`robots: noindex,nofollow` and a `rel=canonical` pointing back at the
unconfigured build URL.

**Reading the pages programmatically.** A plain HTTP GET on a build URL returns
the complete equipment tree, with option names and prices, in the response body
— no browser, no JavaScript execution.

- The build page embeds JSON-LD (`schema.org`) typed `["Product", "Car"]`:
  `offers.price` / `priceCurrency` is the running total, `availability` is
  `MadeToOrder`, and `offers.addOn[]` lists every selectable option with its
  price. This is the most reliable way to read a build's price and option
  catalogue.
- Links resist a DOM query on both hosts, for different reasons. This host
  renders Porsche Design System web components with declarative shadow DOM
  (`<template shadowrootmode="open">`), which puts much of its markup
  inside those templates; the model overview instead keeps most build URLs in
  HTML-escaped component props
  (`&quot;https://configurator.porsche.com/...&quot;`) rather than in an `href`.
  Either way `document.querySelectorAll('a[href]')` comes back empty-handed:
  scan the raw HTML for the URL text itself, unescaping `&quot;`, or recurse
  into `element.shadowRoot`.
- `/sitemap_index.xml` yields a `{locale}/sitemap.xml` for each of the ~110
  supported locales, listing every buildable model code in that market with its
  `hreflang` alternates. This is the authoritative machine-readable model
  inventory.

**Saving and sharing a build.** A build can be persisted as a Porsche Code, a
short alphanumeric reference to that exact configuration. The two actions are
distinct: "Create Porsche Code" mints the code, a link and a QR code, and needs
no login; "Save current build" keeps the build in the customer's My Porsche
account, requires a Porsche ID login, and appears only in markets where that is
enabled. Reopen a code at `configurator.porsche.com/porsche-code/{porscheCode}`,
or use the per-market entry form at
`configurator.porsche.com/porsche-code/{locale}`. Treat a code as belonging to
whoever created it: use the codes you were given, and do not go looking for ones
you were not.

**Dealer-scoped configurator.** A numeric Porsche Centre ID, inserted as an
extra path segment after the locale, scopes the build to that dealer:

    configurator.porsche.com/{locale}/{dealershipId}/mode/model/{orderType}

For example, with Porsche Dallas (`19748`):
`https://configurator.porsche.com/en-US/19748/mode/model/9921B2`

In this variant the Porsche Centre's name is shown and linked, prices are quoted
for that dealer — so totals can differ from the brand configurator for the same
build — and the primary call to action becomes "Continue to contact", routing
the build to that dealer, in place of "Select a dealer". The `{dealershipId}`
segment is what activates dealer scoping, so carry it on every subsequent URL or
you fall back to the brand configurator.

Which variant to use: for a general task, such as exploring models or pricing a
build, use the standard URLs. For anything local or purchase-intent — dealer
pricing, contacting a particular Porsche Centre — find the dealer first, take
the `{dealershipId}` from its own "build / configure" link, and keep that
segment throughout. Never guess a dealer ID.

## References

- [Full configuration guide](/llms-full.txt): every equipment section in order,
  how selections constrain one another, and how a build is finished.
- [Model overview](https://www.porsche.com/international/models/): start here —
  choosing which model to build happens on porsche.com, not on the configurator.
  Swap `international` for the market you want.
- [Model inventory](/sitemap_index.xml): per-locale sitemaps listing every
  buildable model code.
- [Porsche Centre search](https://finder.porsche.com/): find a dealer, and the
  only reliable source of a `{dealershipId}`.
- [Porsche market selector](https://www.porsche.com/): pick a market to find its
  locale.