Skip to content

All best practices

CS-005mixed

Nike, Inc.

Global supply-chain programme: i2 demand and supply planning, then SAP ERP

Region
North America, Global
Country
United States, Canada, Global
Industry
Apparel and Footwear (brand owners) (Specialty Retail and Omnichannel Commerce)
Functions
Supply Chain & Logistics, IT, ERP & Digital, Sales & Revenue Operations
Topics
Inventory is simultaneously excessive and unavailable; Forecasts are unreliable in a volatile environment; Legacy ERP and fragmented systems block execution; Margins are eroding despite revenue
Starting situation
In-flight initiative
Period
1998–2004
Last verified
31 October 2026

Executive summary

From 1998 Nike rebuilt its global supply chain around SAP, i2 planning software and Siebel CRM, replacing 27 order-management systems [C01, C21]. The i2 demand-planning system, installed first and heavily customised, distorted factory orders in 2000; on 26 February 2001 Nike cut its quarterly earnings guidance, and its filings tied a 15% fall in US footwear revenue and a lower gross margin partly to the disruption [C05, C09, C10, C11, C12]. Nike then moved footwear planning to SAP, rolled SAP out region by region starting with Canada, and trained users before giving them access [C06, C07, C08]. The three numbers that matter: an estimated US$80m–100m of lost revenue [C13]; a quarterly net income drop of 33% [C16]; and pre-built inventory reported down from about 30% to about 3% of units by 2004, a Nike figure [C30]. Gross margin rose from 39.0% in fiscal 2001 to 44.5% in fiscal 2005, though Nike's own filings attribute part of that to product costs and mix [C18, C43, C44]. The one lesson: put a new planning engine into the core business only after its data, interfaces and users are proven, and roll the backbone out where mistakes are small [C24, C25, C07].

Outcome: mixed

Documented shortfalls or reversals sit alongside documented gains. For example: an initial failure later recovered, or a strategic goal met while a major adverse event in the same programme was recorded.

Basis of the outcome

The 2000-2001 demand-planning implementation was followed by a profit warning, a fall in US footwear revenue and a lower gross margin that Nike attributed partly to the disruption. Nike then moved footwear planning onto SAP, rolled SAP out region by region without reported disruption, and reported (company-sourced) inventory and lead-time improvements, while the programme's cost and timeline grew.

Key figures

PhaseFigureValueWhenVerification
BeforeOrder-management systems worldwide271998press_reported
BeforeProgramme budget (as reported)about US$400m1998–2001press_reported
DuringQ3 FY2001 net incomeUS$97.4m (–33%)Q3 FY2001regulatory_filing_unaudited
DuringQ3 FY2001 US footwear revenueUS$734.3m (–15%)Q3 FY2001regulatory_filing_unaudited
DuringQ3 FY2001 gross margin38.2% (40.5% a year earlier)Q3 FY2001regulatory_filing_unaudited
DuringQuarterly EPS guidance34–38c (from 50–55c)26 Feb 2001press_reported
DuringEstimated revenue impactUS$80m–100m2001press_reported
DuringFY2001 revenue / gross marginUS$9,488.8m / 39.0%FY2001audited_filing
AfterSAP users6,350end 2002press_reported
AfterProgramme cost / duration (Nike)US$400m → US$500m; 2–3 years → 5–7 years2004company_reported
AfterFY2005 revenue / gross marginUS$13,739.7m / 44.5%FY2005audited_filing
AfterPre-built shoes as share of units (Nike)about 30% → about 3%2004company_reported
press_reported
A journalist's own reporting.
regulatory_filing_unaudited
Text in an 8-K, 6-K or 10-Q, which is filed with a regulator but not audited.
audited_filing
A figure in audited financial statements, such as an annual report's financial statements or a 10-K.
company_reported
A company statement, press release or investor presentation that no one has independently checked.

Sources

  1. S01 Nike, Inc. Form 10-Q for the quarter ended February 28, 2001 · Nike, Inc., Nike, Inc. / U.S. SEC, 2001-04-16 · accessed 2026-10-31
  2. S02 Nike blames financial snag on supply-chain project · Marc L. Songini, Computerworld, 2001-02-27 · accessed 2026-10-31
  3. S03 Nike's Supply Woes Could Signal Broader Trend · not stated, eWeek, 2001-03 · accessed 2026-10-31
  4. S04 Nike Rebounds: How (and Why) Nike Recovered from Its Supply Chain Disaster · Christopher Koch, CIO, 2004-06-15 · accessed 2026-10-31
  5. S05 Form 10-K for fiscal year ended 31 May 2001 · not stated, Nike, Inc. / U.S. SEC, 2001-08 · accessed 2026-10-31
  6. S06 Form 10-K for fiscal year ended 31 May 2003 · not stated, Nike, Inc. / U.S. SEC, 2003-08 · accessed 2026-10-31
  7. S07 Form 10-K for fiscal year ended 31 May 2005 · not stated, Nike, Inc. / U.S. SEC, 2005-08 · accessed 2026-10-31
  8. S08 Nike blames ebiz software · Robert Blincoe, The Register, 2001-02-28 · accessed 2026-10-31
  9. S09 Nike Accuses i2 of Being a Bad Fit · not stated, Supply & Demand Chain Executive (reporting InformationWeek), 2001 (date not printed; content refers to the February 2001 disclosure) · accessed 2026-10-31
  10. S10 i2 Falls on Reported Link to Nike Woes · not stated, E-Commerce Times, 2001-02-27 (date not printed; inferred from 'Tuesday' after the 26 February disclosure) · accessed 2026-10-31
  11. S11 Playing the Blame Game · eWEEK Editors, eWeek, 2001-03-05 · accessed 2026-10-31
  12. S12 Nike CIO Resigns · Laurie Sullivan, InformationWeek, 2005-01-11 · accessed 2026-10-31

Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026 · Last verified 31 October 2026

Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.