Before selling a shopper-selected gift box, verify the candidate variants and the complete purchase path. A configuration screen, a public demo or a successful selection alone does not establish that a store is ready for live orders.
This checklist describes the tnova workflow’s intended checks. It does not certify any store, theme, market or checkout customization.
Quick answer: A candidate is ready for this tnova workflow when it is a physical, inventory-tracked variant that stops selling when out of stock, uses the supported default quantity rule, and shares one active online-fulfillment location with every other candidate. Then test a complete selection and the real cart path. A missing or uncertain Shopify result is a failed check until investigated.
Confirm the candidate data
Use the real variants you intend to fulfill. In Shopify admin, open Products, then each product variant and its inventory details. Check the variant ID, title, image, available quantity and location. Distinguish unavailable candidates from a missing sync result: an unknown value is a reason to investigate, not proof of availability.
For this version of tnova, verify each component against the following app requirements. These are tnova restrictions, not a claim that Shopify requires the same setup for every kind of bundle.
| Check | Supported tnova value | What to do if it differs |
|---|---|---|
| Product type | Physical item that requires shipping | Replace a digital or non-shippable candidate. |
| Inventory | Tracking enabled; selling when out of stock disabled | Turn on tracking and stop overselling before retrying. |
| Quantity rule | Minimum 1, increment 1, no maximum | Restore the default rule or use another variant. |
| Fulfillment | Exactly one active online-fulfillment location for each candidate, and the same location for the entire pool | Resolve extra, different or third-party fulfillment locations before publishing. |
Shopify explains how to set up variant inventory tracking. Check the actual available quantity at the supported location; an overall store total can conceal a shortage there.
Check fulfillment assumptions
Confirm the single shared location can supply every candidate item. This tnova workflow does not support split-location sourcing or third-party fulfillment locations for these components. If one candidate moves to another location, rerun readiness before taking orders.
Shopify’s bundle considerations provide platform context. Your app’s supported workflow and your own store tests remain separate checks.
Check selection feasibility
Work through at least one valid combination with the configured total and repeat limits. Repeat the check when inventory or the candidate pool changes. For each candidate, compare available quantity with the quantity needed per box and the number of boxes you expect to sell. Shopify's fixed-bundle inventory explanation illustrates why the scarcest required component constrains a complete bundle; use tnova's actual readiness result for a shopper-selected box.
For a fictional six-item box with three varieties and a repeat limit of two per variant, a shopper needs two of each to reach six. If one variety has only one available unit at the shared location, that particular combination cannot make one complete box. Do not report the box as ready merely because the other varieties have abundant stock. Read the selection-rules guide for a separate worked example.
Check the storefront
- Open the intended product page and verify the picker block is present.
- Check the same page on a narrow screen.
- Review the price, total, repeat rules and item names.
- Confirm the store uses the default market and currency supported by this box configuration; test another market separately instead of assuming the price will transfer.
- Confirm unavailable items produce an understandable result.
- Verify only the theme and cart path recorded as supported for your store.
Visual similarity to the demo is not evidence of compatibility. Test any drawer cart or other customization as part of the actual purchase path.
Check the cart and edit flow
Inspect the selected component variants and quantities in the cart. Try the supported “remove and reconfigure” edit path. Cover both success and failure, including a failed removal, a failed replacement and cancellation.
Do not use a stale price or a newly edited configuration to reinterpret what the customer originally selected. If a result cannot be verified, preserve the relevant details and stop the affected flow until the cause is understood.
Check eligibility and release status
Review readiness and current selling eligibility independently of the desired configuration state. A merchant can want a box to be published while another requirement prevents effective selling.
Follow the store’s applicable validation process before accepting live orders. Product claims, platform eligibility and technical transaction checks each need their own evidence.
Keep a useful test record
Record the tested product, configuration version, candidate IDs and available quantities at the shared location, market/currency, theme/cart path, time and observed result. For a failed check, note the exact readiness message and the variant it names. Use test data where appropriate. Keep customer information out of screenshots shared for support unless it is necessary and authorized.
If a check fails, use the troubleshooting guide to narrow the issue without deleting the configuration or replacing the shopper’s choices.
See a gift box in action
Try the sample picker with fictional products. It creates no cart or order.
Try the box builder