01 / backbone
SAP S/4HANA is the ledger
Finance, plants, condition-record pricing, the order-to-cash document chain. The authoritative record the business is run on.
SAP runs the business. The store runs the customer. The work is the space between.
SAP S/4HANA holds finance, plants, condition-record pricing and the order-to-cash chain. Shopify is where B2B buyers self-serve. The middle is where it breaks: duplicate customers, orders written twice, pricing that drifts, silent failures at month-end close.
02 / front door
Shopify is self-serve
Where B2B buyers place repeat orders without a phone call, a rep, or an EDI batch.
03 / the gap
The middle is where it breaks
Duplicate customers. Orders written twice. Pricing that drifts. Silent failures at month-end close.
Our position
The Makro Middleware platform runs in production today. SAP S/4HANA plugs into it as a first-class adapter, its path fully mapped against SAP's released OData surface.
One direction for master data. Both directions for orders.
Business partners, products, ATP inventory and pricing are read out of SAP and pushed to Shopify. The storefront never writes to the ledger. Orders are the only thing that travels both ways, and a Shopify order becomes a full SAP document chain.
System of record
SAP S/4HANA
read · never overwritten
The platform
Makro Middleware.
map · reconcile · audit
The storefront
Shopify Plus B2B
where buyers self-serve
Master data: SAP → Makro Middleware → Shopify, one way
Orders: Shopify → SAP, status returns
OData v4 servicesA layered API surface, not a single API. The named commerce services carry the load:
API_BUSINESS_PARTNER, API_PRODUCT_SRV, API_MATERIAL_STOCK_SRV, read out of SAP and normalized before they reach Shopify.SAP → MKDeep-insert order writeA Shopify order becomes a SAP sales order in one transactional POST.
API_SALES_ORDER_SRV only supports a deep insert: header plus line items plus partners plus pricing together. A header-only create is not supported.Shopify ↕ SAPEnterprise Event EnablementSAP announces a change instead of being polled. A CloudEvents notification (
SAP_COM_0092) carries only the key, so the platform then calls the OData API for full state. Delta queries are the fallback.SAP → MKCommunication ArrangementNothing is callable until a Communication Arrangement binds a scenario. The platform authenticates as a single Communication User over OAuth 2.0 client credentials or X.509 mTLS, scoped to the whitelisted commerce scenarios and nothing else.handshake
Order-to-cash chainAn order does not stand alone; SAP turns it into a document chain. Sales order, then outbound delivery, then goods issue, then billing document, with returns referencing back up the chain. The platform maps every link.Shopify ↕ SAP
The three ways to connect SAP S/4HANA and Shopify, and when each is right.
There are three ways to connect Shopify to SAP S/4HANA: the official SAP Integration Suite accelerator, a third-party iPaaS connector like APPSeCONNECT, Celigo, or Alumio, and a custom-built integration maintained by a Shopify Plus development partner. The right method is decided by S/4HANA edition, B2B pricing complexity, and how many plants and company codes route through your store, not by price alone.
Option 01
SAP Integration Suite accelerator
SAP's own "Shopify Integration with SAP S/4HANA Cloud" package on the Business Accelerator Hub. A template set of Cloud Integration iFlows, B2C-first, competent on the happy path.
- needslicensed Integration Suite on BTP
- targetsS/4HANA Cloud Public Edition
- failure pathmonitoring and retry are yours
- B2Ba DIY partner extension
Right for standard order-to-cash on S/4HANA Cloud Public Edition where the B2C happy path is enough.
Option 02
Third-party iPaaS (APPSeCONNECT, Celigo, Alumio)
Subscription middleware on a shared platform with pre-built SAP adapters. Strong for templated multi-system sync across many endpoints.
- mappingsconfigurable, template-bound
- tenancyshared platform, row filtering
- pricingannual fee, grows with volume
- SAP depthcondition pricing often shallow
Right for templated multi-system sync where the SAP B2B logic fits a fixed-mapping template.
Option 03 · our build
Custom middleware
Built around your exact order flow and SAP configuration, owned by you, operated with a support agreement. Where Plus and B2B manufacturers end up.
- mappingscondition pricing to price lists
- tenancysingle-tenant, isolated per client
- recovery7 failure classes, DLQ, replay
- scopemulti-plant, multi-company-code native
Right for B2B condition pricing, multi-plant inventory, company-code routing, on-prem or Private Cloud S/4HANA, or high B2B complexity a fixed-mapping connector cannot model.
Where off-the-shelf SAP to Shopify connectors break.
SAP S/4HANA ⇄ Shopify integrations break at the same predictable points. The official accelerator and most iPaaS templates handle the happy path and skip these. A custom middleware layer is built to handle all of them, explicitly.
Condition-record pricing to B2B price lists
SAP price is a runtime computation over the condition technique: customer-, material-, and scale-based condition types, resolved per order type and customer. Shopify Plus B2B resolves by a fixed price-list entry on the buyer's catalog. These are structurally different, and standard connectors skip the mapping. We flatten the right condition level into a Shopify catalog per company.
→ explicit mapping per condition type, plus live checkout simulationMulti-plant inventory & StorageLocation mapping
Inventory in S/4HANA is managed at the plant level, and API_MATERIAL_STOCK_SRV returns physical stock that is read-only and ignores open orders. Publish that and you oversell. The sellable number is the ATP availability-check quantity, a dynamic projection, mapped per plant and storage location to a Shopify Location.
Company-code order routing
Orders route through company codes, and the same SKU legitimately carries a different price, tax, and even pricing procedure across sales organizations. The middleware must send the correct sales-area context on every call, or it gets a valid price that is the wrong price. A generic connector does not model this.
→ correct sales-area context on every callMulti-currency & single price per product
SAP holds a condition currency per record distinct from the document currency, and converts between them using a configured exchange-rate type after the multiplication. A nightly sync against converted prices lags the true rate and produces penny variances. We let SAP resolve the price in the document currency rather than re-implement SAP's conversion and rounding.
→ SAP resolves the document-currency price by simulationNon-idempotent order POST
A plain OData POST is not idempotent: a retry after a timeout creates a second sales order, and SAP assigns the document key itself. The Shopify order id rides in PurchaseOrderByCustomer as a correlation field, not a dedup guarantee. Reliable idempotency needs a middleware idempotency-key store with a unique constraint.
iPaaS throttling at peak
SAP publishes no universal requests-per-second limit; it gives per-API parallelism guidance and hard limits, including a custom OData fetch ceiling of 5,000 records that cannot be raised. Sustained over-calling can get API access temporarily blocked. A connector that hammers SAP on every page view hits this. We design with backoff, events, and scheduled deltas from day one.
→ exponential backoff, events over polling, scheduled deltasThis is not a connector. It is something you operate.
Every sync, every failure, every reconciliation is visible. This is the same Makro Middleware console your team would watch in production. Move through the views.
console.makro.agency / meridian-manufacturing / sync
live
Sync Monitor
Sync Monitor
Dead Letter Queue
Observability
Entity Key Map
Schedules
Order Relations
Records / 24h ▲
48,210
across 9 entities
Queue depth
3 pending
2 retrying · 1 review
Avg latency
1.2s
event → Shopify
Last reconcile
04:00
0 drift detected
Activitylive · last 60s
Throughputrecords / hr
In queue
3
of 48,210 processed
Auto-retrying
2
transient · rate-limit
Needs review
1
permanent
Resolved / 24h
41
38 auto · 3 manual
Dead Letter Queuenothing is dropped in silence
| Time | Entity | Error class | Attempts | Next | Action |
|---|---|---|---|---|---|
| 08:13:04 | sales order · 0000010288 | PERMANENT · validation | 3 / 3 | held | Inspect |
| 07:55:22 | business partner · 1000910 | TRANSIENT · timeout | 2 / 5 | 09:50 | Retry now |
| 06:40:11 | product · MAT-44120 | RATE_LIMIT · paced | 1 / 5 | paced | Inspect |
Sync volume7-day · records
Circuit breakersper endpoint
SAP · ODatalast trip · never
closedShopify · Admin APIlast trip · 3d ago
closedEvent Enablementlast trip · never
closedUptime · 90 dayserror rate 0.03%
business partner · Meridian Westentity_key_map
SAP BP0001004182
canonical8f2a-c1d9-4e07-44b0
shopify gidgid://shopify/Company/61…
checksuma91f… unchanged
versionv17
→ decision: SKIP · already in sync
Every record carries three identities at once. The middleware reads this row before every write and decides create, update, or skip.
Sync a record twice and it updates. SAP owns the document key, so the Shopify order id rides in PurchaseOrderByCustomer as correlation while the platform dedupes on its own key. This is what stops duplicate business partners and double-posted orders before they reach your ledger.
Change detection runs on the stored checksum, so a catalog of 50,000 materials with 12 real edits syncs 12 records, not 50,000.
Active schedules
7
all workflows enabled
Runs today
96
0 failures
Next run
09:46
ATP levels
Nightly batch
01:00
full catalog · 48,210 records
Workflowstenant · meridian
Product delta syncAPI_PRODUCT_SRV · watermarkedevery 15 min✓ 09:38 · 142 recordsnext 09:53Run now
ATP inventory levelsper plant → Shopify Locationevery 5 min✓ 09:41 · 3 SKUsnext 09:46Run now
Price listscondition cube · per companyhourly✓ 09:00 · 1,204 rowsnext 10:00Run now
Business partnersAPI_BUSINESS_PARTNER · deltaevery 15 min✓ 09:40 · 6 recordsnext 09:55Run now
Order status returnSAP → Shopifyevery 5 min✓ 09:42 · 11 ordersnext 09:47Run now
Full catalog batchscheduled bulk exportnightly · 01:00✓ 01:00 · 48,210 recordsnext 01:00Run now
Daily reconciliationboth systems vs key mapdaily · 04:00✓ 04:00 · 0 driftnext 04:00Run now
Shopify order#1042
gidgid://shopify/Order/57…
companyMeridian West
line 1MAT-99320 × 12
line 2MAT-44120 × 4
total$8,420.00
#1042↔SO 0000077231✓
gid://Company/88…↔BP 0001004182✓
MAT-99320 × 12↔99320 · qty 12✓
MAT-44120 × 4↔44120 · qty 4✓
$8,420.00↔8,420.00 USD✓
entity key map · every id matched before write
SAP sales order0000077231
SalesOrder0000077231
SoldToParty0001004182
item 1099320 · qty 12
item 2044120 · qty 4
statusconfirmed
Order journey#1042 → SO 0000077231 · 5s end to end
09:42:04webhook received→
09:42:04HMAC ✓ · dedup ✓→
09:42:05deep insert built→
09:42:06POST to SAP→
09:42:09SO 0000077231 confirmed→
09:42:09status → Shopify
drag, scroll, or use the tabs
Feature by feature.
Ten engineered subsystems carry every SAP S/4HANA ⇄ Shopify build. The sync engine, mapping layer, error handling and Shopify integration never change when a new ERP plugs in.
01 / 10
What you will hear, and what the docs actually say.
Every reality below is verified against a primary SAP source or a named vendor or Shopify doc. This is the difference between a team that read the marketing and a team that shipped against the documentation.
01
The claim"SAP ships an official Shopify accelerator. Install it and you're integrated."
The realitySAP's "Shopify Integration with SAP S/4HANA Cloud" package is a template set of Cloud Integration iFlows, not a managed turnkey product. It requires a licensed SAP Integration Suite tenant on BTP, targets S/4HANA Cloud Public Edition, and is explicitly built for B2C. Critically, monitoring, error reprocessing, retry policy, and reconciliation are the customer's responsibility.
02
The claim"Just read the customer's price from SAP and show it at checkout."
The realityNo SAP API returns a customer's price as a stored field. SAP price is a runtime computation over the condition technique, and the condition-record API
API_SLSPRICINGCONDITIONRECORD_SRV returns, in SAP's own words, "stored condition records and their structural metadata only, not resolved or effective prices." To get the real number you resolve it in SAP via API_SALES_ORDER_SIMULATION_SRV, or flatten the cube into Shopify price lists at sync time.03
The claim"Sync the SAP stock figure and you're good."
The realityNever push raw SAP stock to Shopify
available. API_MATERIAL_STOCK_SRV returns physical stock and is read-only; unrestricted-use stock ignores open sales orders, deliveries, and future receipts and oversells. The sellable number is the ATP availability-check quantity (warehouse stock plus planned inward minus planned outward), a dynamic projection, mapped to Shopify available.04
The claim"SAP calculates your cart tax during checkout."
The realityIt cannot. Shopify's Tax Platform is available by invitation only to select tax software companies, so a custom middleware or an ERP is not an eligible checkout-tax provider. Cart-time tax runs in Shopify Tax or an approved partner app (Avalara, Vertex); SAP computes the tax of record on the billing document via its External Tax Interface (
TAXUSX). Point both sides at the same engine so the rates reconcile.05
The claim"We'll use IDoc. It's the SAP standard."
The realityYou do not feed IDocs directly into a Cloud Public Edition tenant. Native IDoc is an on-prem and Private Cloud capability; on Cloud you land them in SAP Integration Suite and convert to OData or SOAP. New S/4HANA Cloud integrations should be built on OData, SOAP, REST, so an IDoc-native connector is a dead end on Public Cloud.
06
The claim"SAP has a requests-per-second rate limit you tune against."
The realitySAP publishes no single tenant-wide req/sec limit for S/4HANA Cloud OData. It gives per-API parallelism guidance (for example Journal Entry Post 15 parallel sync, 30 async), hard limits (OData V4 URL 8,000 chars, payload 500 MB, custom OData fetch ceiling 5,000 records, cannot be raised), and self-configured throttling. On throttling, retry with exponential backoff; sustained over-calling can get API access temporarily blocked.
07
The claim"Retry the order if it fails. The connector handles duplicates."
The realityA plain OData POST is not idempotent: a retry after a timeout creates a second sales order. SAP also assigns the document key itself, so
PurchaseOrderByCustomer, where you carry the Shopify order id, is a correlation field, not a dedup guarantee. Reliable idempotency needs a middleware idempotency-key store with a unique constraint, a GET-before-POST key check for master data, or external number ranges.08
The claim"Creating an order in SAP is a simple API call."
The realityIt is a mandatory deep insert:
API_SALES_ORDER_SRV only creates a header with its line items, partners, and pricing in one transactional POST. A header-only create is not supported. And the order cannot stand alone: SAP turns it into a document chain (sales order, outbound delivery, goods issue, billing document), with returns referencing back up the chain.09
The claim"The official accelerator handles B2B contract pricing and multi-plant."
The realityIt doesn't out of the box. SAP's accelerator is B2C-first; B2B is a DIY partner extension. SAP B2B pricing is condition records with customer-, material-, and scale-based condition types, plus customer-hierarchy discounts, and Shopify Plus B2B resolves by a fixed price-list entry. Translating SAP's hierarchy into Shopify price lists requires explicit mapping logic for each condition type in use. There is no automatic equivalent.
10
The claim"Multi-plant inventory and company-code routing just work."
The realityIn S/4HANA, inventory is managed at the plant level and orders route through company codes. The same SKU legitimately carries a different price, tax, and even pricing procedure across sales organizations, so the middleware must send the correct sales-area context on every call or it gets a valid price that is the wrong price. A generic connector does not model this.
11
The claim"A custom field in SAP means another fragile, hand-coded endpoint."
The realityUsually the opposite. A key-user custom field (the
YY1_ namespace) enabled on an extensible, released OData API and published joins that service's metadata and its GET, POST, PATCH bodies, with no new endpoint. The middleware just re-reads metadata and adds a mapping. Whole new entities (Custom Business Objects, RAP services) are the exception that needs a dedicated endpoint wrapped in a Custom Communication Scenario.12
The claim"Public Cloud and on-prem / Private Cloud S/4HANA integrate the same way."
The realityThey don't, and conflating them loses technical buyers. Cloud Public Edition is whitelisted OData and SOAP only, behind communication arrangements, no native IDoc or RFC into the tenant. On-prem and Private Cloud give the full IDoc, RFC, BAPI toolbox via Cloud Connector, plus more configuration variability. Edition is the first scoping question, not a detail.
Integrations are judged by how they fail. Follow one failed record.
It is classified before it is retried, and nothing disappears into a log file. Colour carries the verdict: amber arrives and is sorted, teal retries, red is held, green replays and reconciles.
01
It arrives
A deep-insert order write to SAP times out, or a master-data record fails to write to Shopify. Instead of disappearing into a log, it enters the pipeline.
captured→ 02
It gets classified
Every failure is sorted before anything is retried, so a bad record never loops forever and a duplicate order is never created by a blind retry.
classified→ 03
Transient retries
Timeouts and SAP throttle responses retry with exponential backoff and pacing, automatically, deduped against the idempotency key so the order writes once.
retrying→ 04
Permanent is held
A validation or permission failure routes straight to the dead-letter queue for review. It is never retried blindly or lost.
held for review→ 05
You replay it
Fix the cause, replay from the queue. A daily reconciliation pass catches anything the live path missed.
replayed · reconciledBuilt to pass your review, and your SAP Basis architect's questions.
Credentials never in plain config
SAP and Shopify secrets are held as encrypted fields, isolated per tenant and rotatable without downtime. No credential sits in plaintext, anywhere.
encrypted · rotatableInbound traffic is verified
Every Shopify webhook is HMAC-verified before it is trusted, then deduplicated by event id, so a replayed webhook cannot create a second order.
verify · dedupeLeast-privilege access to SAP
The integration authenticates as a single Communication User over OAuth 2.0 client credentials or X.509 mTLS, scenario-scoped to the whitelisted commerce APIs. On-prem, least-privilege is scoped at S_SERVICE per OData service and S_RFC per BAPI, never wildcarded, never SAP_ALL.
Everything is on the record
An append-only audit trail logs every operation, source-tagged, so you can prove what happened during month-end close.
audit · source-taggedWhere SAP S/4HANA integrations get hard, and where we land.
The details that separate a team that read the docs from a team that shipped against them. Open any one.
01How do you integrate SAP S/4HANA with Shopify?+
Three ways: the official SAP Integration Suite accelerator (the "Shopify Integration with SAP S/4HANA Cloud" package on the SAP Business Accelerator Hub, which needs SAP Integration Suite on BTP), a third-party iPaaS connector like APPSeCONNECT, Celigo, or Alumio, or a custom-built integration from a Shopify Plus development partner. The right choice depends on your S/4HANA edition, your B2B pricing complexity, and how many plants and company codes route through your store.
02What does the official SAP S/4HANA Cloud Shopify integration package cover?+
It syncs customer replication, new orders, and order cancellations and returns from Shopify to S/4HANA, and products, inventory, pricing, and delivery status from S/4HANA to Shopify, using pre-built Shopify iFlows in SAP Integration Suite. It targets S/4HANA Cloud Public Edition and standard order-to-cash. Complex B2B contract pricing, multi-plant inventory routing, on-premise and Private Cloud setups, and custom payment and tax edge cases generally need additional mapping or custom middleware.
03Where do Shopify to SAP S/4HANA integrations usually break?+
In the data-model gap between the two systems. The hardest points are condition-record pricing (S/4HANA's customer-, material-, and scale-based condition types have no automatic Shopify equivalent), plant-level inventory and company-code order routing for multi-plant manufacturers, and B2B contract pricing that Shopify's native tools and off-the-shelf connectors can't replicate. A custom middleware layer maps each of these explicitly.
04Should we use IDoc, OData, or API to connect S/4HANA to Shopify?+
On S/4HANA Cloud Public Edition you can't feed IDocs directly into the tenant; integrations use OData and SOAP through SAP Integration Suite or a custom middleware layer. IDoc still works on on-premise, Private Cloud, and legacy ECC, but an IDoc-native connector is a dead end on Public Cloud. Modern S/4HANA to Shopify builds use OData and event-based interfaces.
05How much does an SAP S/4HANA ⇄ Shopify integration cost, and how long does it take?+
A templated accelerator or iPaaS connector can go live in days to a few weeks for standard order-to-cash but requires an SAP Integration Suite or BTP subscription. A fully custom build that handles condition-record pricing, multi-plant inventory, and B2B contract logic is a larger engagement (commonly ~10 to 16 weeks) that scales with edition and complexity. We price it as an engineering engagement, scoped per build, and put the figure in writing before anything starts.
06SAP Integration Suite accelerator vs APPSeCONNECT vs a custom build, which is best?+
The official accelerator is the fastest path for standard order-to-cash on S/4HANA Cloud Public Edition. An iPaaS like APPSeCONNECT or Celigo is strong for templated multi-system sync with pre-built SAP adapters. A custom build wins when you have B2B condition pricing, multi-plant or multi-company-code routing, on-prem or Private Cloud S/4HANA, or B2B complexity a fixed-mapping connector can't model. Makro builds the custom path for Shopify Plus brands that have outgrown the accelerator or an off-the-shelf connector.
07Who builds custom SAP S/4HANA ⇄ Shopify Plus middleware?+
Makro Agency is a Shopify Plus partner that builds custom middleware between Shopify Plus and ERPs including SAP S/4HANA, for enterprise manufacturers and B2B distributors whose contract pricing, multi-plant inventory, or company-code structure exceeds the official SAP accelerator or a standard iPaaS connector.
08Which system is the source of truth, and will it touch production?+
SAP S/4HANA. Master data (business partners, products, ATP inventory, pricing) flows one way, SAP to Shopify; orders flow both ways. The storefront never writes to your ledger. Master-data syncs are read-only against SAP, order writes go through a sandbox or test tenant first, and production posting starts only when the reconciliation report says zero drift and you sign off. The append-only audit trail covers every record from day one.
A proven platform. SAP S/4HANA is the next first-class adapter.
Every ERP sits behind the same contract: authenticate, fetch master data, push orders, validate, report. The platform runs in production today against NetSuite. SAP S/4HANA is a registered target on that same framework, its path fully mapped against SAP's released OData surface: the deep-insert order model, the condition-technique pricing engine, ATP-per-plant inventory, and the communication-scenario access gate.
We say this plainly: the credibility is a real platform in production and a precisely understood, docs-backed S/4HANA path, not a live SAP deployment behind us yet. That distinction is exactly what your architect can verify, which is why we lead with it. The rest is an engagement away.
adapter contractbase.ts
01authenticate()Comm User / OAuth · mTLS
02fetchMasterData()OData v4 services
03pushOrder()deep insert
04validate()schema check
05report()audit + status
S4
SAP S/4HANA
ERP adapter · OData · deep insert
NS
NetSuite
ERP adapter · SuiteQL · token auth
Timeline by scope, not a contact-us wall.
An SAP S/4HANA ⇄ Shopify Plus build lands in one of three bands depending on edition, B2B pricing complexity, the number of plants and company codes, and how many of the break points above are in play.
Band 01 · foundation
days–weeks
templated · standard order-to-cash
- The accelerator or an iPaaS path for standard order-to-cash
- Business partners, products and ATP inventory, SAP to Shopify
- New orders and cancellations or returns, Shopify to SAP
- Requires an SAP Integration Suite or BTP subscription
Band 02 · B2B custom
10–13 weeks
Shopify Plus B2B · condition pricing
- The flattened condition cube into per-company Shopify price lists
- Live checkout simulation for the authoritative line price
- Deep-insert order writes with idempotency and the document chain
- Dead-letter queue, daily reconciliation, the console
Band 03 · multi-entity
13–16 weeks
multi-plant · multi-company-code
- Everything in B2B, plus multi-plant ATP and company-code routing
- Multi-currency with SAP resolving the document-currency price
- On-prem or Private Cloud edition via Cloud Connector
- Custom fields and custom entities through the mapping engine
Cost · scoped per build
We price an SAP S/4HANA integration as an engineering engagement: a build with a support agreement, not a per-record meter or a platform seat that renews forever. For market context, a templated accelerator or iPaaS path can go live in days to a few weeks for standard order-to-cash but carries an SAP Integration Suite or BTP subscription, while a fully custom build that handles condition-record pricing, multi-plant inventory and B2B contract logic commonly runs ~10 to 16 weeks. Your exact figure is scoped to the band and the break points in play, and we put it in writing before anything starts.
Claims you can check.
1,756
Test suite · run on every changeAutomated tests across 139 suites, run on every change. Counted in the repository, not rounded for the slide. No code reaches your production data without passing them.
85%
Coverage gate enforced before any deploy.
39
End-to-end browser tests, Chromium, Firefox, WebKit.
7
Failure classes, each with its own pre-decided policy.
0
Credentials stored in plaintext, anywhere, ever.
Multi-system proof
This is our NetSuite and Salesforce work; the SAP S/4HANA path is built on the same platform and the same engineering standard. For Clarius, Makro built a unified account page integrating NetSuite ERP, Salesforce CRM and Shopify Plus into a single view of orders and invoices across three enterprise systems, with Shopify Flow automation feeding order data into the ERP, eliminating manual order entry and reducing operational costs by over $100,000 annually. It is evidence that Makro builds reliable multi-system ERP to Shopify integrations.
Bring your SAP Basis architect and your renewal quote. We will walk the platform, not a deck.
A real conversation about your S/4HANA edition, your condition pricing, your plants and company codes, and the three sharp questions you already have.