Skip to main content

Manual Tax Checkout Behavior

This page explains how manual tax affects the numbers a customer sees at checkout and the totals stored on the order.

It focuses on the merchant-facing behavior, not just the field names.

The Core Calculation Model​

Under manual tax, the system uses the store’s default tax settings rather than a jurisdiction-specific rule set.

The main decisions are:

  • whether the store’s prices are tax-inclusive or tax-exclusive
  • whether shipping is taxable
  • what default rate should be used

Inclusive vs Exclusive Pricing​

If Prices Are Inclusive​

When tax included in prices is enabled, the catalog price already contains the tax amount.

Operationally, that means:

  • the product price a customer sees is already the full taxed amount
  • checkout derives the tax portion from the line amount
  • the tax line is still useful for transparency and reporting, but it is not added on top of the price

This model is commonly used when merchants want “shelf price equals checkout price” for tax-bearing items.

If Prices Are Exclusive​

When tax included in prices is disabled, the catalog price is pre-tax.

Operationally, that means:

  • the subtotal is based on the untaxed item values
  • tax is calculated separately
  • the total increases when tax is added

This model is commonly used when merchants want to show the tax addition explicitly during checkout.

Shipping Treatment​

Shipping is governed by the apply tax to shipping setting.

  • If enabled, shipping participates in the taxable base.
  • If disabled, shipping remains outside the taxable amount in manual mode.

This is a store-wide behavior in manual tax. If shipping taxability needs to change by destination, the merchant should move to Advanced Tax Rules.

Discounts​

Discounts affect the base the tax is calculated against. The exact operational question is:

Is tax being calculated on the original price, or on the discounted amount?

In the tax engine and order flow, discounted amounts are taken into account before final totals are produced, so merchants should test discounted checkout scenarios whenever they change pricing or tax settings.

What the Customer Sees​

Under manual tax, the customer experience should remain legible:

  • the subtotal reflects the store’s base pricing model
  • shipping is shown separately when applicable
  • the tax line reflects the manual policy
  • the final total reflects whether tax is inside the price or added on top

The merchant’s job is not merely to save settings, but to validate that the numbers a customer sees align with the intended price communication model.

Good Validation Scenarios​

Every merchant should test at least these scenarios after changing manual tax:

  1. one product, no shipping
  2. one product plus shipping
  3. one discounted product
  4. multiple products with mixed quantities

If the merchant cannot explain the result of those scenarios confidently, the tax setup is not operationally ready yet.

When Manual Checkout Behavior Stops Being Enough​

Manual behavior becomes limiting when the merchant starts asking questions like:

  • “What if tax only applies in certain destinations?”
  • “What if digital items behave differently from physical items?”
  • “What if shipping is taxable in one place but not another?”

Those are not manual-tax questions anymore. They are advanced tax questions.

Keep manual tax if the checkout outcomes are stable and easy to explain.

Move to advanced tax only when the merchant needs:

  • destination-based collection
  • multiple active tax contexts
  • shipping rules by jurisdiction
  • product-level tax classification
  • simulator-driven pre-launch testing

Next Reading​