Fulfillment breaks quietly, then all at once.
The Warehouse Is Usually Not the Root Cause
When a founder calls about fulfillment, the first complaint is almost always visible. Late orders. Rising freight costs. Angry customers. Inventory that exists in the system but not on the shelf. A team that feels busy all day and still cannot catch up.
The warehouse gets blamed because the warehouse is where the pain shows up. In my experience, the real problem usually started much earlier. Sales promised a lead time that operations never signed off on. Purchasing chased unit cost and ignored case pack complexity. Product added variants without asking how many pick faces existed. Finance looked at gross margin but not rework, expedited freight, or replacement orders.
In the first 90 days, I do not start by reorganizing racks or changing carriers. I start by mapping the promise. What did the customer buy? When was it promised? What had to be true for that promise to be kept? Where did reality diverge from the plan?
That exercise is uncomfortable because it turns fulfillment from a department problem into a company operating system problem. That is exactly the point.
Days 1 To 30 Are For Truth, Not Solutions
The first month is about establishing facts the business can trust. I want the unvarnished version of order flow, not the slide deck version.
I look at five numbers immediately: on-time shipment, order accuracy, inventory accuracy, backorder rate, and freight as a percentage of net sales. Then I cut those numbers by customer, SKU, channel, order type, and location. Aggregate metrics hide the fire. The average on-time rate might look acceptable while one national account is getting crushed every Friday because replenishment orders drop too late for the current labor plan.
I also spend time on the floor. Not for theater. The floor shows what the dashboard misses. I watch how many times a picker stops to ask a question. I look for handwritten notes taped to monitors. I ask how often the system is wrong and how the team works around it. Workarounds are unpaid consultants. They show where process failed and where experienced people are keeping the business alive.
By day 30, I want a short operating diagnosis. Not a 40-page report. I want to know the handful of constraints that actually matter. Usually it is some combination of poor item master data, uncontrolled SKU growth, inaccurate inventory, weak labor planning, unclear customer rules, and no owner for the full order-to-cash handoff.
Days 31 To 60 Are For Stabilizing The Promise
The second month is where discipline starts. The temptation is to fix everything. That is how companies create more noise.
I focus on stabilizing the customer promise first. If the business cannot ship every order fast, it must at least be honest about what it can ship and when. That means tightening cutoffs, freezing certain exception paths, and creating a daily rhythm around constraints.
In one founder-led consumer products business, the team was missing shipments because every large customer had a different routing guide, labeling requirement, appointment process, and chargeback exposure. The warehouse team was being asked to remember tribal knowledge under pressure. I moved ownership of customer compliance out of memory and into a controlled operating process. The result was not glamorous. Fewer mistakes. Fewer credits. Less panic. Better cash.
This is also when I separate demand issues from fulfillment issues. A warehouse cannot solve a forecast that changes three times a week. A purchasing team cannot solve a sales team that keeps pushing custom bundles into standard flow. Stabilization requires a tighter weekly operating meeting where sales, operations, purchasing, finance, and customer service look at the same demand and constraint picture.
The question is simple: what promises can the business keep this week, and what needs an explicit decision?
Days 61 To 90 Are For Installing The System
By the third month, the goal is to stop heroics from being the operating model.
I look for repeatable mechanisms. Daily order review. Weekly inventory accuracy checks. A clean escalation path for exceptions. Clear ownership for customer-specific requirements. A SKU governance process that prevents complexity from sneaking in under the label of growth.
I also want financial visibility attached to operational behavior. Late shipments are not just service problems. They create expedited freight, chargebacks, credits, extra labor, and customer service burden. If those costs sit in separate accounts and nobody connects them to root cause, the business will keep making bad tradeoffs.
One of the fastest improvements I have seen came from changing the way a company reviewed freight. The team had negotiated decent rates, but orders were being split because inventory was spread poorly across locations. Freight was not the carrier's fault. It was a network and planning problem. Once the team saw cost by order pattern instead of cost by invoice, the fix became obvious.
At the end of 90 days, fulfillment should not be perfect. It should be visible, governed, and improving on purpose. The founder should know which constraints are operational, which are commercial, and which require investment. The leadership team should stop debating anecdotes and start managing facts.
Fulfillment is not fixed by asking people to move faster; it is fixed by building a business that stops making promises its operating system cannot keep.