The footprint at scale
A Middle East FMCG business at the scale of IFFCO, Agthia, Almarai, or Americana is running one of the most complex SAP landscapes in the region. The industry-solution coverage spans the consumer-products end-to-end processes — idea-to-market, procure-to-pay, plan-to-produce, produce-to-deliver, record-to-report — across multiple manufacturing facilities, multiple distribution centres, multiple sales channels, multiple regulatory jurisdictions, and multiple currencies. The IFFCO deployment, documented in the global integrator's case material, covers 32 offices and 30 manufacturing facilities across 10 countries on a cloud-based SAP S/4HANA template.
The deployment works. The investment is meaningful and the operational uplift the standardisation provides is real. The conversation worth having is not whether the deployment was the right move. The conversation is what the operating cost trajectory looks like across the next three renewal cycles, and which of the modules across the estate have the highest cost-to-value ratio for ownership.
This piece is the working REFORGE pattern for the Middle East FMCG CFO.
The module map
The SAP estate at a Middle East FMCG business typically covers the following module footprint.
The core financial backbone — FI, CO, the consolidation modules, the regulatory-reporting surfaces. This is the institutional system of record for the financial workflow.
The supply-chain planning surface — APO or IBP. The demand planning, the supply planning, the production planning, the deployment planning. These are the workflows the supply-chain organisation runs against.
The manufacturing execution and production surfaces — PP, the manufacturing-execution module if the enterprise runs SAP MES, the quality-management module. These are the workflows the plant teams operate against.
The materials management and procurement surfaces — MM, Ariba if the enterprise has activated it. These are the workflows the procurement and logistics teams operate.
The sales and distribution surfaces — SD, the trade-promotion-management module if the enterprise has activated TPM, the customer-relationship-management surface. These are the workflows the commercial team runs.
The warehouse management surface — EWM or the legacy WM. These are the workflows the distribution and warehouse teams run.
The integration footprint connects all of these to the enterprise's broader stack — the demand-signal-sensing layer, the trade-spend analytics, the route-to-market platforms, the consumer-data layer, the e-commerce integration, the regulatory-reporting integration.
The licence and integrator cost across this footprint compounds. The cost-to-value ratio varies meaningfully across modules.
Which modules are the candidates for ownership
Three module families have the highest cost-to-value ratio for ownership at the typical Middle East FMCG business.
The supply-chain planning surface. APO and IBP are products engineered against a manufacturing-flavoured demand-shape that the Middle East FMCG business's reality does not match cleanly. The Ramadan-shifted purchasing windows, the salary-cycle pulses, the regional weather elasticities, the cross-jurisdiction trade dynamics — each is an exogenous feature the standard products handle through configuration or through manual override. The owned-workflow stack — covered separately in our demand-forecasting piece — handles these as first-class inputs. The module's licence cost is the smallest line on the bill the enterprise could reduce.
The trade-promotion-management surface. The TPM module handles the structured trade-spend workflow, the promotion-planning surface, and the post-promotion-evaluation analytics. The Middle East FMCG trade-spend reality is the largest line on the marketing P&L at most enterprises. The standard TPM module surfaces the workflow. The actual optimisation work — the spend-allocation against the retailer-and-segment mix, the elasticity-driven scenario planning, the post-promotion uplift attribution — runs in working sessions outside the module. The owned-workflow agent absorbs this directly.
The customer-relationship-management surface. The CRM module at most FMCG businesses is the institutional commercial system. The Middle East reality is that the customer base is the modern-trade retailers, the general-trade distributors, the foodservice accounts, and the institutional buyers. The standard CRM data model fits this imperfectly. The owned-workflow stack — built against the enterprise's actual customer-relationship taxonomy — handles the customer-success workflow, the trade-term management, the institutional-account relationship, and the channel-conflict resolution at the right shape.
What stays with SAP
The financial backbone. The general ledger. The consolidation. The regulatory reporting. The corporate-side procurement workflow. The financial-side of the manufacturing accounting. The auditor's view of the firm does not change.
The manufacturing-execution surface stays at most enterprises in the first cycle of the REFORGE. The production-planning workflow stays through the same cycle. These modules are working at the enterprise's reality, the integrator's retainer on them is manageable, and the operational risk of moving them is materially higher than the cost-to-value ratio justifies in the first sequence.
The REFORGE sequence
The sequence runs as workflow-led sprints, each two to four weeks of build and one to two months of parallel-run validation.
Sprint one — the supply-chain planning surface. The demand-forecasting agent, the supply-planning surface, and the deployment-planning workflow move to owned software. The APO or IBP module continues to receive the structured plan during the parallel run. The module retires at the next renewal in proportion to the workflows that have moved.
Sprint two — the trade-promotion-management surface. The promotion-planning workflow, the trade-spend allocation, and the post-promotion analytics move to owned software. The TPM module retires.
Sprint three — the customer-relationship surface. The customer-success workflow, the trade-term management, the institutional-account relationship, and the channel-conflict resolution move to owned software. The CRM module retires.
The financial backbone, the manufacturing-execution, and the warehouse-management modules continue to operate on SAP. The licence at the end of the sequence reflects the smaller surface area.
The Middle East dimension
Three dimensions matter at a Middle East FMCG business.
The category-mix complexity. Middle East FMCG businesses run across food, beverages, household products, personal care, and increasingly the adjacent categories. The owned-workflow stack handles the category-specific differences through configuration the enterprise's team owns.
The regulatory-jurisdiction density. The Middle East FMCG business works across multiple regional regulatory frameworks plus the broader MENA and African markets. The owned-workflow stack respects this through architecture the regulatory team operates against.
The trade-promotion economics. The trade-spend is the largest controllable line on the marketing P&L. The owned-workflow stack changes the economics of the optimisation directly.
The saasinator perspective
The argument is not against SAP. The financial backbone is the right system of record. The argument is that the supply-chain planning, the trade-promotion workflow, and the customer-relationship surface are workflows the FMCG business's reality does not match the standard product cleanly, and the owned-workflow stack delivers the operational outcome at materially better economics.
What to bring to the diagnostic
Bring the SAP module breakdown, the integrator retainer, the supply-chain forecast-accuracy history, the trade-promotion analytics archive, and the commercial-team's customer-relationship taxonomy. The diagnostic is ten working days. The output is the sprint recommendation, the architecture sketch, and the first-quarter scope. Book a diagnostic at /diagnostic.