# Import warehouse transfers from CSV
URL: https://support.starshipit.com/articles/14700000000065-import-warehouse-transfers-from-csv
Canonical: https://support.starshipit.com/articles/14700000000065-import-warehouse-transfers-from-csv
Markdown: https://support.starshipit.com/articles/14700000000065-import-warehouse-transfers-from-csv.md
Updated: 2026-10-20

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

> Create warehouse transfers from a CSV, preview destinations and quantities, and recover incomplete imports without duplicating source orders.

Create several inter-warehouse transfers from one CSV instead of entering each transfer separately. Preview the destinations, SKUs and quantities before WMS creates the source orders and destination purchase orders, then review the result for every transfer.

## Before you begin

* Sign in to the WMS warehouse that will send the stock. That warehouse is the source for every transfer in the file.
* You need **Manage purchase orders** permission with access to the whole account. Client-scoped users cannot import, retry or reconcile transfer imports.
* Use different source and destination WMS warehouses in the same Starshipit parent and child account family. The destination needs a complete sender address in Starshipit.
* Each SKU must exist unambiguously in both warehouses, belong to the warehouse rather than a 3PL client, and have the same unit-of-measure conversion in both accounts.
* Check the stock needed for later fulfilment. Importing creates orders; it does not reserve inventory or move stock.

Your team will still need the usual permissions to release and ship the source orders and receive the destination purchase orders. See [Transfer stock between warehouses](/articles/14700000000040-transfer-stock-between-warehouses) for those steps and permissions.

## Prepare the CSV

1. Go to **Purchase Orders > Transfers** in the source warehouse.
2. Select **Import CSV**, then **Download CSV template**.
3. Replace the example rows with your destinations, SKUs and quantities. Keep the four header names below.
4. Save the file as CSV. Each file can contain up to **100 grouped transfers**, **10,000 data rows** and **5 MB**.

| Column | What to enter |
| --- | --- |
| `transferKey` | A stable identifier for one transfer, up to 100 characters. Repeat it on every row belonging to that transfer. Keys are case sensitive. |
| `destinationAccountNumber` | The destination warehouse's numeric WMS account number, rather than its name. All rows for one transfer must have the same destination. |
| `sku` | An existing warehouse-owned SKU in both accounts, up to 50 characters. Repeated SKUs within one transfer are added together, ignoring letter case. |
| `quantity` | A positive whole number in that SKU's units. The combined quantity for one SKU in a transfer cannot exceed `2147483647`. |

For example, these rows create two transfers. The first contains five units of `SKU-A` and one unit of `SKU-B`:

```csv
transferKey,destinationAccountNumber,sku,quantity
RESTOCK-001,100001,SKU-A,2
RESTOCK-001,100001,SKU-A,3
RESTOCK-001,100001,SKU-B,1
RESTOCK-002,100002,SKU-A,4
```

Replace the example account numbers and SKUs. Enter carton quantities only when the SKU itself represents a carton.

Keep the same `transferKey` when resubmitting the same intended transfer from the same source warehouse. WMS skips matching transfers that were already imported and leaves their orders, purchase orders and quantities unchanged. Reusing a key with different destinations, SKUs or quantities is rejected.

:::caution
Use a new key only for a new transfer. Changing a key to bypass a failed import or manual-review result can create another source order.
:::

## Preview and create the transfers

1. Return to **Import CSV** and select your file under **CSV file**.
2. Select **Preview transfers**. Correct any validation errors and preview the corrected file again.
3. Confirm the **Source warehouse**, destination names and account numbers, grouped SKUs and quantities. Review any **Already imported** messages.
4. Select **Confirm create** to start the import.
5. Follow the progress notification. You can continue working elsewhere in WMS while creation runs.
6. Select **View results** when the import finishes and review each transfer's outcome.

Preview does not create or change orders, purchase orders, transfers or inventory. WMS validates the file before allowing creation, then checks each transfer again as it processes the import.

To stop unfinished work, select **Cancel import** on the progress notification. Transfers already created remain in place, and a transfer already processing may finish before cancellation takes effect. Review the results before deciding what to retry.

Each new transfer receives an `XFER-CSV-...` reference. After creation, confirm the linked source order and destination purchase order, then follow the normal [release, shipping and receiving workflow](/articles/14700000000040-transfer-stock-between-warehouses#release-and-ship-from-the-source-warehouse). The import itself does not ship or receive stock.

## Review results and retry incomplete work

The result shows each transfer's key, generated reference, destination and outcome:

| Result | What to do |
| --- | --- |
| **Created** | Confirm the source order and destination purchase order, then continue fulfilment. |
| **Already imported** | Use the existing transfer. WMS left it unchanged. |
| **Failed — can retry** | Resolve the reported issue, then select **Retry incomplete**. If a confirmed source order is shown, WMS resumes from that order after checking it. |
| **Needs manual review** | A source order may already exist. Find it in Starshipit using the generated reference, then reconcile its ID as described below or contact Support. This transfer is excluded from retry. |

To reopen an incomplete import after a reload:

1. Open **Purchase Orders > Transfers** in the same source warehouse.
2. Choose the file and creation time under **Import results**. Select **Load more imports** if you need an older unresolved import.
3. Select **View import results** and resolve the reported issues.
4. Select **Retry incomplete** when available, then review the new results.

This list contains incomplete imports for the current warehouse. A new import does not hide earlier unresolved results, but retry and reconciliation must wait until the active import finishes.

**Retry incomplete** preserves created and skipped transfers and resumes only eligible failed or unfinished work. It can also recover a failed or cancelled run when detailed results are unavailable, using saved progress. Transfers needing manual review remain excluded. If the source-order state is unclear, contact Support before starting another import.

## Reconcile a source order needing manual review

Use this action only when you have identified the source Starshipit order for a transfer marked **Needs manual review**.

1. Find the order in the source Starshipit account using the `XFER-CSV-...` reference from the import result.
2. Confirm its order ID, products, quantities and destination. The order must be unarchived, have an **Unshipped** or **Saved** status, and have zero shipped quantity on every line.
3. Enter the numeric order ID in **Source order ID** beside the affected transfer, then select **Reconcile source order**.
4. Wait for processing to finish and review the result. Confirm the linked destination purchase order before continuing the transfer.

WMS checks the order's reference and order number, SKUs, quantities and destination street, city, postcode and country against the intended transfer. These checks run again during processing. Reconciliation resumes from a verified order; it never creates another source order.

If the order is printed, shipped, returned, archived or does not match, work with Support to resolve it. If you cannot identify the order, leave the transfer awaiting manual review. Do not create a replacement transfer to clear the result.

## Troubleshooting

| Problem | What to check |
| --- | --- |
| **Import CSV** is unavailable | Confirm **Manage purchase orders** permission and whole-account access. Wait for any active transfer import to finish. |
| A destination or SKU fails preview | Check the destination's WMS account family and sender address, and confirm the SKU exists in both warehouses with matching unit conversions and no client ownership. |
| A transfer key was already used with different contents | Check the original import. Keep its key for the original transfer; use a different key only for a genuinely new transfer. |
| Results are unavailable | Check recent transfers and the source Starshipit account. Use **Retry incomplete** only when WMS offers it; otherwise contact Support before importing again. |
| Reconciliation rejects the source order | Check its numeric ID, reference, status, shipped quantities, products and destination. Contact Support if the order cannot be verified. |

## Related articles

* [Transfer stock between warehouses](/articles/14700000000040-transfer-stock-between-warehouses)
* [Import and export WMS data by CSV](/articles/14700000000041-import-and-export-wms-data-by-csv)
* [Manage orders and allocation in WMS](/articles/14700000000010-manage-orders-and-allocation-in-wms)