# Set up Cin7 Core with Starshipit WMS
URL: https://support.starshipit.com/articles/14700000000035-set-up-cin7-core-with-starshipit-wms
Canonical: https://support.starshipit.com/articles/14700000000035-set-up-cin7-core-with-starshipit-wms
Markdown: https://support.starshipit.com/articles/14700000000035-set-up-cin7-core-with-starshipit-wms.md
Updated: 2026-07-20

> For the complete documentation index, see [llms.txt](https://support.starshipit.com/llms.txt).

> Connect Cin7 Core directly to Starshipit WMS, map a warehouse, import opening stock, and manage product, purchase order and inventory syncs.

Connect Cin7 Core directly to Starshipit WMS to keep products, purchase orders and warehouse-level inventory aligned while your team manages day-to-day warehouse locations and movements in WMS. Cin7 Core was previously known as DEAR Inventory.

## Before you begin

You need:

* A Cin7 Core account with API access and webhooks available.
* Permission to create an API application in Cin7 Core.
* Permission to manage settings and products in Starshipit WMS.
* Access to **Operations** and **Process Logs** if you will monitor the rollout yourself.
* One active, top-level Cin7 Core warehouse for this WMS account.
* A WMS location with the **Staging dock**, **Quarantine** or **Overflow** type to use as the reconciliation location.
* A secure password manager for the API application key and webhook bearer secret.

This direct WMS integration is separate from the standard [Cin7 Core integration](/articles/211651203-cin7-core-integration) used to import sales orders into Starshipit or request shipping rates from Cin7 Core.

## Decide which system owns each type of data

:::important
Treat Cin7 Core as the source of truth for the product catalogue, suppliers, Advanced Purchase orders and the total stock in the mapped warehouse. Treat WMS as the source of truth for stock locations and operational movements within that warehouse.
:::

| Data | Source of truth | How the integration handles it |
| --- | --- | --- |
| Product catalogue | Cin7 Core | WMS imports supported products and updates the Core-managed product fields. |
| Suppliers and Advanced Purchase orders | Cin7 Core | WMS imports eligible purchase orders and matches or creates suppliers by name. |
| Total stock in the mapped warehouse | Cin7 Core | WMS compares the Cin7 Core warehouse total with total WMS on-hand stock. |
| Bins, pick faces and other WMS locations | WMS | Cin7 Core bins are not imported or mapped to WMS locations. |
| Putaway, replenishment and internal movements | WMS | These movements stay within WMS and do not create matching Cin7 Core bin movements. |
| Sales and shipping | Your existing Starshipit and Cin7 Core workflow | This direct integration does not replace the sales-order and shipment integration. |

## Connect Cin7 Core while the integration is disabled

Keep **Enable Cin7 Core sync** and **Enable Cin7 Core writeback** off while you configure and test the connection.

### Create Cin7 Core API credentials

1. Open the Cin7 Core API setup page.
2. Create a dedicated API application for Starshipit WMS.
3. Copy the **Account ID** and **Application key** into your password manager.

See [Connecting to the Cin7 Core API](https://help.core.cin7.com/hc/en-us/articles/9982480315407-Connecting-to-the-Cin7-Core-API) for detailed API setup instructions.

Treat the account ID and application key like a username and password. Do not send them by email, place them in process notes or share them with users who do not manage the integration.

### Enter the connection details in WMS

1. In WMS, go to **System > Settings**.
2. Under **Products & Inventory**, select **Direct Integrations**.
3. Find **Cin7 Core**.
4. Enter the **Core account ID** and **Application key**.
5. Create a long, unique secret in your password manager and enter it in **Webhook bearer secret**. This secret is created by you; it is not the Cin7 Core application key.
6. Leave **Enable Cin7 Core sync** and **Enable Cin7 Core writeback** off.
7. Select **Save and test connection**.

When the test succeeds, WMS displays the number of active Cin7 Core warehouse locations it found. Saved application keys and webhook secrets are not displayed again. Enter a new value only when you intend to replace the saved value.

### Map the warehouse

1. Select the matching location under **Cin7 Core warehouse**.
2. Select a **WMS reconciliation location**.
3. Select **Save settings**.

One WMS account maps to one active, top-level Cin7 Core warehouse. The reconciliation location is where WMS places eligible opening balances and inventory differences that cannot be attributed to an existing WMS location.

## Enable inbound sync and register webhooks

1. Turn on **Enable Cin7 Core sync**.
2. Keep **Enable Cin7 Core writeback** off.
3. Select **Save settings**.
4. Under **Initial rollout**, select **Register webhooks**.
5. Confirm that WMS reports four configured webhooks.

WMS creates or reactivates the required Cin7 Core subscriptions:

| Cin7 Core event | What WMS does |
| --- | --- |
| `Product/Updated` | Fetches the latest product record from Cin7 Core. |
| `Stock/AvailableStockLevelChanged` | Fetches and reconciles stock for the mapped warehouse. |
| `Purchase/OrderAuthorised` | Imports an eligible authorised Advanced Purchase order. |
| `Purchase/Updated` | Fetches the latest eligible Advanced Purchase order. |

You do not need to copy webhook URLs or authentication values into Cin7 Core manually.

## Import products and opening stock

### Import the product catalogue

1. Under **Initial rollout**, select **Import products**.
2. Go to **Operations > Background work**.
3. Find **Cin7 Core product import** under **Tracked jobs**.
4. Wait for the job to complete before importing opening stock.

WMS imports active Cin7 Core products that have the **Stock** type and a non-empty SKU. A product import or webhook updates these Core-managed fields:

* **Product details:** Name, barcode, brand, description and tags.
* **Pricing:** Price Tier 1 and average cost.
* **Physical and customs details:** Dimensions, weight and country of origin.
* **Tracking:** Batch or serial tracking based on the Cin7 Core costing method.

WMS hides a linked Stock product when it is deprecated in Cin7 Core. Edit these managed fields in Cin7 Core because a future import or product webhook can replace the WMS values.

### Apply opening stock

Use the opening stock import only when you are starting with an empty WMS inventory or have reviewed the expected result for every affected SKU.

:::caution
Do not use the opening stock import to overwrite an active WMS inventory. WMS only applies a positive opening balance when the SKU is untracked, the Cin7 Core quantity is a whole number and total WMS on-hand is zero. Other cases are left unchanged; compare unsupported products manually and review any warnings.
:::

1. Confirm that the product import has completed.
2. Select **Apply opening stock**.
3. Go to **Operations > Background work**.
4. Find **Cin7 Core opening stock** under **Tracked jobs**.
5. Review the warning count when the job finishes.
6. Open **System > Process Logs** to investigate any warnings.

Accepted opening balances are added to the WMS reconciliation location. Batch-tracked products, serial-tracked products, fractional or negative differences, and non-zero WMS stock that differs from Cin7 Core require manual review. A zero balance with zero WMS stock makes no change.

Cin7 Core bin, batch and expiry rows are not used to create opening balances. Compare tracked products manually even when the opening-stock job has no warnings.

## Understand ongoing sync flows

Cin7 Core webhooks notify WMS that something changed. WMS then retrieves the latest record from Cin7 Core before processing it.

### Product updates

Cin7 Core remains the product catalogue master. When an imported product changes, WMS refreshes the Core-managed product fields. Only active Stock products with a non-empty SKU are imported. Linked Stock products marked as deprecated in Cin7 Core are hidden in WMS.

### Purchase orders

WMS imports a purchase order when all of these conditions are met:

* It is an **Advanced Purchase** in Cin7 Core.
* Its order stage is **Authorised**.
* It belongs to the mapped Cin7 Core warehouse.
* It is not service-only.
* It contains at least one stock line, and every line has a product and SKU, a positive whole-unit quantity and a valid non-negative price.

The purchase order appears in WMS with its Cin7 Core order number, supplier, dates, products, quantities and prices. If a product on the order is not yet linked, WMS imports the product before creating the purchase order.

Make purchase-order changes in Cin7 Core before receiving begins. Once the WMS purchase order has receiving activity, later Cin7 Core updates do not replace its lines.

### Inventory changes

For a stock-change event, WMS compares Cin7 Core on-hand stock for the mapped warehouse with total on-hand stock across WMS locations.

* For an untracked SKU with a whole-unit difference, WMS adds the difference to the reconciliation location.
* WMS can remove a difference only when the reconciliation location contains enough stock.
* Batch-tracked, serial-tracked, fractional or otherwise unsafe differences are not applied automatically. WMS adds a warning to Process Logs instead.
* Cin7 Core bin quantities are not copied into WMS locations.

## Enable inventory writeback after testing

**Enable Cin7 Core writeback** adds these outbound flows:

| WMS action | Cin7 Core result |
| --- | --- |
| Receive stock against a Cin7 Core-sourced Advanced Purchase order | WMS sends the completed receipt to the matching Cin7 Core purchase. |
| Make an explicit inventory adjustment for a linked product | WMS sends the resulting on-hand quantity for the product, or for the affected batch or serial number, to the mapped Cin7 Core location. |

Writebacks run in the background. A Cin7 Core error does not undo the completed WMS receipt or inventory adjustment.

For purchase receipts, WMS handles Cin7 Core's **Use put away** setting automatically.

Before enabling writeback:

1. Confirm that the connection, warehouse mapping and webhooks are working.
2. Complete the product import and review any opening-stock warnings.
3. Authorise a small test Advanced Purchase order in Cin7 Core for the mapped warehouse.
4. Confirm that the order and its products appear correctly in WMS.
5. Receive the test order in WMS and confirm the WMS stock result.
6. Turn on **Enable Cin7 Core writeback** and select **Save settings**.
7. Receive another controlled Cin7 Core purchase and confirm the receipt in both systems.
8. Review **Operations > Background work** and **System > Process Logs** before expanding the rollout.

Writeback is not retroactive. Receipts and adjustments completed while writeback is off are not sent later when you enable it.

## Monitor background work and process logs

Use **Operations > Background work** for a quick operational view:

* **Tracked jobs** shows product imports and opening-stock imports, including progress and warning counts.
* **Queue activity** shows recent product updates, stock updates, purchase-order updates and writebacks.
* **Retryable** means WMS plans another attempt after a temporary response such as rate limiting.
* **Needs review**, **Failed** or **Dead letter** means you should inspect the error before changing data in either system.

Use **System > Process Logs** for detailed warnings and audit information. Look for entries related to Cin7 Core, inventory sync, purchase orders or stock movements.

If a writeback outcome is uncertain, check Cin7 Core before repeating the WMS action. WMS avoids automatically repeating an operation when doing so could create a duplicate receipt or adjustment.

## Understand the limitations

The direct integration does not:

* Map Cin7 Core bins to WMS locations.
* Write back putaway, replenishment or ordinary movements between WMS locations.
* Replace the existing Starshipit and Cin7 Core sales-order and shipment flow.
* Write back cross-warehouse transfers, assemblies or kitting, returns, or bulk stocktake and cycle-count adjustments.
* Apply automatic stock reconciliation to batch-tracked, serial-tracked or fractional quantities.
* Cancel or delete an imported WMS purchase order if the Cin7 Core purchase later becomes unauthorised or moves outside the mapped warehouse.
* Map more than one Cin7 Core warehouse to one WMS account.

## Troubleshooting

| Problem | What to check |
| --- | --- |
| The connection test fails | Confirm the account ID and application key belong to the correct Cin7 Core company, the API application is active and the values were copied without extra spaces. |
| The expected warehouse is missing | WMS lists active, top-level Cin7 Core locations only. Check the location in Cin7 Core, then test the connection again. |
| An Initial rollout button is disabled | Save all changes and turn on **Enable Cin7 Core sync**. Writeback can remain off. |
| A product is missing | Confirm it is an active Cin7 Core **Stock** product with a non-empty SKU, then check Background work. |
| A purchase order is missing | Confirm it is an authorised, non-service Advanced Purchase for the mapped warehouse and every stock line has a product, SKU, positive whole-unit quantity and valid non-negative price. |
| Opening stock has warnings | Check for batch or serial tracking, fractional or negative differences, or non-zero WMS stock that differs from Cin7 Core. |
| Inventory differs after a webhook | Check whether the item is tracked or fractional, or whether the reconciliation location had enough stock for a negative adjustment. Review the warning in Process Logs. |
| Webhooks stop arriving after the secret changes | Do not rotate the webhook bearer secret during live processing. Contact Starshipit support to coordinate the secret change and webhook registration. |
| A receipt or adjustment did not write back | Confirm both sync and writeback are enabled, the record is linked to Cin7 Core, and the operation was completed after writeback was enabled. Check Background work and Process Logs. |

If the problem continues, contact [Starshipit support](https://help.starshipit.com) with the affected WMS account, SKU or purchase-order number, the time of the event and the Background work or Process Logs status. Do not include API keys or webhook secrets.

## Related articles

* [Cin7 Core integration for sales orders and shipping](/articles/211651203-cin7-core-integration)
* [Set up WMS locations and your warehouse](/articles/14700000000033-starshipit-wms-locations-and-warehouse-setup)
* [Configure WMS products and inventory](/articles/14700000000006-starshipit-wms-products-and-inventory-configuration)
* [Manage suppliers and purchase orders](/articles/14700000000007-suppliers-and-purchase-orders)
* [Receive stock in WMS](/articles/14700000000008-receiving-stock)