SAP problems we see in retail
Retail SAP landscapes tend to grow one channel at a time. Each new channel gets its own interface, and the merchandise system ends up reconciling rather than leading.
SAP that sees every store and every channel the same day. We migrate SAP IS-Retail to S/4HANA Retail, connect POS, e-commerce and marketplaces through clean integration, and fix the batch jobs and custom code that keep store inventory a day behind. Senior SAP and integration engineers own the design, AI coding agents carry the volume, and every line is reviewed by a human.
Key highlights
Retail SAP landscapes tend to grow one channel at a time. Each new channel gets its own interface, and the merchandise system ends up reconciling rather than leading.
We cover the merchandise management core and the integrations that connect SAP to stores, distribution centres and digital channels.
Article master with generic articles and variants, site master for stores and distribution centres, merchandise categories, listing and assortments, retail pricing and promotions, configured as close to SAP standard as your business allows.
POS transaction logs into SAP Customer Activity Repository and POS Data Transfer and Audit, aggregated for inventory and financial posting in S/4HANA, with monitoring so rejected transactions are fixed the same day, not at month end.
Replenishment parameters per store and article, allocation of new season and promotional stock, and store orders that work from near real time sales instead of last night's batch.
SAP EWM for retail distribution centres: inbound from suppliers, putaway, wave picking for store deliveries and e-commerce orders, cross docking and returns, integrated with S/4HANA stock and deliveries.
Orders, stock availability, prices and product content synchronised between SAP and platforms such as SAP Commerce Cloud, Shopify, Adobe Commerce and marketplaces, through SAP Integration Suite or your existing middleware.
Usage analysis of IS-Retail custom code and interfaces, then each one is retired, adapted to S/4HANA simplifications, or rebuilt as a clean extension on SAP BTP, so the next upgrade is not another rewrite.
We review article and site master quality, custom code usage, POS and channel interfaces, and your replenishment and month end processes. Output: a written migration approach, scope and risk list.
Fit to standard workshops for merchandise management, pricing, replenishment and DC processes, a target integration architecture for POS and channels, and a decision on every custom object.
Configuration, interface build, extensions on SAP BTP and repeated mock data loads. A pilot group of stores and one distribution centre go live first, with POS reconciliation checked daily.
Hypercare through the first trading peak, then ongoing support with agreed response times. We roll out to remaining stores and add forecasting, analytics or new channels once the core is stable.
Retail SAP systems handle payment related data, customer data and high volumes of invoices. We design for the obligations that touch SAP directly.
Card data stays out of SAP. We design POS and e-commerce integrations so that only tokens and settlement data reach SAP, never full card numbers. That keeps SAP out of PCI DSS cardholder data scope and makes audits simpler.
Customer data is minimised and traceable. Loyalty, click and collect and returns data in SAP is limited to what each process needs, with retention rules and blocking that support GDPR and UK GDPR erasure and access requests.
E-invoicing mandates are designed in. Belgium made structured B2B e-invoicing mandatory from 1 January 2026, France started its phased mandate in September 2026, and Germany phases in issuing obligations from 2027. We plan supplier and customer invoice formats with SAP Document Compliance or your chosen provider.
Standard SAP retail scope first, with integration tooling that keeps stores and channels decoupled from the core.
Tell us about your stores, channels and SAP landscape. Written scope, timeline and estimate within 48 hours.