warehouse-distribution

Run the receive subcommand with the PO number and the --verify flag to check expected quantities against received items. The script returns a receipt record with discrepancies for short or damaged shipments and marks putaway status as pending.

Use the pick-wave subcommand with --type store-replenishment and an optional --wave-size. The planner batches picks by order priority, zone proximity, and carrier cutoff times, rejecting waves that exceed the configured maximum size.

Cross-docking transfers inbound shipments directly to outbound staging when they match open store replenishment orders, skipping storage. Use it when timing between inbound arrival and outbound carrier pickup is tight, since a 30-minute delay can miss the wave.

Yes, carriers are defined in layout.yaml with their pickup times, such as DHL and SF Express. The dispatch subcommand assigns shipments by destination, service level, cost, and pickup schedule, then generates manifests.

The wave size exceeds the configured maximum set by WAREHOUSE_MAX_WAVE_SIZE, which defaults to 500. Reduce the requested wave size or raise the limit, but note that oversized waves create zone congestion.

Do not use it for store-level inventory management, which belongs to the store-replenishment skill. Also avoid wave planning without first checking carrier cutoff times, since missing a pickup window causes a 24-hour delay.