Reference · built on requestOperator by FibricOrders & fulfillment

Split Shipment

Decides, for an order with only part of its stock on hand, whether to ship what is here now or wait and send one box.

Request accessPricing ↗

About

A multi-line order where one line is short forces a choice: send two packages or make the customer wait. This operator reads each order whose lines cannot all be filled from one location today, the available quantity of the short line by location and its incoming date, and the rate for a second package. It weighs those against the rules you set, such as the ceiling on added carrier cost and how many days a customer may wait, and proposes one of two outcomes.

Ship-partial-now becomes a fulfillment order split with the second shipment's rate attached. Hold-and-consolidate becomes a hold with the release date. Either way the customer notice is drafted with it, and a person approves before anything moves.

This is a reference listing. It documents what Fibric would read from Split Shipment and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Shopify fulfillment orders whose line item quantities exceed the available quantity at the assigned location
  • InventoryLevel quantities per location, including available, committed, and incoming, with the item and location they belong to
  • Katana current inventory per variant and location, with quantity_committed, quantity_expected, and quantity_missing_or_excess
  • Rates for the second package from EasyPost or Shippo, one per carrier account and service, with price and delivery estimate
  • ShipHero warehouse_products per warehouse and purchase_orders with quantity_received
  • The order's shipping method and the shipping amount the customer paid

Proposed actions

  • Target capability: propose a fulfillmentOrderSplit that moves the in-stock lines to a new fulfillment order for shipment today
  • Target capability: propose a hold on the whole fulfillment order with reason notes naming the short line and the expected date
  • Target capability: propose the rate to buy for the second package, with its price shown next to the shipping the customer paid
  • Target capability: propose the customer notice for either outcome: two packages and their dates, or one package and its date

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Split when the second box is cheap

    Read the Shopify inventory by location, quote the second package through EasyPost, and propose the split when the rate is under your ceiling.

    With Shopify, EasyPost

  • Hold when the stock is days away

    When Katana shows quantity_expected on a dated purchase order within your wait limit, propose the hold with that date and the notice to the customer.

    With Katana Cloud Inventory, Shopify

  • Consolidate at the 3PL

    For ShipHero orders, compare the warehouse's stock against the inbound purchase order and propose whether the pick waits or goes as two shipments with Shippo rates.

    With ShipHero, Shippo

Requirements

  • A store connector that exposes fulfillment orders and per-location inventory, such as Shopify
  • An inventory or warehouse source with incoming quantities and dates: Katana, ShipHero, or Linnworks
  • A rating source for the second package: EasyPost, Shippo, or a carrier rating API
  • Your thresholds: the added cost you will absorb per order and the longest wait you will impose
Authentication
Operates with the store, inventory, and shipping API credentials granted to the listings it is built on.

Limits

  • It decides per order, not per catalog; a standing rule to always split a SKU belongs in your store settings
  • If Shopify cannot split the fulfillment order in its current state, the mutation creates a replacement fulfillment order; the proposal says which will happen
  • Incoming dates come from purchase orders. Without an expected date, hold-and-consolidate is not offered
  • Rates are quoted at proposal time and may differ when the label is bought

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Split Shipment ↗

Questions and answers

What is the person approving?
One recommendation per order: split now with the second package's quoted rate, or hold until a named date. The customer notice is attached. Approving the split changes the fulfillment order; buying the label remains a separate step in your shipping tool.
What record does a split or hold leave?
On the order: which lines moved to which fulfillment order, the rate quoted for the second package, or the hold reason and release date; the thresholds in force; the approver; and the notice sent.
Does it ever ship, hold, or message on its own?
No. Every split, hold, rate purchase, and customer notice is a proposal. If your thresholds are not met in either direction, it explains why and leaves the order untouched.
Ask about Split Shipment

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy