A plain-language manifesto from the people who run our floors. How we onboard, integrate, price, and recover when something goes wrong. Read it before you call. The conversation will be sharper.
A program that hits OTIF on a calm Tuesday isn't impressive. The job is to hit OTIF on the Tuesday when a port closes, a supplier ships short, a forklift goes down, and a customer changes priority. We run programs so that the right thing happens because the system is built right — not because three people stayed late. Heroes are unscalable. Discipline is the moat.
OTIF, inventory accuracy, line-down hours avoided, dock-to-stock time, fill rate, exception resolution time. We pick three to five with the customer at scope, post them where everyone can see, and run weekly variance review. If we miss, we own it the same week. We don't manage to internal metrics. We manage to the metrics our customers' boards are watching.
Most 3PLs sell components. RK is the rare operator that runs global freight forwarding (Warehouse to World), the technology stack (Innovation Center), the physical facilities (16 across six states), and domestic capacity (Brokerage) under one operating discipline. That means one contract, one set of metrics, one escalation path, and zero finger-pointing across vendor seams when something goes wrong.
For dedicated programs we run open-book cost-plus. Our customers see the labor model, the capacity model, and the cost build. Procurement should never have to read between the lines. For per-unit programs the published rate sheet is the rate. For mission-critical programs we'll tie a portion of margin to the OTIF or inventory accuracy number we're committing to. There's only one model where the operator and the customer want the same thing — and that's the one we want to run.
The Inbound Control Tower wasn't built because exceptions are rare. It was built because exceptions are constant — late ocean carriers, supplier short-ships, weather, customs holds, missed scans, mis-picks. What separates a mission-critical operator from a 3PL is the exception loop: detection in seconds, named owner in minutes, root cause and counter-measure documented the same week. That loop is what you're paying for. Everything else is table stakes.
A million dollars an hour. That's the line-down number that drives most of our customers' decisions. We don't sell pallets, we sell the absence of that line-down hour. Every architectural decision — facility layout, staffing model, technology stack, escalation path — gets evaluated against one question: does this make the customer's production line more uninterruptible. If the answer is no, we don't ship the change.
A 14-page operating brief — the principles above, plus the full onboarding sequence, our integration playbook for ERP / WMS / TMS, our exception-handling protocol, and three anonymized case-study summaries. Sent to your inbox after a quick form.