Inbound Integrations

Inbound integrations handle data flowing from the external platform into VARIO ERP. The most common inbound flow is order import — pulling new orders from a shop or marketplace into the ERP for fulfillment.

General Pattern

All inbound integrations follow the same three-step pattern:

┌──────────────┐     ┌──────────────┐     ┌──────────────┐
│   Fetch      │────►│  Transform   │────►│   Import     │
│  from        │     │  to ERP      │     │  to ERP      │
│  Platform    │     │  format      │     │  (MultiPart) │
└──────────────┘     └──────────────┘     └──────────────┘

1. Fetch — Retrieve data from the platform's API (orders, products, customers)

2. Transform — Map the platform's data structure to the format VARIO ERP expects

3. Import — Use the MultiPart Import API to push data into the ERP

Incremental Imports

Most inbound integrations use timestamp-based incremental imports:

1. Store the timestamp of the last successful import

2. On each import run, fetch only items created or modified after that timestamp

3. After a successful import, update the stored timestamp

This avoids re-importing data that has already been processed. Store the timestamp as a sales channel parameter.

Import Presets

Before you can import data into VARIO ERP, you need an import preset that defines how the incoming data maps to ERP entities. Import presets are created during your app's installation migration using the Migrator. See MultiPart Import for details on creating and using import presets.