SKU & pricing fields

The SKU is the bridge between a configured product and your commerce platform: every selection the embed reports is a set of variation SKUs (see The commerce boundary).

Setting SKUs

Each variation has a SKU field in the panel. Three rules make commerce work end to end:

1. Every sellable variation needs a SKU. Variations without one silently drop out of the add-to-cart payload — the shopper picks them, your cart never hears about them. The Setup Check warns when some variations have SKUs and others don’t.
2. SKUs must be unique. If the same SKU is used by several variations, deep links and cart mapping resolve to only the first — the rest become unreachable from a share URL. The Setup Check names the exact duplicates.
3. Use your real store SKUs where they exist — that makes the SKU → variant-ID mapping on your storefront a lookup instead of a translation (see Add to cart).

If you’re publishing a showcase without a store, skip SKUs entirely — nothing else depends on them.

Where prices come from

Deliberately not from the configurator. Prices displayed inside the viewer are pushed in by your page from your own catalogue, keyed by these same SKUs — the viewer formats and displays them verbatim and never computes a total on its own. The full pattern: Prices in the configurator.

This is why there is no “price” column next to the SKU field: a second source of pricing truth inside the configurator would drift from your store’s tax, currency and promotion logic. One source — yours — stays correct.