Maintain a buffer of approximately 30 minutes worth of tasks or bins based on your system’s throughput (for example, for 1000 bins/hour, aim for about 500 tasks). This allows AutoStore to prepare bins in advance. Adjust between 20–40 minutes as needed, but avoid dropping below 15 minutes. Feed tasks steadily rather than in large waves to prevent spikes in wait times.

Overloading the system with several hours’ worth of work can reduce efficiency, as AutoStore may not be able to optimize effectively. Instead, add new tasks as existing ones complete to maintain a consistent look-ahead buffer.

Urgent requests disrupt planned jobs and can reduce throughput. Simulations assume up to 5% urgent orders; higher rates negatively impact efficiency. Use high-priority task groups sparingly, as unused high-priority tasks waste preparation resources and grid space.

If you use multiple categories (for example, different order types or port groups), apply the look-ahead guideline per category based on its throughput share. Ensure each category has enough tasks to avoid starving ports. High-priority categories that are not actively used negatively impact performance by wasting preparation space and resources.

These parameters add restrictions that limit AutoStore’s ability to optimize, which can increase wait times. Use them only when they are functionally required.

Overriding the next task group using methods such as openbin causes a performance penalty, because already prepared bins may need to be moved away. This should be avoided during normal operation and only used for resuming suspended task groups.

Providing an expected handling time (typically between 5 and 300 seconds) helps AutoStore optimize planning and throughput. If the value is accurate, it improves performance. If it is not needed or unknown, it can be omitted.

The req_time value should represent deadlines for prioritization. Port-level req_time limits can be used to enforce cut-offs. Misalignment between req_time and priority can cause AutoStore to prepare bins that are not actually needed, wasting resources and grid space.

With the Bin Interface, the WMS takes responsibility for performance-related decisions, including bin sequencing, preparation, port queues, and conflict resolution. Poor implementation can lead to suboptimal throughput. The interface is powerful and flexible, but requires a solid understanding of digging and transport costs.

Bins should be prepared in advance and placed in accessible positions. Monitor physical positions and preparation status using getbinlocation or the Log Publisher. Unprepared bins will directly cause picker wait times.

Maintain port queues that cover approximately 10–15 minutes of operation. Avoid bin conflicts, such as assigning the same bin to multiple ports at the same time. Consider travel distances between bins and ports. Use port queue grouping to give AutoStore flexibility to optimize delivery order.

Referring to content codes in queues allows AutoStore to select suitable bins, but overlaps with existing queues must be avoided. For empty bins, automatic preparation must be configured carefully. Higher values may be useful during ramp-up, but should later be normalized to balance putaway and picking performance.

The WMS must sequence bins with awareness of bin positions and preparation state. Suboptimal sequencing increases robot travel distances and reduces throughput. Grouping bins into batches allows AutoStore to optimize within those groups.

Unused ports should be set to CLOSED to avoid wasting robot resources. In AUTO mode, bins are selected automatically, while MANUAL mode requires explicit bin selection. Mismanaged port modes can lead to unnecessary resource allocation.

Recommended values depend on port speed:

• 0 – very slow ports (long delivery times)
• 1 – putaway operations
• 2 – medium-performance picking ports
• 3+ – fast-picking ports (often matches picks per minute)

AS Router can auto-adjust, but manual limits are useful in corner cases.

The minimum cycle time should reflect the theoretical minimum time required to consume one bin (default is 8 seconds). Setting it too low can overload robots, while setting it too high wastes capacity. Adjust based on operator and robot performance.

Bins remaining outside their temperature zones for too long can damage inventory. Use AutoFlush port configuration to return idle bins automatically. Implement WMS-level timeouts for open bins. Incorrect content codes can store bins in the wrong zone, negatively impacting product lifespan.

Unprepared task groups or short queues lead to picker wait times. Avoid inefficient sequences on carousels (for example A–B–A). Use long sequences (10–15 minutes) and monitor preparation states.

For MultiPort, ensure physical ports are closed and flushed before enabling the configuration. For PickUpPort™, follow strict operational flows: use LED guidance, close bins promptly, and ensure operators complete actions without delays to avoid locking and throughput issues.