Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

ERP programmes in public: penalties and lessons

Six companies whose SAP programmes are on the public record, with what each cost where it was reported. Only one is a clean case of an SAP rollout hurting the business. The others are a non-SAP add-on, a supply-network merger, two licence disputes over how other systems reached SAP data, and a consent fine with no ERP failure. Each has a lesson for a layer like the one in An alternative to a full S/4HANA upgrade.

CompanyWhere it failedSAP programmeWhat happenedPenalty or cost (as reported)Lesson for an ECC → Xano layer
RevlonE-commerce and channels: orders the ERP couldn’t fillSAP rollout at its Oxford, North Carolina plant, 2018Failure. Production and shipping were disrupted; a material weakness in financial reporting was disclosed, and the share price fell.About $54M in expenses to remedy the disruption, including about $10M in incremental production and labour costs; a shareholder class action alleges about $64M of net sales went unfulfilled.The ERP cutover reached customers. Keep commerce and feeds off the ERP’s critical path at go-live.
NikeGlobal channels: demand forecast wrong, too much of some shoes and too little of othersSAP as the ERP backbone, with i2 for demand planning, 2000–2001Failure, in the i2 add-on, not SAP. Nike moved its short- and medium-range planning into SAP afterwards.$80M to more than $100M in lost sales; the share price fell about 20%; class actions followed.Often misquoted as an SAP failure. A rushed, customised layer beside the ERP can fail on its own: build the layer to fixed, tested rules.
Coty (Kylie Cosmetics)Global: warehouses and planning consolidated across Europe and the USIntegrating about 40 P&G beauty brands, 2016–2019Supply-chain disruption. Coty attributed it to consolidating warehouses and planning centres; no source found blames SAP.About $150M hit from the disruptions (reported 2019).Kylie Cosmetics, launched on Shopify in 2015 and 51% bought by Coty for $600M in 2019, ran on its own. The trouble came when back-end operations were consolidated: keep the storefront’s record separate from the ERP merger.
DiageoGovernance: other channel systems reaching SAP dataRISE with SAP S/4HANA, a five-year programme with IBM from 2023In progress, not a failure. Earlier, in SAP v Diageo (2017), the UK High Court held that Diageo’s Salesforce-based systems accessing SAP data needed SAP licences (“indirect access”).£54.5M in additional licence fees (2017 ruling).The risk to check for this layer: non-SAP systems reading SAP data can carry licence fees. Read the client’s SAP contract terms on indirect or digital access before the exports start.
AB InBevGovernance: other systems reaching SAP dataSAP S/4HANA migration, prepared with Celonis process mining from 2018No reported migration failure; a licence dispute. In 2017 SAP claimed AB InBev breached its 2010 licence through unlicensed direct and indirect access to SAP systems and data, and underpaid fees.SAP sought damages of more than $600M. Settled on 30 June 2017; terms not disclosed.The same lesson as Diageo, at a larger claim: how other systems reach SAP data is a licence question. Settle it in the contract before any export or integration runs. Mapping processes before migrating (about 100 changes designed in) is the part that went well.
HondaGovernance: consent on the web channel and ad-tech vendorsHonda Australia: two divisions onto one S/4HANA core. Sundiro Honda (China): SAP Commerce Cloud, 2021No reported ERP failure; a consent penalty. In March 2025 California’s privacy regulator (CPPA) found American Honda’s cookie tool took two steps to opt out of advertising cookies and one to opt back in, asked for more information than needed to act on privacy requests, and had no compliant contracts with its ad-tech vendors.$632,500 fine under the CCPA (2025), plus changes to its consent tool and request process. Honda did not admit most findings.The penalty was in the consent layer, not the ERP. Opting out must be as easy as opting in, and every vendor that receives the data needs a contract: the banner and the release gate are where that is enforced.

The common thread

None of these is an ERP failing on its own terms. Each broke where the ERP meets the channels around it: e-commerce and retail orders it had to fill, the same products planned and shipped across global markets, and the governance that has to hold across every channel (licences for the systems that read ERP data, and consent for the people the channels reach).

RequirementWhat it takesCases
E-commerceOrders and feeds keep flowing while the ERP and the commerce APIs change underneathRevlon, and the escalation below
GlobalOne product record, priced, planned and stocked per marketNike, Coty
GovernanceLicences settled for every system that reads ERP data; consent enforced the same way on every channelDiageo, AB InBev, Honda

That is the scope of the layer in this book: the record that faces the channels (products, customers, consent) lives in Xano, is carried at the edge by Cloudflare, and passes one release gate, so the ERP can change without the channels breaking and every channel answers to the same rules. See An alternative to a full S/4HANA upgrade.

The next escalation: e-commerce, then agentic commerce

The ERP-to-e-commerce integration is where the next failures are scheduled. The commerce side is changing its data shapes and its credentials on fixed dates, whatever the ERP is doing:

ChangeDateWhat breaks in an SAP integration
Shopify’s REST Admin API is legacy; new public apps must use GraphQL onlyLegacy since 2024-10-01; GraphQL-only for new public apps since 2025-04-01Every mapping written against REST payloads: IDs become global IDs (gid://shopify/...), amounts become money objects, lists become cursor-paged connections
Shopify replaces non-expiring offline tokens with expiring ones (1 hour, with a 90-day refresh token)New public apps since 2026-04-01; all public apps by 2027-01-01; Admin API calls with the old tokens rejected from 2027-04-01Middleware that stored one token and never refreshed it stops: every call returns 403
GA4 renames and reshapes: conversion events become key events; Google recommends the Data Manager API over the Measurement Protocol for new server-to-server integrationsOngoing through 2026Revenue and conversion feeds built on the old event names and endpoints

Agentic commerce is the bigger problem. When an AI agent places the order through Shopify and Google’s UCP or Stripe’s ACP, the ERP integration has to accept an order that carries who authorised it, under which consent, and with which limits, and every channel has to answer to the same rules for an agent as for a person. That is governance multiplied by every agent, on top of the data-shape and token changes above.

The layer in this book takes both off the ERP: the GraphQL shapes and token refresh live in the Worker and Xano, the converted ECC record stays the same, and the release gate decides for agents as it does for people.

Reading the table

  • Penalties are as reported, not audited. Revlon’s $64M is an allegation in a shareholder suit; Nike’s loss is its own estimate, and sources give a range. Coty’s $150M is not attributed to an ERP.
  • Consent fines and wiretap suits are separate. Honda’s fine came from the regulator under the CCPA. California’s wiretap law (CIPA) is a different route: private suits over tracking that runs before or despite consent, with statutory damages of up to $5,000 per violation. No CIPA suit against Honda was found; in 2026 one was filed against Toyota, alleging tracking continued after visitors chose “decline”. Both point at the same control: nothing loads or sends before the consent decision, and a refusal is honoured everywhere.
  • The licence point applies to any layer. The exports in this book are batch extracts, not live users of SAP, but how a contract counts them is for the contract to say. SAP v Diageo and SAP’s claim against AB InBev, both in 2017, are why the question comes first. SAP changed its licensing model for indirect access in 2018 after customer pushback; which model a contract uses decides how exports are counted.

Licensing penalties by flow

Running SAP on external VMs carries no penalty of its own: SAP supports AWS, Azure and GCP. The costs come from four other places, and for a layer like this book’s, the first is the one that matters.

1. Other systems using SAP data. Under older user-based contracts, a non-SAP system reading or writing SAP data on behalf of people can be counted as needing SAP user licences: that is the Diageo and AB InBev lesson in the table above. SAP’s Digital Access model (2018) counts documents created in SAP by other systems instead, in nine types: sales, invoice, purchase, service and maintenance, manufacturing, quality management, time management, financial and material documents. Reading is generally not counted. Each flow in this book, under that model:

FlowExposure under Digital Access
ECC → Rust → Google Merchant (read materials, prices, stock)Low: a read
ECC → Xano for identity and blockingLow: a read
ECC → BigQuery extractsLow: a read
Shopify order → ECC sales order (VBAK / VBAP)Counted: a sales document, then deliveries and invoices follow
Returns and refunds posted to ECCCounted: sales, financial and material documents
Consent written to ECCAvoided by design: ECC never holds consent

Which model a contract uses decides how any of these is counted; a customer still on user-based licensing, never moved to Digital Access, carries the most risk. Read the contract before any flow that writes to SAP.

2. Certified VMs. SAP supports HANA and S/4HANA only on certified instance types and sizes for each cloud. An uncertified VM costs no fee, but support can be declined until a problem is reproduced on a supported setup.

3. HANA memory. HANA licences are often sized by memory. A larger VM costs nothing by itself; giving HANA more memory than is licensed leads to a true-up.

4. Network, contract and maintenance.

  • Egress. Moving SAP data between clouds or regions (S/4 on one cloud, BigQuery on another) incurs the provider’s data-transfer charges. Send deltas, not full extracts.
  • RISE with SAP. SAP runs the infrastructure; your own VMs can’t sit inside it, but they can connect to it. Extensions are expected on BTP and paid for with BTP credits. Running them on your own VMs or Kubernetes is allowed; point 1 still applies.
  • ECC maintenance. Mainstream maintenance ends in 2027; extended maintenance to 2030 costs about 2% a year more. Where the VMs run doesn’t change this; staying on ECC does. See An alternative to a full S/4HANA upgrade.
PenaltyTriggerHow to avoid it
Indirect / Digital Access feesOther systems creating SAP documentsRead-mostly flows; settle the licence model before writing orders back
Support declinedAn uncertified VM typeCertified instance types only
HANA licence true-upHANA memory beyond the licenceSize HANA to the licence
Egress chargesSAP data moved between clouds or regionsOne region per regime; deltas, not full extracts
Extended maintenance (about 2% a year)ECC past 2027Plan the move, or the alternative in this book

These are general terms as publicly reported; every contract differs. Confirm with the customer’s SAP account team or a licensing adviser before quoting any of them.

Sources