Skip to main content
The Data Import Service is the bulk loading path used by Store Service, Offers and others. It validates, processes and imports data from external systems in a controlled, observable way — asynchronously, so a large load never blocks your call. It handles tens of thousands of records or more, and applies back-pressure and throttling so a big import cannot overwhelm the service receiving it. Use it to migrate from legacy systems, bulk load POS transactions, run scheduled synchronisations, or correct records in bulk.

​
How an import runs

1

​
Create the job

Returns a jobId that identifies the operation from here on.
2

​
Upload and validate

The file is parsed and every record checked against business rules.
3

​
Process valid records

Validated data is passed to the target service.
4

​
Read the results

Processed, succeeded and failed counts, with detailed errors per failed row.
Poll the job status to follow progress. When rows fail validation, pull the errors, fix the source and re-run.
The v2 API creates the job and uploads the file in one request. Prefer it for new integrations — it removes a round trip and a whole class of half-created-job states.

​
File formats

Both formats require field names matching the target entity’s schema. A JSONL file looks like this:

​
API reference

Endpoint documentation: Data Import.
  • Retail Master Data — the data each import carries, and the order to run the imports in.
Last modified on October 19, 2026