What does a warehouse need from a bulk shipping run?
A run has to connect the orders, the labels and the bins the picker can actually use. Bulk shipping brings box planning, label purchase, aisle-ordered pick sheets and shipment sync into one label-first, multi-order picking flow.
The app runs across Las Vegas and Mexico. It handles 3,000+ orders a day, with 5,000 at peak.
How does the work move from order to shipment?
Box planning and label purchase happen before the multi-order pick. The system allocates live warehouse bins at label time, produces aisle-ordered pick sheets and syncs the shipment.
The implementation uses Next.js, PostgreSQL, BullMQ, Redis, the WMS API and UPS.
What happens when the original bin cannot be picked?
The app redirects pickers around empty or reserved locations mid-pick. The allocation is tied to live warehouse bins, so the pick is grounded in the location the warehouse can use.
Where does the automation stop?
Pre-flight quantity gates stop the run when the pick does not match the need. That prevents over-labelling and a reconciliation problem later.
Orders and inventory need explicit rules. This is deterministic operations work, rather than a decision delegated to a language model.
What is running in production?
3,000+ orders a day. 5,000 at peak. Las Vegas and Mexico.
Have the same handoff?
We build automation and AI agents for ecommerce teams whose orders move through a real warehouse.