Skip to content
Inbound and Receiving

Nothing enters your warehouse unaccounted for.

CanShip's receiving workflow is built around scan-to-confirm. Every unit gets scanned, every discrepancy gets flagged, every damaged item gets a photo. The inventory ledger updates the moment receipt is confirmed.

The workflow

Six steps. One audit trail.

Inbound is where most warehouse pain starts. Wrong SKUs received, damaged units missed, multi-pallet receipts that take an hour to confirm. CanShip turns receiving into a structured workflow where every unit is accounted for the moment it's logged.

Step 1

Receipt creation

Create the inbound receipt before the truck arrives. Enter the PO or ASN, expected SKUs, and expected quantities. Optionally tag the client (3PL) or storage location.

Step 2

Arrival and staging

Mark the receipt as arrived. CanShip queues it for processing. Multiple receipts can be in-flight at once across your dock doors and zones.

Step 3

Scan to confirm

Your team scans each unit against expected quantities. CanShip flags over-receipts, under-receipts, and SKU mismatches in real time. Mobile scanner UI works on any phone with a camera.

Step 4

Damage and discrepancy capture

Found damage? Tap to add a photo. Found a discrepancy? CanShip records it against the receipt with a timestamp and the operator's name. Nothing gets resolved off the books.

Step 5

Put-away

Assign each unit to a bin. Suggest-by-rules (FIFO, by SKU history, by client zone) or pick the bin manually. Multi-warehouse, multi-zone, multi-bin all supported.

Step 6

Ledger update

The moment receipt is confirmed, the inventory ledger updates with a transactional entry. Every received unit is now visible to allocation, to the client portal, and to your storefront.

When things go wrong

Receiving exceptions, handled in the same workflow.

Quantity mismatch

Over-receipts and under-receipts, flagged

If the count doesn't match the PO, CanShip flags it before put-away. The receipt stays open until the discrepancy is resolved or explicitly accepted.

Damage

Photo evidence on every damaged unit

Damaged on arrival? Snap a photo from the scanner UI. The image attaches to the receipt line and the inventory ledger. Useful for vendor claims and insurance.

Wrong SKU

Unexpected items, captured not lost

Vendor sent the wrong SKU? CanShip lets you receive it as an unexpected item, attach it to the PO with a note, and route it for vendor review. Nothing disappears into a backroom.

Returns receiving

Returns are inbound too

When a return arrives, your team receives it the same way: scan, inspect, and decide. Restock, quarantine, or flag for disposal. The ledger reflects the movement.

Why it matters

Get receiving right, the rest of the warehouse follows.

Compounding errors
A receiving error becomes 50 picking errors

If 5 units are missed at receive, every downstream pick draws against a phantom count. CanShip catches receiving errors at the source, where they're cheap to fix.

Audit trail
Every unit, every operator, every timestamp

Each receipt entry is immutable. If something doesn't add up later, you can trace it back to the exact moment it was scanned and who did the scan.

See it live

See receiving running on a real dock.

Live walkthrough using a real PO, real scans, real exception handling. Most calls wrap in 30 to 45 minutes.