Whether a bundle gets its own Shopify product comes down to a single checkbox: leave it unticked and the bundle stays widget-only; tick it and choose Physical or Shopify. There's no separate "create a product" setting anywhere else in the bundle.

Found at the top of the Bundle type card, on Separate products and Product groups bundles only — Volume discount and BOGO bundles never show the Bundle type card at all.

When it's locked: it's greyed out while you're editing a saved bundle — this is the lock that matters most, because it's the reason the bundle type can never be changed later (see "Changing the type of a saved bundle" below). It's also greyed out when a group points at a collection or the whole store, when a tiered or volume discount is on (the checkbox then shows the text "Not available with tiered discounts"), when the quantity selector is on, and when optional products are on in Popup mode. On current plans — Free, Tier 1, Tier 2, Tier 3, Tier 4 and Enterprise — nothing about your plan locks this checkbox, including on Free. A lock with a "PRO" badge only appears on an older legacy plan generation.

The rule: the choice to give a bundle its own Shopify product is made once, while you create the bundle — on a Separate products or Product groups bundle whose items are individual products, with no tiered discount, no quantity selector and no popup optional products — on any current plan.

What the shopper sees: a real product page for the bundle, in addition to the widget on the item pages. With it on, the app's own copy applies: "Shows the bundle as a single product in the cart, but splits it into separate items at checkout and in the order."

A radio option under the checkbox, shown once "Create a product for this bundle additionally to widget" is ticked. Locked under the same conditions as the checkbox above.

Pick Physical while creating the bundle to have each bundle item appear as its own line in the cart and at checkout, and to sell the bundle on the Google, YouTube, Facebook and Instagram channels.

What the shopper sees: each component listed separately in the cart and at checkout.

A radio option under the checkbox, shown once "Create a product for this bundle additionally to widget" is ticked. Locked under the same conditions as the checkbox above.

Pick Shopify while creating the bundle to get a native Shopify bundle product that works with Shopify POS and is split into its components at checkout and in the order.

What the shopper sees: one product line in the cart, split into the individual items at checkout and on the order.

Shown under the checkbox while you're creating a bundle whose settings rule a type out — never shown while editing a saved bundle. The caption names the exact setting that's blocking it:

The card's note adds that the quantity selector, tiered discounts and collections all belong to widget-only bundles.

There's no control for changing the type after the first save. To change a saved bundle's type: open the Bundles list, use the ••• menu on the row → Duplicate, set the type on the copy while it's still unsaved, save the copy, then deactivate or delete the original.

Only available while creating or duplicating a bundle — it's permanently locked on any bundle that's been saved once. A widget-only bundle stays widget-only for its whole life, and a bundle with its own product can never be reduced to widget-only. Duplicate the bundle and set the checkbox on the copy before its first save.

The product is created by the app as soon as the bundle is saved with "Create a product…" ticked, and Shopify answers asynchronously — so it may take a moment to show up.

Shown in the page header's secondary actions when you're editing a saved Physical or Shopify bundle that already has both a product id and a handle — it's absent until the product exists, never greyed out.

"View in admin" opens the generated product in Shopify admin (Products → the bundle's internal name), and appears as soon as Shopify has created it. If it's missing, save the bundle and reload — product creation is asynchronous.

Shown in the page header's secondary actions when you're editing a saved bundle. Greyed out while the bundle isn't Active or the app embed is off in the theme — the tooltip then reads "To preview bundle be sure bundle and app embed are active".

"View in online store" opens the bundle on the published theme: the bundle product's own page for a Physical or Shopify bundle, and the first visible component product, collection, or /collections/all for a widget-only bundle — with the app's cache cleared on load.

Always applies. These are not two independent switches: the app writes the Shopify product's status from the bundle's status on every rebuild, so an Active bundle produces an ACTIVE published product, a deactivated bundle produces a DRAFT product, and an archived bundle produces an ARCHIVED one. Always change the status in the app — a status set by hand in Shopify is overwritten at the next rebuild.

A rebuild is skipped when nothing meaningful changed, so a status you've hand-edited in Shopify can survive for a while — but it will be overwritten the next time something in the bundle actually changes and triggers a real rebuild.

What the shopper sees: the bundle product's page is reachable only while the product is ACTIVE and published.

Shown when the bundle creates its own product. Build the bundle image inside the app by clicking the component thumbnails onto a 500×500 canvas, dragging and resizing them, ordering overlaps with "Send to back" / "Bring to front", and saving. The composition is kept so you can reopen it with "Edit image" — or use "Upload image" to supply your own .jpg, .jpeg or .png instead.

Shown when the bundle creates its own product. Tick "Hide compare at price" to send the bundle product's variants to Shopify with no compare-at price.

What the shopper sees: only the bundle price, with no crossed-out amount beside it.

Shown when the bundle creates its own product. Tick this to also show, on this bundle's own product page, the widgets of other active bundles that contain any of this bundle's products. Leave it unticked for this bundle's widget alone.

A radio, "Separate items" / "Single product", shown on every Shopify bundle, and on a Physical bundle only while it's still saved as "Single product" — it's hidden rather than greyed out once unavailable.

Choose Single product for the bundle to appear in the cart as one line, or Separate items for each component to get its own line. Shopify bundles default to Single product; Physical bundles default to Separate items. Once a Physical bundle has been saved as Separate items, the option disappears for good — duplicate the bundle to get it back.

What the shopper sees: one cart line, or one line per component.

The two pickers appear while creating or duplicating a bundle. When editing a saved bundle, the card shows a single link into Shopify admin instead.

Set the generated product's tags and collections here while creating the bundle — type a new tag and press Enter, or pick existing ones from the list. After the bundle is saved, edit its tags, collections and product description on the product in Shopify admin, through the "Edit tags, collections, description" link on this card.

Shown when the bundle creates its own product. This is the heading the widget shows on the bundle's own product page, translatable per widget language with the Translate button beside it — it does not rename the Shopify product. The Shopify product title is always the Bundle internal name.

Shown when the bundle creates its own product. This is the description text the widget shows on the bundle's own product page, translatable per widget language.

Always shown, in the Bundle information card. Greyed out on a non-primary variant of a running A/B test.

Bundle internal name is required, at most 255 characters, and is used verbatim as the Shopify product title of a bundle that creates its own product.

Validation: required — "Bundle internal name" cannot be empty and is capped at 255 characters.

This is the combinations grid inside the products card. It's rendered only for Shopify bundles, 10 rows per page, and the rows are generated by the server and regenerated (after a 300 ms pause) whenever the products, the discount, the quantity settings or the optional-product settings change. Your edits to Variant name and SKU survive that regeneration; Price and Compare at price are always taken from the server.

The first column. The chevron at the left of a row expands it to list that combination's contents as "Product title - Variant title x Quantity". Always clickable.

An editable field in the first column. This is what the shopper sees as the bundle variant at checkout and on the order. It's required, must be unique across the grid, is capped at 255 characters, and arrives pre-filled from the component product titles with repeats collapsed as "Title x2".

Validation: required and unique, both blocking save — "Variant name is required", "Variant name must be unique".

What the shopper sees: this exact text as the variant name of the bundle at checkout and in the order.

A bundle with exactly one combination is a single-variant Shopify product, so Shopify stores "Default Title" there instead, and the name you typed isn't what comes back.

Always shown, always read-only. Price is calculated by the app from the component prices and the discount you configured, and is shown here for checking only — change it by changing the discount or the component products.

Always shown, always read-only. Compare at price is the sum of the components' prices, or of their compare-at prices when "Display discount to customers from Compare-at price" is on. It's display-only here — suppress it on the storefront with "Hide compare at price".

Always shown, on Shopify bundles only. SKU is optional — leave it blank and an empty SKU is sent to Shopify. Anything you type there (up to 50 characters, unique across the grid) is written to the matching Shopify variant, where Shopify's own fulfilment, inventory, reports and any external channel or 3PL that reads SKUs will pick it up.

Validation: filled values must be unique and block save otherwise — "SKU must be unique".

Physical bundles have no per-combination SKU column at all — every generated variant carries a single shared legacy SKU value, if one was ever set for the bundle. It isn't confirmed whether any screen in the current app still lets you set that value; if you need SKUs on a Physical bundle's variants and can't find a way to set one, contact support and mention that you're looking for the legacy per-bundle SKU field.

Appears immediately, as soon as a Physical bundle's distinct price combinations exceed 250 — not only on Save. A Physical bundle holds at most 250 distinct price combinations, so keep the selectable variants few enough that they multiply out to 250 or fewer.

Validation: blocks save — "250 max price combinations for this bundle type. You have {count}. Reduce product variants."

Appears immediately, as soon as a Shopify bundle's generated combinations exceed 2048. A Shopify bundle holds at most 2048 combinations. While you're still creating the bundle you can switch it to Physical instead of trimming; once it's saved, the only remedy is to reduce the number of selectable product variants.

Validation: blocks save —

Appears when the server-side combination generator returns a failure for a Shopify bundle. Reduce the number of products or product variants, starting with the Uncombined quantity and optional-products settings, which multiply combinations fastest.

Validation: blocks save — "Failed to generate combinations. Please check your settings and try again. Try reducing the number of products or product variants. Note: the "Uncombined quantity" and "Optional products" settings significantly increase the number of possible combinations."

The cartesian product of every group's selectable variants; each optional product group adds an "included / not included" dimension; the quantity selector and uncombined quantity widen the quantity dimension; "combine identical bundle items" collapses repeats. For the Physical 250 check, variants sharing the same price/compare-at pair are deduplicated first, so 250 counts distinct price outcomes rather than raw variant permutations.