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.
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.
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.
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.
Mark the receipt as arrived. CanShip queues it for processing. Multiple receipts can be in-flight at once across your dock doors and zones.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Live walkthrough using a real PO, real scans, real exception handling. Most calls wrap in 30 to 45 minutes.