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

Four ways to get data into Commerce Cloud. That’s it. ImpEx for bulk loads. Hot Folders for scheduled file-based updates. OCC APIs for real-time stuff. SAP Integration Suite when you need to orchestrate across multiple systems. Pick the wrong one and nothing blows up, but your implementation gets slower and harder to maintain over time. I’ve watched teams struggle with this for years.

Here’s how each works and where people keep getting it wrong.

TL;DR: SAP Commerce Cloud supports four data loading methods: ImpEx (bulk import/export via scripting), Hot Folders (automated file-based processing), OCC REST APIs (real-time CRUD operations), and SAP BTP Integration Suite (enterprise middleware). ImpEx handles the vast majority of initial data loads and migrations. Gartner has recognised SAP as a Leader in Digital Commerce for 11 consecutive years (SAP News, 2025). Choose your method based on volume, frequency, and whether you need real-time or batch processing.

What Is ImpEx and When Should You Use It?

Global retail e-commerce hit $6.334 trillion in 2024, crossing the 20% mark of all retail sales for the first time (eMarketer, 2024). The product data, pricing, and customer records behind that volume need to get into your platform fast. ImpEx is where almost every Commerce Cloud implementation starts. Every developer on your team should learn it properly before touching anything else on the platform.

ImpEx (Import/Export) is SAP’s scripting language for bulk data operations. CSV-like syntax, headers that map to item types and attributes. Simple concept, surprisingly deep.

What ImpEx does well:

• Initial data migration: loading thousands of products, categories, customers from a legacy system
• Environment setup: seeding dev and staging environments with test data
• Content updates: batch updates to prices, stock levels, product descriptions
• Configuration: setting up CMS pages, site configs, 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

When ImpEx isn’t the right tool: real-time anything. It’s batch-oriented. Runs scripts against the database. If you need to update a single product price because a customer triggered something, reach for the OCC API instead.

How Do Hot Folders Work?

Mobile commerce reached $2.07 trillion in 2024, accounting for 57% of total e-commerce (Oberlo, 2025). That volume means product data, inventory, and pricing need continuous updates. Hot Folders are honestly the most underrated feature in Commerce Cloud. Dead simple way to automate recurring imports without writing integration code.

Drop a CSV into a monitored directory. Commerce Cloud picks it up, converts it to ImpEx, runs the import, and archives the file. That’s the whole thing.

How the process goes:

1. An external system or scheduled job places a CSV/XML file in a monitored directory
2. Commerce Cloud detects the new file
3. A converter transforms the raw data into ImpEx format
4. The platform executes the ImpEx import
5. Processed files move to archive; failed files go to an error directory

Best use cases:

• Scheduled inventory updates from a warehouse management system
• Price feed imports from an ERP on a fixed schedule
• Product catalogue syncs from a PIM tool that exports CSV/XML
• Media imports: bulk image uploads with metadata mapping

One thing though: always set up error handling. Hot Folders process files silently. If nobody’s watching the error directory, failed imports pile up and nobody knows. We’ve walked into production environments with months of failed files just sitting there. Months. Set up email alerts or log monitoring for the error folder. Nota bene: this is the single most common Hot Folder mistake we see.

When Should You Use OCC APIs?

Sixty-one per cent of B2B buyers prefer an overall rep-free buying experience (Gartner, 2025). Self-service digital commerce needs APIs that respond in real time. That’s the job of OCC (Omni Commerce Connect) APIs.

OCC APIs are RESTful endpoints that expose Commerce Cloud’s commerce functionality to anything that can call REST. The Composable Storefront runs on them exclusively. But they’re also the right pick for:

• Custom storefronts built in React, Vue, Next.js, whatever your team likes
• Mobile apps: native iOS/Android accessing cart, checkout, 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 100 records in response to a user action? API. Thousands of records on a schedule? ImpEx or Hot Folders.

How Does SAP Integration Suite Fit In?

The SAP BTP Integration Suite is where things get interesting. Commerce Cloud talking to multiple enterprise systems at the same time.

Common Integration Suite flows:

• Order replication: orders placed in Commerce Cloud flow to S/4HANA for fulfilment, invoicing, and accounting
• Real-time pricing: checkout calls S/4HANA for customer-specific pricing and ATP (available-to-promise) inventory
• Customer master sync: new accounts in Commerce Cloud replicate to SAP CRM or S/4HANA business partners
• Product master data: product attributes, classifications, and hierarchies flowing from S/4HANA into Commerce Cloud

Integration Suite ships pre-built integration content packs for the most common Commerce Cloud-to-S/4HANA flows. They aren’t plug-and-play (you still need configuration and mapping), but they cut the custom integration effort by a lot.

What Are the Most Common Data Loading Mistakes?

E-commerce now accounts for 34% of B2B revenue, dethroning in-person sales for the first time (McKinsey, 2024). At that transaction volume, data loading mistakes hit your bottom line fast. The number one mistake we see? Teams trying to ImpEx everything. Including operations that should clearly be API calls.

Loading too much data at once. Full product catalogue imports during business hours. They compete with live traffic for system resources. Schedule bulk imports during off-peak windows. Use incremental loading: only push changed records.

Skipping data validation. ImpEx will happily import malformed data that then breaks the storefront. Validate before import. Check required fields, data types, referential integrity. Commerce Cloud won’t stop you from importing a product that references a non-existent category.

Ignoring Hot Folder error handling. I already mentioned this, but it’s worth repeating. Failed files just sit there. Nobody gets notified. We’ve walked into production systems where nobody knew imports had been failing for months.

Using ImpEx for real-time updates. ImpEx is a batch tool. Running ImpEx scripts in response to individual user actions creates performance bottlenecks and race conditions. Use OCC APIs for real-time single-record operations. Full stop.

Not testing data loads in staging. Always run your ImpEx scripts and Hot Folder configs in staging first. A malformed ImpEx script can corrupt product data that takes hours to clean up. I’ve seen it happen more than once.

FAQ

What is ImpEx in SAP Commerce Cloud?

ImpEx (Import/Export) is SAP’s scripting language for bulk data operations. CSV-like syntax with headers that map to Commerce Cloud’s type system. You define the item type, the attributes to populate, and the data rows. It handles products, customers, orders, CMS content, configurations. Virtually any data type in the platform.

Can I use ImpEx for real-time data updates?

Technically yes. Practically, don’t. ImpEx is built for batch operations: initial loads, scheduled updates, environment seeding. For real-time single-record operations (updating a price when a customer logs in, creating an order from a mobile app), use OCC REST APIs. They’re designed for low-latency, request-response interactions.

What’s the difference between Hot Folders and ImpEx?

Hot Folders use ImpEx under the hood. The difference is automation: you drop a file into a monitored directory and Commerce Cloud processes it on its own. With raw ImpEx, you run scripts manually through the Backoffice or HAC (Hybris Administration Console). Hot Folders are the better fit for recurring imports (inventory feeds, price updates, product syncs) where you want hands-off processing.

How do I handle large data migrations to Commerce Cloud?

Break the migration into phases. Start with reference data (categories, classifications), then products, then customers, then orders. Use incremental ImpEx scripts that can be re-run without creating duplicates (INSERT_UPDATE with unique keys). Test each phase in staging. For very large datasets (millions of records), consider parallel ImpEx execution and off-peak scheduling so you don’t choke the platform.

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

When you need to orchestrate data flows across multiple systems. An order in Commerce Cloud needs to trigger pricing in S/4HANA, update inventory in a WMS, and send a notification to Emarsys? That’s Integration Suite territory. Direct OCC APIs work fine for point-to-point integrations. Integration Suite handles the transformation, error handling, monitoring, and retry logic that multi-system scenarios demand.