What moves between Drupal and SAP
Drupal is a content management system; with the Drupal Commerce module it can also run a store. Which SAP you run matters only on the ERP side. SAP Business One is reached through its Service Layer, while S/4HANA publishes OData APIs on the SAP Business Accelerator Hub and ECC is usually reached through BAPIs and IDocs.
Either way, SAP stays the record for products, prices, stock and customers. Drupal presents that data and collects what visitors send back, from account registrations to orders placed through Drupal Commerce.
Drupal
Where content is published and visitors act
- Content entities (nodes)
- Users
- Drupal Commerce products
- Drupal Commerce orders
SAP
Business One, S/4HANA or ECC
- Items or materials
- Prices and stock
- Customers (business partners)
- Sales orders
- Deliveries and invoices
Drupal to SAP record mapping
Drupal names as Drupal and Drupal Commerce use them; SAP names are plain descriptions, because Business One, S/4HANA and ECC name their objects differently. Discovery fixes the details for your SAP.
| Drupal | SAP | Direction |
|---|---|---|
| Content entity (product page) | Item or material | SAP to Drupal |
| Drupal Commerce product and price | Item price and stock | SAP to Drupal |
| User | Customer (business partner) | Both ways |
| Drupal Commerce order | Sales order | Drupal to SAP |
| Order status on the site | Delivery and invoice | SAP to Drupal |
How the Drupal sync runs
Product content from SAP
Connect reads products from SAP and writes them into Drupal through the JSON:API module in Drupal core, which gives create, read, update and delete access to Drupal's content entities. Technical data, prices and availability stay in step with the ERP, while marketing copy written in Drupal is left alone.
Drupal Commerce orders into SAP
If the site sells, each completed Drupal Commerce order is mapped to an SAP sales order with its customer, lines and shipping address. Delivery and invoice status from SAP can then be written back to the order, so customers see progress in their account on the site.
Customer accounts matched to SAP
A new registration can be matched to an existing SAP customer or queued for your team to approve before an account is created. Once linked, the customer's own prices and order history can follow them onto the site.
See Clarity Connect move an order
Watch an online order travel into the ERP and its status come back in our Clarity Connect demo, or book a live walkthrough on your own systems.
Drupal versions to plan around
Drupal 10 reaches end of life on December 9, 2026, and Drupal 12 is scheduled for release the same week, so a new integration should target Drupal 11 or later. Drupal Commerce 3.x supports Drupal 10.3 and 11. Drupal Commerce also has a Commerce API module that extends JSON:API, but it has no stable release yet, so order data may need a custom endpoint instead.
Drupal 7 security support ended on January 5, 2025. If your site is still on Drupal 7, plan the upgrade before connecting it to SAP rather than integrating twice.
How Clarity Connect runs it
Clarity Connect is Clarity's integration platform. It holds a two-way connection between Drupal and SAP and runs each flow as a separate task, as events happen or on a set schedule. Connect is asynchronous, so if SAP is down for maintenance, orders from the site wait in the queue and are retried instead of disappearing. Clarity has built more than 3,000 integrations on it; recorded demos are in the Clarity Connect video playlist.
Discovery
A Clarity business analyst documents the data fields and workflows each system can share and which ones you need.
Tasks and mapping
Each flow becomes a Connect task, such as orders to the ERP or stock to the store, set to run in real time or on a schedule.
Testing
Orders and updates are run end to end, including the return trip of statuses back to the customer-facing system.
Live, with a dashboard
Queues and scheduled tasks show in Connect's Hangfire dashboard. A job whose target is offline is retried 10 times, every 30 minutes, and can be re-queued once the cause is fixed.
Clarity Connect is sold as a SaaS subscription at $599 a month or as a one-time license at $15,000 with no ongoing fees, and larger projects are priced to scope. See pricing.
Questions
Which SAP does this work with?
Business One, S/4HANA or ECC. The Drupal side doesn't change; Connect uses the interface your SAP offers, such as Business One's Service Layer or S/4HANA's OData APIs.
Do we need Drupal Commerce?
Only if the site takes orders. A product or dealer site can run on Drupal core, with SAP supplying the product data through JSON:API.
We're on Drupal 10. Is that a problem?
Drupal 10 reaches end of life on December 9, 2026. It's worth moving to Drupal 11 before or alongside the integration, so it isn't built against a version that's about to lose support.
Related resources
Connect Drupal and SAP
Tell us which SAP you run and what your Drupal site needs from it. A Clarity business analyst will map the content, customers and orders with your team before anything is built.
Book a demo
