Orders

Choose a warehouse before work reaches the floor

For locally managed orders, Cybership checks every linked Product against accessible sellable inventory, keeps complete candidates when they exist, and selects one warehouse with a fixed distance-and-default score. That assignment stays on the fulfillment work operators allocate, pick, and move.

Eliminate stock gaps before comparing distance

Cybership aggregates the order by internal Product and checks sellable inventory at every accessible warehouse. When one or more warehouses can cover the full requirement, incomplete candidates stop before the score.

DAL-01 and STL-02 each cover all 36 units. PHX-03 is 16 pouches short, so its distance cannot disguise the inventory gap or create an automatic cross-warehouse split.

#10428

Manual

Northline Field Ops · Jul 23, 2026 · 9:14 AM

No eligible fulfillment order exists to merge into, so this order needs a new warehouse assignment.

Product requirements

36 units
  • Product

    Field Jacket · Slate / M

    SKU JKT-SL-M

    × 12

  • Product

    Utility Pouch · Black

    SKU POUCH-BLK

    × 24

Destination

Morgan Reed

1100 Walnut Street
Kansas City, MO 64106

Latitude
39.0997
Longitude
-94.5786

Sellable inventory by accessible warehouse

Every linked Product must meet the full order quantity.

2 of 3 cover all
WarehouseJKT-SL-MPOUCH-BLKCoverageDecision
DAL-01
Default

Dallas, TX

18 / 1240 / 24Complete
Continues
STL-02

St. Louis, MO

14 / 1229 / 24Complete
Continues
PHX-03

Phoenix, AZ

30 / 128 / 2416 POUCH-BLK short
Stops
DAL-01 and STL-02 cover all 36 units, so only those two continue. PHX-03 is 16 pouches short and stops before distance can influence the route.

Turn the winner into allocated fulfillment work

Complete candidates receive the fixed score used by the selector: full coverage, the default preference, a coordinate-pair term, and Haversine kilometers. The winner is persisted on the new fulfillment order and becomes its allocation boundary.

STL-02 scores 9,667.3 and beats default DAL-01 at 9,419.2. Operators then see STL-02 on the fulfillment record with all 36 units allocated and ready for downstream work.

Warehouse selection calculation

Fixed weights used for this locally managed order.

Complete coverage +10,000 · default +100 · coordinate pair +50 · Haversine distance −1/km

WarehouseCompleteDefaultCoordinatesDistanceScoreResult
DAL-01
Default

Dallas, TX

+10,000+100+50730.89,419.2Compared
STL-02

St. Louis, MO

+10,000+0+50382.79,667.3
Selected
STL-02 scores 9,667.3 and outranks default DAL-01 at 9,419.2. The selected warehouse becomes the fulfillment-order and allocation boundary below.

#10428

Manual

Fulfillment Order · Northline Field Ops

Open
Unsubmitted
Unlocked
Ready To Ship

Current view · Line Items

Fulfillments and Charges remain adjacent views on this same fulfillment-order record.

ProductUnfulfilledOrderedAllocated
Product

Field Jacket · Slate / M

SKU JKT-SL-M

12x12x12x
Product

Utility Pouch · Black

SKU POUCH-BLK

24x24x24x
All 36 ordered units are allocated to the selected warehouse; none remain unassigned.

Operators see STL-02 on the fulfillment record and all 36 units allocated there. The calculation above explains the route; Cybership does not present the automatic selection as an order-log event.

Move exact units without losing the trail

When an eligible, unlocked, non-Shopify fulfillment order needs an exception, Change Warehouse accepts exact remaining quantities and a fulfiller-owned target. Cybership rebuilds allocation at both warehouses instead of rewriting the original record in place.

Lauren moves 18 of 36 units from STL-02 to DAL-01. The source stays open with 18 units, the destination remains unsubmitted, and the order timeline records the actor, items, and warehouse change.

Change Warehouse

Select items to move and assign them to a new warehouse location.

Items

2 of 2 items selected

  • Product

    Field Jacket · Slate / M

    SKU JKT-SL-M

    6
    of 12
  • Product

    Utility Pouch · Black

    SKU POUCH-BLK

    12
    of 24

Change Location

Assign selected items to:

DAL-01Fulfiller owned

Remaining fulfillment work

Allocation rebuilt at both warehouses.

18 moved

Source remains open

STL-02

18 units remain

6 jackets · 12 pouches

Destination created or reused

DAL-01

18 units moved

Open · Unsubmitted · not auto-requested

Current view · Timeline

Items, Charges, Returns, Config, Automation Runs, and Tags & Notes stay on this same order record.

Fulfillment order moved for 18 items by Lauren H.

One fulfillment-order move event keeps the transferred Products and both warehouse locations together.

Items

  • 6x Field Jacket · Slate / MJKT-SL-M
  • 12x Utility Pouch · BlackPOUCH-BLK

Fulfillment location

Changed from: STL-02

To: DAL-01

Keep one warehouse decision intact from stock check to floor work

Cybership narrows the candidate pool with complete Product coverage, selects one warehouse with a fixed score, and persists that assignment on fulfillment work. When an operator moves exact remaining units later, both allocation records and the order timeline change with it.

warehouses cover the full order
2/3#10428 needs both linked Products; PHX-03 stops before distance because it is 16 pouches short
from STL-02 to the destination
382.7 kmthe fixed score compares complete candidates with a coordinate-pair term, default preference, and Haversine distance
units allocated at STL-02
36/36STL-02 persists on the fulfillment order that downstream floor work uses
units moved / left at source
18/18Lauren H. moves exact quantities; both allocations rebuild and the order timeline retains the items and locations

Trusted by 3PLs and brands

2FLYcoAmmoSquaredAxion FulfillmentIndustry Thread Worksadrafül labs

See it in your operation

Bring us the warehouse choice your team still checks by hand

Show us the Product requirements, sellable inventory, warehouse coordinates, default preference, delegation boundary, and exception moves behind a repetitive order flow. We’ll map one candidate gate and operator handoff against your network.

No sales call is required to get sandbox access.

Continue exploring

View all features