Overview
When replenishment moves cases (or another higher pack type) from reserve to a pick face that's picked in units, Logiwa IO can convert that stock to the UOM (unit of measure) pack type automatically. Conversion happens on the server when the pick is completed. The operator does the task as usual and is never asked to choose a pack type. Lot, expiry date, production date and PO carry over to the converted units, so inventory lineage is kept.
When to use it
Turn on conversion when:
You store cases in reserve but pick orders in units from pick faces.
The same stock serves both case (B2B) and unit (B2C) orders.
You want overnight replenishment to break cases so pick faces are ready before peak.
Operators currently hit pack type errors or you fix pack types with manual stock adjustments after replenishment.
Prerequisites
The product has a higher pack type (for example Case) and a UOM pack type (for example Unit) with a UOM ratio, such as 1 Case = 12 Units. Without a ratio, conversion can't happen.
A replenishment job type. See Create a Job Type for Replenishment.
You can edit Job Types.
Step-by-step setup
Go to Settings > Job Types and open the replenishment job type, or create one.
On Settings, find Allow Higher Pack Type Conversion to UOM (right after Pick Full Pack).
Set it to Yes. The default is No.
Click Save.
The field's tooltip reads: "When enabled, higher pack types picked during this job will be automatically converted to their UOM equivalent at pick completion. Associates will not be prompted."
Changing the setting only affects tasks created after you save.
When conversion happens
Conversion runs at pick completion only when all of these are true:
The job type has Allow Higher Pack Type Conversion to UOM on.
The stock being picked is a higher pack type, not already the UOM pack type.
The picked quantity converts to whole units. If it doesn't (for example after an exceed or short pick that leaves a part pack), the task goes ahead in the higher pack type.
Static and Dynamic tasks convert the same way.
Example: A task picks 3 cases of 12 for a unit pick face. Conversion runs and the target receives 36 units.
How it works by flow
Pick & Put
On the pick screen, a blue info box says higher pack type inventory will convert to the UOM pack type once picking is confirmed. For an LP task, it adds that the units stay in the LP.
The operator picks the cases as usual. At pick confirmation, the stock on the cart or interim location is converted to units.
If any task in the job was converted, the pick success screen shows a blue info box saying some products were converted.
On the put screen, the product shows the UOM pack type and quantity with a Converted from Higher Pack Type chip. For an LP, a blue info box says the LP now holds converted units.
An orange info box explains that the suggested location is based on the original higher pack type. For a unit-based suggestion, tap Suggest Another Location (requires Allow Suggest Another on the job type).
Example: A Pick & Put task picks 34 six-packs. At pick confirmation the cart holds 204 units, and the put task shows 204 units.
Direct Put
On a product task, a conversion chip (for example Case → Unit) appears next to the pack type.
A blue info box says the inventory will convert to the UOM pack type when the put is confirmed, and that the location suggestion is based on the original higher pack type. For an LP task, it says the units stay in the LP.
The operator scans and confirms as usual. Picking, conversion and placing at the target happen together; if any part fails, nothing is moved.
💡 Suggest Another Location is still offered on the Direct Put screen when conversion applies, but every suggestion is based on the original higher pack type. Conversion only happens when the task is completed, so you can't get a suggestion based on the unit quantity in Direct Put.
Example: A Direct Put task moves 24 six-packs to BB-2. BB-2 receives 144 units.
LP tasks
Conversion happens inside the LP; the LP keeps its code and arrives at the target holding units. An LP that holds more than one product can't be converted, and the pick is rejected without moving anything.
Seeing conversions in reports
On the replenishment Task Details screen:
Column | Shows |
Pack Type / To Pack Type | The pack type picked, and the pack type it arrived as. To Pack Type changes to the UOM pack type when conversion runs |
Initial Task Qty | The task quantity when the wave created it. It never changes, even if conversion, an over-pick or a short pick changes Task QTY |
Task QTY | The current task quantity |
Pack Type Conversion Applied | Yes if conversion ran on the task, otherwise No. Shown on the replenishment Task Details screen and included in its Excel export |
Task QTY changes differently per flow:
Pick & Put: the put task's Task QTY becomes the unit quantity (34 cases → 204). Initial Task Qty still shows 34.
Direct Put: Task QTY stays at the picked case quantity (24); only To Pack Type changes to the UOM pack type.
Each conversion also writes a replenishment transaction with From Pack Type = the higher pack type and To Pack Type = the UOM pack type. See Understanding Pack Type Conversion: Lineage, Limitations and Audit Trail.
How it works with other settings
Setting | Interaction |
Pick Full Pack | No conflict. Pick Full Pack rounds the task to whole packs; conversion applies to what was actually picked |
Only Replenish Full LPs | Works together. The whole LP moves and its contents are converted |
Allow Exceed Task Quantity / Update Task Quantity If Less Picked | Conversion uses the quantity actually picked. If that isn't a whole number of packs, the task stays in the higher pack type |
Enable LP Swap | The substitute LP is checked in its original pack type. Conversion then applies to the chosen LP as usual. With conversion on, a substitute LP in a different pack type is accepted |
Common questions
What happens if a Pick & Put job is cancelled after picking? Converted stock on the cart stays as units. It isn't reverted; transfer it manually.
Will replenishment create extra tasks while converted stock is still on the cart? No. Stock on the way to the target is counted as part of the open replenishment task.
A job has a unit task and a case task for the same product. What happens? Each task runs on its own. Only the case task is converted.