Supply Chain, Procurement and Sales Operations Case Studies
Professional5 Case StudiesUpdated Sep 2026
These five case studies come from the day-to-day work of a regional distribution business, a fabrication plant, a health supply account, a sales operations group, and a procurement office that shares buyers with two other sites. Each one begins with a problem that looks simple in a status meeting and turns out to involve roles, service levels, workflow data, stakeholder expectations, and delivery targets pulling in different directions. The analysis moves from what the teams could see to what the data showed, then to the choices leaders made and what followed.
Case Study 1
Order desk misses targets as roles blur
Cedar Lane Distribution, a regional supplier of electrical and plumbing parts with three warehouses and about 2,400 active trade accounts
The situation
Cedar Lane's inbound order desk handles roughly 1,100 customer orders a week for contractors across three states. The service level set by the operations director is confirmation within four business hours for any order received before noon, with a target of 95 percent met each month. In the second quarter the desk hit that target only in two of the last six months. Account managers were quietly handling pricing exceptions and rush shipments by phone, so some orders were keyed twice, once by the desk and once by the account manager. Nobody owned the exception queue, and the desk lead, Priya, reported that her team spent most mornings chasing approvals instead of confirming orders.
The challenge
The operations director, Tomas, wanted the team to meet the four-hour standard without adding headcount. Sales leadership saw the problem as a desk performance issue, and the desk saw it as a sales issue. Both groups were right about their own piece. The task was to find where accountability actually broke down, define who owned each step, and build a plan the team could run without heroics.
Analysis
Teams grounded in Supply Chain, Procurement and Sales Operations usually start with the workflow log before they talk to anyone. Cedar Lane's order system timestamped every touch, and the log showed that 38 percent of exception orders passed through three or more hands before confirmation. The desk's own time stamps were accurate. The gap came from the handoff between intake and account management, where nobody was named as the owner of a held order. The service level was written for the desk alone, so the desk carried the clock for steps it could not control. Roles on paper said the desk confirms and the account manager approves, yet the approval had no deadline.
Stakeholder expectations had drifted apart. Contractors expected a same-day answer on rush orders, the sales group expected account managers to protect margin on special pricing, and the operations director expected a clean queue at the start of each shift. None of those targets was wrong, but they were measured in different units. Once the team split the 95 percent target into two measures, one for desk confirmations and one for approval turnaround within two business hours, the problem became visible on a single board. Accountability followed the measures, not the org chart.
- Week oneLogs traced every held order to a named owner.
- Week threeTarget split into two measurable service levels.
- Week fiveAccount managers committed to two-hour approval turnaround.
- End of quarterConfirmation rate cleared target in five of six months.
Actions taken
- Name one owner for every held order and record that owner in the order system before the order leaves intake. The desk lead, Priya, will run the exception queue each morning.
- Split the service level into two measures, desk confirmation within four business hours and approval turnaround within two, and publish both on the shared board by the start of the next month.
- Write a one-page decision rule for special pricing so account managers approve within two hours or escalate to Tomas before the end of the same business day.
- Hold a fifteen-minute review each Friday where the desk and account managers read the exception log together and agree on one change to the process before the following week.
Results
Within six months the desk confirmed 96 percent of orders inside the four-hour window, up from 71 percent at the start of the effort. Average approval turnaround fell from about one business day to under two hours on the measured accounts. The number of orders keyed twice dropped by roughly three quarters, which freed Priya's team from most of the morning backlog. Tomas reported that two account managers had asked for a second exception review, a sign the owner rule was working rather than being resented. Headcount stayed flat throughout the period.
Questions for discussion
- Which of the two new measures would you have chosen as the single headline number for the board, and why?
- Where in your own team does a held item have no named owner, and how would you find out without a formal audit?
- How would you handle an account manager who sees the new approval deadline as a constraint on customer relationships?
Case Study 2
Hospital group threatens contract after short shipments
Marrow Point Clinical Supply, a distributor of surgical consumables serving about 40 hospital and clinic accounts from two regional centers
The situation
Ridgeview Health Partners, a group of four hospitals, buys about 2,300 line items a month from Marrow Point on a standing replenishment schedule. Over the last quarter, the fill rate for its surgical kits dropped to 88 percent against a contracted target of 97 percent, and three deliveries arrived with substitute items that the supply chief had not approved. The group's director of materials, Dana, sent a formal letter asking for a corrective plan within ten business days and copied the chief executive of Marrow Point. Her letter said the group would begin a rebid if the trend continued into the next month.
The challenge
Dana's letter mixed three complaints: late deliveries, unapproved substitutions, and a lack of contact from the account team. The account manager, Osman, believed the fill rate was mostly a supplier allocation problem and that the group had not updated its par levels. Before anyone promised a recovery date, the team needed to separate what was actually broken from what was a misunderstanding, fix the urgent shortages, and set commitments Dana could hold them to.
Analysis
The first step was a line-level pull from the order system, filtered to Ridgeview's surgical kit SKUs for the quarter. The data split the failures into two groups. About 60 percent of short lines traced to kit par levels that had not moved since the group's procedure mix changed. The remainder came from a single distribution center that had been allocating scarce stock to newer accounts. The service level in the contract measured fill rate per order, but nobody at Marrow Point owned the par review, so the account manager and the supply planner each assumed the other was tracking it.
Dana's expectations were reasonable but not written down. She expected substitutions to be called before shipment, a named contact who would answer within the same day, and a recovery curve with dates. Marrow Point's contract said nothing about substitution notice, and its only commitment on contact was a general account phone line. The fix was not a new target but a set of commitments tied to measures she could see each week: fill rate by kit, substitution requests approved before dispatch, and a two-hour response window for urgent shortage calls. Those three numbers became the agreed scorecard for the next ninety days.
Actions taken
- Call Dana the same day to confirm the urgent shortages, and send a written list of the forty-two lines that would be filled from the next truck, with dates for each.
- Reset the par levels for the eleven affected surgical kits using the last six months of usage, and have the supply planner sign each change before the next replenishment run.
- Move the Ridgeview allocation off the shared distribution center for ninety days so its orders are picked from the stock tied to its account, and report pick accuracy weekly.
- Put a substitution rule in writing: no substitute ships without Dana's approval, and any request that cannot be answered within two hours gets a named escalation contact on the account team.
Results
Fill rate for the surgical kits recovered to 97 percent by the end of the third month, and no further substitutions were shipped without approval. Dana did not start the rebid. She asked that the weekly scorecard be extended to all four hospitals, and the group added a standing call with the supply planner. Two urgent shortage calls in the second month were answered inside the two-hour window, and both were logged in the scorecard. The team also found that three of the eleven par changes had been overstated, which freed about 400 cases of stock for other accounts.
Questions for discussion
- What would you have put in the first written update to Dana, before the par review was finished?
- Which of the three scorecard measures is hardest for a supplier to control, and what would you do about that?
- When a customer's expectations were never written into the contract, whose job is it to surface that gap?
Case Study 3
Requisition rework adds days to every purchase order
Tallow Creek Fabrication, a contract manufacturer of sheet metal enclosures with two plants and a purchasing group of six buyers
The situation
At Tallow Creek, a purchase requisition for production material passes through five people before a purchase order reaches a supplier. The requester enters it, a planner checks the quantity, the cost center owner approves, a buyer selects the supplier, and the supplier confirms. The service level set by the plant manager is a purchase order issued within two business days for standard items. In the most recent quarter, median time from requisition to issued order was 6.5 business days, and about 1,400 requisitions a month came back at least once for correction. The buyers said the rework was the real drain on their week.
The challenge
The plant manager, Ines, wanted the cycle time under two days without adding buyers, and she wanted the answer before the next budget review. The planners blamed incomplete requests, the requesters blamed slow approvals, and the buyers blamed vague specifications. Each explanation pointed at a different step. The team had to map the handoffs, find the root causes that actually drove rework, and compare options they could realistically fund.
Analysis
The handoff map was the first useful artifact. Each requisition was traced through the workflow log, and every return to an earlier step was counted as rework. The largest loop ran from buyer review back to the requester, which accounted for roughly half of all returns. The most common reason code was missing or conflicting specification data, not approval delay. Approvals were slow in a few cost centers, but they added little total time because most approvals cleared within one day. The loop was where the days went.
Root causes sat in the roles and the requisition form. The form let requesters skip the drawing number and the approved supplier list, and nothing in the workflow told a planner which fields were mandatory for each item family. Buyers were absorbing the gap by phoning requesters, which ate about a third of their working hours. The planners, measured on quantity accuracy, were not rewarded for stopping incomplete requests early. Comparing the options against the two-day service level, the cost of each change, and the buyer capacity freed made the choice clearer. Ines needed a plan that met the service level without asking for new headcount.
- Complete data entry Required drawing, supplier and cost fields block submission until filled.
- Route by family Item families send to a named planner with a same-day review window.
- Confirm suppliers early Buyers pre-select approved suppliers before the requisition reaches approval.
- Review return codes Monthly reason codes feed back into form fields and planner training.
Actions taken
- Add the drawing number, approved supplier and cost center as required fields on the requisition form, and block submission until each one is filled.
- Route requisitions by item family to a named planner, who has a same-day review window and authority to return incomplete requests before they reach a buyer.
- Have buyers pre-select approved suppliers for standard item families so that the approval step checks spend rather than rechecking supplier choice.
- Review return codes every month with the planners and requesters, and change the form or the routing rule for any code that accounts for more than one tenth of returns.
Results
Median time from requisition to issued order fell to 1.8 business days within the quarter, and the share of requisitions returned for correction dropped from roughly half to about one in six. Buyer time spent on phone clarification fell by nearly half, which let the team absorb a seasonal increase in volume without overtime. The planners' quantity accuracy held steady, which answered Ines's concern that tighter intake would slow production. The largest remaining loop is now supplier confirmation for custom brackets, and that is the next item on the review list.
Questions for discussion
- If the planners' incentive stayed tied only to quantity accuracy, how would you expect their behavior to change after the new routing rule?
- Which of the four loop steps would you measure first, and what would you accept as evidence that it had worked?
- How would you decide whether custom brackets should be handled outside this workflow entirely?
Case Study 4
New catalog policy meets quiet resistance in sales
Larkmere Outdoor Goods, a wholesale distributor of outdoor equipment that sells through about 600 independent retailers
The situation
Larkmere's sales operations group began requiring that all new orders be entered against the central product catalog rather than through free-text item lines. The policy took effect after the procurement office signed a new supplier agreement that depended on catalog codes for pricing and rebates. Within the first weeks, about 22 percent of order lines were still entered as free text, and the order desk was spending extra time matching them by hand. The policy owner, Marisol, had a service level of 98 percent catalog-matched lines by the end of the month, and the trend was well below it.
The challenge
Marisol had to move nineteen account reps and four order desk staff onto a new routine without slowing renewals, which were already behind. Some reps saw the catalog as a rigid tool that blocked custom deals. Others believed the policy was a procurement control dressed up as a sales tool. The desk was willing but had been burned by two earlier system rollouts. She needed to know what each group was actually worried about, sequence the changes, and show uptake in numbers leadership would accept.
Analysis
The resistance was specific once it was sorted. Reps raised three concerns in one-to-one conversations: custom bundles could not be built in the catalog, special pricing took longer to request, and their commission statements would show unmatched lines as errors. The workflow data backed up the first two. Bundles accounted for about one in five of the free-text lines, and the special pricing request form still lived in a separate tool with its own approval path. The commission concern was unfounded, but nobody had told reps how the statement would treat legacy lines, so the rumor filled the gap.
Sequencing mattered more than the message. Marisol's first draft launched the policy to everyone in one week, which would have left the desk to absorb every mismatch. The revised plan moved the desk to catalog-only entry after reps had a working bundle template and a two-day pilot for special pricing. Uptake was measured by three figures: share of new order lines matched to the catalog, share of pricing requests closed inside two business days, and the number of desk escalations per week. Each figure had a named owner and sat on the same weekly page as the renewal target.
Actions taken
- Publish a written answer on how commission statements will treat legacy free-text lines, and send it to every rep before the catalog-only date.
- Build bundle templates for the twelve most requested custom offers so reps can enter them as catalog kits, and have the desk confirm each template before it goes live.
- Run a two-day pilot for special pricing requests with four reps who volunteered, and move the approval path into the catalog tool only after the pilot meets its two-day target.
- Give the order desk a standing escalation rule for free-text lines, with a same-day answer from the policy owner and a weekly count of exceptions reported to the sales director.
Results
Catalog-matched lines rose from 78 percent to 97 percent over the following six weeks, just under the 98 percent target, and the desk's manual matching time fell by about half. Pricing requests closed inside two business days for 91 percent of cases after the pilot. Two reps who had been the loudest critics asked to present the bundle templates at the weekly huddle. Renewals ran close to plan throughout, which removed the argument that the policy was slowing sales. Marisol still has one open item, a legacy pricing tool that a few reps continue to use for older accounts.
Questions for discussion
- How would you have changed the rollout if the desk had refused to do manual matching for more than a week?
- Which of the three uptake figures would you trust least, and what second source would you use to check it?
- What separates a rep who resists a policy from one who simply has a case the policy does not yet cover?
Case Study 5
Choosing which supply initiative to fund first
Brightline Sporting Components, a manufacturer and distributor of bicycle and fitness parts with one plant and two regional warehouses
The situation
Brightline's leadership team had four supply chain initiatives competing for the same funding pool for the coming year. A supplier consolidation project would cut the vendor list for machined parts from 140 suppliers to about 60. A demand sensing pilot would feed point-of-sale data from three large retail partners into the replenishment model. A returns automation project would route damaged-goods claims through a new intake portal. A second warehouse expansion would add roughly 30,000 square feet to the western site. The funding pool covered two of the four with full scope. The chief operating officer, Yusuf, asked for a recommendation within the month.
The challenge
The data was thin for most options. The consolidation savings rested on supplier quotes that were not yet firm, the demand pilot had only eight weeks of partner data, and the warehouse case relied on a volume forecast that the sales planning group had not yet signed off. Yusuf did not want a spreadsheet exercise that picked a winner by accident. He wanted criteria that everyone could defend, a risk view for each option, and a staged decision that kept the most useful options alive while the gaps closed.
Analysis
The criteria were agreed before any score was assigned. Four were chosen: effect on the two-day replenishment service level for the top 200 SKUs, first-year cash required, dependence on decisions outside the supply group, and reversibility if assumptions failed. Each had a named owner. Pradeep, the planning lead, owned service impact, the finance partner owned cash, and the sales planning group owned the volume assumption behind the warehouse case. The first draft weighted all four equally, which rewarded the cheapest option and hid the fact that the warehouse commitment could not be undone.
The consolidation project had a high expected return but depended on supplier quotes that could move by a wide margin. The demand pilot had a smaller payoff but would produce evidence within a quarter, so a short pilot would shrink the largest unknown. The returns project was modest and carried little downside. The warehouse expansion was the hardest to reverse. Retail partners expected the pilot to keep their replenishment promises, so a failed pilot would cost credibility as well as money. The staged plan funded returns and the demand pilot now, and held consolidation and warehouse money behind gates tied to quote confirmation and the volume sign-off.
Actions taken
- Set the four criteria and their owners in writing before the next steering meeting, and get Yusuf's sign-off on the weights so the ranking cannot be reopened by preference alone.
- Fund the returns automation project and a ninety-day demand sensing pilot now, with a written stop rule that ends the pilot if forecast error does not improve against the current model.
- Hold the consolidation project behind a gate that requires firm supplier quotes covering at least 80 percent of the machined parts spend, confirmed by finance before any vendor is released.
- Defer the warehouse expansion until the sales planning group signs the volume forecast and the demand pilot results are in, and bring the decision back with a reversible lease option.
Results
Yusuf approved the staged plan in the next steering meeting. The returns project went live in the second quarter and cut the average claim handling time by about a third, which freed two staff members for backlog work. The demand pilot ran its ninety days, and forecast error on the three partner accounts improved enough to justify a wider rollout, although the gain was smaller than the most optimistic estimate. The consolidation gate was reached in the third month, and the vendor list was reduced by 55 vendors so far. The warehouse decision was deferred and is now scheduled for the next budget cycle.
Questions for discussion
- What evidence would have to appear in the first month of the demand pilot to convince you to stop it early?
- How would you weight reversibility against expected return if the finance partner pushed hard for the cheapest option?
- Which of the four criteria would you be least comfortable defending to the board, and why?
Learning Resources
Professional CASE STUDIES
China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.