CartRover Integration

The CartRover integration provides bidirectional data exchange between CartRover and Logiwa. CartRover sends orders and product data into Logiwa, while Logiwa sends inventory and shipment information back to CartRover. This allows CartRover to continue communicating with the connected sales channels while Logiwa manages warehouse fulfillment.

⚠️ Important Point: Logiwa does not create or modify CartRover products or warehouses through these standard integration flows.

ℹ️ Order updates: Logiwa pulls orders from CartRover with a status of New or at_wms. Updates are only allowed if the Logiwa status equals Open, On-hold, or Shortage. CartRover can receive updates from some of the Order Sources it connects to, or use its own Edit button for edits inside the CartRover UI.

2.Locate the CartRover integration card.

3.Click Connect Now.

During setup, provide the CartRover credentials and the Logiwa configuration that should be used by the connection.

💡 Default values: Product Pack Type defaults to Each, and Currency defaults to USD, unless a different value is requested and configured during onboarding.

ℹ️ Note: The CartRover Merchant ID identifies the merchant account within CartRover (see below) and is used for credential retrieval, troubleshooting, and support — but is not entered as a separate field in the Logiwa connection configuration itself.

2.Retrieve the CartRover Merchant API User and API Key from CartRover using the Merchant API credential process.

3. Enter the values in the Logiwa connection setup and save the configuration.

After entering the CartRover API credentials, a pop-up window appears letting you choose which workflows to enable for the connection.

When a new order appears in CartRover with status New (or at_wms), the integration imports the order into Logiwa. After the order is successfully received by Logiwa, the CartRover order status changes to at_wms.

Shipment Order Types in Logiwa are configurable and determine how the warehouse is allowed to fulfill CartRover orders. They are maintained under Settings > Data Setup > Shipment Order Type.

After an order is shipped or partially shipped in Logiwa, shipment information is sent back to CartRover. When the update succeeds, the corresponding order in CartRover changes to Shipped.

If partial shipments are allowed, the Shipment Order Type must have Allow Partial Shipment = Yes and Enable Partial Order Packing = Yes. Logiwa can then send the available items first and send later shipment updates for the remaining quantities.

💡 Example: If an order contains 10 units of a SKU and only 6 are available, Logiwa can ship the 6 available items and send that shipment to CartRover. Later shipments can carry the remaining items with their own carrier, tracking number, and shipment date.

If backorders are allowed, the Shipment Order Type must have Create Back Order = Yes. The first shipment is sent to CartRover, while remaining quantities are tracked on a separate backorder in Logiwa. A later shipment confirmation is sent when the backorder is fulfilled.

Cadence & Trigger: Scheduled automation running every 10 minutes.

For each affected SKU, the integration retrieves inventory data from Logiwa's Available to Promise (ATP) report. The ATP report represents Logiwa's authoritative view of inventory that is eligible to be sold and accounts for operational constraints such as existing orders.

The integration publishes the Sellable Quantity from the ATP report to CartRover. Sellable Quantity represents the portion of on-hand inventory that is available for future orders.

This ensures that inventory already committed to open orders is not overstated on CartRover.

For standard products, the CartRover inventory synchronization uses the Sellable Quantity from Logiwa's Available to Promise (ATP) report.

For Kit to Order products, however, inventory is calculated differently. Instead of using the standard Sellable Quantity, the integration uses the kit's Net Kitting Capacity from Logiwa's Kit Inventory Report.

Inventory Calculation Source for Kits

The Net Kitting Capacity represents the maximum number of complete kits that can currently be assembled from the available component inventory. Because a kit may contain multiple component SKUs, the available quantity of the kit is limited by whichever required component has the lowest available capacity.

💡 Example: Kit SKU MovieBundle requires 1× MovieA (100 available) and 1× MovieB (150 available) per kit. Although there are 150 units of MovieB available, only 100 complete MovieBundle kits can be assembled because only 100 units of MovieA are available. Therefore, Net Kitting Capacity = 100, and the CartRover inventory synchronization publishes 100 units as the available inventory for MovieBundle.

How Component Inventory Affects the Kit

The kit quantity changes automatically as the inventory of its components changes:

This prevents CartRover from advertising more kit inventory than Logiwa can physically assemble.

For standard products:

For Kit to Order products, Logiwa instead determines the number of complete kits that can be assembled based on the available inventory and quantity requirements of all kit components.

Cadence & Trigger: Scheduled automation running every 10 minutes.

The Product Synchronization flow retrieves product and SKU information from the single CartRover warehouse associated with the connection and ensures the corresponding products exist in Logiwa.

Each CartRover connection is linked to one Logiwa warehouse. If a client needs to support multiple warehouses, a separate CartRover connection and workflow must be configured for each warehouse.

⚠️ Important point: CartRover does not know whether a SKU is a kit item or a non-kit item.

💡 Example: If a CartRover connection is configured for Warehouse A, Logiwa retrieves and evaluates only the products associated with Warehouse A for that workflow. If Warehouse B also needs to be integrated, a separate CartRover connection and workflow must be configured for Warehouse B.

⚠️ Direction limitation: The standard Product Synchronization flow is CartRover → Logiwa. Logiwa does not create the product in CartRover as part of this synchronization. If a new product needs to be used with the integration, it should first be created in CartRover and then synchronized into Logiwa.

CartRover can connect to multiple order sources, such as WooCommerce, BigCommerce, Shopify, and other sales channels. Although these channels may all sell the same physical product, they may use different SKU values to identify that product.

Logiwa uses Product Listings to associate these channel-specific CartRover Product Aliases with the corresponding master product in Logiwa.

⚠️ Products must first be created in CartRover before they can be synchronized into Logiwa.

The Logiwa Product Synchronization flow retrieves products from CartRover and creates or matches the corresponding products in Logiwa. The CartRover master SKU becomes the Logiwa product SKU, resulting in a one-to-one SKU relationship between the two systems. For example:

Logiwa does not create the product in CartRover as part of this synchronization. If a new product needs to be used with the integration, it should first be created in CartRover and then synchronized into Logiwa.

Because CartRover acts as middleware between Logiwa and multiple sales channels, the SKU received on an order may not always match the CartRover master SKU. For example, the same physical product may be represented as:

Without additional mapping, a CartRover order received with Big-12345, Woo-12345, or Shop-12345 does not directly match the Logiwa product SKU 12345. If Logiwa cannot identify the product referenced by an incoming order line, the order may be rejected because the SKU cannot be matched to a product in Logiwa.

When an order source uses a SKU that differs from the CartRover master SKU, configure that identifier as a Product Alias for the product in CartRover.

💡 Example: CartRover product 12345 could contain the following aliases:

Each alias should identify the same physical product represented by the CartRover master SKU.

⚠️ Important: Product Alias values should uniquely identify the intended product. CartRover expects an alias code to correspond to a single master product.

CartRover Aliases can be added inside CartRover by navigating to: Locations & Products > Add/View Products > Search for SKU > Edit Product Aliases

After the CartRover Product Aliases have been created, they can be imported into Logiwa as Product Listings.

ℹ️ Important point: This can occur as part of the CartRover Product Synchronization process. Product Listings may also be imported or managed separately when a manual listing import is required. See Product Listings.

The Logiwa master product remains unchanged:

Logiwa SKU: 12345

The CartRover aliases are associated with that product as Product Listings:

⚠️ A Product Listing does not create another inventory product in Logiwa. It provides an alternate identifier that points back to the existing Logiwa product.

After the CartRover aliases have been imported as Logiwa Product Listings, Logiwa can resolve orders that contain a channel-specific SKU.

💡 Example: CartRover receives 3 orders for the same product, but with 3 different SKUs:

All three orders can therefore be fulfilled against the same Logiwa inventory product, 12345.

⚠️ Important: The CartRover Product Alias does not replace the Logiwa master SKU. It acts as an alternate channel identifier — orders containing channel-specific aliases can still be fulfilled against the Logiwa master SKU because each alias is linked to it through a Product Listing.

API requests and responses are logged with the following diagnostic details:

Why doesn't my order create in Logiwa?
Confirm the Client, Warehouse, Shipment Order Type, required address/order data, and that every order-line SKU exists in Logiwa.

Why does inventory route to the wrong warehouse, or not update at all?
Confirm the Logiwa and CartRover warehouse names match exactly.

Why is a product missing in Logiwa?
Confirm the product exists in CartRover and is available under an active warehouse so it can be discovered by Product Synchronization.

Why doesn't the shipment update CartRover?
Confirm the Logiwa shipment contains a carrier, tracking number, shipped quantities, and that the order is in a shipped/partially shipped state.

Why does API authentication fail?
Reconfirm the CartRover API User, API Key, and Merchant ID.

Why doesn't a CartRover order with a channel-specific SKU (e.g., a BigCommerce or Shopify SKU) get created in Logiwa?
Confirm that a CartRover Product Alias exists for that channel SKU and that it has been imported into Logiwa as a linked Product Listing. Without that mapping, Logiwa cannot resolve the SKU to a master product.

When reporting a CartRover integration issue, include the affected order number or SKU, CartRover merchant/account context, Logiwa client and warehouse, approximate time of the error, and the error message or HTTP response if available. These details help identify the affected integration event more quickly.