Why does my free shipping threshold stop working during a sale?

The threshold is evaluated against a subtotal, and a discount changes which subtotal. Whether it applies before or after the discount decides whether the threshold is met.

Why the numbers break

3 patterns, and the order they usually arrive in.

Fix it in this order

5 steps, in the order they depend on each other.

  1. Determine which subtotal your threshold uses: pre-discount or post-discount. This is a configuration fact, not a guess — test it.
  2. Run a test order with a discount applied and watch the shipping line: at cart, at address entry, and at payment. Note where it changes.
  3. Decide deliberately which subtotal should govern a sale, then set it that way instead of leaving the default.
  4. If the intent is 'sales do not affect free shipping', evaluate on the pre-discount subtotal.
  5. Re-test at the exact threshold boundary and one currency unit below it — that is where the behaviour shows.

Confirm the fix

3 checks, each with a clear pass or fail.

The packaged version

the shipping-threshold and discount interaction checks behind this page are packaged as Cross-Border Automation Pack. No API key and no telemetry — it runs on Python's standard library, locally. Inside are 10 importable workflow files; the bundled self-test passes 10 of 10. One-time $37.05.

Quick answers

The 3 questions below cover the usual follow-ups.

Is this a bug?

No. It is a configuration choice you inherited. The default is one of the two options, and it may not be the one you want.

Why does it only happen during sales?

Because outside a sale the pre- and post-discount subtotals are the same, so the difference is invisible.

Can I have different rules per market?

Often yes, which is how a rule that works domestically surprises you internationally.

956231 Studio's rule-based checks and configuration behaviour; not legal advice. Updated 2026-10-23.