Platform

Find the record that can explain what changed

Replace screenshot hunts with operational evidence beside the order, inventory movement, return, delivery, rule, or file job your team is already investigating.

Get a free sandboxFollow an investigation

Answer the address question from the order timeline

Northline asks why FO-11929 shipped to a corrected apartment. The order’s Timeline keeps creation, the address update, the brand’s approval, picking assignment, and fulfillment in sequence.

Expand Updated shipping address to see only the fields that changed: Address 2 moved from N/A to Apt 4B, and Shipping Zip moved from 78701 to 78701-1042. The answer stays attached to the order instead of a support thread.

#NFO-10482

FO-11929

Northline Field Ops → Cybership Dallas · DAL-01

Fulfilled
DetailsTimeline
MT
Leave a comment...
Post
Event

Order #NFO-10482 created

Imported from Shopify · 2 line items

Apr 30, 9:14 AM

Updated shipping address

Apr 30, 9:18 AM

Shipping Address 2
N/A → Apt 4B
Shipping Zip
78701 → 78701-1042

Brand approved the apartment correction.

Morgan T. · 1 attachment

Apr 30, 9:20 AM

2 items added to picking session by Lauren H.

Single Item Batch 01

Apr 30, 10:02 AM

2 items fulfilled via Pick & Pack by Lauren H.

Apr 30, 10:26 AM

Changed fields stay specific

The expanded address event shows only Address 2 and Shipping Zip because those are the fields that changed.

Comments remain operational notes

Only the authoring team member can edit for 5 minutes.

Trace the physical movement behind the fulfillment

Inventory History keeps the date, Product, location, operation, signed delta, actor, and description together. The -2 pick names #NFO-10482, while the paired -6 and +6 transfer rows show where stock moved.

Operations can distinguish a pick, transfer, and return receipt without treating one warehouse total as an explanation. The transfer pair nets to zero across locations, while the order pick and return receipt remain separate movements.

Inventory History

Dallas Fulfillment Center

All Locations
All Products

  • Cybership Hoodie

    SKU-4491

    -2
    L-A12-04
    PickLHLauren H.

    Picked 2 eaches to TOTE-10482 for #NFO-10482 in Single Item Batch 01

    Apr 30, 10:11 AM

  • Cybership Beanie

    SKU-2210

    -6
    BULK-A-02
    Transfer
    API key

    Transferred 6 eaches from BULK-A-02 to L-A05-12

    Apr 30, 9:54 AM

  • Cybership Beanie

    SKU-2210

    +6
    L-A05-12
    Transfer
    API key

    Transferred 6 eaches from BULK-A-02 to L-A05-12

    Apr 30, 9:54 AM

  • Cybership Hoodie

    SKU-4491

    +1
    RETURNS-STAGE
    Return received
    System

    Received 1 each from RMA-00418

    Apr 30, 8:43 AM

Order pick

#NFO-10482 · -2

Transfer pair

-6 + 6 = 0

Return receipt

RMA-00418 · +1

Keep each exception on the record that can resolve it

RMA-00418 keeps Return Created, Inspection Started, Mispick Detected, and Warehouse Processing Complete in its Timeline with actor and date. The warehouse exception is visible without pulling it into a generic activity feed.

Use the same pattern for the rest of the operation: open webhook deliveries from the endpoint, executions from the automation rule, and row results from Import/Export Jobs. Each surface keeps the detail its team needs to act.

RMA-00418

Return detail

Inspecting
ItemsReturn LabelsChargesNotesTimeline
  • Return CreatedApr 30, 8:21 AM

    Return created from order #NFO-10411

    MTMorgan T.
  • Inspection StartedApr 30, 8:39 AM

    Inspection started

    LHLauren H.
  • Mispick DetectedApr 30, 8:42 AM

    Wrong item received - mispick detected

    LHLauren H.
  • Warehouse Processing CompleteApr 30, 8:46 AM

    Warehouse processing marked as complete

    System

Follow the record that owns the next question

The return timeline explains the warehouse exception. Delivery, rule, and file questions keep their richer detail on the surfaces that produced them.

Webhook deliveries

Open from Webhook endpoint

Delivery status, attempt count, request and response, and retry state

Automation executions

Open from Automation rule

Published version, step progress, input, output, errors, and re-run lineage

Import/Export Jobs

Open from Job directory

Status, processed and failed counts, row messages, and retained output

Cybership keeps these six evidence surfaces close to the work instead of flattening them into one generic event feed.

Keep the answer close to the work that produced it

Orders, inventory, returns, webhooks, automations, and file jobs each retain the evidence their operators need, without flattening every workflow into the same generic event.

order timeline event types
29including address changes, holds, splits, picking, packing, fulfillment, comments, and returns
return lifecycle event types
19from creation and labels through inspection, discrepancies, disposition, and completion
inventory actor types
3user, API key, and system attribution stay next to each physical location delta
owning evidence surfaces
6orders, inventory, returns, webhook deliveries, automation executions, and file jobs

Trusted by 3PLs and brands

2FLYcoAmmoSquaredAxion FulfillmentIndustry Thread Worksadrafül labs

See it in your operation

Bring us the operational question your team still answers from screenshots

Show us the order, inventory movement, return exception, integration failure, automation run, or file job your team has to reconstruct today. We’ll map the exact records and evidence your operators would use to answer it.

Get a free sandboxBook a demo

No sales call is required to get sandbox access.

Continue exploring

Related workflows

View all features