# Troubleshoot the Cin7 Core WMS integration
URL: https://support.starshipit.com/articles/14700000000074-troubleshoot-the-cin7-core-wms-integration
Canonical: https://support.starshipit.com/articles/14700000000074-troubleshoot-the-cin7-core-wms-integration
Markdown: https://support.starshipit.com/articles/14700000000074-troubleshoot-the-cin7-core-wms-integration.md
Updated: 2026-11-08

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

> Investigate Cin7 Core connection, import, webhook and writeback failures without repeating an uncertain stock operation.

Find the failed Cin7 Core stage before repeating a WMS import, receipt, adjustment or sync. A successful warehouse action and its background writeback can have different outcomes.

## Before you troubleshoot

Record the WMS account, SKU or PO, event time and the visible error. Check **System > Background Work** and **System > Process Logs**. If stock already changed in WMS, check Cin7 Core before repeating the warehouse action.

## Troubleshooting

| Problem | What to check |
| --- | --- |
| No connected Core account appears, or Test connection is disabled | Configure an enabled Cin7 Core connection in the Starshipit account connected to WMS, select API Version 2 and save. Return to **Connect** in the WMS setup checklist and select **Refresh settings**. |
| The connection test fails | Check the saved account ID and key in Starshipit, and confirm the Cin7 Core API application is active. If the error says the connection differs from the saved warehouse source, restore the original Core company connection. |
| 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. |
| A Cin7 Core location import cannot start | Check the saved Starshipit connection and mapped warehouse, then wait for **Saved**. Resolve duplicate location names beneath the warehouse or ambiguous same-name WMS locations, then wait for any other location import to finish. |
| A product, opening-stock or webhook action is disabled | Turn on **Sync** and wait for **Saved**. Complete the preceding checklist steps and resolve any **Save failed** error. Wait for an active import to finish. Repeating opening stock also requires account-wide inventory adjustment permission. 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. |
| A supplier invoice cannot be selected for receiving | Confirm sync and inventory writeback are enabled and the purchase uses **Invoice First**. The invoice must be authorised and unpaid, with no existing received stock or draft receiving work in Core. Review the reason shown beside the invoice before continuing. |
| Opening stock has warnings | Check for existing WMS stock, fractional quantities, missing bin links or unbinned Core stock without a reconciliation location. |
| Inventory differs after a webhook | Check bin links, tracking details, fractional quantities, allocated or container-held stock, and unresolved outbound writes. Review Process Logs. |
| Webhooks are not active or changes stop arriving | Check the saved Starshipit API v2 connection, then select **Register webhooks** or **Update webhooks** in WMS. Confirm all four events show **Active** and check Background work and Process Logs. Contact support if notifications still do not arrive. |
| 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.

## Monitor background work and process logs

Use **Review setup** in the **Cin7 Core actions** menu to check the product import, opening-stock run and webhook steps. The menu also offers **Import products again**, **Reapply opening stock** and **Update webhooks** for an existing integration. Reapplying opening stock makes a fresh Core snapshot authoritative for existing WMS stock; review the opening-stock guidance before using it. If a run is stopped or needs review, open its background-work link and resolve the issue before repeating it.

Use **System > Background Work** for a quick operational view. See [Manage background work in WMS](/articles/14700000000066-manage-background-work-in-wms) for filters, status meanings and supported recovery actions.

* Set **Execution source** to **Tracked jobs** for product imports and opening-stock imports, including progress and warning counts.
* Set **Execution source** to **Queue** for product updates, stock updates, purchase-order updates and writebacks.
* **Automatic retry** means WMS has another attempt available after a temporary failure. Check the scheduled time where shown.
* **Review needed**, **Failed**, **Retries exhausted** or **Retry needed** means you should inspect the error and the supported recovery action 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.

## Confirm recovery

Refresh the relevant work item and verify the affected product, bin or purchase receipt in both systems. A queued retry or preparation step alone does not confirm a completed Cin7 Core change.

## Related articles

* [Set up Cin7 Core with Starshipit WMS](/articles/14700000000035-set-up-cin7-core-with-starshipit-wms)
* [Reconcile Cin7 Core inventory in WMS](/articles/14700000000072-reconcile-cin7-core-inventory-in-wms)
* [Receive an existing Cin7 Core supplier invoice](/articles/14700000000091-receive-an-existing-cin7-core-supplier-invoice)