Skip to main content

Cin7 Core

The CargoWise Warehouse integration for Cin7 Core (previously named DEAR) imports sales from Cin7 Core as warehouse orders in CargoWise, updates being pushed back to Cin7 Core as orders are completed.

Cin7 Core Setup​

API Access​

For the integration to access the Cin7 Core API an API ID and Key needs to be provided.

Sales Filtering​

So only the relevant sales are imported into CargoWise to process, filtering criteria needs to be provided.

Cin7 Core sales are typically filtered using the following criteria:

  • Status - The order sale used to indicate the order is not in a draft state and is ready to fulfill.
  • Order Location ID - The location ID used to indicate the 3PL warehouse location to fulfill orders from.

CargoWise Setup​

Data Mapping​

For the creation of warehouse orders in CargoWise, the following details are required to configure the integration:

  • Organization Code - The client / consignor the warehouse orders are being created for.
  • Warehouse Code - The warehouse the orders are being assigned to. Multiple warehouses can be used if required.

Products​

Products should exist in CargoWise with Product Codes / SKUs matching the products that can be ordered in Cin7 Core. Any orders containing unknown or empty Product Codes / SKUs will be rejected by CargoWise.

Order Creation​

The following eAdaptor Inbound Service details are required to allow the creation of warehouse orders in CargoWise:

  • User Name
  • Password
  • Inbound eAdaptor Service URL

Order Updates​

For the optional order updates to be pushed back to Cin7 Core:

  1. The eAdaptor Relay for CargoWise middleware is required to receive order update messages from CargoWise.
  2. The CargoWise eAdaptor Outbound Service requires setup to use the eAdaptor Relay for CargoWise middleware.
  3. A WorkFlow Template needs to be configured in CargoWise to trigger the sending of messages once warehouse orders have been completed.