The short answer: most of the easy wins in ShipStation are already built in — right carrier, right service level, automatic rate shopping. The savings people miss come from three places ShipStation’s native rules don’t fully cover: matching packaging to carrier flat-rate programs, right-sizing boxes against actual product dimensions, and adjusting for special handling (temperature, fragility) instead of defaulting to standard packaging for everything. Below is how each one works, and what it actually takes to fix it.
This is the biggest lever most ShipStation users don’t know they’re missing.
Carriers like USPS, FedEx, and UPS all offer flat-rate or cubic-rate programs — a fixed price if the order is packed into one of their specific box sizes, regardless of weight (within limits). These can be significantly cheaper than standard weight-based rates, but only if the order actually fits into one of those boxes.
Here’s the problem: packing and rate selection are usually treated as two separate steps. A box gets picked first, based on the item’s dimensions. Only after that’s decided does the system check shipping rates for whatever box got chosen. If a flat-rate box would have been cheaper, it never gets evaluated — the box was already locked in before the rate comparison happened.
What actually needs to happen: every order needs to be priced against your standard carrier rates and every eligible flat-rate option at the same time, with whichever comes out cheaper automatically selected.
“But I use Rate Shopper — doesn’t that cover it?” No, and the reason is architectural rather than a setting you’ve missed. Rate Shopper does check live rates, and it’s a genuinely good feature. But it compares services for a package you’ve already chosen. ShipStation’s own setup documentation makes this explicit: when you build a Rate Shopper automation rule, the rule that sets package dimensions must run before the Rate Shopper rule, so that orders generate a rate at all. The box is an input to rating. By the time any rate is fetched, the packing decision is already made — and if you packed into your own carton, the carrier’s flat-rate box was never eligible, whatever it would have cost.
You won’t see these misses. Rate Shopper reports a win every time, because it correctly found the cheapest service for the box you handed it. There’s no report line for the box you didn’t consider.
Why ShipStation can’t rate shop flat rate and standard rates together →
If you’re checking this manually today: a reasonable stopgap is auditing a sample of your recent orders by hand — pull the dimensions and weight, check them against your carriers’ current flat-rate box sizes and price breaks, and see how often you’d have qualified. Most operations are surprised by the percentage of orders that would have.
It’s tempting to assume the lowest advertised rate for a service level is always the right pick, but the number that actually hits your account depends on more than the base rate:
The real cost of an order only becomes clear once weight, dimensions, destination zone, and applicable surcharges are combined for that specific shipment — which means “cheapest” has to be evaluated per order, not assumed from a fixed service-level ranking. This is the same underlying issue as the flat-rate problem above: a decision that looks simple in isolation (pick the cheapest service) actually depends on variables that shift order to order.
Dimensional weight pricing means an oversized box costs you money even if the item inside is light. ShipStation can select from custom package presets you’ve set up, but the accuracy depends entirely on how well those presets match your actual product catalog — and most catalogs drift over time as SKUs get added, packaging changes, or new product lines launch.
The fix here is less about a single trick and more about discipline: keep your package presets current against your actual SKU dimensions, review them whenever you add new products, and periodically audit a sample of recent shipments to check whether the box selected was actually the smallest one that fit. This is manageable in-house for a stable, narrow catalog. It gets harder to keep current as SKU count and packaging variety grow.
Two categories of order regularly get shipped in standard packaging when they shouldn’t:
The reliable way to catch these is a rule that checks order contents (and, for temperature sensitivity, the forecasted temperature at the delivery address) before packaging is finalized, and automatically swaps in insulated packaging, ice packs, sturdier boxes, or a different carrier when the conditions call for it. Static “if SKU X, then use package Y” rules can cover the simplest cases. Where it gets harder is when the right answer depends on more than one variable at once — SKU and destination temperature and time of year, for example — which is closer to a small piece of custom logic than a single automation rule.
Most of the above is achievable inside ShipStation directly for straightforward cases — a narrow product catalog, one or two carriers, no perishables. It gets harder to maintain as complexity increases: more SKUs, more carriers, seasonal packaging needs, or products that need real-time data (like weather) factored into the decision.
At that point, most operations either accept the inefficiency, hire someone to review orders manually, or look at a dedicated logic layer that runs these checks automatically on every order. That’s the category String operates in — we build this kind of rate, packing, and carrier logic directly into an existing ShipStation setup, without requiring a migration to a full warehouse management system.
Is the cheapest advertised shipping rate always the actual cheapest option? Not necessarily. Dimensional weight thresholds, zone-based pricing, and surcharges can all shift the real cost of a specific order, so the cheapest choice varies order to order rather than being fixed by service level alone.
Does ShipStation automatically check flat-rate carrier programs against standard rates? No. ShipStation’s Rate Shopper compares services for a package that has already been selected — its documentation requires the package dimensions rule to run before the Rate Shopper rule. Since flat-rate programs require packing into the carrier’s specific box, eligibility is decided upstream of rating, and a flat-rate option you didn’t pack into can’t win on price.
How much can flat-rate optimization actually save? It varies by product mix and order profile — bulkier, lighter items relative to their flat-rate box size tend to see the largest savings, since weight-based pricing would otherwise scale with dimensional weight. The only reliable way to know your number is auditing a sample of recent orders against current flat-rate price breaks.
Can I build cold-chain logic with standard ShipStation automation rules? Basic version, yes — a simple rule like “if SKU is perishable, use insulated box” can be set up directly. It gets harder once the decision depends on more than one variable at once, such as destination temperature at time of shipping, which native automation rules aren’t built to evaluate dynamically.
Why does my rate shopper never pick a flat rate box? Almost always because an automation rule set your package or dimensions before the Rate Shopper rule ran. Once the package is your own carton, the carrier’s flat-rate program is excluded by definition, regardless of price.
Most ShipStation stores are — oversized boxes, rate programs that never get checked, and packaging that doesn't match what's actually being shipped.
String builds custom packing, rate, and shipping logic directly into your ShipStation setup, so every order ships at the real lowest cost without manual
review.
Book a free shipping audit
We'll show you exactly what's costing you, and whether String can fix it.
