Platform

Every workflow keeps its own paper trail

Cybership writes operational history into the record that owns the work. Orders, returns, inventory, jobs, and webhooks each carry a timeline operators can read without leaving the page they were already on.

Inventory History

Every adjustment, transfer, and pick is in the same table

The same Inventory History table operators use day to day — picks, replenishments, cycle count adjustments, transfers, and manual edits — with the actor, location, product, delta, and reason on the row.

  • Filter by location, product, or warehouse
  • Color-coded delta for positive and negative changes
  • Click a product or location to jump to the record

Inventory History

DAL-01
SKU-4491
DateProductLocationTypeDeltaActorDescription

Cybership Hoodie

SKU SKU-4491

L-A12-04
Pick
-3Lauren H.
Picked for FO-11929 - Single Item Batch · 4 lines

Cybership Hoodie

SKU SKU-4491

L-A12-04
Cycle Count Adjustment
-1Warehouse Ops
Cycle count recount

Cybership Beanie

SKU SKU-2210

L-B03-01
Replenishment
+24System
Replenishment from bulk to pick face

Cybership Tee

SKU SKU-8810

L-A05-12
Transfer
-6Api Key
Transfer to L-A05-13 - Tote T-104

Cybership Hoodie

SKU SKU-4491

RECEIVING
Manual Create
+50Warehouse Ops
PO PO-3398 received

Where logs live

No separate logging app to switch into

The audit trail sits next to the record it describes. Support and operations stay in one workflow instead of cross-referencing a centralized log viewer.

Orders & fulfillment orders

Routing, holds, splits, edits, manual fulfillments, and assignment changes attach to the order timeline.

Returns

RMA inspection, restock, refund, and discard events live on the return record next to the inspection result.

Inventory & locations

Adjustments, putaway, replenishment, and cycle count results write to product and location histories.

Shipments & labels

Label purchases, voids, refunds, scan-form runs, and tracking event drift land on the shipment record.

Webhooks & jobs

Delivery attempts, retries, response codes, and job runs are kept on the webhook and job records.

Automation & rules

Rule firings, condition matches, and downstream actions stay attached to the triggering event.

inventory.adjusted

Captured
1{
2"actor": "warehouse-ops@acme.com",
3"object": "Fulfillment FO-11929",
4"warehouse": "DAL-01",
5"location": "L-A12-04",
6"sku": "SKU-4491",
7"delta": -1,
8"reason": "cycle_count_recount",
9"trace_id": "5b2…e8a"
10}

Investigation

Narrow the trail to one actor, object, and event

Audit history is only useful when teams find the relevant event quickly. Filter by user, integration, object, workflow, or event type and jump straight back to the affected record.

Review the audit trail your team needs

Walk through order, inventory, job, webhook, return, and shipment history across the workflows your team runs every day.

Schedule a Demo