question

The pickup points implementation was designed to be essentially a mirror of the dropoff points implementation. When there are pickup points, the item moves from the queue to the pickup point, then is loaded by the AGV. When there are dropoff points, the item is unloaded from the agv into the dropoff point, and then eventually moves into the queue. You don't see the items in the dropoff points because you've left the dropoff retrieval time at 0, so the dropoff retrieval process happens in 0 time, and the item is moved immediately into the destination queue.

If you don't want the queue to actually move the items into the pickup location, you can change the Item Pickup section to not do that. The logic there selects a pickup point (Get an Available Pickup Point) and then moves it into the pickup point (Move Item Into Pickup Point). You could remove the activity that moves it into the pickup point, and instead assign a label named pickupPoint to the item that references the selected pickup point. To do this, add an Assign Labels activity with an Assign Labels To of Label: item, and a single label assignment with the name pickupPoint and a value of Label: pickupPoint (this copies the selected pickupPoint from the token to the item itself). Then in the load logic change the agv's destination from wherever the item is held to the item's pickupPoint label (in Travel to Pickup Location change Destination to getlabel(getlabel(token, "item"), "pickupPoint"), i.e. the pickup point that was assigned to that item.

Also, in selecting a pickup point (Get an Available Pickup Point), I set the default query to ORDER BY distance, simply because I didn't know a good prioritization what would work for everyone. If you want to prioritize different, you can just change that query. You could add "priority" labels to each of the pickup points, and then use a query like ORDER BY priority DESC.