Every enterprise leader talks about anticipating customer needs. The reality inside most organisations is far less ambitious: recommendation engines serve generic products because behavioural data sits in isolated silos. Marketing emails fire on rigid calendar schedules, not when a user actually shows intent. Loyalty programmes reward transactions while ignoring whether a customer even feels valued.
This is the gap SAP is now trying to close — not by adding another AI tool, but by restructuring the fragmented commerce data structures that prevent personalisation from working at the execution layer.
The Infrastructure Problem Behind Broken Personalisation
The technical ambition is straightforward in theory: align commerce data so AI can operate systematically across digital touchpoints. But the current infrastructure inside most enterprises fails to support this at volume. Behavioural data from web sessions sits apart from purchase history. Email engagement metrics live in a separate system. Loyalty programme data is transactional only — no visibility into broader relationship signals like support interactions or content consumption.
This fragmentation means AI models trained on incomplete data produce generic outputs. A customer who browsed hiking gear three times might still see kitchen appliances because the browsing data never reached the recommendation engine. SAP's initiative aims to unify these data sources so AI can act on a complete picture — not a fragmented one.
Why Execution Layer Matters More Than Strategy
Most enterprises already have personalisation strategies. The failure is operational: the systems cannot execute at the required scale. SAP is focusing on the execution layer — the infrastructure that actually delivers personalised interactions in real time. This is a shift from "what we want to do" to "what the system can actually do."
For customers, the difference is tangible. Instead of receiving a generic "we miss you" email on a fixed schedule, a user who abandoned a cart might get a relevant offer within hours — triggered by actual behaviour, not a calendar rule. Instead of loyalty points based only on spend, a frequent support caller might receive recognition for engagement, not just transactions.
What This Means for Enterprise Customer Experience
The impact is most visible in three areas: recommendation engines, marketing automation, and loyalty programmes. Recommendation engines currently show generic products because behavioural data is isolated. Marketing departments dispatch emails based on rigid schedules rather than adapting to individual user habits. Corporate loyalty programmes issue rewards based entirely on financial transactions while ignoring broader relationship metrics.
SAP's restructuring aims to connect these dots. If successful, enterprises could move from batch-and-blast marketing to behaviour-triggered personalisation. But the challenge is execution — aligning data structures across legacy systems is notoriously difficult, and AI models are only as good as the data feeding them.
Confirmed Facts vs What Remains Unclear
Confirmed: SAP is aligning fragmented commerce data structures to enable operational AI personalisation at the execution layer. The initiative addresses known enterprise failures: siloed behavioural data, calendar-based email schedules, and transaction-only loyalty rewards.
Unclear: No specific product launch, timeline, or technical architecture has been announced. It is not yet known which SAP products (SAP Commerce Cloud, SAP Customer Data Platform, or others) will be involved. The scope of the restructuring — whether it applies to all SAP commerce customers or a subset — remains unspecified.
Speculation: The initiative likely involves SAP's existing data integration and AI capabilities, but the exact implementation path is not confirmed.
Risks and Balanced View
Aligning fragmented data structures across enterprise systems is technically complex. Legacy integrations, data quality issues, and organisational silos can derail even well-funded initiatives. There is also the risk that AI personalisation, if implemented poorly, can feel intrusive rather than helpful — customers may perceive behaviour tracking as surveillance rather than service.
Critics may argue that SAP is catching up to what customer data platforms (CDPs) and specialised personalisation engines already offer. The real test is whether SAP can execute at scale across its massive enterprise customer base, where system complexity is highest.
Wider Trend: From Strategic Ambition to Operational Reality
SAP's move reflects a broader industry shift: enterprises are moving from "we want to personalise" to "we need the infrastructure to personalise." The focus is shifting from AI models to the data pipelines that feed them. Companies like Salesforce, Adobe, and specialised CDP vendors are all pursuing similar goals — unifying customer data for real-time AI execution.
The difference for SAP is its deep integration into enterprise ERP and commerce systems. If SAP can align commerce data within its own ecosystem, it may offer a more seamless path than stitching together multiple vendors. But the complexity of its own product portfolio could also be a barrier.
Practical Guidance for Enterprise Leaders
For CIOs and CMOs evaluating SAP's initiative: assess your current data fragmentation before expecting AI personalisation to work. Identify where behavioural data, transaction data, and engagement data live separately. Understand that AI models cannot compensate for broken data pipelines. Consider whether SAP's approach fits your existing infrastructure or whether a specialised CDP might be more appropriate.
For customers: expect incremental improvements rather than overnight transformation. Personalisation will improve as data silos are reduced, but the timeline depends on enterprise adoption and implementation quality.
Future Outlook
If SAP succeeds, enterprises could see a meaningful shift from generic, schedule-based marketing to behaviour-triggered, context-aware personalisation. Loyalty programmes could evolve beyond transaction-based rewards to recognise broader customer engagement. Recommendation engines could finally reflect actual user behaviour rather than incomplete data.
If execution falters, the initiative will join a long list of enterprise AI projects that promised personalisation but delivered marginal improvements. The outcome depends on whether SAP can align its own product portfolio as effectively as it aims to align customer data.
Our Take
SAP is addressing a real and painful problem: enterprises have personalisation ambitions but lack the infrastructure to execute. The focus on the execution layer — rather than another AI model — is the right priority. But the gap between strategic intent and operational reality is wide, and SAP's own product complexity adds risk. This is a story to watch, not a solution to adopt immediately. The real test will be whether SAP can deliver systematic execution at scale, not just another slide deck about AI ambition.
Frequently Asked Questions
What is SAP doing with commerce data for AI personalisation?
SAP is restructuring fragmented commerce data structures — such as behavioural data, transaction data, and engagement data — so that AI can execute personalised interactions across digital touchpoints at scale. The focus is on the infrastructure layer, not just strategy.
Why do enterprise personalisation efforts fail currently?
Because behavioural data remains isolated in separate systems. Recommendation engines show generic products, marketing emails follow calendar schedules instead of user behaviour, and loyalty programmes reward only transactions while ignoring broader relationship signals.
What will change for customers if SAP succeeds?
Customers could see more relevant recommendations, behaviour-triggered marketing communications instead of generic schedules, and loyalty programmes that recognise engagement beyond just spending. Personalisation would become more contextual and timely.
Is SAP's initiative a product launch or a strategic direction?
Based on available information, it is a strategic initiative to align data structures. No specific product launch, timeline, or technical architecture has been announced. It represents SAP's direction rather than a ready-to-deploy solution.
