The Eight Patterns That Tell Me an Operation Needs Custom Shipping Logic | String
String

String — Operational Diagnostic

The eight patterns that tell me an operation needs custom shipping logic

Most warehouses don't suddenly become inefficient. They slowly accumulate operational complexity that is specific to how they actually ship.

I've spent years building custom operational automation for warehouses using ShipStation. Across millions of shipments, the same eight patterns appear over and over again. If four or more of them sound familiar, your shipping logic has probably become specific enough to need building rather than configuring.

Read the eight patterns

Paul Everton  · 

01 The premise

Every growing warehouse quietly becomes unique.

Not because someone planned it. Because reality stopped matching the assumptions built into generic software.

One customer needs frozen products packed differently in July than they do in January. Another has negotiated carrier rates that only become competitive above a certain weight. Another has one warehouse employee who just knows which orders shouldn't ship together.

None of those sound dramatic on their own. But together they slowly increase shipping costs, manual work, and operational complexity.

If four or more of the patterns below sound familiar, your shipping logic has probably become specific enough to need building rather than configuring.

02 Diagnostic

The eight patterns

Each one is written the same way: what happens, the symptom you'd actually notice on the floor, and the gap between what horizontal software assumes and what your operation really does.

None of them show up as a line item. They show up as labour, exceptions, and a shipping cost per order that drifts upward while volume grows.

01

Packing and rate selection are solved separately

Most shipping software decides what box to use first. Then it decides which shipping service to buy. The problem is that those two decisions affect each other.

Changing the package changes the shipping cost. Choosing a carrier's flat-rate packaging changes the best box. Negotiated carrier rates can make a different package the cheapest option.

If packing and rate selection happen independently, you're often leaving money on the table without realizing it.

The tell
Nearly identical orders regularly ship in different packaging or on different services without any obvious reason.
Horizontal software assumes
Packaging and carrier selection are independent decisions.
What actually happens
They're part of the same optimization problem.
02

Rate shopping stops at the easy orders

Modern shipping platforms have become very good at comparing carrier rates. For straightforward orders, they're excellent.

The expensive decisions are the exceptions. Orders where:

  • a slower service still arrives on the same day
  • negotiated discounts beat published rates
  • dimensional weight changes the winner
  • changing the package changes the cheapest carrier

Those situations require context that simple rate shopping often doesn't have.

The tell
Two similar shipments regularly leave on different carriers even though nothing obvious changed.
Horizontal software assumes
The cheapest visible rate is the correct answer.
What actually happens
The cheapest answer often depends on factors outside a single rate comparison.
03

You're paying to ship air

Carriers don't just charge based on weight. They also charge based on how much space a package occupies.

A slightly oversized box can dramatically increase the billable weight of a shipment, even if the products inside barely weigh anything.

Most warehouses don't intentionally choose oversized packaging. It simply becomes the default because nobody has enough time to evaluate every order individually.

The tell
Your shipping spend keeps increasing even though your products haven't changed much.
Horizontal software assumes
Any box that fits is good enough.
What actually happens
The wrong box quietly becomes a surcharge.
04

Multi-box orders are still human decisions

Eventually orders stop fitting neatly into one package. Now someone has to decide:

  • split into two boxes?
  • use one larger carton?
  • ship separately?
  • use carrier packaging?

Those aren't packing decisions. They're pricing decisions.

And they're often made in seconds by someone trying to keep orders moving.

The tell
Multi-package shipments seem consistently more expensive than expected.
Horizontal software assumes
People will make good packaging decisions.
What actually happens
People make fast decisions.
05

Your warehouse runs on more than one batching rule

Most systems batch orders using one or two attributes. Real warehouses rarely work that way.

Actual batching depends on combinations of:

  • shipping zones
  • carrier cutoffs
  • service levels
  • warehouse layout
  • pick path
  • order priority

When software only understands one rule, employees spend every morning rebuilding batches manually.

The tell
Someone's first task every day is reorganizing work that software already grouped.
Horizontal software assumes
One batching rule is enough.
What actually happens
Operations become multi-dimensional as they grow.
06

Perishable shipping changes with the weather

Cold-chain operations don't simply ship frozen products. They manage risk.

An order shipping to Arizona in July isn't the same shipment as Arizona in January. The packaging changes. The amount of coolant changes. Sometimes even the carrier changes.

Those decisions can't be made using static SKU rules.

The tell
Summer and winter use exactly the same packaging standards.
Horizontal software assumes
Every product ships the same way every day of the year.
What actually happens
The destination matters as much as the product.
07

Inventory decisions happen too late

Many warehouses release orders immediately. Only afterward do they discover inventory shortages.

The result isn't simply backorders. It's:

  • split shipments
  • manual intervention
  • customer service work
  • repicks
  • more shipping labels
  • more labour
The tell
Split shipments increase whenever popular products sell out.
Horizontal software assumes
Inventory is either available or unavailable.
What actually happens
Inventory decisions are often more nuanced than that.
08

The most important rule lives in one person's head

Every warehouse has them. The employee who knows:

  • which customers always need special handling
  • which SKUs should never ship together
  • which addresses require signatures
  • which orders always need an exception

That knowledge creates consistency. It also creates risk.

Eventually that person takes vacation. Or changes jobs.

The tell
Shipping quality noticeably changes depending on who's working.
Horizontal software assumes
Operational knowledge lives inside software.
What actually happens
It often lives inside people.

Recognise four or more? Then the question is which of them are running in your operation, and what they cost you.

03 Context

Complexity isn't failure.

None of these patterns mean your warehouse is poorly run. Quite the opposite. They usually appear because your business has grown.

You've added products. Carriers. Packaging options. Customers. Processes. Your shipping logic became specific to your business, and no off-the-shelf ruleset is written for one business.

That's a good problem to have. But it's still a problem worth understanding.

04 — What to do about it

What to do about it.

Twenty minutes on a call is how we find that out. You walk me through what your team still decides order by order, and I will tell you whether it is something I can build, something ShipStation can already do, or neither. If it is worth building, I build it and you run it free for 30 days on your real orders — and the 30 days do not start until it is working the way you described.

Book twenty minutes

Prefer email? paul@meetstring.com

Not sure it is even a String problem?

Several of these patterns turn out to be missing configuration rather than missing logic. I will review your ShipStation account against the twelve layers of its configuration, for nothing, and tell you which of the two you have.

Free configuration review →

Start here

Try it on your own orders before you decide anything.

Twenty minutes to tell me what your team decides by hand, a ShipStation API key, and I build it. You run it free for 30 days on your real orders, and the 30 days do not start until it is right. If it does not solve the problem, I will tell you.

Book twenty minutes
You speak with
Paul, who builds it
Cost
None
Free period
30 days, once it is right
Prefer email
paul@meetstring.com