Appearance
Price list synchronization ​
A price list synchronization flow imports price lists from a source system into the platform's database, with optional enrichment steps applied along the way. Both the primary data source and any enrichments can be fully configured.
Flow Setup ​
Every synchronization flow starts with a source and can optionally include one or more enrichment steps to enhance or overwrite specific price list data.
Source ​
The source is always the first step in the flow and defines where the initial price list data originates. You can choose from the following options:
- Current data
Uses price list data that already exists in the database. No external requests to connectors are made. - Connector
Retrieves price list data from a connector, treating the connector as the source of truth.
If the connector removes a price list, that price list will eventually also be deleted in the OCP.
Optional Enrichments ​
Enrichment steps allow you to enhance or overwrite price list data retrieved from the primary source.
You can configure exactly which aspects of the price list data should be enriched, and from which connectors.
Aspects ​
For every step in the flow (except when using the current data option), you can specify which aspects of data should be retrieved from the connector. This ensures you always get the correct price list data from the right source.
For both aspect types, the data from the latest connector is always used.
Example: Multi-connector Pricing
If your base item prices originate from an ERP system, but tier-based pricing is managed separately, you can configure the flow to:
- Retrieve item prices from the ERP connector.
- Enrich with tier data from another connector.
Supported aspects ​
The following aspects are available within a price list synchronization flow:
| Aspect | Merge method |
|---|---|
| Item price (info) | Latest connector |
| Item tier (info) | Latest connector |