Supply Chain Interview Questions

"I studied engineering, and my final-year internship was in a plant's stores team. I expected it to be boring, but I saw how one late component could stop a whole production line, and how the planners juggled that every day. That got me hooked. My first job was as an inventory analyst, setting reorder points and chasing why stock records didn't match the shelf. Over two years I got more involved in the monthly forecast meeting, and that's the part I enjoy most, because it's where demand, supply and money all meet. So I want to grow on the planning side, demand and supply planning, and this role sits right there while still keeping me close to the warehouse and suppliers."

"At my last company we made packaged snacks. Raw materials like flour, oil and film came from about twenty suppliers into two plants. Finished goods went to three regional warehouses and from there by road to distributors and big retail chains. My part was supply planning for one plant: I turned the demand forecast into a weekly production and material plan, checked it against line capacity, and raised the purchase requirements the buyers placed. I depended on demand planning for a good forecast and on buyers for supplier dates. The warehouses and customer service depended on me to have the right stock there on time, so when a plan slipped I was usually the first to tell them."

"From your site and annual report, you sell small kitchen appliances through big retailers and your own online store, and most units are made by contract manufacturers overseas. So my guess is the hardest part is the long, one-way lead time. You're committing to production and ocean freight months before you know how a season sells, and retailers expect high fill rates with penalties if you miss. Add the online channel, which wants single units fast, and you've got two very different ways of serving customers pulling on the same stock. I'd want to check how you split inventory between those channels and how much you rely on air freight to recover, because that usually shows where the pain is."

"I accept it comes with the job, because supply chain sits where everyone's mistakes land. When someone blames us, I listen first and don't argue on the spot. Then I look at what actually happened, with the data, and I'm honest if it was our miss. Often it's a mix, like a late forecast change plus a slow reaction from us. When I go back, I don't lead with whose fault it was. I say here's what happened, here's our part, and here's what would stop it next time, like an earlier cut-off for changes. Most people calm down quickly once they see you're trying to fix the process, not win the argument."

"At my last job our main suppliers were about eight hours ahead of us, so we had a short overlap in my morning. I kept that window for calls on anything urgent and did routine work outside it. Because a question can cost a full day, I made sure my emails were complete: the order number, what I need, by when, and what happens if we can't get it. We also kept a shared tracker of open orders so both sides could see status without waiting for a reply. And I tried to learn how they worked, their holidays, their busy seasons, and even a few words of their language. It sounds small, but partners respond faster to people who respect their time."

"I'd think of it in five steps. First, plan: forecast what customers will buy and work out what supply we need. Second, source: pick suppliers and buy raw materials and parts. Third, make: turn them into finished products. Fourth, deliver: store the goods in warehouses and move them to distributors, stores or straight to the customer. And fifth, return: products that are faulty, unwanted or at end of life come back to be refunded, repaired or recycled. Running through all of that are three flows. Goods move towards the customer, information like orders and forecasts moves back up the chain, and money flows back from the customer to the suppliers. A supply chain goes wrong when those three get out of step."

"First I'd ask which orders really need three weeks. It might be a few key customers, not everything. Then I'd take a sample of recent orders and map the six weeks step by step: order entry and credit checks, waiting to be scheduled, waiting for materials, production, packing and transport. Usually most of the time is waiting, not work. Say we find two weeks is waiting for one imported component. Then holding stock of that part, or moving it to a closer supplier, could cut two weeks at once. If production batches are large, smaller batches cut queue time. Another option is to build a common base product to stock and only finish it to order. I'd cost each option, because holding stock and faster freight aren't free, and pick the mix that gets the priority customers to three weeks first."

"At my last company, replenishment from our central warehouse to the regional sites took about eight days, and the regions kept high safety stock to cover it. I followed a few orders through and found the actual truck journey was two days. The rest was waiting: orders batched once a week, then a day for approval, then a wait for a full truck. I worked with the regional managers and the transport team to switch to twice-weekly orders with no approval under a set quantity, and we agreed fixed truck days so loads were planned. Lead time dropped to about four days. Because of that, we lowered the regions' safety stock, and after three months their stock-outs hadn't gone up, which was the proof the change was safe."

"Purchasing is the transactional part. Someone needs something, a purchase order goes out to an approved supplier, the goods arrive, they're checked and received, and the invoice gets paid. Procurement is the bigger process that purchasing sits inside. It starts earlier, with working out what the business actually needs, finding and evaluating suppliers, negotiating and agreeing contracts, and it carries on afterwards with managing supplier performance and risk over time. So I'd say procurement decides who we buy from and on what terms, and purchasing carries out the individual buys within those terms. In a small company one person might do both, but in a bigger one they're often separate teams."

"The main number I use is OTIF, on time in full. For each order line I check whether the full quantity arrived inside the agreed window, and it only counts if both are true. Alongside that I track how much their actual lead time varies, the share of deliveries rejected for quality, and how quickly they respond when something changes. A supplier can still look fine while we run short for a few reasons. The scorecard might measure against the date they re-confirmed after pushing it out, not the date we asked for. The on-time window might be a whole week wide. A line might count as delivered when only part of it came. Or the average hides it, because they're great on fifty easy parts and late on the two critical ones. So I measure against our requested date, line by line, and I look at our critical parts separately."

"In the short term I'd protect our line. I'd raise safety stock on that part, freeze our order schedule so we're not adding changes, and track every open order weekly. Then I'd sit down with the supplier with the delivery data, not just complaints, and ask what's driving it. Sometimes it's their capacity or their own materials, but sometimes it's us, changing quantities inside their lead time. From that we'd agree a recovery plan with specific actions and dates, and review it every week. At the same time, being late on a third of deliveries tells me a single source is too risky for a critical part, so I'd work with procurement and engineering to start qualifying a second supplier. I'd tell the current one openly, because it's about risk, not punishment."

"The reorder point is the demand you expect during the lead time, plus safety stock. Demand during lead time is 40 a day times 5 days, which is 200 units. Add the 60 units of safety stock and the reorder point is 260. So when stock on hand, plus anything already on order, drops to 260, we place the next order. If everything goes to plan, the 200 get used up while we wait and the new delivery arrives just as we're down to the 60. The safety stock is there for the days when demand runs higher than 40, or the supplier takes six days instead of five."

"EOQ, economic order quantity, is the order size that keeps the total of ordering cost and holding cost as low as possible. If I order in big lots, I pay the ordering cost fewer times but hold more stock; small lots are the reverse. The formula is the square root of 2 times annual demand times cost per order, divided by the holding cost per unit per year. Here that's 2 times 10,000 times 100, which is 2 million, divided by 2, which is 1 million. The square root is 1,000 units. So about 10 orders a year. At that point the yearly ordering cost and holding cost come out equal. In practice I'd use it as a starting point, because it assumes steady demand and no volume discounts or pack-size rules."

"I start with the service level we want, say not running out in 95 out of every 100 order cycles, which gives a z value of roughly 1.65. Then there are two risks to cover. Demand can swing while we wait for delivery, and the delivery itself can be late. So safety stock is z times the square root of two parts added together: the average lead time times the variance of daily demand, plus the average daily demand squared times the variance of the lead time. I make sure demand and lead time are in the same time unit, usually days. And I treat it as a living number. If the supplier becomes more reliable, the second part shrinks, and that's often a cheaper way to cut stock than squeezing the service level."

"I'd support the goal, because less inventory frees cash and space and makes problems visible. But I'd be honest that just-in-time works when suppliers are close and reliable, demand is fairly steady and quality is consistent. A ten-week ocean lead time means one late ship or port delay stops our line, and with lean stock there's nothing to absorb it. So I'd suggest splitting it. For local parts with short, reliable lead times, we move to frequent small deliveries. For the overseas parts, we keep a buffer sized to the lead-time risk, but ask the supplier to hold stock in a nearby warehouse or on consignment, so it's off our books until we use it. And I'd show leadership the inventory saving and the risk side by side, so it's their decision with the facts."

"Both are usually true at once, because inventory isn't in the right items or places. We might have months of cover on slow sellers and days on the fast ones. So I'd pull item-level data and segment it. ABC by value and volume, and then by how steady or erratic demand is. A fast, steady A item deserves a high service level and tight replenishment. An erratic C item might need a lower target or be made to order. Then I'd set safety stock and reorder rules per segment instead of one policy for everything. At the same time I'd clear slow and dead stock with sales and finance, and move stock between warehouses where one site is short and another is full. I'd report both numbers together each month, total inventory and fill rate, so neither team sees only half the story."

"The bullwhip effect is when a small change in what end customers buy turns into bigger and bigger swings in orders as you move up the chain, from retailer to distributor to manufacturer to their suppliers. There are a few classic causes. Each step forecasts from the orders it receives instead of real sales, and adds its own buffer. People order in big batches, say once a month, which makes demand look lumpy. Promotions and price deals make customers stock up, then go quiet. And when supply is short, buyers order more than they need because they expect to be rationed. The fixes follow the causes: share real point-of-sale data up the chain, order smaller and more often, keep pricing steadier, and allocate scarce stock based on past sales, not on inflated orders."

"I start with the sales history and clean it, taking out one-offs like a stock-out week where sales were low only because we had nothing to sell. Then I fit a simple statistical method that suits the pattern, such as exponential smoothing with seasonality if there's a clear yearly shape. On top of that I add what the business knows, like planned promotions or a new retailer coming on. To judge it, I look at two things. Error size, usually weighted MAPE, which is total absolute error divided by total actual sales, so tiny slow sellers don't distort the picture. And bias, which tells me if we're consistently over or under. A forecast that's a bit noisy but unbiased is far easier to live with than one that's always high."

"First I'd ask sales what's behind the number, because they may know about a big retailer deal I don't. Then I'd bring my own evidence: how similar products did in their first three months, how many stores have actually committed, and any pre-orders. If there's still a gap, I'd suggest we plan on a range, a low, base and high case, rather than fight over one number. Then I'd set supply up to handle the range. Commit firmly to the base volume, secure extra capacity or long-lead materials for the high case without building finished goods, and agree to look at sell-through after the first two or three weeks and adjust. That way if sales is right we can chase it, and if I'm right we're not stuck with a warehouse full of it."

"At my last company I forecast a seasonal product off the previous two summers and missed a hot, early start to the season. We sold through in about four weeks instead of ten, and we lost sales while the next production run caught up. When I looked back, the problem wasn't the weather itself, it was that I'd only reviewed that forecast monthly, so it took us three weeks to react to what the sell-through was telling us. I also hadn't asked the sales team about a new retailer who'd started stocking it. After that, I moved seasonal items to weekly reviews in the first six weeks of the season, set a simple trigger if sales ran well above forecast, and added a check-in with sales on new customers before locking the plan."

"I start with what the shipment is and how urgent it is. Ocean is the cheapest per unit over long distances and handles big volumes, but it's slow and less predictable, so it suits planned, bulky or low-value goods. Air is fast and reliable but costs much more and has the highest emissions per unit carried, so I keep it for high-value, urgent or perishable items, or for recovering from a problem. Road is the most flexible and goes door to door, which makes it the default for regional moves and the last leg of most journeys. Rail works well for heavy loads over long land distances and is cleaner than road, but needs a road leg at each end. I also count the inventory sitting in transit, because slow modes tie up stock for weeks."

"I'd want a small set that covers accuracy, speed, cost and capacity. For accuracy, order picking accuracy, meaning the right item and quantity went out, and inventory record accuracy from cycle counts, because if the system is wrong, planning is wrong. For speed, the share of orders shipped on time, and dock-to-stock time, how long received goods take to become available to pick. For productivity, units picked per labour hour and cost per order shipped. Then space utilisation, so we see when we're running out of room, and safety incidents, which I'd never drop. I'd look at them together, because it's easy to push picks per hour up while accuracy quietly falls."

"At my last job our pick accuracy had slipped and customers were getting wrong items. I could see the error reports, but I spent two shifts on the floor with the pickers to see why. They showed me that two similar products in different sizes sat in bins right next to each other, with labels that looked almost the same. It wasn't carelessness, it was the layout. With the shift lead, we moved those look-alike items apart and added scanning of the item barcode at pick for that area, not just the bin. Mis-picks on those items dropped to almost none within a month. The pickers suggested half the fixes, so they owned it, and we used the same idea for other look-alike items after that."

"It runs as a monthly sequence. In the first week we close last month's numbers and refresh the statistical forecast. Then the demand review, where sales, marketing and demand planning agree what customers are likely to buy over the next year or more, including promotions and launches. Next is the supply review, where operations, procurement and supply planning check that demand against capacity, materials and inventory targets, and flag the gaps. Then there's a reconciliation meeting where finance joins, the gaps are costed, and options are prepared, like adding a shift or cutting a promotion. Finally, the executive meeting makes the calls. What comes out is one agreed plan that sales, operations and finance all work to, with decisions and owners written down."

"First the customer. I'd have the team check other bins, overflow areas and anything received but not yet put away, because the stock is often in the building but in the wrong place. If it's truly gone, I'd find it elsewhere or give the customer an honest new date. Then I'd trace the record. I'd look at the item's recent transactions for a receipt booked to the wrong location, a pick that was done but never confirmed, or a return logged but not physically there. Once we've counted, the adjustment goes in with approval and a reason. The part people forget is that while the system thinks there are 500 units, it won't trigger a reorder, so I'd check the replenishment for that item straight away and then fix whatever step let the record drift."

"Our commercial director wanted to run a big promotion on a product line the month we were changing over a production line. In the supply review I could see we'd be short by roughly a third of the promoted volume. Instead of just saying it won't work, I built a short summary: capacity by week, the gap, and three options. Move the promotion two weeks later, build stock early at the cost of extra holding, or cut the promoted range to the items we could actually make. I took it to her before the executive meeting, not in front of everyone. She chose to build ahead for the top items and drop two from the offer. The promotion ran without shortages, and after that she started asking for a supply check before promotions were locked."

"We kept running short on one family of components even though the ERP's material planning run said we were ordering on time. I compared actual supplier delivery times with the lead time held in the item master, and found most of those items still said three weeks, when the supplier had moved them to five after a change in their own sourcing a year before. So the system was ordering two weeks too late, every time. I pulled a list of every item from that supplier, confirmed the real lead times with the buyer, and got the updates approved and loaded. Shortages on that family stopped within a couple of months. Then I set up a quarterly report comparing planned and actual lead times across all suppliers, so drift like that gets caught early."

"First I'd confirm the facts in the first few hours: stock in every warehouse and store, what's in transit and when it lands, and the promotion forecast, so I know if we're short by days or by half the event. Then I'd work both sides at once. On supply, I'd ask the plant or supplier what they can bring forward, check other regions for stock we can move, and price out faster freight for part of the next shipment. On demand, I'd agree an allocation with sales so our biggest customers get a fair share based on past sales, and look at a substitute item or shortening the promotion on this one. By the end of day two I'd want sales and key customers told plainly what they'll get and when. Once it's over, I'd find out why we didn't see it sooner."

"A packaging supplier had a fire at their plant and told us they couldn't ship for at least three weeks. We had about ten days of their cartons in stock. Within the first day, I worked out which finished products used those cartons and which customers they served, and we switched production to the items where we had packaging, to stretch what we had. Procurement found a backup supplier who could make a close match in two weeks, and quality approved it quickly. I told sales on day one which products might go short and when, so they could manage customers rather than be surprised. We had short gaps on two items but no customer lost supply entirely. Afterwards we qualified that backup properly for packaging, so there's always a second option ready."

"A shipment for one of our distributors got held at the port for extra inspection, and I could see it would miss their delivery date by about a week. I called the account manager that morning instead of waiting to see if it cleared. I gave her the facts, a realistic new date with a little margin, and two options: a partial delivery from local stock of the fastest-moving items in two days, or the full order when it cleared. She took the partial option to the customer, who appreciated hearing it from us first rather than finding out on the day. What I learned is that people handle a late order much better than a surprise, as long as they get a real date and a choice."

"I'd start by measuring, because you can't show a cut without a baseline. I'd get emissions by lane and mode from our carriers or an agreed calculation method, and find the biggest few lanes. The good news is the first levers usually save money too. Cutting emergency air freight is the big one, and that's really a planning fix, since most air shipments come from late orders. Next is filling trucks and containers better and consolidating small shipments, so we move the same goods in fewer trips. Where transit time allows, I'd move some lanes from road to rail or from air to ocean. After that, longer-term work like lighter packaging, carriers with cleaner fleets, and whether our warehouses sit in the right places. I'd report progress against the baseline with the method stated."