Data Loading in SAP Commerce Cloud: ImpEx, Hot Folders and APIs

SAP Commerce Cloud gives you four ways to get data in. ImpEx for bulk loads. Cloud Hot Folders for scheduled, file-based feeds. OCC REST APIs for real-time, single-record changes. SAP Integration Suite when a flow spans several systems, typically Commerce and the ERP. Picking the wrong one rarely breaks anything on day one, but the implementation gets slower and harder to maintain with every release.

Below is how each method works, where it fits, and the mistakes we most often find when we take over an existing Commerce Cloud project.

TL;DR: Use ImpEx for initial loads, migrations and environment setup. Use Cloud Hot Folders for recurring file feeds from a PIM, WMS or ERP. Use OCC APIs when a user action changes a handful of records. Use SAP Integration Suite for orders, prices and master data that flow between Commerce Cloud and S/4HANA. Decide by volume, frequency and whether the change has to happen in real time.

What is ImpEx and when should you use it?

ImpEx (Import/Export) is the text-based import and export engine that ships with SAP Commerce. It reads CSV-like files whose header lines map to item types and attributes, and it creates, updates, removes or exports platform items such as products, customers or orders (SAP Help: ImpEx). Simple concept, surprisingly deep. Almost every Commerce Cloud implementation starts here, and every developer on the team should know it well before touching anything else.

What ImpEx does well:

• Initial data migration: loading thousands of products, categories and customers from a legacy system
• Environment setup: seeding development and staging environments with test data
• Content updates: batch changes to prices, stock levels and product descriptions
• Configuration: CMS pages, site configuration, user groups

ImpEx syntax example:

INSERT_UPDATE Product; code[unique=true]; name[lang=en]; catalogVersion(catalog(id),version)
; PROD001 ; Widget A ; productCatalog:Staged
; PROD002 ; Widget B ; productCatalog:Staged

Where ImpEx is the wrong tool: anything real-time. It is batch-oriented and runs scripts against the database. If one product price has to change because a customer did something, use the OCC API instead. SAP’s own ImpEx import best practices are worth reading before the first large import.

How do Cloud Hot Folders work?

Hot Folders automate recurring imports without integration code. In SAP Commerce Cloud (the SAP-hosted version) they run as Cloud Hot Folders: instead of a local or shared directory, files land in Microsoft Azure Blob Storage, and the platform picks them up from there (SAP Help: Cloud Hot Folders). If you are moving from an on-premise installation with classic Hot Folders, plan that switch as part of the migration.

How the process goes:

1. An external system or scheduled job uploads a file (typically CSV, optionally zipped) to the Blob Storage container
2. Commerce Cloud moves it to a processing area and picks it up
3. A converter maps the raw data to ImpEx
4. The platform runs the ImpEx import
5. Processed files are archived; failed files end up in an error location

Typical use cases:

• Scheduled inventory updates from a warehouse management system
• Price feeds from the ERP on a fixed schedule
• Product catalogue syncs from a PIM tool that exports files
• Media imports: bulk image uploads with metadata mapping

Always set up error handling. Hot Folders fail quietly: if nobody watches the error location, failed imports pile up unnoticed. On one project we took over, catalogue files had been failing for weeks before anyone noticed missing products in the shop. Use the Cloud Hot Folder monitoring in Backoffice and add an alert on failures. It is the most common Hot Folder mistake we see.

When should you use OCC APIs?

OCC (Omni Commerce Connect) APIs are the REST endpoints that expose Commerce Cloud’s commerce functions to anything that can call REST (SAP Help: Omni Commerce Connect). SAP Composable Storefront runs entirely on them. They are also the right choice for:

• Custom storefronts in React, Vue or Next.js (we compare the options in SAP Composable Storefront vs React and Next.js)
• Mobile apps: native iOS or Android apps reading cart, checkout and product data
• Third-party integrations: POS systems, kiosks, partner portals
• Single-record operations: updating one product’s price or one customer’s address

The rule of thumb I give our developers: fewer than about 100 records in response to a user action, use the API. Thousands of records on a schedule, use ImpEx or Hot Folders.

How does SAP Integration Suite fit in?

SAP Integration Suite on SAP BTP comes in when Commerce Cloud has to talk to several enterprise systems, above all the ERP.

Common Integration Suite flows:

• Order replication: orders placed in Commerce Cloud flow to S/4HANA for fulfilment, invoicing and accounting
• Real-time pricing: checkout asks S/4HANA for customer-specific prices and available-to-promise (ATP) stock
• Customer master sync: new accounts in Commerce Cloud become business partners in S/4HANA
• Product master data: attributes, classifications and hierarchies flow from S/4HANA into Commerce Cloud

SAP ships prepackaged integration content for the most common Commerce-to-S/4HANA flows (the SAP Commerce Cloud Integration Extension Pack and the integration packages on the SAP Business Accelerator Hub). They are not plug-and-play: you still configure and map. But they save a large share of custom integration work. How this looks with S/4HANA Public Cloud as the ERP core is covered in SAP Commerce Cloud and S/4HANA Public Cloud for B2B.

What are the most common data loading mistakes?

The mistake we see most often: teams run everything through ImpEx, including operations that should clearly be API calls. The others follow close behind.

Loading too much data at once. Full catalogue imports during business hours compete with live traffic for resources. Schedule bulk imports in off-peak windows and load incrementally: only changed records.

Skipping data validation. ImpEx will import malformed data that then breaks the storefront. Validate before import: required fields, data types, referential integrity. Commerce Cloud will not stop you from importing a product that references a category that does not exist.

Ignoring Hot Folder error handling. Failed files sit in the error location, and nobody is notified unless you set it up.

Using ImpEx for real-time updates. Running ImpEx scripts in response to individual user actions creates performance bottlenecks and race conditions. Use OCC APIs for real-time single-record changes.

Not testing data loads in staging. Run ImpEx scripts and Hot Folder configurations in staging first. A faulty script can corrupt product data that takes hours to clean up.

Planning a larger migration, or want a second opinion on an existing setup? Talk to our Commerce team, or read how we compare SAP Commerce Cloud partners in Switzerland.

FAQ

What is ImpEx in SAP Commerce Cloud?

ImpEx (Import/Export) is SAP Commerce’s text-based engine for bulk data operations. It uses CSV-like syntax with headers that map to the Commerce type system: you define the item type, the attributes and the data rows. It handles products, customers, orders, CMS content and configuration, so virtually any data type in the platform.

Can I use ImpEx for real-time data updates?

Technically yes, in practice no. ImpEx is built for batch work: initial loads, scheduled updates, environment seeding. For real-time single-record operations (a price update when a customer logs in, an order from a mobile app) use the OCC REST APIs, which are designed for low-latency request and response.

What’s the difference between Hot Folders and ImpEx?

Hot Folders use ImpEx under the hood. The difference is automation: a file lands in a monitored location (in SAP Commerce Cloud, Azure Blob Storage) and the platform processes it on its own. With plain ImpEx you run scripts manually through Backoffice or the Administration Console (HAC). Hot Folders are the better fit for recurring imports such as inventory feeds, price updates and product syncs.

How do I handle large data migrations to Commerce Cloud?

Split the migration into phases: reference data (categories, classifications) first, then products, then customers, then orders. Write ImpEx scripts that can be re-run without creating duplicates (INSERT_UPDATE with unique keys) and test each phase in staging. For millions of records, use parallel ImpEx execution and off-peak scheduling so the platform stays responsive.

When should I use SAP Integration Suite instead of direct APIs?

When a data flow spans several systems. If an order in Commerce Cloud has to fetch pricing from S/4HANA, update stock in a WMS and trigger a message in SAP Engagement Cloud (formerly SAP Emarsys), that is Integration Suite territory. Direct OCC API calls are fine for point-to-point integrations; Integration Suite adds the mapping, error handling, monitoring and retry logic that multi-system flows need.