Quick answer: Check a gift box's tax on its actual Shopify component lines, then compare their total with Platform tax in tnova's order view. A fixed box price does not establish one tax rate for every selectable item. Record whether the order includes tax in its prices before adding or subtracting anything: otherwise, you can count the same tax twice.
This is an order-verification worksheet for an authorized tnova store, not a guide to deciding which taxes your business must charge. Shopify's tax guidance assigns that decision to the merchant, with advice from the relevant tax authority or tax professional. Use their approved treatment as the expected result for your test.
Public installation is not available yet. The verified tnova checkout baseline is Dawn 16.0.0 with cart type Page, the default market and currency, and a shared component fulfillment location. A successful development-store test does not establish tax correctness for another store or destination.
Make a component tax sheet before checkout
List each selectable Shopify variant and identify the product record that owns it. Beside it, record the tax treatment approved for your store, any applicable product category or override, and the destination you will test. Keep the source of that decision with the sheet; do not infer it from a product's name or its presence in a gift box.
The distinction between the box parent and its components matters. Shopify's tax-override documentation says that an override on the bundle parent is ignored at checkout. Where a component override is appropriate, the individual component products belong in the override collection. Review existing settings with the person responsible for your taxes rather than changing them simply to make a test total match.
A useful sheet has these fields:
| Field | What to record |
|---|---|
| Candidate | Product, variant and stable Shopify variant reference |
| Expected treatment | Approved taxable, exempt or other applicable treatment, with its source |
| Shopify setting | Relevant product/category setting and override membership, if used |
| Test context | Destination, customer exemption state if applicable, currency and tax-included setting |
| Observed result | Order and component line references, allocated amount and actual tax |
Keep private customer details out of a shared worksheet. A destination category sufficient to reproduce the issue is more useful than copying an entire customer's address into a support note.
Test selections that exercise different treatments
Choose a small set of legal selections from your actual saved box rules. If all candidates have the same approved treatment, test a representative selection and a repeated variant. If treatments differ, include a mixed selection and selections concentrated in each treatment wherever the rules permit them.
For a fictional six-item box with a maximum of four per variant, two units of variant A plus four of variant B is a valid mixed selection. That example defines a selection, not a real-world tax classification. Record the saved box version so that a later assortment change cannot be mistaken for the tested offer.
Use the authorized test-order workflow, including the store's approved Shopify test payment method. Inspect the checkout before completing the test, and retain the resulting order for component review. An unpublished picker preview or the tnova sample cannot produce an order or validate taxes.
Start without a promotion. Add one intended, supported discount in a separate test only after the baseline is understood. Shopify's bundle documentation explains that a bundle discount is allocated to components and taxes are calculated on those components. Read the actual allocations; do not divide the box price equally among item units. The discount-code test guide covers targeting and combinations.
Compare Shopify lines with tnova's group tax
In Data and orders, use Read and reconcile order for the accessible recent test order, then open its detail page. Record Last checked, payment state and integrity state. Follow Open order in Shopify to inspect the corresponding component lines and tax details.
tnova's group view displays Original component amount, Allocated discount, After discount and Platform tax. Platform tax is the sum of Shopify's tax lines for the components belonging to that box group, in the recorded currency. It is not a rate selected by tnova and does not prove that the merchant's tax configuration is legally correct. Component integrity and payment confirmation answer different questions.
Here is a fictional tax-excluded order extract for one box. The amounts are assumed recorded Shopify values; they are not predicted allocations or recommended rates.
| Component line | Purchased units | Recorded amount after discount | Recorded tax |
|---|---|---|---|
| Variant A | 2 | 12.00 | 0.00 |
| Variant B | 4 | 18.00 | 1.80 |
| Box-group sum | 6 | 30.00 | 1.80 |
For this example, tnova's After discount should be 30.00 and Platform tax 1.80. The merchandise amount including the recorded tax is 31.80. This does not establish the whole order total: shipping, shipping tax, unrelated products and other order adjustments must be reviewed separately.
Preserve every component line reference. Shopify can represent a variant across more than one line; comparing only the first matching product title can miss part of the group. Keep other box groups and standalone purchases outside this sum.
Resolve tax-included amounts before comparing reports
Shopify's tax-included pricing guidance explains that included tax remains visible in order details even though it is already part of the price. Check the actual order's tax-included state instead of assuming that the separate tax label means an additional charge.
Suppose another fictional order records After discount of 30.00 and Platform tax of 2.10, with taxes included. Its recorded merchandise amount excluding tax is 27.90. Adding 2.10 to the 30.00 would count included tax again. These are illustrative recorded amounts, not a formula for calculating a mixed-rate checkout.
tnova's paid box-sales calculation subtracts the recorded component tax from the after-discount amount when the order has taxes included. For tax-excluded orders, it uses the after-discount amount without that subtraction. Shopify-marked test orders are excluded from summary sales totals, so use the order detail for this test rather than expecting a test purchase to appear as revenue. The CSV report guide explains the report's date and row meanings.
Keep a discrepancy actionable
If the values differ, save the order, box version, group and component line references, checked time, recorded currency, tax-included state and expected treatment. Separate a wrong expected classification from a missing component, a stale reconciliation or an order-wide tax amount that includes shipping.
Refresh an accessible recent order before comparing again. An Unknown amount or a warning that the current data is unconfirmed needs investigation; replacing it with zero hides the issue. Avoid changing live tax settings merely to remove a difference. Review Shopify configuration questions with the person responsible for your taxes, and send app reconciliation questions through a focused tnova support report.
About this guide: Prepared with AI assistance and checked against tnova's order reconciliation, order display and report calculation, plus the official Shopify sources linked here on October 15, 2026. Examples are fictional. This worksheet does not certify tax compliance or claim customer results.
See a gift box in action
Try the sample picker with fictional products. It creates no cart or order.
Try the box builder