> For the complete documentation index, see [llms.txt](https://docs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akinon.com/technical-guides/project-zero/next.js/checkout-variant-system-configuration.md).

# Checkout Variant System Configuration

Project Zero lets you choose the checkout layout through a single setting, without changing your integration. The default multi-step checkout is unchanged; you opt in to a different layout when you are ready.

### <mark style="color:red;">Enabling a Variant</mark>

Set the variant in your project's `settings.js`:

```
checkout: {
  variant: 'one-page',
  options: { enableEditMode: true, autoAdvance: true, stickyMobileCta: true }
}
```

* `settings.checkout.variant` — a string that selects the layout (see below).
* This is a **build-time configuration value** — not an admin-panel or API setting.
* If the value is missing or unrecognized, checkout falls back to `multi-step`. (On a fresh project the variant is not set, so checkout defaults to multi-step until you add the key.)

### <mark style="color:red;">Available Variants</mark>

| Variant                | Description                                                                                                                              |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `multi-step` (default) | Classic two-step wizard: Shipping, then Payment, with a side order summary.                                                              |
| `one-page`             | Single-page checkout: Contact, Address, Shipping and Payment shown as stacked accordion sections that auto-advance as each is completed. |
| `accordion`            | Same layout as `one-page` (alias).                                                                                                       |
| `basket-and-checkout`  | The one-page flow with the cart shown on top, so basket editing and checkout live on one unified page.                                   |

### <mark style="color:red;">Fine-Tuning (Optional)</mark>

`settings.checkout.options` toggles behavior within a variant:

* `enableEditMode`
* `autoAdvance`
* `stickyMobileCta`
* `showOrderReview`
* `showTrustBadges`
* `gtmEnabled`
* `compactMode`

### <mark style="color:red;">Switching and Compatibility</mark>

* **No data migration.** All variants share the same checkout state and data layer, so switching is a configuration change only.
* The default `multi-step` checkout and its components are untouched — nothing is removed.

{% hint style="info" %}
`basket-and-checkout` turns the basket page into a redirect to checkout (cart and checkout become one page). If you rely on a standalone basket page, choose a different variant.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akinon.com/technical-guides/project-zero/next.js/checkout-variant-system-configuration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.