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

Commerce Cloud offers four ways to load data — ImpEx, Hot Folders, OCC APIs, and SAP Integration Suite. Each has a sweet spot: ImpEx for bulk imports and initial loads, Hot Folders for scheduled file-based updates, APIs for real-time operations, and Integration Suite for complex multi-system flows. Picking the wrong method doesn’t break anything — it just makes your implementation slower and harder to maintain.

This guide covers each method, when to use it, and common mistakes to avoid.

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 reached $6.334 trillion in 2024, crossing the 20% threshold of all retail sales for the first time (eMarketer, 2024). Managing the product data, pricing, and customer records behind that commerce volume requires efficient data loading — and ImpEx is where most Commerce Cloud implementations start.

ImpEx (Import/Export) is SAP’s proprietary scripting language for bulk data operations. It reads and writes items in Commerce Cloud’s type system using a CSV-like syntax with headers that map to item types and attributes.

What ImpEx does well:

• Initial data migration — loading thousands of products, categories, customers, and orders from a legacy system
• Environment setup — seeding development and staging environments with test data
• Content updates — batch updates to prices, stock levels, or product descriptions
• Configuration — setting up CMS pages, site configurations, and 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 operations. ImpEx is batch-oriented — it runs scripts against the database, not against live API requests. If you need to update a single product price in response to a customer action, use the OCC API instead.

How Do Hot Folders Work?

Mobile commerce reached $2.07 trillion in 2024 — 57% of total e-commerce (Oberlo, 2025). That volume means product data, inventory, and pricing need continuous updates. Hot Folders automate that.

Hot Folders are file-system directories that Commerce Cloud monitors for incoming files. Drop a CSV file into the designated folder, and Commerce Cloud automatically processes it using configured converters and ImpEx templates.

How Hot Folders work:

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 an archive directory; failed files move to an error directory

Best use cases:

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

Configuration tip: Always configure error handling. Hot Folders process files silently — if you don’t monitor the error directory, failed imports go unnoticed. Set up email alerts or log monitoring for the error folder.

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 requires APIs that respond in real time — and that’s where OCC (Omni Commerce Connect) APIs come in.

OCC APIs are RESTful endpoints that expose Commerce Cloud’s commerce functionality to external consumers. The Composable Storefront uses them exclusively. But they’re also the right choice for:

• Custom storefronts — React, Vue, Next.js, or any frontend that consumes REST
• Mobile apps — native iOS/Android apps accessing cart, checkout, and product data
• Third-party integrations — point-of-sale systems, kiosks, or partner portals
• Single-record operations — updating one product’s price or one customer’s address

API vs ImpEx rule of thumb: If you’re updating fewer than 100 records in response to a user action or event, use the API. If you’re loading thousands of records in a scheduled batch, use ImpEx or Hot Folders.

How Does SAP Integration Suite Fit In?

The SAP BTP Integration Suite handles the complex scenarios where Commerce Cloud needs to communicate with multiple enterprise systems simultaneously.

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 flow from S/4HANA to Commerce Cloud

Integration Suite provides pre-built integration content packs for the most common Commerce Cloud ↔ S/4HANA flows. These aren’t plug-and-play — they still need configuration and mapping — but they dramatically reduce custom integration effort.

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). With that volume of digital transactions, data loading mistakes have real revenue impact.

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

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

Ignoring Hot Folder error handling. Failed files sit in the error directory silently. Set up monitoring and alerts. We’ve seen production systems with months of failed imports that nobody noticed.

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.

Not testing data loads in staging. Always test your ImpEx scripts and Hot Folder configurations in a staging environment before running them in production. A malformed ImpEx script can corrupt product data that takes hours to fix.

FAQ

What is ImpEx in SAP Commerce Cloud?

ImpEx (Import/Export) is SAP’s proprietary scripting language for bulk data operations. It uses a 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. ImpEx handles products, customers, orders, CMS content, and configurations — virtually any data type in the platform.

Can I use ImpEx for real-time data updates?

Technically yes, but you shouldn’t. ImpEx is designed for batch operations — initial loads, scheduled updates, and 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 automatically. With raw ImpEx, you run scripts manually through the Backoffice or HAC (Hybris Administration Console). Hot Folders are better 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 (use 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 to avoid impacting platform performance.

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

Use Integration Suite when you need to orchestrate data flows between multiple systems — for example, when an order in Commerce Cloud needs to trigger pricing in S/4HANA, update inventory in a WMS, and send a notification to Emarsys. Direct OCC APIs are fine for point-to-point integrations. Integration Suite handles transformation, error handling, monitoring, and retry logic for complex multi-system scenarios.