Primo Brands’ First Post-Merger Factory Needs a Production-to-Delivery Ramp Scorecard

A new production line does not create customer-ready capacity the moment it starts running. Bottles still have to clear quality controls, enter inventory correctly, move through the warehouse, receive a dock appointment, and meet a truck with enough time left to deliver. During a factory launch, each handoff is learning at a different rate. Measuring only cases per hour can therefore make a ramp look healthy while finished goods accumulate behind it.

That is the operating challenge at Primo Brands’ new Mountain Valley facility in Hot Springs, Arkansas. The site brings production, storage, and shipping together, which creates an opportunity to manage the entire flow as one system. It also creates a risk: upstream output can overwhelm downstream execution before the constraints are visible. A production-to-delivery ramp scorecard should connect released volume to warehouse and transportation capacity before customer allocations grow.

The factory is significant, but nameplate capacity is not the baseline

Supply Chain Dive reports that the 200,000-square-foot plant is Primo Brands’ first new factory since the company’s 2024 merger with BlueTriton’s water brands. It contains logistics and warehouse space, a high-speed retail production line, and two large-format lines. The investment supports Mountain Valley spring and sparkling water as demand for premium beverages rises.

The commercial context makes disciplined execution especially important. Primo Brands recorded about $1.8 billion in sales in the quarter ended June 30, up 3.8% year over year, with growth attributed to premium brands and regional spring waters. Those figures explain the pressure to add output. They do not establish how much reliable volume the new site can ship during commissioning.

Nameplate speed is an engineering capability under defined conditions. Executable capacity is the lower volume that survives changeovers, startup loss, quality release, labor availability, storage limits, dock schedules, carrier commitments, and customer receiving windows. Planning from the first number while operating at the second creates avoidable expedites and missed promises.

Establish four linked baselines

The first weeks of operation should produce a baseline by line, SKU family, shift, and customer channel. Four measures expose where usable capacity is being lost.

First-pass yield is the share of output that passes production and quality checks without rework, hold, or scrap. Report both gross cases produced and cases released. If the line makes 10,000 cases but only 9,200 become shippable on time, transportation should plan against 9,200—not the larger headline number.

Finished-goods dwell measures time from production completion to outbound loading. Split that clock into quality hold, system receipt, putaway, allocation, staging, and dock wait. A rising average can hide a serious tail, so operators should also track the 90th percentile and the oldest pallet awaiting movement.

Dock turns show whether doors, labor, yard space, and appointments can convert inventory into dispatched loads. Measure planned versus actual arrival, loading duration, departure time, and door idle time. A door is not productive merely because a trailer occupies it.

Order fill and delivery performance connect the launch to the customer. Track cases shipped in full, on-time departure, on-time delivery, short shipment, damage, and rejection by customer and lane. Inbound Logistics’ capacity-planning guidance emphasizes matching facilities, people, and other resources to demand while identifying bottlenecks. That principle matters here because production, warehouse, and transportation capacity must become available together.

Gate allocations on commissioning evidence

Commercial allocations should advance through explicit ramp gates rather than jump to the line’s theoretical ceiling. A practical sequence might begin with controlled production runs and internal transfers, progress to predictable regional customers, and add longer or more appointment-sensitive lanes only after stable performance.

Each gate needs an owner, a review window, and thresholds. For example, release the next tranche of demand only after first-pass yield, inventory-record accuracy, dwell, dock cycle time, tender acceptance, and on-time delivery remain within target for several consecutive operating days. A single strong shift is encouraging; it is not proof of repeatable capacity.

Carrier planning should follow the same milestones. Procurement can reserve core capacity before launch, but committed pickup volume should rise with released product and demonstrated dock throughput. For each lane, record primary and backup carriers, equipment requirements, lead time, daily pickup ceiling, weekend coverage, and customer appointment rules. This prevents planners from treating a carrier’s broad verbal assurance as guaranteed capacity for every day and destination.

The allocation rule should use the tightest constraint. If production can release 24 loads, the warehouse can stage 21, dock schedules support 19, and confirmed transportation covers 17, the executable plan is 17 loads. The other seven are opportunities to remove constraints, not customer orders ready to promise.

Put exceptions beside the score, not in email

A launch dashboard should show daily actuals, target ranges, trends, and an owner for every miss. It should also preserve the reason behind exceptions. Common codes might include quality hold, label or packaging shortage, changeover loss, inventory interface failure, labor gap, late carrier, missed appointment, trailer rejection, or customer reschedule.

That detail distinguishes a recurring structural constraint from random launch noise. Three late departures caused by missing labels require a different response from three caused by carriers arriving outside their slots. Operators should review the scorecard in one cross-functional meeting with production, quality, warehouse, transportation, customer service, and sales rather than reconcile separate versions afterward.

The scorecard also needs a forward view. Pair actual performance with the next seven to fourteen days of planned production, orders, appointments, and contracted trucks. Flag any date on which released supply, warehouse labor, door hours, or confirmed transport falls below demand. This turns the tool from a launch report into a decision mechanism.

Connect the ramp in CXTMS

CXTMS can translate approved production releases into shipment demand, match that demand with lane-level carrier capacity, manage dock and delivery milestones, and surface exceptions before a customer commitment fails. The critical design choice is to preserve the link among production batch, inventory release, order, load, carrier, appointment, and proof of delivery.

Primo Brands’ new facility should ultimately be judged by reliable service, not the fastest isolated production run. When every increase in output is supported by warehouse flow and executable transportation, the ramp can grow without turning success on the line into congestion at the dock.

Ready to connect production plans with real delivery capacity? Request a CXTMS demo and build a shipment-level ramp scorecard for your network.