ERP Implementation / Manufacturing
Hershey order and distribution system rollout
Hershey's late-1999 rollout tied together ERP, CRM, and supply-chain platforms but disrupted order fulfillment at the worst possible point in the retail calendar. The company later recovered, but the initial launch became a standard example of how tightly coupled go-lives can hurt the business before process change is absorbed.
Why this failure matters
Hershey's late-1999 rollout tied together ERP, CRM, and supply-chain platforms but disrupted order fulfillment at the worst possible point in the retail calendar. The company later recovered, but the initial launch became a standard example of how tightly coupled go-lives can hurt the business before process change is absorbed.
Failure signals
Each signal is normalized against the approved case base. Recurrence is a deterministic count, not a claim that the cases share identical causes.
- 011 / 8 cases
process redesign failure
A large cross-platform rollout hit core order fulfillment before the organization had adapted
Operating Model - 024 / 8 cases
integration complexity
ERP, CRM, and supply-chain tools were introduced as a tightly linked change
Technical - 032 / 8 cases
insufficient contingency planning
The business absorbed disruption during a critical sales window
Operating Model - 042 / 8 cases
communication gaps
Leaders struggled to explain the system problem and response clearly
Change Management
Evidence record
- The rollout contributed to missed Halloween-season deliveries worth about $100 million.
- The implementation linked SAP, Siebel, and Manugistics into a single operational change.
- The business eventually stabilized, but investor confidence and delivery credibility took a hit first.
Good example of combined platform rollout risk and business-calendar sensitivity.
Decision checklist
Actions derived from the normalized lessons in this approved record.
- 01align process design before technology rollout
Enterprise software is not only software; it changes the way the business works
- 02reduce big-bang scope
Avoid exposing peak business periods to unstable go-live risk
- 03define measurable outcomes early
Explain operational disruption quickly and concretely when launch issues appear
Questions answered
What happened in Hershey's 1999 system rollout?
Hershey's late-1999 rollout linked SAP ERP, Siebel CRM, and Manugistics supply-chain platforms into a single tightly coupled change. The go-live disrupted core order fulfillment just before the Halloween sales season.
How much did the Hershey failure cost?
The rollout contributed to missed Halloween-season deliveries worth about $100 million, and investor confidence and delivery credibility took a hit before the business stabilized.
Why did Hershey's rollout fail?
Three platforms went live as one tightly linked change before the organization had adapted its processes, the disruption hit a critical sales window, and leaders struggled to explain the problem and response clearly.
Did Hershey recover from the failure?
Yes. The company later recovered and the case is classified as partially failed, but the launch remains a standard example of how tightly coupled go-lives hurt the business before process change is absorbed.
What lessons does the Hershey case teach?
Enterprise software changes how the business works, so align process design before rollout, avoid exposing peak business periods to unstable go-live risk, and explain operational disruption quickly when launch issues appear.
Source and method
This analysis uses the cited public source, controlled failure-signal and lessons taxonomies, and human approval. Cross-case comparisons are calculated only from approved, published records.