Overview
LP Swap in Replenishment lets pickers substitute a different LP at the same reserve location when the LP a replenishment task was originally assigned is hard to reach, damaged, or otherwise unavailable.
Logiwa IO validates the substitute in real time — checking the product, the applicable date threshold, and any job type conditions — before completing the task, so pickers keep moving without a supervisor override. A single toggle on the replenishment job type governs both Full LP and Pick-from-LP tasks.
When to Use It
Use LP Swap in Replenishment when:
A picker arrives at the assigned LP and finds it damaged, blocked, or otherwise inaccessible
The reserve location holds more than one LP of the same product and you want pickers to substitute freely instead of stalling the task
You want receiving-date or expiry-date flexibility instead of requiring an exact match to the originally assigned LP
Prerequisites
Before LP Swap can be used, the following must be in place:
Your user account has administrator access to edit job type settings
A replenishment job type already exists for the relevant workflow
Configuration
Step 1 — Enable LP Swap on the Replenishment Job Type
Navigate to Settings → Job Types.
Open the replenishment job type you want to configure, or create a new one.
Click the Settings tab.
Locate the Enable LP Swap toggle and set it to Yes. Default is off.
Click Save.
Step 2 — Set the LP Swap Threshold (optional)
Once Enable LP Swap is on, the LP Swap Threshold field becomes available.
Enter a number of days (±). Logiwa IO applies this to Receiving Date when the job type's rotation is FIFO, or to Expiry Date when it's FEFO — only one ever applies to a given job type.
The threshold is symmetric: a substitute LP's applicable date can fall earlier or later than the original LP's, within the configured number of days either direction.
Setting the threshold to 0 behaves as an exact-date-match requirement.
💡 The threshold is an LP-level eligibility gate, not a per-record filter. If a scanned LP has multiple inventory records — say, three different receiving dates — the whole LP becomes eligible as soon as any one of those records falls within the threshold. Quantity is then drawn from the LP using the same FIFO/FEFO-ordered query as standard replenishment, not restricted to only the qualifying record.
Step 3 — Job Type Conditions still apply first
If the replenishment job type already has LP Conditions configured, those are checked before LP Swap's own matching logic.
LP Swap only offers substitutes from within whatever the job type's conditions already allow — it never overrides a condition you've set.
How It Works
Attribute Matching
Attribute | Rule |
Product (SKU) | Must match exactly — checked against the product your task actually needs, not the substitute LP's full contents. A mixed-SKU LP is still valid as long as it holds the right product. |
Receiving date or expiry date | Must fall within the configured LP Swap Threshold |
Lot number, production date, PO number | Not checked — a substitute can differ on any of these |
Location | Must be the same reserve location as the original assignment |
Full LP vs. Pick-from-LP
Every scan — the original assignment or a substitute — is classified as Full LP or Pick-from-LP fresh, based on what the scanned LP actually contains at that moment. This isn't inherited from how the task was originally generated, so a substitute LP can resolve differently than the original did.
Pack Type Handling
If Allow Higher Pack Type Conversion to UOM is off on the job type, the substitute LP's inventory must match the original task's pack type. If none of it does, the swap is rejected with a SKU/pack type mismatch error.
If that setting is on, LP Swap accepts any pack type on the substitute LP and works in base units, converting as needed. See Converting Higher Pack Types to UOM During Replenishment for how that conversion behaves.
Quantity Handling
What happens to the task quantity depends on three things: whether the original task was Full LP or Pick-from-LP, whether Only Replenish Full Pallets is on for the job type, and how the substitute LP's available quantity compares to what's needed. Because every scan is freshly classified, a substitute can resolve into a different task type than the one it's replacing.
If the original task is Full LP:
Only Replenish Full Pallets | Substitute's quantity vs. needed | Allow Exceed Task Quantity | Result |
Off | Same | — | Proceeds as a normal Full LP pick |
Off | More | Off | Reclassifies to Pick-from-LP; takes only the quantity needed |
Off | More | On | Reclassifies to Pick-from-LP; can take more, up to the exceed allowance |
Off | Less, substitute still resolves as Full LP | — | Stays Full LP; takes the entire substitute; shortfall becomes a new task on the original LP |
Off | Less, substitute resolves as Pick-from-LP | — | Reclassifies to Pick-from-LP; takes what's available; shortfall becomes a new task on the original LP |
On | Same | — | Proceeds as a normal Full LP pick |
On | More | Off | Rejected — the oversized substitute isn't offered |
On | More | On | Proceeds as a normal Full LP, only for LPs with qty fall into allowed exceed % |
On | Less, substitute resolves as Full LP | — | Takes the entire substitute; task is closed short rather than split into a remainder task |
On | Less, substitute resolves as Pick-from-LP | — | Rejected — the substitute isn't offered since not satisfying full LP requirement |
If the original task is Pick-from-LP:
Substitute resolves as | Quantity vs. needed | Allow Exceed Task Quantity | Result |
Full LP | More | Off | Shows as Pick-from-LP; capped at planned quantity |
Full LP | More | On | Shows as Pick-from-LP; exceeding allowed |
Full LP | Exactly what's needed | — | Reclassifies to Full LP |
Full LP | Less | — | Takes the entire substitute; shortfall remains a task on the original LP |
Pick-from-LP | More | Off | Shows as Pick-from-LP; capped at planned quantity |
Pick-from-LP | More | On | Shows as Pick-from-LP; exceeding allowed |
Pick-from-LP | Exactly what's needed | — | Stays Pick-from-LP |
Pick-from-LP | Less | — | Takes what's available; shortfall becomes a new task on the original LP |
When a Substitute LP Is Already Committed to Another Task
If the substitute LP is already assigned to another open replenishment task, the swap is rejected — the same as if the LP were allocated to a shipment order. The picker needs to choose a different LP at the location.
When a Substitute LP Is Allocated to an Open Shipment Order
If the substitute LP (or part of it) is allocated to an open shipment order, that portion is blocked to protect the order — the swap returns a direct error.
If the LP has both allocated and free inventory, only the allocated records are blocked; the unallocated, qualifying portion can still be used.
Target Location
Swapping to a different source LP doesn't change your suggested putaway target location — Logiwa IO keeps showing the original suggestion unless you explicitly request another.
Common Questions & Edge Cases
Can I substitute an LP from a different location?
No — same location only.
Does the substitute need to match lot number or production date?
No — only product and the applicable date threshold are checked.
What if my job type already has LP Conditions configured?
Those are checked first. LP Swap can only offer substitutes that already satisfy them.
What happens if I scan an LP with a different pack type than my task?
If Allow Higher Pack Type Conversion to UOM is off, the swap is rejected. If it's on, the swap converts to base units automatically.
What happens if I scan an LP that's already assigned to another open replenishment task?
The swap is rejected. LPs committed to another open replenishment task aren't available as substitutes — choose a different LP at the location.
Does swapping affect the suggested location?
No — the original suggestion holds unless you ask for another.