# Import separate Cin7 Core fulfilments
URL: https://support.starshipit.com/articles/1792356012407-import-separate-cin7-core-fulfilments
Canonical: https://support.starshipit.com/articles/1792356012407-import-separate-cin7-core-fulfilments
Markdown: https://support.starshipit.com/articles/1792356012407-import-separate-cin7-core-fulfilments.md
Updated: 2026-10-19

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

> Import eligible Cin7 Core sale fulfilments separately, check their status and resolve missing fulfilments under Ordered parents.

When a Cin7 Core sale ships in parts, you can import each fulfilment as a separate Starshipit order. Choose the fulfilment stage your team is ready to ship, then import and print labels for those items.

## Before you begin

- [Connect Cin7 Core to Starshipit](/articles/211651203-connect-cin7-core-to-starshipit) using **API Version 2**.
- Use the Starshipit-managed order-import workflow. The Cin7-managed rates and label workflow is a separate connection direction.
- Choose the fulfilment stage your team is ready to ship, such as **Packed**. Check the individual fulfilment in Cin7 Core, as its stage can differ from the parent sale's status.
- Confirm that the fulfilment's pick is authorised and that it has not been fully fulfilled.

## Configure fulfilment imports

1. Go to **Settings > Integrations > [Cin7 Core](https://next.starshipit.com/settings/integrations/cin7-core)**.
2. Confirm that the enabled connection uses **API Version 2**.
3. Select **Import Sale Fulfillments instead of Sales**.
4. Set **Status to import** to the stage or stages you want to ship. Separate multiple statuses with a semicolon.
5. Select **Save**.
6. Reopen the settings and check the API version, fulfilment-import option and selected statuses.

If no status is configured, the importer uses **Picked**. Set your intended stage explicitly.

Starshipit imports Advanced Sale fulfilments at your selected stage even when the parent sale is still **Ordered** or **Backordered**. For example, selecting **Packed** imports packed fulfilments and leaves those still at **Picked** in Cin7 Core.

## Check the imported fulfilments

Run your normal import for the period containing the sale, or use the existing webhook subscription if it is configured.

1. Find the sale's imported fulfilments in Starshipit.
2. Compare each order's items and quantities with its corresponding Cin7 Core fulfilment.
3. Confirm that only the fulfilments at your selected stage were imported before printing labels.

Ship each imported fulfilment separately. For carrier-name mappings and tracking writeback, follow the [Cin7 Core connection guide](/articles/211651203-connect-cin7-core-to-starshipit#writeback).

## Resolve a missing fulfilment

Check that the connection uses API Version 2, **Import Sale Fulfillments instead of Sales** is saved, and **Status to import** matches the individual fulfilment's stage. Then check the authorised pick, whether the fulfilment has already been completed, and the import period in Cin7 Core.

Search for the sale reference in Starshipit before creating a replacement order. If the fulfilment is still missing, [contact Support](https://support.starshipit.com/ticket) with the sale and fulfilment references, selected import status and import time.

## Related articles

- [Connect Cin7 Core to Starshipit](/articles/211651203-connect-cin7-core-to-starshipit)
- [Print labels for partial shipments](/articles/360001446756-labels-for-partial-shipments)