Procurement

Inbound stock from PO created to dock-to-stock — on one record

Cybership puts purchasing, receiving, and variance review on the same record warehouse operators receive against. Buyers see what landed, ops see what to put away, and inventory updates without a separate ERP sync.

Book a demoSee putaway flow

Purchase orders

The same PO table buyers and warehouse ops both work from

The same Purchase Orders table operators run from `/teams/purchase-orders` — order status, inventory status, warehouse, expected date, tracking, merchant. Both order and inventory state stay on the row so receiving variance is visible without opening the PO.

  • Filter by order or inventory status
  • Group POs by warehouse or merchant
  • Click a row to receive against it

Purchase orders

DAL-01
Open · Partial
PO
Name
Vendor
Order Status
Inventory Status
Warehouse
Created At
Updated At
Expected At
Tracking Number
Merchant

PO-3398

Spring restock · Acme Apparel—
Pending
Partially Received
DAL-01
1Z999AA10123456784Acme Apparel Co.

PO-3401

Beanie reorder—
Pending
Unreceived
DAL-01
—Loomstead Co.

PO-3402

Holiday tee buildout—
Closed
Received
ATL-02
1Z999AA10123451234Acme Apparel Co.

PO-3404

Sock variety pack—
Pending
Partially Received
DAL-01
1Z999AA10123459876Loomstead Co.

PO-3405

Hat replenishment Q2—
Pending
Unreceived
DAL-01
—Acme Apparel Co.

Receiving log

Every receive event lands on the PO timeline

Operators see exactly when receiving started, what variance was flagged, who flagged it, and whether putaway was generated — without leaving the PO.

Open POs

86

ASN match rate

97%

Variance threshold

≥ 2 units

Avg dock-to-stock

47 min

Receiving timeline

PO-3398
MR

PO created from CSV import

5 lines · 360 units expected · Acme Apparel

8 days ago

ASN attached

1Z999AA10123456784 · 4 boxes · ETA Apr 30

5 days ago

WO

Receiving started · Bay 2

Warehouse Ops scanned tracking on dock

2 hours ago

WO

Variance flagged · SKU-4492

Expected 60 · received 58 · short by 2

1 hour ago

Putaway list generated

238 units routed to L-A12 · L-B03 · L-A05

Just now

Inbound workflow

Procurement and warehouse ops in one workflow

No separate procurement tool, no shadow spreadsheet for receiving. The PO is the operational record — and stays connected to the inventory and putaway models the warehouse already runs.

Create from CSV, ASN, or merchant portal

POs come from where buyers already work — bulk CSV upload, EDI/ASN feed, or merchant-side creation when 3PL clients control their own buying.

Receiving recorded on the dock

Warehouse Ops scans tracking, opens the receive panel, and writes received quantities per line — variances surface immediately on the PO record.

Variance review before stock moves

Short, over, and damaged counts flag against the original line. Discrepancies stay on the PO so vendor follow-ups don't get lost in chat.

Direct hand-off to putaway

Received units feed putaway lists and on-hand inventory in the same workflow — no separate transfer step, no double entry.

Attachments stay on the record

Pack lists, vendor invoices, and inspection photos attach to the PO line so receiving evidence lives next to the count it produced.

One source of truth for inventory

Received stock writes to the same Inventory History table operators already read. No reconciliation between procurement and warehouse views.

Received units feed directly into the same Inventory History table — no batch sync, no end-of-day reconciliation.

See your inbound flow on one record

Walk us through how your team receives and we'll model PO, receiving, variance review, and putaway end-to-end.

Schedule a Demo

Explore more of our features

Inventory Management

Sales channel syncing, cycle counts, purchase orders, receiving, and inventory visibility.

Putaway Lists

Scan a location to start putaway, route received stock, and manage putaway task lists.

Replenishment

Run replenishment reports, configure task rules, and drill into product-level restock work.