Prepare source-system data for onboarding

Purpose

Prerequisites

  • Identify the source system and the webshop or business unit involved.
  • Identify the specific integration planned for this source system. Field coverage and synchronization behavior vary by integration and setup; do not assume every listed value is transferred.
  • Identify who owns product, supplier, and order data in the source system.

Steps

  1. Review the products intended for replenishment. Check their names and identifiers, such as SKU or EAN, and confirm that the source system’s product records are the ones you intend to use.
  2. Review product values that the source system maintains, such as sales price, current stock, product type, or composition. Do not assume every integration sends every value.
  3. Check the supplier relationship for each product that needs purchasing. Where the source system maintains them, review the supplier identifier, supplier-specific product code, purchase unit or lot size, minimum order quantity, price, and lead-time information.
  4. Check whether the source system contains the sales-order history and open purchase orders relevant to the selected integration. Include open orders only where the integration supports that data.
  5. Compare each field with the integration’s documented mapping. Note fields that are missing, ambiguous, duplicated, or owned by a different system.
  6. Resolve source-owned gaps in the system that owns the value. If the supported transfer is not documented for the selected integration, keep it as an unresolved field question instead of editing a second system.
  7. Record which values are present, who owns them, and which integration-specific field questions remain. This checklist does not confirm that data has transferred or been validated.

Fields and columns

Data areaExamples to checkBoundary
Product identityName, SKU, EAN, article codeUse identifiers supported by the selected integration; do not assume a code is unique across systems.
Product valuesSales price, stock, type, compositionConfirm which system owns each value and whether the integration maps it.
Supplier relationshipSupplier, supplier-specific product code, purchase unit, lot size, MOQ, purchase price, lead timeThese can be supplier-product values rather than product-wide values; follow the integration’s field mapping.
OrdersSales history and open purchase ordersInclude only records and fields supported by the selected integration.

Expected result

You have a checklist of the data present in the selected source system, the integration-specific fields that are supported, and any gaps or ownership questions that still need an answer. This is preparation, not confirmation that a synchronization or forecast has completed.

Limitations

  • Field coverage, direction, timing, and required data vary by integration and configuration.
  • This guide does not configure a connector, promise that missing fields can be added through a particular import, or guarantee purchasing advice.
  • A field that appears in one integration guide may not be available in another.

Errors and recovery

  • A product or supplier is missing: verify its identifier and source-system relationship with the data owner, then check the selected integration’s mapping.
  • A value differs between systems: identify which system owns it and confirm synchronization behavior before editing either copy.
  • The supported transfer is not documented: keep the field as an unresolved integration-specific question; do not assume it synchronizes or try an undocumented import path.