> ## 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 RyderShip to Prowork

> Pull RyderShip orders, items, ship notices, and consumer returns into Prowork to automate fulfillment reporting, inventory reconciliation, returns tracking, and SLA alerts.

RyderShip (formerly Whiplash) is the ecommerce fulfillment platform (WMS and OMS) behind Ryder's ecommerce fulfillment business. Brands use RyderShip to manage orders, inventory, inbound shipments (ship notices), returns, and shipping across Ryder's fulfillment centers, with connections to sales channels like Shopify. Connecting RyderShip to Prowork lets ops, finance, and CX teams pull live order, inventory, inbound, and returns data into the same flows they use for channel reconciliation, carrier audits, and reporting, so the weekly spreadsheet work runs on a schedule instead of by hand.

## Pull from RyderShip

The **Pull from RyderShip** step brings live data from your RyderShip account into Prowork. To connect, request V2 API access from RyderShip, enter the client ID, client secret, and scope they give you, then log in to the RyderShip web app as the user you want to connect.

## How to authenticate

RyderShip uses OAuth 2.0. Prowork acts on behalf of the RyderShip user who logs in, so Prowork can access all of that user's resources, such as orders and items. Access tokens last two hours. Prowork renews them automatically after setup, so you only log in once.

**1. Request V2 API access from RyderShip**

The RyderShip V2 API is invite only. Request access with the [RyderShip V2 API request form](https://help.whiplash.com/hc/en-us/requests/new?ticket_form_id=360001303092), or ask your RyderShip Onboarding Specialist or Customer Success Manager.

In your request, ask RyderShip to register this callback URL:

```text theme={null}
https://parabola.io/api/steps/generic_api/callback
```

RyderShip sends you an **application ID** (client ID), a **client secret**, and a **user scope**. The scope is either **user\_read** (read the data the user has access to) or **user\_manage** (create and change data). For pulling data into Prowork, ask for **user\_read**.

**2. Add the step and authorize**

In your flow, add a **Pull from RyderShip** step, then click **Authorize**. The **RyderShip OAuth2** form opens.

**3. Enter your credentials**

Enter your application ID (client ID), client secret, and the scope RyderShip gave you (**user\_read**). The authorization and token URLs are already filled in.

**4. Log in to RyderShip**

When prompted, log in to the RyderShip web app as the user you want to connect, and approve access.

**5. Choose your data**

Back in Prowork, pick the RyderShip data you want to pull, such as Orders, Items, or Ship Notices.

For more detail, see RyderShip's [Authentication for the V2 API](https://help.whiplash.com/hc/en-us/articles/360050870691-Authentication-for-the-V2-API) guide.

## Available data

The Pull from RyderShip step gives you access to:

* **Orders**: Order records with status (such as Processing, Packed, Label Purchased, Shipped, Delivered, Cancelled, Paused, Insufficient Inventory, and return statuses like Pending Return and Refund Requested), order type (retail, wholesale, DTC, dropship, transfer), created, shipped, and due dates, shipping method and carrier, tracking numbers and links, shipping and billing addresses, actual shipping cost, packages (dimensions, weight, cost, tracking), warehouse, originating store or channel (Shopify, Magento, and more), expedited, gift, and signature flags, and customs info.
* **Order details**: The full record for a single order, useful when you need every field for a specific order.
* **Order history**: The status timeline for an order, including the date, event type, description, and who made each change.
* **Order items**: Line items on an order with SKU, quantity, price, item ID, packed quantity, and wholesale details.
* **Serial numbers**: Serial numbers recorded for an order line item, linking each device's serial number to the order it shipped on.
* **Items**: Your catalog of SKUs and variants with title, SKU, description, scancode/EAN, dimensions, weight, price, wholesale cost, vendor, category, available quantity, published quantity (including inbound), low inventory threshold, lot control, hazmat, country of origin, tariff number, returnable and bundle flags, and velocity.
* **Ship notices**: Inbound shipments (ASNs) expected at or received by a RyderShip warehouse, with ETA, status, carrier, tracking, purchase order numbers, line items with quantities expected, good, and damaged, unit cost, lot info, arrival and delivered dates, warehouse, and box count.
* **Consumer returns**: Returns (RMAs) with status, original order, exchange order, return items (SKU, quantity, quantity good and damaged, return action), carrier, tracking, arrival, delivered, and completed dates, ETA, warehouse, shipping costs, and notes.
* **Consumer return details**: The full record for a single consumer return.
* **Notification subscriptions**: The webhook, Slack, and email notifications set up on your RyderShip account, with the event, type, destination, and whether each one is active.

You can filter most of this data before it reaches your flow, for example to orders shipped in the last 7 days, items updated since yesterday, or ship notices with a certain status. You can also sort results and choose only the fields you need.

## Common use cases

* **Reconcile orders across sales channels**: Join RyderShip orders with [Shopify](/docs/product/integration/shopify), [Amazon Seller Central](/docs/product/integration/amazon-seller-central), or [NetSuite](/docs/product/integration/netsuite) to flag orders that never made it to the warehouse, status mismatches, or tracking that never synced back to the channel.
* **Monitor fulfillment SLAs and stuck orders**: Compare order created dates with shipped dates and flag orders sitting in Paused, Insufficient Inventory, or Processing for too long, then send a [Slack](/docs/product/integration/slack) alert so ops can step in before customers notice.
* **Audit shipping costs against carrier invoices**: Match RyderShip's actual shipping cost and package data against [UPS](/docs/product/integration/ups), [FedEx](/docs/product/integration/fedex), or [DHL](/docs/product/integration/dhl) invoices and your expected rates to catch overcharges, surcharges, and billing errors.
* **Track inbound inventory and receiving accuracy**: Compare ship notice quantities expected against quantities received good and damaged by PO number, and flag shortages, overages, and late arrivals for your purchasing team.
* **Report on returns and exchanges**: Roll up consumer returns by SKU, return action, and condition (good vs. damaged) to spot problem products, track restock rates, and reconcile refunds with finance.
* **Trigger low-stock and replenishment alerts**: Compare each item's available quantity with its low inventory threshold and velocity, include inbound quantities from ship notices, and send a daily reorder list to purchasing.

## Tips for using Prowork with RyderShip

* **Schedule your flow to run on a regular cadence.** Daily works for inventory and returns reporting, hourly for SLA and stuck-order alerts, and weekly for shipping cost audits.
* **Use date filters to keep pulls fast.** RyderShip's API guidance recommends filtering to records that changed since your last sync. Pull orders shipped in the last 7 days or items updated since your last run instead of your full history every time.
* **Join orders with order items.** Order records and line items come in separately, so join them on the order ID to get SKU-level views of what shipped.
* **Pair ship notices with items for a full inventory picture.** Combine available quantity with inbound ship notice quantities to see what's on hand and what's on the way.
* **Use Alerts to flag discrepancies.** Add checks for orders past their due date, received quantities that don't match the ship notice, or returns marked damaged, and get notified when something looks off.
* **Push results where your team works.** Send outputs to Google Sheets, [Slack](/docs/product/integration/slack), email, or your data warehouse so ops, finance, and CX work from the same numbers.
* **Connect with a shared, long-lasting RyderShip user.** The connection acts on behalf of the user who logs in, and RyderShip allows one API connection per customer account. Use a user that won't be deactivated when someone changes roles.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.