Quick answer
Use this article when a SKU is physically in one storage location, lot, or container but Logentic appears to expect another. Stop the affected workflow, identify the mismatch, collect evidence, and have a supervisor or Support confirm the correction path.
Warning
Do not force an inventory move, location change, container release, receiving validation, replenishment validation, or inventory adjustment unless a supervisor confirms the correct workflow.
Tip
Many teams map a storage container code one-to-one with a storage location or lot, but this is not universal. Confirm your team’s setup before correcting anything.
Do this first
Stop the current workflow if the product, SKU, barcode, storage location, lot, container, tote, quantity, warehouse, or active task does not match what Logentic expects.
Keep the screen open if possible.
Check the physical label on the product, location, and container.
Review the product or task context in Logentic that shows the expected location/container.
Ask a supervisor to confirm whether this is a physical move, app-state mismatch, receiving/putaway issue, replenishment issue, scan-code misunderstanding, or route/picking issue.
Resume only after the supervisor confirms that the app state and physical warehouse state match.
Stop and escalate if
The iPad or route view shows a style, SKU, product, location, lot, bin, or container that does not match what the associate expects.
Multiple SKUs appear mapped to one location and your warehouse expects a one-to-one setup.
The old location or old scan still appears after a correction.
Active picking, route picking, replenishment, receiving, or order work depends on the old code.
Changing the state could affect live orders, stock availability, cycle counts, or fulfillment accuracy.
Common blockers
Issue | What it means | What to do next |
SKU is physically in a different location. | Stock may have moved without the app state matching. | Stop and have a supervisor confirm the correction workflow. |
Container code and location/lot do not match. | The mapping may be wrong, outdated, or different from your team’s setup. | Collect both codes and escalate if the mapping is unclear. |
Multiple SKUs appear mapped to one location. | This can be valid for some setups, but it can also indicate a setup/data issue. | Do not change inventory blindly. Send examples and confirm whether the location is intentionally shared. |
iPad or route work shows an unexpected SKU/location. | Route work may be using a different product/location state than expected. | Stop route work and send the route/task, SKU, expected location, shown location, and screenshot. |
Scan keeps rejecting the expected code. | The visible code may not be the accepted scan code. | Use scan troubleshooting and send the exact code scanned if still blocked. |
When to contact Logentic
Contact Logentic
Contact us before changing inventory if the correction could affect active orders, route picking, receiving, replenishment, cycle counts, or stock availability.
Workspace and warehouse.
Product name, SKU, and barcode or scan code attempted.
Old location/lot/container code and expected new code.
Quantity affected.
Workflow where the mismatch appeared.
Related order, handling order, pick route, replenishment, receiving, cycle count, or inventory task.
Exact error message, timestamp, and screenshot with private data avoided.
Contact options
Email Logentic Support: best for detailed requests, screenshots, or follow-up context.
Open in-app chat: fastest when you are already signed in and need help in context.
Call Logentic: call +1 438-256-9777 for an urgent launch, warehouse, or fulfillment blocker.