Picking and packing · private preview
Pick the route. Check the box.
Start with reserved stock, walk the locations in order, and leave a visible exception when the shelf does not match the order.
01 · start with a commitment
Picking begins after reservation.
A pick run is for an order whose parts have been reserved. The reservation keeps those quantities committed while the operator visits each stop; this page does not describe picking as a way to claim unreserved stock.
Illustrative example · synthetic order
- A-03Plate 1 × 2 · red12
- B-07Tile 1 × 4 · dark bluish gray6
- C-11Brick 2 × 4 · white4
02 · walk the locations
The route tells you where to go next.
Brick Pulse orders the stops by the bin route recorded for the reserved lots. The operator sees the current location, the requested quantity, and the next stop. A completed stop stays visible in the run so the route can be reviewed instead of reconstructed from memory.
The app includes a handheld mobile layout and barcode-scanner input in the picking flow. This preview does not name a phone, tablet, scanner model, or connection standard as universally supported; check the hardware and viewport you use during private review.
03 · stop when the shelf disagrees
A short pick stays an exception.
If a bin is short or the item is wrong, record the bounded reason and leave the stop open. The exception does not silently change inventory or reservation facts, and the run cannot complete while a stop remains unresolved. Resolve the physical problem, then return to the route with the exception still part of the history.
Reason: short pick. No inventory or reservation change recorded.
04 · verify before shipment
A completed pick run does not consume stock.
Finishing a pick run leaves order reservations and on-hand stock unchanged. The current app interface does not expose the complete pack-to-ready-shipment workflow. Once an order has a ready shipment, recording it as shipped with its carrier and tracking facts validates the reserved quantities, then reduces on-hand and reserved stock together. A pick exception alone changes neither total, and a refund never implies an automatic restock.
05 · shipment details
Carrier and tracking stay beside the local record.
When a ready shipment is recorded as shipped, its carrier and tracking facts are saved with the local shipment record and its reservations are consumed. This transition does not contact a marketplace. Marketplace writes are currently disabled; any future write would be a separate action with its own controls.
06 · file boundary
Pirate Ship receives a CSV, not an API connection.
Brick Pulse can produce the supported Pirate Ship order CSV for the operator to upload on Pirate Ship's own site. Pirate Ship is not an integration here: there is no Pirate Ship API, credential exchange, or background write from Brick Pulse.
07 · practical questions
Know what the run can and cannot change.
- Can I pick an order before its stock is reserved?
- No. A pick run starts from an order with reserved stock.
- What happens when the bin is short?
- Record the exception. It does not change inventory or reservations, and the run stays incomplete until resolved.
- Does recording a shipment update a marketplace?
- No. The shipped transition records the local shipment and consumes its reservations; marketplace writes are currently disabled.
- Does Brick Pulse connect to Pirate Ship?
- No API integration. Export the supported CSV and upload it on Pirate Ship's site yourself.
08 · private review
See the route with your own shelves.
Seller access is private while the workflow and hardware fit are reviewed. No measured speed, public availability, automatic oversell prevention, or live marketplace outcome is promised by this page.