Skip to main content

Whiplash (Ryder) integration setup

Map warehouses, then configure two-way orders, SKU product import, inventory reconciliation, and inbound transfers.

A
Written by Argo Ohvril

What syncs between Katana and Whiplash (Ryder)

Data flow between Whiplash (Ryder) and Katana

The table below summarizes each data type and the direction it flows between Katana and Whiplash (Ryder).

Data

Direction

Status

Orders

Two-way

Available

Products

Whiplash (Ryder) → Katana

Available

Inbound stock transfers

Whiplash (Ryder) → Katana

Available

Inventory sync

Whiplash (Ryder) → Katana

Available

Locations and mapping

After Whiplash (Ryder) approves the connection, the configuration screen opens on the Location tab. Each Whiplash (Ryder) warehouse maps 1:1 to its own dedicated Katana location.

  • Not mapped: The warehouse has never been mapped. Click Add to Katana to create its Katana location automatically.

  • Unlink: Pauses a mapped warehouse. Its status then shows Unlinked.

  • Relink: Resumes syncing for an unlinked warehouse.

Only mapped warehouses sync. Nothing syncs until you click Activate sync in the header.

the warehouse location mapping panel on the Location tab, listing Whiplash (Ryder) warehouses with their mapped Katana locations, status labels (mapped, Unlinked, Not mapped), and the Add to Katana, Unlink, and Relink buttons

Products sync

Product mapping creates the required link between each Whiplash (Ryder) product and a Katana item. You can match SKUs in one of two ways:

  • Direct 1:1: The Whiplash (Ryder) SKU matches the Katana SKU.

  • Via SKU aliases: An alias links two different SKUs.

Products are imported by SKU. If a Katana product already has the SKU, it's matched. If the SKU is unknown, Katana creates the product just-in-time.

Kits and bundles become Katana products. Add a bill of materials (BOM) with the components in Katana. On a sales order, a kit line stays a single sales-order row.

the products mapping settings screen showing the SKU matching choice between direct 1:1 matching and matching via SKU aliases

SKU aliasing

An SKU alias links a Whiplash (Ryder) SKU to a different Katana SKU. Use one when the same item has different SKUs in the two systems, for example a legacy or warehouse-specific code. Upload your SKU alias mapping before importing products so mismatched SKUs match existing Katana items and don't create new products.

the products mapping screen with SKU alias mapping, showing Whiplash (Ryder) SKUs paired with different Katana SKUs and the option to upload an alias mapping file

Orders sync

Orders from Whiplash (Ryder) to Katana

Orders import once they reach the configured import-from status (by default, the Open state). After import, they keep updating automatically through every later status change. Each Whiplash (Ryder) order becomes one Katana sales order, with one row per order line. The order source is Whiplash (Ryder).

Each shipped package becomes a Katana fulfillment with the carrier and tracking number. A multi-package shipment creates one fulfillment per package, so an order can show several fulfillments. Together, they never exceed the ordered quantities.

If a Whiplash (Ryder) order is canceled, Katana deletes the matching sales order only if that sales order is still open.

the order sync settings screen with the import and status options, showing the import-from status selector set to Open

Orders from Katana to Whiplash (Ryder)

When a Katana sales order reaches the Ready for fulfillment status, Katana pushes it to Whiplash (Ryder) as an outbound order. From then on, its progress is tracked back in Katana like an imported order.

  • Canceling the Katana sales order doesn't cancel the pushed Whiplash (Ryder) order.

  • Changes you make in Katana after the push don't update the Whiplash (Ryder) order.

the order push settings screen showing that Katana sales orders are sent to Whiplash (Ryder) when they reach the Ready for fulfillment status

Inventory sync

Whiplash (Ryder) stock levels appear in Katana as read-only External inventory at each warehouse's mapped location. The number shown is the warehouse's on-hand quantity. You can't edit it in Katana.

Reconciliation compares Katana's in-stock quantity with the Whiplash (Ryder) on-hand quantity. It runs on a schedule or on demand. When the numbers differ, Katana creates stock adjustments so your Katana stock levels match the warehouse.

the inventory sync settings screen showing read-only External inventory on-hand quantities per mapped location and the reconciliation schedule and run-now options

Inbound shipments

Each Whiplash (Ryder) inbound shipment becomes one Katana stock transfer. The transfer number is the PO number when there is one. Otherwise, it's the inbound ID.

  • Destination: The Katana location mapped to the inbound's warehouse.

  • Origin: The location assigned for each destination warehouse. This location must be mapped.

The stock transfer follows the inbound's status, and received quantities update the transfer. Katana stock transfers have two states: in transit and received. Partial receiving therefore shows as updated expected and received quantities until the shipment is fully received. If an inbound is canceled, Katana deletes its stock transfer.

the inbound shipments screen listing Whiplash (Ryder) inbounds as Katana stock transfers with transfer number, origin and destination locations, status, and expected versus received quantities

What does not sync

  • Products and stock changes aren't sent from Katana to Whiplash (Ryder).

  • Changes to a Katana sales order after it's pushed don't update the Whiplash (Ryder) order.

  • Canceling a pushed Katana sales order doesn't cancel the Whiplash (Ryder) order.

  • Returns and RMAs don't sync.

  • Serial numbers aren't tracked. Lot/batch data appears read-only where Whiplash (Ryder) provides it.

Disconnecting

Go to Katana's Integrations page, open the Whiplash (Ryder) tile, and disconnect. Syncing stops immediately: no new orders, inbounds, or stock levels are imported, and no sales orders are pushed. Records already in Katana stay, including sales orders, fulfillments, stock transfers, and products.

Did this answer your question?