Skip to main content

AI Job Optimization FAQ

Frequently Asked Questions & Critical Configuration Tips for AI Job Optimization

Updated over 2 weeks ago

Overview

This knowledge base covers the most common configuration issues, setup questions, and operational FAQs for Logiwa IO's AI Job Optimization feature. It is organized into two sections:

  • Critical Tips — Known system limitations with required workarounds that must be applied for correct AI behavior.

  • Frequently Asked Questions — Setup guidance, behavioral explanations, and system limits.

Section 1: Critical Configuration Tips

The following items are known system limitations that require manual workarounds. These are not optional steps — failing to apply them will result in incorrect AI behavior.

Tip #1: Mobile Cart Dimensions are 0 or Locked

  • Root Cause: IO UI does not allow editing dimensions after a Cart Type is created.

  • Solution: For each mobile cart type, create a new mobile cart type with correct dimensions and create one mobile cart per mobile cart type. These mobile carts will not be used by clients — they are created for AI purposes only.

Tip #2: Walking Path is Inefficient

  • Root Cause: System sorts alphanumerically (e.g., A1, A10, A2) instead of logically (A01, A02).

  • Solution: Rename Aisles in Excel: 1. Export Locations. 2. Rename aisles to use leading zeros (e.g., change A1 to A01). 3. Make sure zone names are entered for the locations. 4. Make sure column information is entered. 5. Import to force correct sorting order.

Section 2: Frequently Asked Questions

Dimensions & Definitions

  • FAQ 1: How is "Length" defined?

    • Root Cause: Confusion on axis orientation.

    • Answer: Length is the Picker Facing dimension. Refer to the "Length Width Height" tab in the configuration reference for a visual guide.

  • FAQ 2: What happens when we do not have dimensions of products?

    • Root Cause: Some or all products may be missing dimensions.

    • Answer: When products do not have dimensions, there are two key risks to communicate to the client: 1. Under-utilization of totes and picking carts — instead of fitting as many items as possible, the system will fall back to hard limits configured for the client and warehouse. 2. If items are physically large, the system may create jobs where items do not fit into the assigned tote or picking cart.

  • FAQ 3: Is volume mandatory for locations, mobile carts, and LP Types?

    • Answer: Volume information is not mandatory.

  • FAQ 4: When volume is entered and dimensions are also entered, which does the system use?

    • Answer: The system calculates volume from the entered dimensions and compares it against the manually entered volume value. It then selects whichever value is smaller.

LP Types & License Plates

  • FAQ 5: How many different LP Types do I need?

    • Root Cause: Batch picking and cluster picking require LP types in the system.

    • Answer: You need one LP type for batch picking and one LP type for cluster picking job types. The batch picking LP type must be larger than the cluster pick LP type so the system can correctly distinguish between them for each job type.

  • FAQ 6: Do I need an LP Type for multi-item cluster picking or identical item cluster picking?

    • Answer: Yes. You need at least one LP type for cluster picking. The LP type must have the "Use for AI Jobs" toggle turned on and dimensions entered, since LPs created from this type are used during cluster pick. The dimensions of this LP type should be equal to or less than the cell dimensions of the mobile cart.

  • FAQ 7: Do I need to create an LP Type for batch picking job types?

    • Answer: Yes. Create one LP type that is larger than all other LP types — this is used for batch picking. The "Use for AI Jobs" toggle must be on and dimensions entered correctly. When entering height, you may add a top-off margin (e.g., if physical height is 50 cm, you may enter 60 cm or more depending on overflow allowance).

  • FAQ 8: Do I need license plates created from LP Types?

    • Answer: Yes. Create at least several license plates from any LP type that has the "Use for AI Jobs" toggle turned on.

  • FAQ 9: The customer already has LP Types in the system. Do they need to print new license plate numbers for AI LP types?

    • Answer: No. The customer does not need to relabel totes with the AI LP type. The LP type is a required configuration so AI can capture tote dimensions — it does not need to be physically used in the warehouse during picking. There is no need to relabel any LPNs or totes that are physically in use.

  • FAQ 10: I already have a batch pick cart set up as a location in the system. Do I still need to create an LP Type?

    • Answer: Yes. Having a batch pick cart as a location is a common practice, but the LP type is still required. Similar to the tote LP type, this LP type does not need to be used during picking — it is only for AI to capture batch picking cart dimensions.

  • FAQ 11: What if we have more than one bushel cart type with different physical sizes?

    • Answer: The system selects the largest LP type with the "Use for AI Jobs" toggle turned on as the single batch picking cart reference. Job size will be based on this one LP type only.

Map & Location Setup

  • FAQ 12: Is the 2D Map mandatory?

    • Answer: Using the 2D map is not mandatory but is highly recommended. It is a beneficial additional setup for job optimization, but not required.

  • FAQ 13: What happens when we do not have a 2D map?

    • Also applies to: "How is the task sequence created?" "How is the picking path decided?"

    • Answer: When there is no 2D Map in the system, the optimization algorithm relies entirely on the Location Metadata provided in your IO data setup. To create a pick path, the system sequences tasks based on a specific hierarchy:

      1. Zone

      2. Aisle

      3. Column (Bay)

      How to Improve Optimization: From a "bird's-eye view" perspective, the Zone, Aisle, and Column data must be unique enough for the system to distinguish between different physical positions.

Job Types & Wave Configuration

  • FAQ 14: Why do I get too many order-based pick and pack jobs, or why don't I get multi-item cluster picking jobs even though the job type is enabled?

    • Root Cause: Order-based jobs are generally the result of either order size being too large to fit into totes, or an LP type and mobile cart setting mismatch.

    • Also applies to: "Why are all orders in AI-OrderBasedPickPack?", "Why are these orders in Order Based Pick and Pack job type?"

    • Answer:

      Check 1 — Mobile Cart Type & Mobile Cart Dimensions

      First, verify that the client has Mobile Cart Types created and that cell dimensions are entered correctly. If cell dimensions are set to 0, the system will not create multi-item cluster picking jobs.

      • Go to Mobile Cart Types and confirm that Cell Length, Cell Width, and Cell Height are all entered with non-zero values.

      • Go to Mobile Carts and verify that there is at least one mobile cart from the correct type in the system.

      • Valid example: Cell Length: 12, Cell Width: 13, Cell Height: 15

      • Invalid example: Cell Length: 0, Cell Width: 0, Cell Height: 0 — system will not create cluster pick jobs

      Check 2 — LP Types (Container Check)

      If the client has mobile carts, they must also have LP Types configured for use with AI. Verify the following:

      • At least one LP Type must have the Use for AI Jobs toggle turned on, with dimensions and max weight entered.

      • The LP Type must have dimensions equal to or smaller than the cell dimensions of the mobile cart. If no LP Type fits into the mobile cart cell, the system will not create multi-item cluster picking jobs.

      • At least one LP number (license plate) must be created from this LP Type.

      • To verify fit: multiply Length × Width × Height of the LP Type and confirm each individual dimension is smaller than the corresponding cell dimension — volume alone is not sufficient.

        • Valid: LP Type 12×13×15 fits into a cell of 12×13×15

        • Invalid: LP Type 13×13×15 does not fit into a cell of 12×13×15 — one dimension exceeds the cell

      Additionally, a second, larger LP Type must also exist for Batch Picking job types. This LP Type must:

      • Have the Use for AI Jobs toggle turned on

      • Have dimensions larger than the mobile cart cell dimensions

      • Have a max weight greater than the cluster pick LP Type

      • Have at least one LP number created from it

      • Example: 20×15×20

    • Check 3 — Product & Order Volume Check

      Once mobile carts and LP Types are confirmed to be configured correctly, check whether the actual order volumes fit within the LP Type and mobile cart cell. In most cases, order-based pick and pack results from item volumes exceeding the available cell or tote capacity.

      Follow these steps for the jobs reported as incorrect:

      1. Go to the tasks of the job in question (the one assigned to Order Based Pick and Pack).

      2. Retrieve the dimensions (Length, Width, Height) of each SKU from the Products page.

      3. Calculate the volume of each individual SKU: Length × Width × Height.

      4. Multiply each SKU's volume by its Task Quantity — a single unit may fit, but multiple units of the same SKU may not.

      5. Sum the total volumes of all SKUs in the order.

      6. Compare the total order volume against the LP Type volume and mobile cart cell volume.

      If the total order volume exceeds the mobile cart cell capacity, the system will assign those orders to the Order Based Pick and Pack job type. This is expected behavior — the fix is to either adjust LP Type dimensions, increase cell dimensions (see Critical Hack #1), or review order sizes with the client.

  • FAQ 15: Can I enable only the Identical Item Batch Pick job type?

    • Answer: Even when only one job type is enabled, Order-based Pick and Pack remains the default job type active alongside any enabled type. For example: if a client enables Identical Order Batch Pick only, the system will create identical order batch picking jobs when minimum limits are met — but all other order types (single item, non-identical) in the wave will fall into the Order-based Pick and Pack job type.

  • FAQ 16: When there are identical items with lot/batch tracking, does AI group them into separate jobs?

    • Answer: No. If there are identical items with different lot or batch numbers, they will still be grouped into the same job. This may disrupt operations in lot-tracked warehouses and should be communicated to the client as a known limitation.

  • FAQ 17: Does AI create separate identical order batch pick jobs for identical orders that are in a sort wall job type?

    • Answer: There is a configuration setting to separate identical orders from sort wall jobs. If this setting is set to True, the system will create an identical order batch pick job when there are enough qualifying identical orders.

  • FAQ 18: Why are there identical item orders or single item orders in a multi item cluster pick (AI-MultiItemClusterPick) jobs?

    • Answer: The reason for this is the minimum item settings for identical item batch pick job type or minimum single item item count for single item batch pick job type. As an example if the minimum identical item item count limit is set to 5 AI will try to find orders that match the criteria. If it cannot find orders enough for this job type these orders become order based pick and pack initially. But AI tries to fit them into multi item cluster pick cart to at least gain some efficiency.

      In some cases, wave might have more than 5 identical item orders. Let's say 18 orders. AI was able to fit 14 of these orders into 1 or 2 identical item jobs. There are 4 identical item orders left and since it is less than 5 AI will not create an identical item batch picking job. Same logic applies to single item batch picking as well.

Activation & Client

  • FAQ 19: Can we activate AI Job Optimization only for certain clients (one or more)?

    • Answer: Yes. Activation is done at the account/warehouse level, but clients can create a wave rule that allocates only specific clients' orders to be optimized by AI.

Performance & Limitations

  • FAQ 20: What is the maximum number of order lines an individual wave can have?

    • Answer: The system has been successfully tested with waves of approximately 50,000 order lines.

  • FAQ 21: What is the maximum number of waves that can be triggered from one account at the same time?

    • Answer: A maximum of 5 waves from one account can be triggered simultaneously. Leave at least 5 to 10 minutes between different AI wave schedules to avoid conflicts.

  • FAQ 22: How long does it take to optimize a wave?

    • Answer: Optimization time depends on wave size. It may take between 5 minutes and 60 minutes for a typical wave.

  • FAQ 23: Is there a time limit to finalize optimization?

    • Answer: Yes. The current time limit for job optimization is 2 hours. If a wave optimization is not finalized within 2 hours, rule-based jobs will be released to users to allow warehouse operations to continue.

  • FAQ 24: What happens when optimization is not complete within 2 hours?

    • Answer: The rule-based jobs are automatically released to allow operations to continue in the warehouse without delay.

Did this answer your question?