Rydership (formerly Whiplash) is an omnichannel fulfillment and ecommerce technology provider. The Rydership (formerly Whiplash) connector sends products, shipping requests, arrivals, and returns from the app to Rydership, and brings inventory, fulfillments, receipts, return updates, and locations back into the app.
With this connector, you can:
- Push your product catalog to Rydership (formerly Whiplash).
- Push shipping requests to Rydership, and pull fulfillments with tracking back into the app.
- Pull inventory changes from Rydership.
- Push arrivals to Rydership, and pull receipts back into the app.
- Push returns (RMAs) to Rydership, and pull return updates back into the app.
- Pull your Rydership warehouses into the app as locations.
Setup
Before you begin
- A Rydership (formerly Whiplash) login for the environment you want to connect. You sign in with it to authorize the app.
- The exact name of your customer account in Rydership. The app needs it to find your account.
- Your warehouses set up in Rydership. The app brings them in as locations, and shipping requests and arrivals must use one of these locations.
- Any dedicated API values that Rydership gave you, such as a client ID and secret. Most accounts don’t need them.
Prepare Rydership
- Decide which environment to connect: production or sandbox. The sandbox is a separate Rydership account with its own login. If you want to test in the sandbox first and don’t have a sandbox login, ask your Rydership Onboarding Specialist or Customer Success Manager for one.
- Check that you can sign in to Rydership in that environment:
https://www.getwhiplash.comfor production orhttps://sandbox.whiplash.appfor the sandbox. - Find your customer account name exactly as it appears in Rydership. If you aren’t sure, or your login can see more than one customer account, ask your Rydership Customer Success Manager for the exact customer name.
- You don’t need to request your own API access. The app connects through its own Rydership application. Only if Rydership gave you a dedicated client ID and secret, webhook signing secret, or user ID, keep those values ready. To learn more about Rydership API access, see The RyderShip API.
Connect in the app
- Navigate to Integrations in the app.
- Click Add Integration, and then select Rydership (formerly Whiplash). The connection pop-up opens.
- In Select Rydership (formerly Whiplash) environment, select Rydership (formerly Whiplash) (https://www.getwhiplash.com) for production or Rydership (formerly Whiplash) Sandbox (https://sandbox.getwhiplash.com) for the sandbox.
- In Rydership (formerly Whiplash) Customer name, enter your customer account name exactly as it appears in Rydership. The app doesn’t connect without it.
- Leave Rydership (formerly Whiplash) API Client Id, Rydership (formerly Whiplash) API Client Secret, Rydership (formerly Whiplash) API Webhook Signing Secret, and Rydership (formerly Whiplash) API User Id empty unless Rydership gave you dedicated values.
- Click Connect. You’re redirected to Rydership. Sign in with a login for the environment you selected, and approve access for the app. You’re then returned to the app.
- In the integration settings, turn on Pull locations from Rydership (formerly Whiplash) first. Shipping requests and arrivals need these locations.
- Turn on the other flows you want to use: Push product catalog information to Rydership (formerly Whiplash), Push shipping requests to Rydership (formerly Whiplash), Pull fulfillments from Rydership (formerly Whiplash), Pull inventory changes from Rydership (formerly Whiplash), Push arrivals to Rydership (formerly Whiplash), Pull receipts from Rydership (formerly Whiplash), Push returns (RMAs) to Rydership (formerly Whiplash), and Pull returns (RMAs) updates from Rydership (formerly Whiplash).
Note: Finish the Rydership sign-in within 15 minutes of clicking Connect. If you don’t, the integration shows Error with an authorization timeout, and you must click Connect again.
Confirm the connection
- On Integrations, check that the integration shows Connected and that its switch is on. If it shows Error, check that Rydership (formerly Whiplash) Customer name matches your customer account name in Rydership and that you signed in to the environment you selected, and then click Connect again. If it shows Not Configured, the Rydership sign-in didn’t finish. Click Connect again.
- Wait about 5 minutes, and then navigate to Locations. Check that your Rydership warehouses appear.
- Pick one test order in the app. In the integration settings, add its order ID to Process only shipping requests with specific order IDs and save.
- Make sure the order’s shipping request is routed to a Rydership location and is ready for fulfillment.
- Wait about 5 minutes. The app pushes shipping requests every 5 minutes. Check that the shipping request status changes to sent to fulfillment, and that the order appears in Rydership.
- When Rydership ships the order, the fulfillment with tracking appears on the order in the app. The app gets most updates from Rydership right away and also checks every 5 minutes.
- Remove the order ID from Process only shipping requests with specific order IDs and save, so the app pushes all shipping requests.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Process only shipping requests with specific order IDs | The app processes only shipping requests for these order IDs. Use it for testing, and leave it empty in production. | Optional |
| When shipping request is canceled in Rydership (formerly Whiplash), apply the following status to Pipe17 | The status the app gives a shipping request when Rydership cancels it. | Review required, Canceled, Canceled Restock, or Failed. Default: Canceled |
| Use special processing for shipping requests with number of line items exceeding 500 | Turns on special handling for shipping requests with more than 500 line items. | On/Off. Default: Off |
| Allow updating products already existing in Rydership (formerly Whiplash) product catalog | Lets the app update products that already exist in Rydership. When off, the app only creates new products. | On/Off. Default: Off |
| Process only products with specific SKUs | The app pushes only products with these SKUs. After you change this setting, run a product resync. | Optional |
| Force product catalog resync | Resyncs the whole product catalog, and then turns itself off. A full resync can take several days. | On/Off. Default: Off |
| Process inventory information only for products with specific SKUs | The app pulls inventory only for these SKUs. Use it for testing. | Optional |
| Force inventory resync | Resyncs all inventory, and then turns itself off. | On/Off. Default: Off |
| Process only arrivals with specific order IDs | The app processes only arrivals for these order IDs. Use it for testing. | Optional |
| Pull receipts for completed arrivals only | The app pulls receipts only for arrivals that are complete in Rydership. | On/Off. Default: Off |
| Force receipts resync | Resyncs all receipts, and then turns itself off. | On/Off. Default: Off |
| Exclude Rydership (formerly Whiplash) locations from automatic inventory adjustments for receipts | Stops receipts from automatically adjusting inventory at Rydership locations in the app. | On/Off. Default: Off |
| Push returns when there is no matching shipping order at Rydership (formerly Whiplash) | Sends returns for orders that Rydership didn’t ship. | On/Off. Default: Off |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Locations | Rydership → Pipe17 | Runs every 5 minutes when Pull locations from Rydership (formerly Whiplash) is on. Locations are required for order routing and inventory. To learn more, see Using Locations. |
| Products | Pipe17 → Rydership | Runs every 5 minutes when Push product catalog information to Rydership (formerly Whiplash) is on. Sends product updates since the last successful push. |
| Shipping requests | Pipe17 → Rydership | Runs every 5 minutes when Push shipping requests to Rydership (formerly Whiplash) is on. Sends shipping requests created or updated since the last successful push. |
| Fulfillments | Rydership → Pipe17 | Runs every 5 minutes when Pull fulfillments from Rydership (formerly Whiplash) is on. Rydership also sends order status updates to the app as they happen. |
| Inventory | Rydership → Pipe17 | Runs every 5 minutes when Pull inventory changes from Rydership (formerly Whiplash) is on. Pulls the latest inventory since the last successful pull. Rydership also sends inventory changes to the app as they happen. |
| Arrivals | Pipe17 → Rydership | Runs every 5 minutes when Push arrivals to Rydership (formerly Whiplash) is on. |
| Receipts | Rydership → Pipe17 | Runs about once an hour when Pull receipts from Rydership (formerly Whiplash) is on. |
| Returns | Pipe17 → Rydership | Runs every 5 minutes when Push returns (RMAs) to Rydership (formerly Whiplash) is on. |
| Return updates | Rydership → Pipe17 | Runs every 5 minutes when Pull returns (RMAs) updates from Rydership (formerly Whiplash) is on. |
Integration actions
| Action | What it does |
|---|---|
| Pull fulfillments by date | Pulls fulfillments created after a date. |
| Pull fulfillments by ids | Pulls the fulfillments with the IDs you enter. |
| Pull receipts by date | Pulls receipts created after a date. |
| Pull receipts by ids | Pulls the receipts with the IDs you enter. |
| Pull returns receipts by return IDs | Pulls return receipts for the return IDs you enter. |
| Pull return receipts by date | Pulls return receipts created after a date. |
| Pull inventory by SKUs | Pulls inventory for the SKUs you enter. |
Troubleshooting
- The integration shows Error right after you authorize it
The app couldn’t find your customer account in Rydership. Rydership (formerly Whiplash) Customer name is empty or doesn’t match the name in Rydership. Enter the exact customer name, and then click Connect again. If you aren’t sure of the name, ask your Rydership Customer Success Manager. - A shipping request fails with a matching warehouse not found error
The shipping request is routed to a location that didn’t come from Rydership. Turn on Pull locations from Rydership (formerly Whiplash), and route the order to one of the Rydership locations. Arrivals need a Rydership location too. - The integration shows Error with an authorization timeout
The Rydership sign-in wasn’t finished within 15 minutes. Click Connect again and finish the sign-in. - You can’t authorize the app after you click Connect
Check that you selected the right environment in Select Rydership (formerly Whiplash) environment, and that you sign in with an account for that environment. Clear the optional client ID, secret, and user ID fields unless Rydership gave you dedicated values. Finish the sign-in within 15 minutes of clicking Connect. - Product updates don’t reach Rydership
Products that already exist in Rydership update only when Allow updating products already existing in Rydership (formerly Whiplash) product catalog is on. Also check Process only products with specific SKUs. - A shipping request changes status after Rydership cancels it
The app applies the status in When shipping request is canceled in Rydership (formerly Whiplash), apply the following status to Pipe17. Change it if you want a different status, such as Review required. - A return isn’t sent to Rydership
If Rydership didn’t ship the original order, turn on Push returns when there is no matching shipping order at Rydership (formerly Whiplash). - Receipts don’t appear for an arrival
Receipts sync about once an hour. If Pull receipts for completed arrivals only is on, the app waits until the arrival is complete in Rydership.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the platform page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
We’re here to help you succeed with your operations.
Comments
0 comments