Munchkin Names Its First Chief Supply Chain Officer: Define the Role by Decisions, Not Org Charts

Creating a chief supply chain officer role signals that supply chain has become an enterprise concern. It does not, by itself, change a single purchasing decision, inventory target, production sequence, or carrier assignment.

Munchkin now has that opportunity. The baby products company appointed Kunal Thakkar as its first chief supply chain officer, with responsibility for global operations, supply chain, compliance, costing and sourcing, demand planning and analytics, order management, and program management. According to Supply Chain Dive, the company created the position as omnichannel selling requirements continue to evolve.

Thakkar brings more than 20 years of industry experience. In a previous CSCO role, he managed more than $100 million in spend across sourcing, warehousing, transportation, and inventory, while leading a nearly 50% inventory reduction over 18 months. Those figures matter because they show what executive ownership can connect: cash, service, capacity, and execution.

The first test for any new CSCO is therefore not the organization chart. It is whether the company can make better cross-functional decisions, faster, with explicit accountability.

Assign rights to the decisions that create tradeoffs

Supply chain decisions rarely stay inside one function. A sourcing change can reduce unit cost but extend lead time. A higher inventory target can protect availability but consume cash. A premium freight move can save a customer order while destroying its margin.

The new operating model should identify who recommends, approves, executes, and is consulted for each recurring tradeoff.

Sourcing: Procurement can lead supplier selection and commercial negotiation, while the CSCO approves choices that materially change lead time, geographic concentration, compliance exposure, or continuity risk. Finance validates total landed cost rather than purchase price alone.

Inventory: Demand planning recommends targets by item and channel. Sales supplies promotion and customer intelligence, finance sets working-capital boundaries, and the CSCO owns the final service-versus-cash policy. Exceptions should expire; otherwise temporary buffers quietly become permanent inventory.

Manufacturing: Operations controls daily sequencing within agreed capacity and service rules. The CSCO decides when a shortage, quality issue, or demand shift warrants reallocating supply across products, channels, or customers.

Transportation: Logistics chooses carriers and modes inside approved routing guides. The CSCO owns policies for premium freight, constrained-capacity allocation, and systemic service recovery. Individual expedites can stay operational; repeated expedites require executive review.

Customer service: Commercial teams define customer commitments, but operations must validate whether the network can fulfill them. When supply is constrained, a documented allocation rule should replace whoever escalates loudest.

A one-page decision register is more useful than a complex responsibility matrix. For every important decision, record the trigger, accountable owner, required inputs, approval threshold, deadline, and escalation path.

Build a 90-day operating baseline

A first CSCO inherits metrics built by separate teams, often with different definitions. The initial 90 days should produce one baseline across four outcomes.

Start with availability: order fill rate, on-time-in-full performance, backorders, substitutions, and lost sales by product and channel. Average service can conceal important failures, so segment the data by customer, item family, and promised service level.

Next measure working capital: inventory value, days of supply, excess and obsolete stock, purchase commitments, and cash-to-cash cycle. Thakkar's previous nearly 50% inventory reduction is a useful reminder that aggregate inventory is not the only target. The goal is to remove stock that does not protect profitable demand while avoiding shortages in critical products.

Then establish lead time from supplier release through customer delivery. Separate planned time from queue time, transport time, inspections, handoffs, and holds. Averages are insufficient; track variability and the late tail that forces buffers and expedites.

Finally, audit exception ownership. Sample late orders, stockouts, supplier misses, premium shipments, and compliance holds. For each one, determine when it became visible, who received the alert, who had authority to act, and how long resolution took.

The baseline should not become a 50-metric dashboard. Select a small executive scorecard, preserve diagnostic detail underneath, and document every definition. Gartner reported in 2026 that 55% of CSCOs were unclear about the return on AI investments even though 67% of supply chain digital investment was allocated to AI. That gap reinforces a broader lesson: investment is not value until operating outcomes and ownership are measurable.

Run a weekly decision cadence

The CSCO needs a forum that makes decisions, not another reporting meeting. A weekly control-tower review should focus on deviations that cross functions or exceed established thresholds.

Each item should arrive with the affected orders or products, financial and service exposure, available options, recommended action, owner, and decision deadline. Close the meeting by recording the choice and the assumption behind it. At the next review, compare the expected and actual result.

Reserve executive attention for issues such as supplier concentration, inventory allocation, capacity constraints, major expedites, and customer commitments. Routine shipment exceptions belong with operations teams unless their frequency or cost breaches a threshold.

This model is consistent with a broader leadership trend. McCain Foods recently appointed a chief manufacturing and operations officer whose scope includes manufacturing, supply chain, engineering, quality, procurement, and operations. Supply Chain Dive reported that the executive joined after nearly two decades at PepsiCo. The title differs, but the intent is similar: integrate decisions that fragmented functions cannot optimize alone.

Give the CSCO shared transportation truth

Transportation data reveals whether plans survive contact with execution. Yet many leadership teams still reconcile carrier portals, spreadsheets, warehouse messages, customer emails, and finance records after a failure has already spread.

A shared TMS record should connect the purchase or customer order to the planned route, tender response, appointment, shipment milestones, delivery outcome, accessorial charges, and exception owner. That lets the CSCO distinguish isolated carrier failure from a recurring sourcing, inventory, manufacturing, or promise-date problem.

The practical payoff is faster governance. Premium freight can be tied to its root cause. Supplier lead-time assumptions can be compared with actual inbound performance. Customer commitments can reflect available capacity. Inventory policies can account for transit variability by lane rather than relying on broad buffers.

For Munchkin, the new role spans enough functions to create genuine enterprise ownership. Success will come when those functions share decision rules and execution evidence—not merely a common executive.

Request a CXTMS demo to see how shared shipment data, exception ownership, and lane-level performance can turn supply chain governance into faster operational decisions.