Orders

Change the plan without rebuilding the order

An order stops matching the original plan when stock moves, a client pauses work, or one line needs another warehouse. Cybership keeps those changes on the fulfillment record: only eligible actions appear, quantities reconcile, and ready work passes directly into picking.

Get a free sandboxSee the order change

Let the fulfillment record decide what is safe

The fulfillment-order detail keeps line items beside status, request state, readiness, warehouse, and its grouped action rail. Order #7342, record 11a929 returns the complete eight-action Fulfillment menu; Create Picking Session remains absent until allocation is ready and fulfillment is in progress.

A temporary hold changes the record to ON_HOLD without changing its eight remaining units. Releasing the final hold returns it to OPEN and UNSUBMITTED before quantity-changing actions resume.

Fulfillment order · record 11a929

#7342

Northline Field Ops

Open
Not ready
ProductUnfulfilledOrderedAllocated
Product

Trail Polo · Navy / M

SKU POLO-NV-M

55
4
Product

Storm Shell · Slate / L

SKU SHELL-SL-L

33
1
5 of 8 units are allocated. The three-unit gap keeps this record out of ready-to-ship work.
Shipping method
UPS Ground
Assigned warehouse
Dallas Fulfillment Center
Request state
Unsubmitted · unlocked
This record remains editable because it has no active lock, but picking cannot start until all eight units are allocated.

Show only actions this record can take

Cybership evaluates order state, request state, allocation, and locks before returning fulfillment actions.

Available fulfillment actions

8
  • Hold Fulfillment
  • Split Fulfillment Order
  • Merge Fulfillment Orders
  • Change Warehouse
  • Start Fulfillment
  • Reprocess Fulfillment Order
  • Check Picking Eligibility
  • Enable Partial Fulfillment

The wider action library remains grouped into Fulfillment (8), View (2), Shipping & Delivery (2), Add Charge (1).

The picker never sees a session that the current record cannot safely create.

Pause the exception without changing quantity

A hold keeps the original line-item quantities on the record, then restores eligible actions when the final hold is released.

Hold recorded

Reason · Other

On hold

Two Storm Shell units are waiting on shelf replenishment.

8 units remain on #7342, record 11a929.

Final hold released

Allocation cleanup runs automatically

Open

8 items released from hold by Lauren H.

Request · Unsubmitted
Cleanup · AUTO
The hold lifecycle stays on the fulfillment record, so operators can explain why work paused and when it became eligible again.

Change the units of work; keep the unit math

Split one Trail Polo and two Storm Shells into a three-unit sibling while five units remain on the original. Both records retain order number #7342 and use their own shortened record IDs. From there, move the complete child to ATL-02 or merge an eligible sibling back into the DAL-01 record without creating a new order.

Move rebuilds destination allocation and leaves the fulfillment request unsubmitted. Merge stays inside the same underlying order and warehouse, and both records must remain unlocked and eligible.

Split an exact quantity into a sibling record

Choose the quantity from each line that should move. At least one unit stays on the source record.

Product

Trail Polo · Navy / M

SKU POLO-NV-M

1of 5 units
Selected item 1
Product

Storm Shell · Slate / L

SKU SHELL-SL-L

2of 3 units
Selected item 2
Original record
11a929
5 units remain
New sibling record
11a92b
3 units move
Quantity check
8 = 5 + 3
DAL-01 · same order and warehouse
3 of 8 units move to the sibling; the underlying order total does not change.
Quantity conserved

Move the sibling to another warehouse

Move all 3 remaining units to ATL-02, then rebuild allocation against stock there.

Source closes

#7342

Record 11a92b

DAL-01

Closed

Destination opens

#7342

Record 11a92c

ATL-02

Open
Allocation is rebuilt at ATL-02; the fulfillment request remains unsubmitted for an operator to review.

Merge only an eligible sibling

The source must be unlocked and share the same underlying order and warehouse as the target.

Underlying order
#7342
Warehouse
DAL-01
Source
11a930 · 2 units
Target
11a929 · 5 units

Target after merge

5 + 2 = 7

Source closed
Holds remain on their original records; the merge moves selected quantities, not hold history.

Rebuild allocation, then hand ready work to picking

When ATL-02 inventory arrives, reprocess order #7342, record 11a92c with the other selected fulfillment orders. That record reaches three allocated units; the locked and already-ready records keep their own failure codes. Start Fulfillment then moves the successful record to IN_PROGRESS and ACCEPTED before Cybership creates a single-order picking session.

A failed sibling does not erase a successful allocation. Start Fulfillment does not create the picking session implicitly; it opens Create Picking Session once the order meets the picking gate.

Retry allocation without hiding partial results

ATL-02 replenishment posted

1 successful
2 failed
Order / recordOutcomeResultCode

#7342

Record 11a92c

Successful
3 of 3 units allocated at ATL-02—

#7350

Record 12001a

Failed
Order is currently being fulfilledORDER_LOCKED

#7351

Record 12002a

Failed
Order is already ready to shipALREADY_READY
Each requested record returns its own result. A locked or already-ready order does not roll back the allocation that succeeded.
Record 11a92c now has all three units allocated and can move to fulfillment.

Carry the ready record into picking

Allocation readiness, request acceptance, and session creation remain separate, reviewable transitions.

1 · Allocation ready

#7342 · 11a92c

3 of 3 units allocated

Ready to ship

2 · Start fulfillment

Submit and accept the request

The order moves in progress only after the fulfillment request is accepted.

In progress
Accepted

3 · Create picking session

#PS-1046

One order enters a single-order session and acquires the picking lock.

Unassigned
Each transition leaves an explicit state for the next operator instead of collapsing fulfillment and picking into one opaque action.

Mobile picking handoff

The eligible session appears in the mobile workflow; the warehouse timer starts only when the picker begins.

Picking session

#PS-1046

Type
Single Order
Orders
1
Bins
1

Ready for assignment

Unassigned

When you start picking, the timer will begin tracking session performance.

Next operator action · Start Picking

Desktop orchestration ends with an eligible session record; mobile picking owns assignment, scanning, and timer start.

Keep exception work on the order that changed

The operational gain is a controlled route from an unexpected warehouse condition back to executable work. Operators can see why an action is available, preserve quantity through the change, and hand the resulting record to picking without reconstructing it in a ticket or spreadsheet.

the record determines the available actions
Live statestatus, request status, platform, remaining quantity, readiness, sibling work, and active locks shape the fulfillment menu
a split keeps the quantity ledger intact
8 = 5 + 3five units remain on order #7342, record 11a929 while three move into sibling record 11a92b at the same warehouse
merge stays inside one operational boundary
1 ordersource and target must share the underlying order and warehouse and remain in eligible unlocked states
allocation retries keep every outcome usable
Per recorda successful allocation stays ready while locked or already-ready records return their own explicit failure codes

Trusted by 3PLs and brands

2FLYcoAmmoSquaredAxion FulfillmentIndustry Thread Worksadrafül labs

See it in your operation

Bring us the order exception your team still rebuilds by hand

Show us the hold, quantity split, warehouse move, sibling merge, or allocation retry that currently escapes into tickets and spreadsheets. We’ll map the eligible action, state transition, quantity ledger, and picking handoff against your operation.

Get a free sandboxBook a demo

No sales call is required to get sandbox access.

Continue exploring

Related workflows

View all features