Billing & PaymentsProducts and Pricing

Variants (options and SKU)

Sell one product in several sizes or colours by giving each one-time price its own options, SKU and image, and show a different picture for a recurring or usage price.

In RevKeen a variant is a price. A cardigan sold in navy and grey, in sizes S, M and L, is one product with one price per combination. Each of those prices can carry:

FieldWhat it isExample
OptionsUp to 3 name and value pairsColour: Navy, Size: M
SKUYour stock code for this variant, up to 64 charactersCARD-NAVY-M
Variant imageOne of the product's imagesThe navy photo

Each price still has its own amount, currency and customer-facing name, as today.

In the Dashboard

  1. Open Products and create a product on the one-time pricing model, or edit an existing one-time product.
  2. Add the product's images under Images first. A variant image is picked from those images.
  3. Open a price (the default price, or one of the Other prices) and fill in its variant section: up to three Options, the SKU and the Variant image.
  4. If the price has no name yet, select Name this price to use the options as the price name, for example "Navy / M". You can still edit the name.
  5. Add one price for each combination you sell, then select Create product or Save changes.

Rules

  • Options and SKU are available on one-time prices only. A price image is also available on recurring and usage prices (see Price images on recurring and usage prices).
  • A variant has up to three options. An option name can be up to 40 characters and an option value up to 60. A SKU can be up to 64 characters.
  • A SKU can be used by only one active price across all your products.
  • Within one product, each combination of options can be used by one active price.
  • The SKU stays with the variant when you edit its price. Editing a price saves a new version of it, and the SKU moves to the new version.
  • Once a variant has been sold, its options are fixed. To change them, archive the price and add a new one. You can still change its SKU and image in the product editor; a new SKU is saved as a new version of the price, so orders already placed keep the SKU they were sold under.

Price images on recurring and usage prices

A recurring or usage price can carry an image of its own, chosen from the product's images. For example, the yearly price of a membership can show a different picture from the monthly price. A price image has no options or SKU; those stay on one-time prices.

When a price has an image, it is shown wherever that price is the one the customer is looking at:

  • Checkout. The picture at the top of the order summary, the picture beside each product, and the picture in the product details window all follow the price selected for that product. If a customer switches price, the picture changes with it.
  • Your RevKeen Storefront. A product card shows the image of the price it displays, and the product page opens on that price's image. This is the product's default price, unless a block on your page points at a different price.

If the selected price has no image, or its image cannot be shown, RevKeen shows the product's main image instead. If neither has an image, a placeholder is shown.

Where variants appear

  • Your RevKeen Storefront. A product page shows one picker per option. The shopper chooses, for example, Colour and Size, and the matching price is what goes in the cart. A combination you do not sell cannot be added. Product cards for a product with several variants link to the product page with Choose options.
  • The API. Prices returned by /v2/prices and by the Storefront product API carry option_values, sku and image_url. They are read-only there; set them in the product editor. On a recurring or usage price, image_url is the price image and option_values and sku are null. image_url is null when the price has no image of its own; the product keeps its own image_url.

Checkout and orders do not show the options and SKU yet. Checkout does show the price image, as described above.

Owner: david · Reviewed 4 Nov 2026 · Next review 1 Nov 2026

On this page