Data integration

To ensure a smooth and functional Scan & Go experience for shoppers, the first essential integration step is setting up the product data feed. This enables the shopreme apps to recognize scanned products, display correct product names, show prices in the cart, and (optionally) display product images during the shopping journey. This article explains how data integration works in the shopreme ecosystem, what types of data are required, and who on your team is usually involved.

Why data integration is essential

When a customer scans a product using one of the shopreme clients — whether it's their smartphone, a handheld scanner, or a smart cart — the app must identify what that product is, display its name and price, and add it to the shopping cart.

This only works if:

• The product information exists in the shopreme system

• The scan code (e.g., barcode) is correctly mapped to a known product

• The scan code has a price for the store the customer is in

That’s why integrating your product master data and price data is one of the first things that must be discussed and developed during a shopreme onboarding project.

Types of data imports

The shopreme DataHub supports structured data imports via JSON files, accessed via remote URLs and secured with authentication. You can schedule these imports at regular intervals or trigger them on demand. There are three main types of data imports:

1. Product Import

This import defines what products are available for scanning in the store.

✅ Mandatory for all Scan & Go clients

• Key fields required per product:

  • productNumber (unique ID, used as key for pricing)

  • productName (what the shopper sees in the app)

• Not required but expected:

  • scanCodes[] (all barcodes that can be used to add this product to the cart)

• Optional fields:

  • Product image URL (remote URL or an external CDN)

  • Age restrictions

  • Deposit info (a related product, such as a glass container, or returnable bottle)

  • Other metadata (used for advanced features)

💡 A product will not be scannable in the app unless it has at least one scan code and a price assigned for the current store.
It is possible to add products without barcodes in other ways that do not involve scanning. You can learn more about that in the shopreme Knowledge Base.

2. Price Import

This import provides store-specific pricing for each product number.

✅ Mandatory for all Scan & Go clients for an out-of-the-box implementation

• Prices are linked to products via the shared productNumber

• Key fields required per product:

  • productNumber (product identifier)

  • price (whole price value before any promotions)

  • taxRate

• Optional fields:

  • strikePrice (Marketing price displayed in strikethrough style)

  • pricePerUnit (Description of the price per unit for a product, e.g., “1.99 €/Kg”)

  • storeIdentifier (to support different prices per location)

💡 Having prices per product can make the product scanning faster. If your implementation does not require a price import and uses only an external pricing system, shopreme can work on retailer-specific changes to satisfy those needs.

📌 Note: Some barcodes may include the price encoded in them. In this case, the price from the import is not relevant.

3. Store Import

This import is optional and configures which stores are active, their location (address), and other properties. This enables accurate store detection in Scan & Go apps and pricing mapping.

✅ Recommended for syncing the store information. Stores can also be added manually instead.

• Includes store IDs, addresses, and optional store metadata

• Can also define Scan & Go configuration, or other legal settings, as needed

Import frequency

You can define how often each import runs:

• Full product imports - All products are updated, which can be slow for high numbers of products.

• Delta product imports - Smaller updates, usually daily.

• Full price imports – usually once a day (e.g., during the night)

• Delta price updates – smaller, more frequent updates (e.g., every hour, or as needed)

• Store imports - Typically performed only once when a new store is created or updates need to be synced.

This depends on your update volume. For example:

• There are small price changes throughout the day → hourly deltas

• There are new products once a day → nightly full import

📌 Check with your shopreme integration consultant to help you configure the optimal schedule.

Who sets this up?

In most retail organizations, this data is managed by teams that work with:

• CRM or ERP systems

• Product master databases

• Central data warehouses

These teams usually extract product and price data in JSON format and expose it via secure URLs for the shopreme DataHub to fetch.

Recommended: Default import

To simplify the integration architecture, we recommend aligning your product and price exports with shopreme’s default (“vanilla”) import structure. This structure is well-documented on the shopreme Management Console and in our Knowledge Base, and supports:

• ✅ Direct parsing by the DataHub

• ✅ No custom transformation logic required on shopreme’s side—enter the URL of the API, and click “run”.

• ✅ Faster and more predictable go-live

If your team can adapt your export format to our standard fields and structure, the shopreme setup becomes much quicker—often out-of-the-box.
Alternatively, shopreme can set up an adapter within the shopreme infrastructure to transform your data feed into a format shopreme can import directly.