> ## Documentation Index
> Fetch the complete documentation index at: https://parabola.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Stord to Parabola

> Pull Stord inventory, sales orders, shipments, and receipts into Parabola to automate fulfillment reporting, reconciliation, and warehouse alerts.

Stord is a cloud-based supply chain platform that combines warehouse management, fulfillment, and transportation across a network of facilities. Connecting Stord to Parabola lets ops, finance, and supply-chain teams pull inventory, orders, shipments, and product data into the same flows used for accounting, sales-channel reconciliation, and BI reporting, without writing code or paying for a separate ETL tool.

## Pull from Stord

The **Pull from Stord** step brings live data from your Stord One Console into Parabola so you can transform it, blend it with data from other systems, and trigger alerts on custom logic.

<Frame>
  <iframe src="https://demo.arcade.software/qXCWibe6qhlAmeohscMI?embed&embed_mobile=inline&embed_desktop=inline&show_copy_link=true" title="Connect Stord API and filter orders in your Parabola flow" frameBorder="0" loading="lazy" webkitAllowFullScreen mozAllowFullScreen allowFullScreen allow="clipboard-write" />
</Frame>

## How to authenticate

Stord uses a **Bearer token** (also called an API secret key). You'll need this token from your Stord account to connect.

<Steps>
  <Step title="Get your credentials in Stord">
    * From the **Stord One Console**, go to **My Profile** > **API Keys** and select **Create API Key**.
    * Add or edit the key name to describe how the key will be used.
    * Modify the key's permissions to grant only the access this key needs.
    * Select **Create Token** to generate the secret.
    * Copy the secret to a secure place; you won't be able to see it again.
  </Step>

  <Step title="Connect in Parabola">
    * In your flow, add a **Pull from Stord** step.
    * Click **Authorize** and enter your API secret key (Bearer token) when prompted.
    * Once connected, select the Stord resource you want to pull and configure any filters (dates, SKUs, facilities, order statuses) offered by the step.
  </Step>
</Steps>

## Available data

The Pull from Stord step gives you access to a wide range of records across inventory, orders, shipments, and products:

* **Inventory**: Current balances by SKU, lot number, facility, and expiration date, including locked, unlocked, and total on-hand quantities.
* **Receipt confirmations**: Received inventory details with order numbers, processing status, and timestamps for purchase and transfer orders.
* **Sales orders**: Outbound order data including order details, customer information, delivery addresses, and order status.
* **Purchase orders**: Inbound purchase order data with supplier information and expected receipts.
* **Transfer orders**: Inter-facility transfer details showing inventory movements between warehouses.
* **Shipment confirmations**: Tracking numbers and shipment details once orders have shipped.
* **Order documents**: Packing slips and other order-related documents.
* **Products**: Product catalog data including SKUs, names, product types (items, kits, listings), and attributes.

## Common use cases

* **Reconcile orders across sales channels**: Join Stord sales orders with order data from [Shopify](/product/integration/shopify), [Amazon Seller Central](/product/integration/amazon-seller-central), and [Walmart](/product/integration/walmart) so customer service catches missing or delayed fulfillments before customers do.
* **Audit carrier invoices**: Cross-reference Stord shipment confirmations against carrier bills from [DHL](/product/integration/dhl), [FedEx](/product/integration/fedex), [UPS](/product/integration/ups), or [EasyPost](/product/integration/easypost) to flag overcharges and billing variances.
* **Push fulfillment data into accounting**: Send Stord shipment and order data to [NetSuite](/product/integration/netsuite) or [QuickBooks Online](/product/integration/quickbooks-online) on a schedule so finance can post fulfillment costs and revenue cleanly.
* **Trigger inventory alerts**: Pull inventory balances across facilities, then send a [Slack](/product/integration/slack) alert when key SKUs drop below reorder thresholds or when a single facility shows a discrepancy.
* **Validate receipts against POs**: Compare Stord receipt confirmations to purchase orders from your ERP (such as [Fulfil](/product/integration/fulfil) or [Cin7](/product/integration/cin7)) to catch short-receipts and quantity mismatches.
* **Build cross-warehouse dashboards**: Export reconciled Stord data to [Google Drive](/product/integration/google-drive), [Smartsheet](/product/integration/smartsheet), or [Snowflake](/product/integration/snowflake) so ops, finance, and CX work from the same numbers.

## Tips for using Parabola with Stord

* **Match cadence to use case.** Hourly during peak fulfillment windows, daily for inventory reconciliation, weekly for performance reporting.
* **Use date filters for incremental pulls.** Pulling "all orders ever" gets slow on a busy operation. Filter to "updated in the last 7 days" and let downstream logic handle history.
* **Filter by facility for multi-warehouse setups.** Add a facility filter when comparing performance or inventory across locations so each pull stays focused.
* **Join sales orders with shipment confirmations** to calculate fulfillment speed and SLA compliance per order.
* **Set up Checks and Alerts** to catch exceptions: orders missing shipping info, inventory adjustments without reason codes, or receipts that don't match expected quantities.
* **Archive history for trend analysis.** Push reconciled Stord data to a warehouse like [BigQuery](/product/integration/bigquery) or [Snowflake](/product/integration/snowflake) so you can analyze trends without hitting the Stord API repeatedly.

## FAQ

### Can I push data back into Stord?

The Pull from Stord step is read-only. To write back to Stord (for example, creating an order or updating inventory), use a generic **Send to an API** step pointed at the relevant Stord endpoint with your Bearer token.

### How do I limit a pull to one facility or SKU?

Use the filters exposed in the Pull from Stord step (facility, SKU, date range, status). For more advanced filtering, add a **Filter rows** step right after the pull.

### Can I pull data from multiple Stord environments in one flow?

Yes. Add multiple Pull from Stord steps and authorize each with a different API key, then union the results downstream.

***

With Stord and Parabola connected, the inventory reconciliations, fulfillment reports, and ops alerts your team rebuilds every week run on a schedule, with output landing in the systems where the work actually happens.