Skip to main content

POS Tax

Tax configuration uses organization defaults with location overrides where configured. Open Tax Configs from the organization's Operator Shortcuts and confirm the affected location before investigating a total.

What Gateway calculates​

  • Tax is destination-based. A store or origin address does not switch it into origin-based calculation.
  • Special-purpose district (SPD) configuration is supported.
  • Negative rates are rejected. Discounts, credits, and promotions are not negative tax rows.
  • Rates use basis points: 100 is 1%, and 825 is 8.25%. The smallest supported increment is 0.01%.
  • Categories are descriptive free text, not a shared validated taxonomy. Check spelling and agreement between systems rather than assuming a category was centrally verified.
  • The stacked manual provider currently calculates percentage rules on retail_price only. If a matching rule wins scope/priority resolution but uses an unsupported basis, fixed amount, or malformed rate, calculation fails rather than silently dropping that rule and quoting zero or a lower fallback rate. In live configuration, inactive, expired, nonmatching, and shadowed rules do not prevent other sales from being calculated. Explicit calculation snapshots still validate every supplied rule before use.
  • Effective windows are exact: start is inclusive and end is exclusive, including transitions within a minute. Live configuration caches load every rule whose window intersects the cache bucket; the provider then checks each transaction's exact timestamp. Caching does not delay a scheduled activation or replacement to the next minute. Frozen calculation snapshots retain their own rules.
  • Storing a fixed-rate configuration is not nicotine-excise support. Do not replace an unsupported excise rule with ordinary sales tax or fold it into the product price. Escalate to the product/tax owner for the required taxable event, exemption interaction, measured basis, receipt, and return policy before activating an excise workflow.

Non-US limitation​

The current manual calculation path is US-only. A non-US address returns zero tax rather than calling an international engine. That zero is not an authoritative tax determination or a statement that no tax is owed. Escalate markets needing non-US calculation to the responsible product/tax owner before relying on the result.

Investigating a discrepancy​

Confirm organization, location override, destination, category, taxable amount, and configured rate. Do not promise origin-based sourcing, authoritative international tax, or automatic category normalization. Keep customer addresses and other personal information in approved support systems only.

See the Management Portal for organization selection and access.