---
title: "Connect fulfilmentcrowd to Rig — Rig guide"
description: "Connect fulfilmentcrowd to Rig with an API key. Sync orders, returns, products, suppliers, stock levels and movements from your 3PL into your warehouse."
canonical: "https://rig.so/guides/connect-fulfilmentcrowd"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect fulfilmentcrowd to Rig

fulfilmentcrowd is a UK 3PL fulfilment platform. Rig syncs its orders, returns, products, stock and reference tables into your warehouse, so fulfilment performance and stock position can be read next to your sales data. It connects with an API key you create in the app.

## Before you start

- You need a fulfilmentcrowd user who can open the Public API settings. If you do not see them, ask your fulfilmentcrowd account manager.
- An API key belongs to one division, which is one trading entity. Connect one source per division you want in the warehouse.

## Step 1: Create a fulfilmentcrowd API key

1. Sign in to fulfilmentcrowd and go to **Settings \> Public API**.
2. Click **Add key** and give the key a name, such as Rig.
3. Set the permissions for each area. Choose **Read** for the areas you want in the warehouse. Rig only reads, so it has no use for **Write**.
4. Click **Save & Complete**, then click **Copy Key**.
5. Store the key somewhere safe. fulfilmentcrowd cannot show it again.

## Step 2: Connect it in Rig

New to Rig? Watch how to find Connections

Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

1. In Rig, open `Connections`, choose the `Connectors` tab and go to `Sources & actions`.
2. Search for **fulfilmentcrowd**, open the card and click `Connect`.
3. **API key**: Paste the key you copied.
4. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
5. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click `Sync` on its row; `Test` pulls a small sample first if you want to check the connection.

## What Rig pulls in

fulfilmentcrowd lands in its own `fulfilmentcrowd` schema in your warehouse:

- **Orders**: orders and order lines, plus order issues.
- **Returns**: returns and return lines.
- **Customers, products and suppliers**: the customers, products and suppliers on your division.
- **Stock**: stores, stock levels per store and stock movements.
- **Reference tables**: statuses, channels, channel types, carriers, carrier service levels, delivery methods, currencies, countries, return reasons, package types and divisions, so the id columns on every other table can be resolved.

Stock by batch, inventory transfers and inventory transfer lines are off by default. Switch them on when you pick streams if you track best before dates or inbound transfers.

## Good to know

- Confirm the key points at the right trading entity by checking the Divisions table after the first sync. A key sees a single division.
- fulfilmentcrowd's API returns at most 100 records per request, so large order histories take many requests.
- The reference tables are small and are re-read in full on every sync.
- To disconnect fulfilmentcrowd, click the bin icon on the source's row under `Sources & actions`. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

## What people use this for

- Track order fulfilment performance
- Monitor stock levels and movements
- Analyse returns
- Plan inbound stock and expiry

[More ideas for using fulfilmentcrowd](https://rig.so/integrations/fulfilmentcrowd)

## fulfilmentcrowd documentation

- [fulfilmentcrowd API reference](https://www.fulfilmentcrowd.dev/api-reference)

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-fulfilmentcrowd)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)