These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Logistics ERP
- Features
- Inventory and Warehouses
Inventory and Warehouses
Establish item identities and active facilities before authorizing warehouse-to-warehouse stock work.
OverviewActive Inventory Items×
Logistics ERP · Inventory and Warehouses
New
Active Inventory Items
Inventory items
| Name | SKU | Unit | Reorder point | Active | |
|---|---|---|---|---|---|
| Item 955 | SKU-854 | UNT-993 | 860 | ||
| Item 254 | SKU-493 | UNT-153 | 290 | ||
| Item 668 | SKU-556 | UNT-283 | 280 | ||
| Item 165 | SKU-440 | UNT-786 | 410 | ||
| Item 162 | SKU-671 | UNT-256 | 580 |
6 of 6 records
Item 955Inventory items · II-15641
SKUSKU-854
UnitUNT-993
Reorder point860
What you can do
Make the transferred stock unambiguous
Inventory item records identify the stock used in logistics warehouse work. Each item has a name, SKU, unit, reorder point and active setting. Admin maintains these definitions so a transfer quantity has a consistent meaning at both facilities. The unit is part of the operating instruction, not a detail to resolve after posting.
Warehouse records identify the facilities by name, code and city, with an active setting. A transfer references the source and destination warehouse explicitly. The team can then inspect an outbound effect at the source and an inbound effect at the destination for the same item and quantity. That comparison depends on clean item and facility references.
How the work is organized
- Item identity. Use the SKU and unit to distinguish the stock being transferred. Maintain the active setting when an item leaves the operating list so staff review existing work before starting another transfer.
- Facility context. Keep warehouse codes and cities recognizable to the people preparing the movement. A similar facility name should not cause a transfer to use the wrong source or destination.
- Transfer readiness. Review the item, both warehouses and the requested quantity before approving the work. The resulting stock movement history preserves the item and facility context used for the posting.
What to agree during setup
Agree a naming and coding convention for warehouses and decide who checks duplicate item records before an import. Use a real interwarehouse movement to confirm that both facilities use the same item definition. If another system describes the stock in different units, configure and test that mapping before relying on the transfer quantity.
Decide how the team uses an item’s reorder point in its operating review. Keep replenishment decisions with the agreed planning process and configure any external inventory connection separately. When discussing stock position, distinguish this app’s posted movement history from balances supplied by the inventory system. Agree the opening-balance source before deriving a current quantity from historical movements.
Check the handoff on an actual case
Choose a packaging item used at a regional warehouse and a city warehouse. Admin checks its SKU and unit, confirms both facility codes and prepares a transfer for 40 units. Ask another authorized participant in the rehearsal to identify the item and facilities from the records without a verbal description.
Repeat the preparation with an inactive warehouse and an item whose unit differs from the expected handling unit. Resolve the setup issue before approving the transfer. After posting the valid case, inspect the movement history to confirm that both effects use the same item reference and quantity. Keep the facility choice visible when investigating a mismatch.
What your team sees
- Active Inventory Items — Item identities, units and reorder settings used in warehouse-transfer preparation.
- Transfer Approval Queue — Draft transfer quantities with their source and destination facilities.
Follow the work through
Use inventory setup and transfer approval, then warehouse transfer posting to inspect the facility effects.
What it keeps track of
Data model- Inventory items
- Stock-keeping units available for freight and warehouse operations.
- Warehouses
- Facilities that hold logistics inventory.
- Stock transfers
- Approved warehouse-to-warehouse inventory movements.
- Stock movements
- Posted inbound and outbound stock effects created from transfers.
Who uses it
Permissions- Admin
- Maintains item and warehouse definitions and the warehouse-transfer access configuration.
- The same operating role prepares the transfer handoff within the scope agreed during setup.
Set up Logistics ERP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.