Rules made fulfilment faster and, at the same time, removed the human check that used to notice when an order never actually shipped.
Anonymized to protect customer confidentiality
Direct-to-consumer apparel company
Outcome
Average label cost
$10.74 → $7.88
Saved per shipment
$2.86
Monthly saving, as reported
~$15,000
Also covers · Rate Selection
An apparel company selling exclusively through its own direct-to-consumer site, shipping internationally from a single warehouse, on ShipStation.
Apparel has a forgiving parcel profile — light, compressible, rarely fragile — which means the cost pressure sits in service selection rather than in packaging.
As the operation grew, the fulfilment team became overloaded and adopted ShipStation automation rules to keep up: a pre-determined service by SLA category, then labels printed in bulk.
That produced two problems, and they are worth separating because only one of them is about cost.
The first was service selection. The rules chose from the options the team had reasoned about when the rules were written, which meant systematically paying more than necessary on orders that would have met their delivery commitment on a cheaper service.
The second was subtler and more expensive in ways that never appear on a shipping invoice. Printing in bulk removed the point at which a person previously looked at each order — and with it, the informal check that noticed when something had not actually gone out. Orders went missing inside the process. The team learned about problems when customers reported them, which is to say after the customer was already unhappy.
The rules engine handled the standard path correctly and did exactly what it was adopted to do: it made a fast operation out of a slow one, and the SLA categories it applied were reasoned rather than arbitrary.
The service-selection gap is the familiar one — a static rule cannot price the alternatives, so it cannot know when a cheaper qualifying service exists.
The second gap is more instructive. Automation replaces a manual step, and a manual step often carries a check that nobody wrote down. Here, the act of handling orders individually was also, incidentally, how stuck orders were caught. Automating the task removed the by-product, and nothing in the platform replaced it, because nothing in the platform knew it existed.
This is not a criticism of the software. It is a general property of automating a process: you inherit responsibility for the incidental checks the manual version was performing for free.
Two separate pieces of logic were required, because these are two different problems that happened to share a cause:
The connection between the two is the reason they are in the same review. Bulk automation is what made the operation fast enough to compete and what removed the human check that made it safe. Restoring the check explicitly — rather than reverting to manual handling — is what let the operation keep both.
Average label cost fell from $10.74 under the previous rules to $7.88, a saving of $2.86 on every shipment. The team reported approximately $15,000 a month.
The exception reporting changed the shape of the CX workload rather than just its volume. The team moved from responding to complaints about orders that had already gone wrong to resolving issues before the customer noticed — the same problems, addressed at a point where they are still fixable.
The team also reported less time spent preparing fulfilment tickets, which is the sort of second-order saving that rarely gets counted and is often larger than it looks.
"Before String, we often became aware of shipment issues only when customers reported them, which negatively affected our reputation for customer service. The unshipped order reports have significantly improved our operational efficiency by helping us minimize errors and quickly address issues with carriers."
What another operator can take from this review, whether or not their operation looks anything like this one.
When you automate a manual step, audit what that step was checking incidentally. The informal checks are the ones nobody documents and everybody relies on.
Cheapest and on-time are one constraint, not two. Evaluate the services that meet the commitment, then price them — the reverse order produces either overspend or late deliveries.
Rate comparison is only as good as the accounts it covers. Partial coverage produces a confident answer to the wrong question.
Exception detection is worth measuring in CX time and repeat purchase, not in postage. It will not show up on a shipping invoice and is frequently the larger number.
Other operational reviews
Cartonization
4 min
A packing process that depended on the judgement of whoever reviewed orders that day. The judgement was good. The dependency was the problem.
Rate Selection
4 min
The team knew their rules were mis-allocating orders when they built them. They built them anyway, because the alternative did not scale.
Rate Selection
3 min
A carrier relationship that solved a real reliability problem, then kept being applied to orders it was no longer the right answer for.
Start here
A short conversation, an export of your order data, and a String Operational Review you keep — along with an honest answer about whether String can meaningfully improve your fulfillment operation. If it can't, we'll tell you. That answer requires a detailed review by us and could save you a year of building the wrong solution.
