# 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-11-03 > 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. In UI 2.0, select **Fulfilment locations to import** if this account should import only particular locations. Save a new connection first so Starshipit can load its locations. Leave the list unselected to import all locations. 6. Select **Save**. 7. Reopen the settings and check the API version, fulfilment-import option, selected statuses and locations. 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. ## Import fulfilments into the matching child account Use a separate Cin7 Core connection in each Full Access child account that ships from a location. This imports the fulfilment directly into the shipping account and retains its source sale and fulfilment for tracking writeback. 1. Sign in to each child account and [connect it to the same Cin7 Core account](/articles/211651203-connect-cin7-core-to-starshipit). 2. Configure API Version 2, separate fulfilment imports and the required import status, such as **Packed**. 3. In **Fulfilment locations to import**, select only that child's locations. Avoid overlaps with other child connections or an unfiltered parent connection, which could import the same fulfilment elsewhere. 4. Enable writeback on print in that child's import settings, then save. 5. Import an eligible fulfilment and check that it appears in the child matching its current authorised Pick location, even if its delivery address is in another region. 6. For the next planned shipment, print from that child and check the tracking on the corresponding Cin7 Core sale and fulfilment. When location filtering is selected, each fulfilment must have one unambiguous location across its inventory Pick lines. Missing or mixed Pick locations are skipped and reported in **Diagnostics**. Create separate Cin7 Core fulfilments for different locations; Starshipit does not split one fulfilment automatically. The location filter applies to manual, scheduled and webhook imports. Changing a location after import does not move an existing Starshipit order to another account. Reconcile that order before importing or shipping it again. A blank location filter retains all-location imports and does not route orders to child accounts by itself. ## 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 fulfilments at your selected stage and locations were imported into the intended Starshipit account 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#set-carrier-names-for-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. If locations are selected, check every inventory Pick line for a single matching location and review **Diagnostics** for a location-filter error. 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)