How Spreadsheets Quietly Cost Supply Chains Millions

电子表格如何悄无声息地让供应链损失数百万美元

A simulation of how a single forecast change moves through five planning teams, and why most retailers lose money in the gap between Sales and Stores. 这是一场关于单一预测变更如何在五个规划团队中流转的模拟，以及为何大多数零售商会在销售与门店之间的缺口中蒙受损失。

Last quarter, a fashion retailer ran a national TV campaign for its best-selling apparel line. The demand planner updated the forecast on a Tuesday morning. But the supply team only found out eleven days later, in the monthly meeting! By then, the factory lead time had expired, and two outlet stores had empty shelves for the first week of the campaign. 上个季度，一家时尚零售商为其畅销服装系列开展了一场全国性的电视宣传活动。需求规划师在周二上午更新了预测，但供应团队直到十一天后的月度会议上才得知消息！届时，工厂的交货周期已经截止，导致两家奥特莱斯门店在活动的第一周就出现了货架空置的情况。

VP of Marketing: Tens of thousands of dollars in lost campaign revenue due to insufficient inventory! The marketing budget was spent. The traffic showed up. The product did not. This is what S&OP was supposed to fix, and in most retailers, it still has not. This is not a technology problem. It is the way most retailers organise the conversation between Sales and Operations. 营销副总裁表示：由于库存不足，损失了数万美元的活动收入！营销预算花出去了，客流来了，但产品却没到位。这本应是销售与运营规划（S&OP）旨在解决的问题，但在大多数零售商那里，问题依然存在。这并非技术问题，而是大多数零售商组织销售与运营沟通的方式出了问题。

Integrated Business Planning, also known as Sales and Operations Planning (S&OP), is the process that translates sales forecasts (“We expect to sell 50 units next month”) to products on the shelf (“75 units delivered at Store 125 last week”). 集成业务规划，即销售与运营规划（S&OP），是将销售预测（“我们预计下个月销售 50 件”）转化为货架上产品（“上周向 125 号门店交付了 75 件”）的过程。

In a spreadsheet world, each team works on its own copy of the data, and a single forecast change takes weeks and the cost is measured in lost sales nobody can trace back to the original delay. What should be a seamless process becomes a chain of emails and meetings, in which teams discover changes too late. 在电子表格的世界里，每个团队都在处理各自的数据副本，单一的预测变更需要数周时间才能传达，而其代价是无法追溯到最初延迟原因的销售损失。本应无缝衔接的流程变成了一连串的电子邮件和会议，导致团队发现变更时为时已晚。

At a fashion retail company I’ve been working with, it took up to 27 days to see a change in the demand signal to be communicated to the warehouse teams. The information was trapped in isolated Excel files shared via email, with limited traceability and version control. The root cause of poor planning execution is rarely the forecasting model alone. It is the siloed organisation around it. 在我合作过的一家时尚零售公司，需求信号的变更传达到仓库团队竟需要长达 27 天。信息被困在通过电子邮件共享的孤立 Excel 文件中，缺乏有效的可追溯性和版本控制。规划执行不力的根本原因很少仅仅是预测模型本身，而是围绕模型形成的孤岛式组织架构。

Merch Team to Demand Planning: Can you send me forecast_jan2026_v12.xslx to prepare tomorrow’s buying session? In most companies, the answer is measured in weeks, and the cost shows up in next quarter’s margin without anyone connecting the dots. In the simulation you are about to read, it is one working day! A perfect forecast that nobody downstream sees in time is worth nothing. 商品团队问需求规划团队：“你能把 forecast_jan2026_v12.xlsx 发给我，以便准备明天的采购会议吗？”在大多数公司，这个问题的响应时间是以周为单位的，而代价则体现在下个季度的利润率中，却无人能将两者联系起来。在你即将阅读的模拟中，这个时间仅需一个工作日！一个下游团队无法及时看到的完美预测，毫无价值。

In this article, I will show how a connected planning platform turns that two-week delay into a same-day action plan, and why this single change can save retailers millions. We will use a simulation platform that I designed from scratch, where you can experiment with how information flows across teams through integrated business planning. 在本文中，我将展示一个互联的规划平台如何将两周的延迟转化为当天的行动计划，以及为什么这一单一的改变能为零售商节省数百万美元。我们将使用我从零开始设计的模拟平台，你可以在其中体验信息如何通过集成业务规划在团队间流动。

To make this concrete, let’s look at SupFashion, a mid-size European fashion retailer that is small enough to be agile and big enough to feel every planning failure in its margin. SupFashion is a mid-size fashion retailer based in Europe. It sells four product lines (wallets, bags, luggage, apparel), sources from five factories on three continents, and runs 12 stores across the United States and Europe. 为了具体说明，让我们看看 SupFashion，这是一家欧洲中型时尚零售商，它既足够灵活，又大到足以让每一次规划失误都影响其利润率。SupFashion 总部位于欧洲，销售四个产品系列（钱包、包袋、行李箱、服装），从三大洲的五家工厂采购，并在美国和欧洲经营 12 家门店。

The brand is small by industry standards, but the planning challenges are exactly the same as those of a global fashion giant. To plan and run this network, four planning teams work in sequence every month, supported by a finance team that closes the loop. Each team’s job depends on the output of the team before it: The merchandiser cannot lock a buy plan until the demand planner has signed off on the forecast. The supply planner cannot place a factory order until the buy plan is approved. Finance cannot project margin until production and freight costs are confirmed. 按行业标准衡量，该品牌规模较小，但其面临的规划挑战与全球时尚巨头完全相同。为了规划和运营这个网络，四个规划团队每月按顺序工作，并由一个负责闭环的财务团队提供支持。每个团队的工作都依赖于前一个团队的产出：在需求规划师确认预测之前，商品规划师无法锁定采购计划；在采购计划获批之前，供应规划师无法下达工厂订单；在生产和运费成本确认之前，财务部门无法预测利润率。

Here is the catch. None of these five teams works in the same tool! This is how every planning error enters the system. Not through bad models, but through copy-and-paste. In a SupFashion, each of these five teams works on its own copy of the data, in its own tool: A demand planner has forecast_jan2026_v22.xlsx. The merchandiser has buy_plan_SS26_FINAL_v3.xlsx. The supply planner manages a Google Sheet shared with the factory. Distribution runs on a Power BI dashboard built three years ago by someone who has since left. Finance reconciles all of it in a separate system, two weeks after the fact. 问题就在这里：这五个团队没有一个使用相同的工具！这就是每一个规划错误进入系统的原因。不是因为模型不好，而是因为复制粘贴。在 SupFashion，这五个团队中的每一个都在使用自己的工具处理自己的数据副本：需求规划师有 forecast_jan2026_v22.xlsx；商品规划师有 buy_plan_SS26_FINAL_v3.xlsx；供应规划师管理着与工厂共享的 Google 表格；分销部门运行着一个三年前由已离职员工构建的 Power BI 仪表板；财务部门则在事后两周通过一个独立的系统进行核对。

When the demand planner changes a number, it sits in her file until the next monthly meeting. From there, it travels by email and is re-typed across four teams. Two weeks later, the distribution finally hears about it. In the next section, we will follow a single forecast change in detail and see what happens when those two weeks become one working day. 当需求规划师更改一个数字时，它会一直留在她的文件中，直到下一次月度会议。此后，它通过电子邮件传播，并在四个团队中被重新输入。两周后，分销部门才最终得知消息。在下一节中，我们将详细跟踪一个单一的预测变更，看看当这两周缩短为一个工作日时会发生什么。