Salesforce Commerce Cloud WebDAV: Orders to SAP as IDoc

Getting Orders from Salesforce Commerce Cloud to SAP as IDoc

Salesforce Commerce Cloud WebDAV integration writes each order as a file to a WebDAV server, so middleware can pick it up, convert it to an ORDERS05 IDoc, and send it to SAP ERP. This guide covers how the flow works and when to use newer API alternatives instead.

In today's retail environment, businesses need to engage customers across multiple channels and devices. Salesforce Commerce Cloud (formerly Demandware) gives retailers a consistent shopping experience across every touchpoint, including mobile apps and websites. Commerce Cloud combines content management, e-commerce application development and order management into one platform for selling online, in retail stores and through call centers.

Table of Contents

What Is Salesforce Commerce Cloud?

Salesforce Commerce Cloud helps you run your entire commerce operation in one place, from marketing and merchandising to fulfillment and customer service. It gives you the tools to build personalized customer experiences across mobile, web and social channels while driving sales and increasing customer loyalty. With Commerce Cloud, you can:

Create powerful, personalized shopping experiences across online, mobile and social channels.
Automatically manage inventory and orders.
Deliver a seamless omnichannel customer experience across every touchpoint.
Provide personalized recommendations based on a customer's purchase history.

Salesforce Commerce Cloud WebDAV: Getting Orders to SAP as an IDoc

Salesforce Commerce Cloud has an option to write each order as a file to a WebDAV server. WebDAV works like SFTP in this context: your integration watches the WebDAV directory, maps and converts each order file into an ORDERS05 IDoc, and sends the IDoc to your SAP ERP system.

How the WebDAV File Flow Works

Commerce Cloud exports each completed order as a file to a designated WebDAV folder.
Your integration layer (SAP Integration Suite, SAP PI/PO, or another middleware) polls or watches that folder for new files.
The integration maps the order file's fields to the ORDERS05 IDoc structure: header data, line items, ship-to and bill-to addresses, and payment references.
The middleware sends the mapped IDoc to your SAP ERP or S/4HANA system, where the sales order is created.
Your team monitors the IDoc status in SAP (transaction WE02 or WE05) to confirm the order posted without errors.

Is WebDAV Still the Right Choice in 2026?

WebDAV file access remains a supported part of B2C Commerce for viewing, uploading and downloading files through Business Manager or a third-party WebDAV client. For broader API access, however, Salesforce recommends the newer B2C Commerce API (also called SCAPI) over the older Open Commerce API (OCAPI) for all new projects and major refactoring work. Salesforce has also deprecated its own B2C Commerce Data and Shop connectors in favor of a generic HTTP connector approach for tools such as MuleSoft.

The table below summarizes when each approach fits.

Method	How it moves order data	When to use it
WebDAV file drop	Commerce Cloud writes each order as a file to a WebDAV folder; middleware picks it up and converts it to an IDoc	Simple, file-based integrations where near-real-time is not required
OCAPI (Open Commerce API)	REST API for reading and writing Commerce Cloud data	Legacy integrations; Salesforce recommends moving new work off OCAPI
SCAPI (Salesforce B2C Commerce API)	Salesforce's current standard REST API for B2C Commerce	New integrations and any major refactor of existing OCAPI-based work

In practice, this means: if you already have a working WebDAV-to-IDoc flow for order files, it continues to work and does not need an urgent rework. If you are starting a new integration or need real-time order or inventory data beyond simple file drops, build it on SCAPI rather than OCAPI.

What Should You Check Before Building This Integration?

Confirm your WebDAV credentials and folder permissions in Business Manager before setting up the polling job.
Map every required ORDERS05 field, including line items, addresses and payment references, and test with representative order variations, such as split shipments, promotions and gift orders.
Plan for error handling: decide what happens to a file that fails IDoc mapping, and how you will reprocess it without duplicating the order in SAP.
If you expect high order volumes, confirm the WebDAV polling interval and file cleanup process will not create a backlog.
Agree on a retry and alerting policy so a failed file does not sit unnoticed for days.

If you are using SAP Integration Suite, check out our adapter for SAP Cloud Integration. If you need professional help with this integration, contact us.

Frequently Asked Questions

Does Salesforce still support WebDAV for B2C Commerce?

Yes. WebDAV file access is still part of Salesforce B2C Commerce for viewing, uploading and downloading files through Business Manager or a third-party WebDAV client.

Should I use OCAPI or SCAPI for a new Commerce Cloud integration?

Use SCAPI (the B2C Commerce API) for new projects and major refactors. Salesforce positions OCAPI as the legacy option and recommends moving off it where practical.

What IDoc type is used for Commerce Cloud orders in SAP?

The ORDERS05 IDoc type is the common choice for mapping Commerce Cloud order data into SAP ERP as a sales order.

Can I use SAP Integration Suite instead of custom middleware for this flow?

Yes. SAP Integration Suite can watch the WebDAV folder, or connect via SCAPI for newer builds, and handle the mapping and IDoc delivery, which reduces the custom code you need to maintain.

Conclusion

WebDAV remains a workable way to move Salesforce Commerce Cloud orders into SAP as IDocs, especially for existing integrations. For new work, evaluate SCAPI alongside it. Contact MDP Group if you need help implementing or troubleshooting this integration.