Rush Orders in WES: Configuring Priority Lanes Without Killing Normal Waves

We had a client, a cross-border beauty brand running out of a warehouse in Ontario, California. On the morning of Black Friday 2024, a viral TikTok mention drove 40,000 orders in two hours — all of them needing to ship the same day. The warehouse already had six normal waves scheduled and a full dock calendar. That day taught me more about WES rush order priority lane configuration than a decade of RFPs ever did.

Here is how we fought the fire: the ops supervisor walked the pick aisles with a two-way radio, pulling pickers off half the waves to chase the rush orders. The rush orders shipped, sure. But on-time performance on the normal waves dropped from 98% to 81%, and the next morning two long-standing clients called my cell directly. The client's ops director said something I still remember word for word: "We accept rush orders. What we don't accept is you sacrificing our normal freight to someone else's rush."

I have been selling 3PL contracts for years, and I have watched too many warehouses turn rush orders into a money-losing exercise. So let me lay this one out properly — how a priority lane should actually be configured in the WES, and how rush terms should be written into the contract. Because a well-configured system with a sloppy contract still leaves the 3PL doing the work for free.

Why Most Warehouses Lose Money on Rush Orders

Let me show you the math that only the 3PL side ever bothers to do. A typical "brute-force expedite" goes like this: the supervisor halts the current wave, pickers drop what they are doing to pick the rush, then they come back — and first they have to figure out where they left off. That round trip alone knocks 20 to 30 percent off the normal wave's labor productivity. The expensive part is on the other side of the ledger: delayed normal waves mean SLA penalties, customer complaints, and a weaker position at renewal. None of that gets booked against "rush." It all gets booked against "your warehouse is unreliable."

And the rush side? In plenty of contracts the rush fee is symbolic — sometimes it is even "included in the base rate," which is another way of telling the client that rushing is free. The worst case I ever saw: rush orders hit 40 percent of total volume during peak, the warehouse fought fires every single day, and at month-end the rush fee revenue didn't even cover the SLA penalties on the normal waves.

So here is my counterintuitive take: the real value of a priority lane is not speed — it is predictability. No client actually needs "infinitely fast." What they need is "ships when you said it would ship, without dragging my normal freight down with it." A predictable priority lane can be priced as a line item and used as leverage at renewal. A rush process that runs on shouting only produces exhausted operators.

The Three Parts of a WES Rush Order Priority Lane Configuration

The second story is even more instructive. An auto parts client, warehouse in Michigan, had a "rush orders ship within 4 hours" SLA written into the contract — the salesperson agreed to it without blinking, because that's what it takes to win the signature. Then peak season hit, rush orders climbed to 35 percent of volume, everything in the WES got tagged "rush," the priority lane was bumper to bumper, and the normal waves had nobody left to run them. The ops manager told me: "In our WES, the word 'rush' doesn't mean anything anymore."

That is the first insider lesson: priority that everyone has is priority that no one has. So the first job of any WES rush order priority lane configuration is not "make rush faster" — it is "make rush rarer, more expensive, and harder to get."

The model we ended up deploying for clients is a three-tier system. The names are boring. They work.

P0 is the life-or-death tier — line-down situations, viral-order explosions, the kind where a single missed order costs real money. The WES fires a standalone micro-wave: dedicated labor, dedicated picking, zero contact with the normal waves. Monthly P0 quota is hard-capped. Over the cap, you wait. This tier protects the warehouse's lifeblood.

P1 is the rush tier — must ship today. It can slot ahead of the current wave, but only ahead of tasks that have not yet been released to pickers' handhelds. Anything already in a picker's hands is untouchable. That is the iron rule. Snatching in-progress picks means wasted travel, and productivity and morale collapse together.

P2 is the priority tier — next-day delivery and the like. No cutting in line at all; it only moves the order forward in the queue for the next wave. You stand a few spots closer to the front. Nobody currently working is affected.

Around those three tiers sit three gates, and all three are non-negotiable. First, a daily rush quota: P0 plus P1 cannot exceed a fixed share of the day's total order volume, with the share measured against the warehouse's actual capacity and written into both the system and the contract. Second, automatic tiering: order priority is assigned by the WES from attributes like client tier, SLA deadline, and sales channel — never by human judgment. Manual tiering is just a back door, and sales and ops will argue until midnight over whether an order "counts" as rush. Third, a wave freeze rule: once a wave is released, its tasks are locked. Rush orders can only draw from reserved capacity or a dedicated labor pool, never by pulling people off normal waves.

Those three gates answer one trade-off: the more flexible rush is, the less predictable normal waves become. You cannot have both. My advice never changes: protect normal-wave on-time performance first, then talk about rush speed. Normal waves are the base business; rush is the upside. Betting the base on the upside is a debt the 3PL always ends up repaying.

Writing Rush Terms Into the Contract: Three Things Your 3PL Won't Volunteer

A configured system with a badly written contract is a wasted configuration. Three things 3PL salespeople — myself included — would rather you not look at too closely:

First, the rush fee must be a separate per-order line item, never bundled into the base rate. Bundle it and you have just told the client that rushing is free — come peak, they will tag 40 percent of their orders as rush. A fixed per-order price is the first gate, and it is priced in dollars, not in good intentions.

Second, write the rush SLA separately from the normal SLA, with hard trigger conditions. What counts as a rush order? Order cutoff time, SKU must be in stock, order-size cap — all three, no exceptions. Leave the conditions vague and sales will promise anything to win the signature, while ops takes the blame.

Third, a monthly rush quota with overage escalation. The first 200 rush orders a month at the standard rush fee; beyond that, the price steps up. This clause protects the 3PL, and paradoxically it protects the client too: it forces them to decide before peak which orders are truly worth rushing, instead of treating rush as an all-you-can-eat buffet.

Next time you negotiate a contract, ask these three questions:

One: "In your WES, are rush orders tiered automatically, or does someone just shout?" — A warehouse that runs rush on shouting will fall apart the moment rush volume spikes, and your normal freight pays for the collapse.

Two: "When a rush order interrupts a normal wave, how is the SLA counted — and is that in the contract?" — If it is not written down, you are absorbing a penalty that belongs to the 3PL.

Three: "How is the rush fee charged — and is there a monthly quota with overage terms?" — A contract with no quota is an open door to unlimited rush, and the bill always lands on your own on-time rate.

Get clear answers to those three, and the priority lane is genuinely green. Don't, and even the most expensive WES is just decoration.

By Susan, 3PL Sales Director