Quick answer

Use this article to understand the difference between a product identifier, a storage location or lot, and a storage container before changing warehouse work. Many teams map a storage container code one-to-one with a storage location or lot, but that is a customer setup pattern—not something to assume in every workflow.

Common use cases

Associate: Know whether the app is asking for a product, location, lot, tote, or container code.
Supervisor: Check the right context before approving a location or container correction.
Support or CS: Ask for the right evidence when a customer says a SKU is in the wrong place.

What each code means

Code or concept	What it means operationally
SKU or product barcode	Identifies the item being received, picked, packed, counted, or adjusted.
Storage location or lot	Describes where stock is expected to live, be picked from, or be replenished from in the warehouse.
Storage container, tote, or container code	Identifies a physical or scannable container that may hold stock or be tied to a workflow.
Order, handling order, route, replenishment, or receiving task	Identifies the work currently using the product, location, or container.

If your team uses one code for location and container

Confirm whether your operation intentionally maps the same code to both the storage location or lot and the storage container.
Even when the codes match physically, check which field or scan Logentic is asking for before retrying.
If the app expects the old code after a change, stop and collect evidence instead of forcing a new scan value.

Before correcting anything

Confirm the product/SKU and warehouse.
Confirm the physical old code and the expected new code.
Check whether active picking, route picking, replenishment, receiving, cycle counts, inventory adjustments, or orders depend on the old code.
Do not release, delete, validate, adjust inventory, or reuse a container just to make an error disappear.