How to check Shopify gift-box purchase entry points

Quick answer: Send shoppers to the gift-box product page to choose their components before adding the complete box. Check every collection card, search result, recommendation and promotional link that exposes the parent product. A normal quick-add button cannot be assumed to carry a shopper's selection, even when the product page works correctly.

This guide audits the routes into an existing tnova box. The current verified baseline is Dawn 16.0.0 with cart type Page, the default market and currency, and a shared online fulfillment location for components. Public installation is not available yet; use this plan for preparation or an authorized existing test setup. Check the current feature status before planning a different theme or cart mode.

Give the parent product one complete selection path

A tnova parent product represents the complete fixed-price box. Its component variants are the items a shopper chooses. Buying a component separately is a different action from choosing that component inside a box.

Shopify's bundle implementation guide describes an app-provided component picker for customized bundles. In tnova, that interface is Box picker. It carries the selected variants and quantities into the add process; the theme's ordinary product controls do not replace it.

Prepare an unpublished copy of your theme. Use a dedicated product template for the parent, add Box picker, and remove that template's native Buy buttons, Quantity selector and Variant picker blocks. Keep ordinary products on their existing templates. Add Box contents to the cart page so customers can review the components Shopify actually placed there. Use the full theme integration test for block placement and the subsequent cart checks.

Shopify explains that template edits affect every page using that template. Create and preview the dedicated template before assigning it. Product-admin template choices come from the live theme, so an unpublished theme's new template might not appear there yet. In the test theme editor, preview the parent with the intended template, then verify assignment again during the theme launch.

Inventory every place the parent can appear

Start from the storefront's navigation, rather than opening only the product URL you already know works. Search for the parent product's name and inspect the pages used by your next promotion.

Use this as a blank audit sheet. The rows are places to inspect if your store exposes them, not a claim that every Dawn installation includes each control.

Record the page URL, theme version, viewport, visible button label and observed destination. A label such as “Choose your items” is useful only if the click actually opens the right picker.

Resolve a shortcut that skips configuration

Suppose a fictional store offers a six-unit box. The parent product page lets a shopper choose two of variant A and four of variant B. A collection card also displays an ordinary Add to cart button for that parent. That card has no information about the shopper's intended two-plus-four selection.

For the current tnova flow, make that route open the parent product page. If your theme offers a suitable quick-add setting, test the resulting behavior. If it cannot distinguish this parent from ordinary products, ask the theme maintainer for a targeted change and keep the shortcut out of the launch path until verified. A product template change alone does not prove that a separately rendered collection card or modal changed too.

Do not remove the parent's component requirement to make a shortcut succeed. Shopify's requiresComponents reference says such a variant can only be purchased as a bundle parent with components. tnova prepares its parent with that requirement. It protects the product's meaning; it does not turn a generic button into a selection interface. An error from an unsupported shortcut is still a storefront issue to fix.

Test the repaired route with an ordinary-product control

For each entry point, run the same short task on desktop and mobile:

1. Open the collection, search result or promotional page as a shopper would.
2. Follow the box action and confirm the parent name, fixed price and required count in Box picker.
3. Try an incomplete selection, then complete one valid selection within the repeat limit.
4. In an authorized cart test, add once and inspect the full cart page. Compare actual component variants and quantities with the selection.
5. Return to the source page and repeat with one ordinary product. Confirm its intended purchase controls still work.

A visual preview can establish the route and presentation. It cannot establish a successful cart add or checkout. Run those steps only when the box has the appropriate authorization; the fictional sample builder creates no Shopify cart or order.

If an add response is interrupted, inspect the actual cart before retrying. Use the separate cart-editing and recovery test when a replacement or removal is involved.

Close the audit with a route-specific decision

Record each route as passed, failed or untested. “Product page passed; mobile quick view untested” is more useful than “theme compatible.” Launch only through routes whose relevant selection, cart and checkout checks have passed. Dawn cart-drawer work remains awaiting release and verification; a drawer opening is not evidence that the box path is supported.

Keep the sheet with the exact theme version. Recheck affected routes after a theme update, a new recommendation or quick-view app, or changes to the box template. This makes the next review a comparison against known behavior instead of another guess from a screenshot.

Prepared with AI assistance and checked against tnova's implementation and the official sources linked in this guide. Examples are fictional.