Why does my shipping rate drop when I add a second item?
A rate that gets cheaper when the cart grows is almost always dimensional weight crossing a band boundary — not a pricing bug and not a discount.
Why the numbers break
3 patterns, in the order a buyer meets them.
- Dimensional weight takes over once a variant has dimensions set. Two units do not weigh twice as much in billable terms by default — they occupy a different box.
- Rate bands are ranges, not curves. A parcel that lands just inside a cheaper band can genuinely cost less to ship than the single-item parcel that fell into an expensive band.
- Carrier-calculated rates compete with your custom rates by priority. When the second item changes the band, a different rate wins, and the winner is not necessarily the one you expected.
Fix it in this order
The 5 steps below, sequenced.
- Print the cart's billable weight for one unit and for two: actual weight versus dimensional weight, side by side. The larger of the two is what the carrier charges on.
- List your rate bands and check both numbers against the boundaries. In most cases the two-unit parcel sits closer to a boundary than you assumed.
- Compare rate priority: if a flat custom rate and a carrier rate both match the new band, confirm which one has the lower priority number. That is the one that wins.
- If you intend volume to be cheaper, create an explicit tier for it — a rate that applies from quantity two upward — rather than relying on band arithmetic to produce the effect.
- Re-test with a real draft order at quantity one, two and three, and record the billable weight each time. The pattern will be obvious once the numbers are side by side.
Confirm the fix
3 checks to run after the change.
- You can state, for your own product, which of actual weight or dimensional weight is the charging basis.
- You know the exact band boundary your two-unit parcel crosses, and can name the quantity where it happens.
- A test order at quantity two returns the rate you intended, at the priority you set.
The packaged version
the rate and band configuration this page walks through is packaged as Cross-Border Automation Pack. Standard-library Python, run locally; no API key, no telemetry. Inside are 10 importable workflow files; the bundled self-test passes 10 of 10. One-time $37.05.
Quick answers
The 3 questions below, answered.
Is this a Shopify bug?
No. It is band arithmetic plus dimensional weight, both working as designed. The configuration is what produces the surprising result.
Can I just disable dimensional weight?
Only by removing dimensions from the variant, which then makes every other calculated rate less accurate. Setting an explicit volume tier is usually the cleaner fix.
Does this affect international rates more?
It is more visible there, because international bands are coarser and a boundary crossing moves the price further.
956231 Studio, from rule-based checks and configuration behaviour — not legal advice. Updated 2026-10-23.