Q4 planning · Modelled on the 2025–26 published schedule
What peak season actually costs you.
Everyone publishes the rate table. This gives you the number that matters: what demand surcharges add to your Q4 bill, where it lands, and which single change removes the most of it.
Your peak volume
Your busy-season weekly volume, not your annual average.
Remaining 10% assumed commercial ground, which carries no per-service demand charge.
Read these off a recent invoice. They aren't inferred from dimensions — the trigger thresholds aren't published in a form we can verify, and guessing them would give you a confidently wrong number.
Exposure
Added to your Q4 bill by demand surcharges
—
—
Your biggest single lever
—
When it lands
How this is calculated
No black box. Every figure comes from UPS's published demand surcharge schedule, and the arithmetic is weekly volume multiplied by the applicable rate across each demand period.
Common questions
Why is Additional Handling usually the biggest line?
Because it's the collision of a mid-sized rate and a non-trivial share of parcels. Large Package and Over Maximum cost far more each, but hit fewer packages. Additional Handling at 6% of a few hundred parcels a week, across sixteen weeks, adds up faster than a handful of oversized items.
Can I avoid these by shipping earlier?
Partly. The size and handling demand charges applied from late September, so early shipping doesn't escape them — but the peak block from 23 November to 27 December carried the highest rates. Pulling volume forward out of that five-week window is where the saving is.
Are these negotiable?
On high-volume contracts, sometimes — caps and waivers more often than removal. Size-based charges are the hardest to get waived, which is why reducing packaging is usually more reliable than negotiating.
Why doesn't this detect surcharges from my box dimensions?
Because the trigger thresholds change and we couldn't confirm the current ones from a carrier-published rate guide. Inferring them from third-party summaries would produce a precise-looking number built on an unverified assumption. Your invoice already knows the answer, so this asks you instead.