# 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-11-10

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

> Set up Cin7 Core in WMS using your saved Starshipit connection, map a warehouse, and manage products, purchase orders and stock syncs.

Set up Cin7 Core in Starshipit WMS using the connection saved in Starshipit to keep products, purchase orders and bin-level inventory aligned. 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 an **Automation module** subscription for webhooks. See [Cin7 Core's API guidance](https://help.core.cin7.com/hc/en-us/articles/9982466354831-User-Questions-Cin7-Core-API) for the subscription requirement.
* An enabled Cin7 Core connection in the Starshipit account connected to WMS, saved with **API Version 2** selected.
* Access to manage that Starshipit connection if it needs setting up or updating.
* Permission to manage settings and products, and view and import locations in Starshipit WMS.
* Account-wide process-log viewing access if you will monitor the rollout in **Background Work** yourself.
* One active, top-level Cin7 Core warehouse for this WMS account.
* Active Cin7 Core bins for the WMS locations used in receiving, storage, staging, equipment and packing.
* If Cin7 Core has stock without a bin, a visible WMS **Staging dock**, **Quarantine** or **Overflow** location that is not linked to a Core bin.
* Account-wide inventory adjustment permission if you will repeat opening stock or use a directional inventory sync.

WMS uses the credentials saved in the standard [Cin7 Core integration](/articles/211651203-cin7-core-integration). Its warehouse mapping, product and purchase imports, inventory sync and writeback settings are configured separately in WMS. You do not enter a Cin7 Core application key or webhook secret in WMS.

## Decide which system owns each type of data

:::important
Manage the product catalogue, suppliers and Advanced Purchase orders in Cin7 Core. Link Core bins to WMS locations so stock changes can stay aligned in both systems. Enable inventory writeback before starting WMS warehouse movements.
:::

| 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. |
| Bin stock | Cin7 Core and WMS | WMS reconciles Core stock by linked bin, preserving batch, serial and expiry details. Enabled writeback sends supported WMS changes to Core. |
| Bins and WMS locations | Cin7 Core for bin identity; WMS for operational settings | Location import creates stable Core bin links. Later Core location changes are not imported automatically. |
| Putaway, replenishment and internal movements | WMS | Enabled writeback sends supported movements between linked bins to Core. With simplified writebacks on, eligible Cin7 sale picking and packing movements stay in WMS. |
| Sales and shipping | Your existing Starshipit and Cin7 Core workflow | This direct integration does not replace the sales-order and shipment integration. |

Keep the existing Cin7 Core–Starshipit sales and shipping connection. WMS uses that saved connection to import products and purchases, reconcile linked bins and send supported warehouse changes back to Core.

## Start with a fresh WMS instance

Set up Cin7 Core before starting warehouse operations. Use a fresh WMS instance, or review **System > Settings > Data Management** if you are deliberately starting over with an existing instance.

:::warning
A transactional data reset permanently deletes inventory, orders, jobs and stock movements. It preserves products, locations and configuration. Only reset an existing instance when you intend to remove its operational data.
:::

Arrange a setup window in which users and connected systems pause product, stock and purchase changes in Cin7 Core. Keep those changes paused from before the first import until webhooks are registered and the final comparison below is complete. Changes made before registration are not captured by these webhooks.

## Connect Cin7 Core while the integration is disabled

This procedure covers full warehouse synchronisation. For product-only sync, select **Choose what to sync** in the Connect step and follow the resulting checklist; stock-specific location, fallback and opening-stock steps are omitted when stock sync is not selected.

Keep **Sync**, **Writeback** and **Outbound Pick/Pack** off while you configure and test the connection.

### Check the connection saved in Starshipit

1. In Starshipit, go to **Settings > Integrations > Cin7 Core**. If there is no connection, follow the [Cin7 Core integration guide](/articles/211651203-cin7-core-integration) to add one.
2. Confirm that **Enable Cin7 Core** is selected.
3. Select **Version 2** for the API version.
4. Confirm that the saved **Account ID** and **Key** belong to the Cin7 Core company you want WMS to use.
5. Select **Save**.

Maintain the Cin7 Core credentials in Starshipit. WMS discovers the connected Core account and keeps it as the source for this warehouse. Changing Starshipit to a different Core company blocks WMS requests; restore the original connection before continuing.

### Test the saved connection in WMS

1. In WMS, go to **System > Settings**.
2. Under **Connections & Integrations**, select **Direct Connections**.
3. Find **Cin7 Core**.
4. Open **Connect** in the setup checklist. If no connection is available after configuring Starshipit, select **Refresh settings**.
5. Leave **Sync**, **Writeback** and **Outbound Pick/Pack** off.
6. Select **Test connection**.

WMS settings save automatically when you change a selection or switch. Wait for **Saved** before continuing. If **Save failed** appears, correct the reported problem and select **Retry save**. **Test connection** also saves changed WMS settings before testing.

The setup checklist unlocks each step after the preceding step is complete. For an existing integration, open the **Cin7 Core actions** menu and select **Review setup** to return to the checklist.

When the test succeeds, WMS marks the connection as verified and loads the active warehouses in the **Warehouse** step. If the connection is unavailable, check that it is enabled, saved and using API v2 in Starshipit, then return to **Connect** and select **Refresh settings**.

### Map the warehouse and import locations

1. Open **Warehouse** and select the matching **Cin7 Core warehouse**.
2. Wait for **Saved**.
3. Open **Locations** and select **Import locations from Core** (or **Import locations again**) to open the import flow in **Setup > Locations**.
4. Review the import confirmation, then select **Import locations**.
5. Wait for the import to finish and review any failed rows.
6. Confirm that every location used for bin-based movements has a Core link, including receiving, staging, equipment and packing locations.

![The Cin7 Core setup checklist with Warehouse expanded and Main Warehouse selected](/uploads/articles/starshipit-wms/web/integrations/cin7-core-warehouse-setup.jpg)

One WMS account maps to one active, top-level Cin7 Core warehouse. The import copies active descendants and links them to their Core IDs. WMS reuses existing Core ID links first, then matches unlinked locations by name without regard to letter case. Existing same-name locations keep their type and settings; new locations are created as **Pick Face** locations. Duplicate names or conflicting mappings require correction before the affected rows can import.

![The location-import confirmation explaining that existing locations keep their type and settings and later Core changes do not sync automatically](/uploads/articles/starshipit-wms/web/integrations/cin7-core-location-import.jpg)

Later Core additions, renames, hierarchy changes and deactivations are not imported automatically. Run the import again when needed and review the links. Continue managing WMS location types, barcodes, capacity, sequence, zones and restrictions in WMS.

### Choose a location for stock without a Core bin

If Cin7 Core holds stock at warehouse level without a bin, open **Stock without a bin** in the setup checklist, select a location under **Stock without a Core bin**, then wait for **Saved**. Choose a visible **Staging dock**, **Quarantine** or **Overflow** location that is not already linked to a Core bin.

This location receives stock that has no Core bin. It does not replace a missing mapping for stock that already belongs to a Core bin. Assign unbinned stock to a Core bin before using bin-based outbound movements.

If all Core stock has a bin, select **Continue without a fallback location** to complete this setup step.

## Enable inbound sync

1. Confirm that the location import has finished and the warehouse mapping is correct.
2. Open **Sync** in the setup checklist and turn on **Sync**.
3. Choose whether to turn on **Import product images**. It is off by default. Leave it off to preserve existing WMS images and skip image retrieval during imports and product updates. Turn it on to import the default product image from Core; this uses an extra API call per product.
4. Keep **Writeback** and **Outbound Pick/Pack** off during the initial import.
5. Wait for **Saved** before continuing to **Products**. Complete the product and opening-stock steps before registering webhooks.

## Import products and opening stock

### Import the product catalogue

1. Open **Products** in the setup checklist and select **Import products**.
2. Go to **System > Background Work**.
3. Set **Execution source** to **Tracked jobs** and find **Cin7 Core product import**.
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. The default product image also imports when **Import product images** is on.
* **Pricing:** Price Tier 1 and average cost.
* **Physical and customs details:** Dimensions, weight, country of origin and the global HS code.
* **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.

### Import Assembly bills of materials

The product import also converts supported Cin7 Core Assembly bills of materials (BOMs) into WMS **exploding bundles**. Orders for these bundles use the component SKUs rather than picking a stocked bundle SKU.

To import a BOM, it must have:

* The **Assembly** BOM type and **Quantity to produce** set to `1`.
* At least one stock component, with a product ID, SKU and positive whole-unit quantity.
* No service components, wastage, duplicate components or nested bundles.
* Component products that can be imported and pass WMS bundle validation.

After the import completes, open a sample bundle in **Products** and check its bundle mode, component SKUs and quantities. Review **System > Process Logs** for any skipped BOMs before using them on orders.

Manage the BOM in Cin7 Core. A later product import or product-update webhook can replace the WMS component configuration and set its mode to **Explode**. This import does not create pre-kitted stock or write assemblies back to Cin7 Core. See [Configure WMS products and inventory](/articles/14700000000006-configure-wms-products-and-inventory) for the difference between exploding and require-stock bundles.

### Apply opening stock

Apply opening stock after both the location and product imports have finished. The first import applies stock only to products with no existing WMS stock; products with existing stock are sent for review.

1. Open **Opening stock** in the setup checklist and select **Apply opening stock**.
2. Go to **System > Background Work**.
3. Set **Execution source** to **Tracked jobs**, find **Cin7 Core opening stock** and wait for completion.
4. Review warnings in **System > Process Logs**.
5. Compare representative SKUs in both systems by bin, quantity and any batch, serial or expiry details.

WMS supports whole-unit untracked, batch-tracked and serial-tracked opening stock. Stock goes to its linked WMS bin, or to the reconciliation location when the Core row has no bin. WMS captures a complete warehouse stock snapshot before applying it. Keep stock changes paused until the run and comparison finish; the run applies that captured balance rather than continuously refreshing it.

After the run completes, **Reapply opening stock** reconciles existing WMS inventory to a fresh Core snapshot across linked products. It requires account-wide inventory adjustment permission and can set a product's WMS stock to zero if it is absent from that complete snapshot.

:::warning
Repeating opening stock makes the captured Core balances authoritative. It can replace existing WMS quantities and remove or relocate allocated or container-held stock. Run it outside warehouse hours with stock changes paused, and confirm Core has the correct balances first. Missing mappings and unsupported stock still require review.
:::

## Register webhooks after the imports

1. Return to the Cin7 Core settings card.
2. Open **Webhooks** in the setup checklist and select **Register webhooks** when you are ready for ongoing changes. Select **Update webhooks** if the subscriptions are already configured.
3. Select **Choose events**. For full warehouse sync, confirm that all four events are selected and show **Active**. If you change the selection, select **Save selection**, wait for **Saved**, then register or update webhooks again. **Not active** or **Update needed** requires registration or an update; **Not checked** means WMS has not confirmed its state.
4. While Core changes remain paused, compare the imported product data and stock by bin and tracking identity against Core. Review any eligible purchase orders that need to reach WMS.
5. Resolve missing or mismatched records before resuming changes. If Core changed during setup, do not assume registration replays those changes: refresh products with **Import products again**, use a directional inventory sync for a reviewed product difference, or **Reapply opening stock** when Core is correct across the warehouse. Contact Starshipit support for missing purchases.
6. Resume Core changes only after this comparison is complete and all discrepancies are resolved.

WMS asks Starshipit to create or reactivate these subscriptions. Starshipit manages webhook authentication and forwards the notifications to WMS. You do not need to create a webhook secret or copy URLs into Cin7 Core manually. For an existing WMS setup, select **Register webhooks** or **Update webhooks** to move its warehouse notifications through Starshipit; this does not replace sales-order or third-party subscriptions.

| Cin7 Core event | What WMS does |
| --- | --- |
| `Product/Updated` | Fetches the latest product record. |
| `Stock/AvailableStockLevelChanged` | Reconciles stock by linked bin and tracking identity. |
| `Purchase/OrderAuthorised` | Imports an eligible authorised Advanced Purchase order. |
| `Purchase/Updated` | Fetches the latest eligible Advanced Purchase order. |

## Enable inventory writeback after testing

**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 using the actual receiving bin. |
| Adjust or write off stock, or complete a stocktake or cycle-count correction | WMS sends the resulting quantity for each affected linked bin and tracking identity. |
| Move stock between linked WMS locations, including putaway and replenishment | WMS sends a Core stock transfer between the linked bins, except eligible picking and packing movements when simplified writebacks are on. |
| Restock a customer return to a linked bin | WMS sends a stock adjustment for the returned quantity. This does not create a Core credit note or return document. |
| Ship a linked product on an order with a known source other than Cin7 Core | WMS sends a stock deduction. Core-sourced sales retain their existing Core sale deduction. |

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.

To test and enable 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. Confirm that receiving and movement locations are linked to active Core bins.
6. Turn on **Writeback** and wait for **Saved** before receiving or moving stock in WMS.
7. Receive the controlled purchase, then test a bin movement and an adjustment. Confirm quantities and tracking details in both systems.
8. Review **System > Background Work** and **System > Process Logs** before starting normal warehouse operations.

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

## Choose how picking and packing movements write back

**Simplify stock movement writebacks** is on by default. It applies to new picking jobs where every order is a Cin7 Core sale, Starshipit manages the Core fulfilment, and **Outbound Pick/Pack** is off.

WMS still records the stock moving through equipment, totes and packing locations. Those picking and packing movements stay in WMS instead of creating Core bin transfers. Core stock remains in its original bin until Starshipit's shipment writeback deducts the sale using Core's authorised Pick lines.

Receiving, replenishment, manual bin transfers, non-Cin7 or mixed-source picking jobs, and WMS-managed **Outbound Pick/Pack** keep their usual writeback behaviour. Turning this setting off restores detailed bin-transfer writebacks for new picking jobs. Existing picking jobs keep the mode they started with.

For an existing integration, these controls appear in the Cin7 Core settings card. The example below shows **Writeback** enabled after setup; keep it off during your initial import.

![The Cin7 Core settings showing Sync on, Import product images off, Writeback on, Outbound Pick/Pack off and Simplify stock movement writebacks on](/uploads/articles/starshipit-wms/web/integrations/cin7-core-sync-and-writeback.jpg)

## Understand the limitations

The direct integration does not:

* Automatically import later changes to the Cin7 Core location catalogue.
* Send bin-based movements from locations without valid Core bin links.
* Replace the existing Starshipit and Cin7 Core sales-order and shipment flow.
* Write back cross-warehouse transfers, assemblies or kitting, or create customer return and credit documents in Core.
* Apply fractional stock quantities automatically.
* 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.

## Verify go-live

Compare representative products, bin quantities and tracking details in both systems. Confirm a controlled purchase receipt, movement and adjustment reach Core after writeback is enabled. Resolve missing records and background-work warnings before resuming normal warehouse activity.

## Manage the integration after setup

| Task | Guide |
| --- | --- |
| Correct an inventory difference or understand ongoing imports | [Reconcile Cin7 Core inventory in WMS](/articles/14700000000072-reconcile-cin7-core-inventory-in-wms) |
| Enable eligible outbound Pick/Pack | [Set up Cin7 Core outbound Pick and Pack](/articles/14700000000073-set-up-cin7-core-outbound-pick-and-pack) |
| Investigate failed imports, webhooks or writebacks | [Troubleshoot the Cin7 Core WMS integration](/articles/14700000000074-troubleshoot-the-cin7-core-wms-integration) |
| Receive an existing supplier invoice | [Receive an existing Cin7 Core supplier invoice](/articles/14700000000091-receive-an-existing-cin7-core-supplier-invoice) |

## Related articles

* [Set up warehouse locations and work areas](/articles/14700000000033-set-up-warehouse-locations-and-work-areas)
* [Configure WMS products and inventory](/articles/14700000000006-configure-wms-products-and-inventory)
* [Manage background work in WMS](/articles/14700000000066-manage-background-work-in-wms)
