---
title: "Connect Stord (OMS) to Rig — Rig guide"
description: "Connect Stord OMS to Rig with an API key, organization ID and network ID and sync inventory, the stock-movement ledger, orders, items and facilities."
canonical: "https://rig.so/guides/connect-stord"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Stord (OMS) to Rig

Sync Stord inventory levels, the stock-movement ledger, sales, purchase and transfer orders, items and facilities into Rig. Every Stord OMS request is scoped to an organization and a network, so connecting takes an API key plus both IDs.

## Before you start

- You need a Stord API key that starts with `stord_sk_`. Stord's developer documentation is password protected, so ask your Stord contact if you cannot find where to create one.
- Have your organization ID and network ID ready. Both are UUIDs.

## Step 1: Collect your Stord credentials

1. In Stord One, open **API keys** and create a key. It starts with `stord_sk_`.
2. Find your network ID in the address of your dashboard, in the `distribution_networks/<id>` part.
3. Find your organization ID in the `/v1/auth/organizations/<id>/` requests the Stord console makes, or ask your Stord contact for it.

## 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 **Stord (OMS)**, open the card and click `Connect`.
3. **API key**: Paste the key that starts with `stord_sk_`.
4. **Organization ID**: Paste your organization UUID.
5. **Network ID**: Paste your network UUID.
6. **Days of history on first sync**: Pre-filled with `365`. This sets how far back the first load reads stock movements and orders.
7. Click `Continue`. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click `Connect`.
8. 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

Stord (OMS) lands in its own `stord` schema in your warehouse:

- **Facilities and items**: your facilities and the product master.
- **Inventory by facility**: a point-in-time stock snapshot per facility.
- **Inventory adjustments**: the stock-movement ledger.
- **Orders**: sales orders, purchase orders and transfer orders.

## Good to know

- Sales orders and purchase orders sync incrementally on their update time, and the ledger on its adjusted time.
- Facilities, items and inventory are read in full each sync. Transfer orders have no date filter, so Rig scans them all each time.
- Stord pages with a cursor that does not carry filters, and Rig repeats the filters on every page so no window is skipped.
- To disconnect Stord (OMS), 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

- Follow stock movement, not just stock level
- Manage transfers between facilities
- Join supply chain to sales

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

## Stord (OMS) documentation

- [Stord developer documentation (password protected)](https://developers.stord.com)

Was this guide helpful?

Yes No

---

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