Warehouse Management System (WMS)
Also known as: warehouse management software
A warehouse management system is software that directs and records the physical movement of inventory inside a facility — what arrived, where it was put, what was picked for which order, and what left the building.
Why it matters
The distinction that matters in practice is against ERP and inventory management software. An ERP knows you own 400 units; a WMS knows they are in aisle 12, bay 4, level 2, in two lots with different expiry dates, and which of them are already allocated. Companies usually discover they need a WMS when inventory is technically "in stock" but nobody can find it quickly enough to ship on time.
In WarePulse
WarePulse is a WMS: it owns location-level inventory, the floor workflows that move it, and the client-facing reporting a 3PL needs on top.
Third-Party Logistics (3PL)
A third-party logistics provider stores and ships inventory it does not own, on behalf of client companies, and bills those clients for the space and labour consumed.
Why it matters
The operational consequence of not owning the inventory is that every transaction has to be attributable to a client. A 3PL cannot run on a single pooled stock figure: it needs per-client inventory segregation, per-client visibility, and a billing record for every storage day and handling event. This is the single largest functional gap between warehouse software built for distributors and software built for 3PLs.
In WarePulse
Client segregation, a client portal, and usage-based billing are core rather than add-ons.
FEFO (First Expired, First Out)
FEFO is an inventory rotation rule that ships the stock with the earliest expiry date first, regardless of when it was received.
Why it matters
FEFO is often confused with FIFO, and the difference causes real write-offs. FIFO ships the oldest received stock first; FEFO ships the soonest-to-expire stock first. These diverge whenever a later delivery has a shorter remaining shelf life than an earlier one — routine with food, pharmaceuticals, and cosmetics. A warehouse running FIFO on perishable goods will expire inventory it could have sold.
In WarePulse
Expiry is captured at receiving and enforced at allocation, so pickers are directed to the correct lot rather than trusting them to check dates.
FIFO and LIFO
FIFO (First In, First Out) ships the earliest-received stock first. LIFO (Last In, First Out) ships the most recently received stock first.
Why it matters
FIFO is the default for most physical goods because it limits how long any unit sits. LIFO is rare in physical fulfilment and appears mainly as an accounting method for costing inventory rather than as a picking rule. Note that a warehouse can run FIFO physically while its finance team uses a different costing basis — the terms mean different things in operations and in accounting, which is a frequent source of cross-department confusion.
Advance Ship Notice (ASN)
Also known as: advance shipping notice, inbound notice
An advance ship notice is a message sent by a supplier before a shipment arrives, declaring what is in it — items, quantities, lots, and often carton-level detail.
Why it matters
Without an ASN, receiving is discovery work: the team opens the truck and finds out what came. With one, receiving becomes verification against an expected manifest, which is faster and surfaces shortages and substitutions at the dock instead of weeks later during a count. For a 3PL, ASNs are also how a client tells you inventory is coming without a phone call.
In WarePulse
ASNs can be submitted by clients through the portal and are matched against physical receipts line by line.
Putaway
Putaway is the step that moves received goods from the receiving dock to their storage locations and records where they went.
Why it matters
Putaway is where inventory accuracy is usually won or lost. A receipt that is booked into the system but physically placed somewhere unrecorded creates stock that exists on paper and cannot be found — functionally the same as having lost it. Directed putaway, where the system assigns the location rather than letting the operator choose, is the main defence.
In WarePulse
Putaway is scan-confirmed against the assigned location.
Dock-to-Stock Time
Dock-to-stock time measures how long it takes for arriving inventory to become sellable — from the moment it hits the dock to the moment it is putaway and available to allocate.
Why it matters
It is a useful metric precisely because it spans two teams. Inventory sitting in a receiving staging area is capital that cannot ship, and it is invisible to most stock reports, so a long dock-to-stock time shows up as phantom stockouts on items that are physically on site. Measuring it tends to expose receiving as a bottleneck that inventory reports alone will never reveal.
Cross-Docking
Cross-docking moves inbound goods directly from receiving to outbound shipping without an intermediate putaway into storage.
Why it matters
It removes two touches per unit, which is why it is attractive for high-velocity or pre-allocated freight. The tradeoff is that it requires the inbound and outbound sides to be coordinated in time: a cross-dock that misses its outbound window becomes an unplanned pile on the floor in the worst possible place. It works best with reliable ASNs and known destinations.
In WarePulse
Cross-dock moves are recorded as a distinct flow rather than a putaway-then-pick.
Cycle Counting
Cycle counting verifies inventory by counting a small subset of locations or items on a rolling schedule, instead of counting everything at once.
Why it matters
The alternative — a full physical inventory — usually requires shutting down operations, and its accuracy decays immediately afterward. Cycle counting trades a single large audit for continuous small ones, which both avoids the shutdown and catches discrepancies close to when they were caused, while the cause is still traceable. Counts are typically prioritised by value or velocity (ABC), because a discrepancy on a fast-moving SKU costs more than one on a slow item.
In WarePulse
Counts are scheduled and assigned as floor tasks, with variance recorded per count.
ABC Analysis
ABC analysis ranks inventory into classes — typically A, B, and C — by how much each item contributes to value or movement, so that attention is allocated unevenly on purpose.
Why it matters
It exists because uniform treatment of inventory is wasteful: a small fraction of SKUs usually accounts for most of the throughput. In a warehouse, the classification drives two decisions — how often an item is cycle counted, and how close to the pack stations it is slotted. The classes are a management tool, not a fixed property of the item; they should be recalculated as demand shifts.
Slotting
Slotting is the assignment of items to specific storage locations, chosen to reduce the travel and handling required to pick them.
Why it matters
Travel is typically the largest component of picking labour, so slotting is one of the few changes that reduces cost without new equipment or headcount. The usual rule is to place fast-moving items in the most accessible positions near packing, and to keep items frequently ordered together nearby. Slotting decays as demand changes, which is why it needs periodic review rather than one-time setup.
Pick Path
A pick path is the route a picker follows through the warehouse to collect the items on an assignment, and the sequence in which the system presents them.
Why it matters
Path quality is mostly a sequencing problem: the same set of items can require very different walking distances depending on the order they are listed. A poorly sequenced list sends pickers backtracking across zones. This is why pick lists should be ordered by location rather than by the order the customer typed the items, and why unoptimised paths quietly cap throughput regardless of how fast the staff work.
Wave Picking
Wave picking releases orders to the floor in scheduled groups — waves — rather than continuously as they arrive.
Why it matters
Waves let picking be aligned to something external: carrier cutoff times, shift boundaries, or packing capacity. The cost is latency, since an order waits for its wave. The opposite approach, continuous or waveless release, minimises latency but makes labour and packing load harder to plan. Which is correct depends on whether your constraint is cutoffs or responsiveness.
Batch Picking
Also known as: multi-order picking
Batch picking collects the same item for several orders in a single pass, then sorts the picked units to individual orders afterward.
Why it matters
It reduces travel by visiting each location once for many orders instead of once per order, which is why it suits operations with many small orders sharing common SKUs. The work does not disappear, though — it moves downstream into a sortation step, and if that step is not resourced, the gain is consumed by mis-sorts at packing.
Lot and Batch Tracking
Also known as: batch tracking, lot control
Lot tracking records which production batch each unit of inventory belongs to and preserves that link through receiving, storage, picking, and shipping.
Why it matters
Its value is realised during a recall or a quality investigation, when the question is "which customers received units from batch X". Without lot-level records that question can only be answered by recalling everything, or by guessing. Lot tracking is a regulatory requirement in food and pharmaceutical distribution, and it only works if the chain is unbroken — a single untracked repack step destroys traceability for everything downstream.
In WarePulse
Lot is captured at receipt and carried through to the shipment record.
Traceability
Traceability is the ability to reconstruct, after the fact, where a specific unit of inventory came from and where it went.
Why it matters
It is a property of records, not of software features: traceability exists only if every handling step wrote down what it did to which lot. The practical test is whether you can answer a two-directional question — given a batch, which shipments contained it, and given a shipment, which batches were in it. Operations that can answer one direction but not the other usually discover the gap during an audit.
Shelf Life and Expiry Control
Shelf life is the period during which a product remains fit for sale; expiry control is the set of rules that prevent stock from being allocated or shipped too close to the end of it.
Why it matters
Expiry control is stricter than simply refusing to ship expired goods, because many customers impose a minimum remaining shelf life on receipt — stock that is technically in date can still be rejected on arrival. Warehouses that only block expired stock discover this through returns. The rule that matters is the customer-specific remaining-life threshold, applied at allocation.
SKU (Stock Keeping Unit)
A SKU is the identifier for a distinct sellable item — distinct in every attribute that affects fulfilment, including size, colour, and pack configuration.
Why it matters
The common failure is under-splitting: treating a case of twelve and a single unit as one SKU, or one product code across two pack sizes. Every such collapse makes inventory counts ambiguous and picking error-prone, because the number in the system no longer maps to a single physical thing. A SKU is not a product; one product routinely spans many SKUs.
Inventory Accuracy
Inventory accuracy is the degree to which recorded stock matches physical stock, usually reported as the percentage of counted locations with no discrepancy.
Why it matters
Measuring it by total units is misleading, because large offsetting errors can net to zero and look clean. Location-level accuracy is the honest measure: it counts a location as wrong if anything about it is wrong. The downstream cost of low accuracy is not the write-off but the shipping failures — orders accepted against stock that is not findable, which surface as late shipments rather than as inventory problems.
Allocation and Backorder
Allocation reserves specific inventory to a specific order so it cannot be promised twice. A backorder is an order line accepted without available stock to allocate to it.
Why it matters
Allocation is what separates on-hand from available: stock can be physically present and entirely unavailable because it is already committed. Systems that report only on-hand quantities cause double-selling. Backorders are not inherently a failure, but they need an explicit fulfilment rule — which order gets the next receipt — or they get filled in whatever arbitrary order the picking queue produces.
Storage and Handling Billing
Storage and handling billing is how a 3PL converts warehouse activity into an invoice — typically a recurring charge for space occupied plus per-event charges for receiving, picking, and shipping.
Why it matters
Most disputed 3PL invoices come from charges that cannot be traced back to a recorded event. If billing is assembled from spreadsheets at month end, the provider cannot show the client which receipt or pick generated a line, and the client is being asked to trust a total. Billing derived from the same transaction records the operation already creates makes each line defensible, which is usually worth more than the pricing model itself.
In WarePulse
Billable events are derived from recorded floor transactions rather than re-entered.
3PL Client Portal
A client portal gives a 3PL customer direct, scoped access to their own inventory, orders, and documents, without going through the provider’s staff.
Why it matters
Its real function is deflecting status enquiries. A large share of a 3PL account manager’s day is answering questions the system already knows — did it arrive, has it shipped, how much is left. The requirement that makes a portal safe is strict scoping: each client must see only their own inventory, which is a data-segregation problem before it is a UI one.
In WarePulse
The client portal is a first-class surface with per-client access boundaries.
Audit Trail
An audit trail is an append-only record of who changed what and when, retained so that past states can be reconstructed and disputes settled from evidence.
Why it matters
The distinguishing property is immutability: a log that can be edited proves nothing. In warehouse operations the trail is what resolves shrinkage investigations, client billing disputes, and quality escalations, because each of those turns into a question about a specific past action. Logs that only retain current values, rather than the sequence of changes, cannot answer them.
In WarePulse
Audit logs are retained as an immutable record; see the trust centre for scope.
Yard Management
Yard management tracks trailers, containers, and dock assignments in the space outside the building, treating the yard as inventory locations rather than a parking lot.
Why it matters
Yards become a problem at the point where trailers hold stock that the warehouse system cannot see. A loaded trailer parked outside is inventory in an unrecorded location, which is the same accuracy failure as an unrecorded putaway, at pallet scale. Dock scheduling matters for the same reason: an unmanaged door is the constraint that determines how fast receiving can run.
In WarePulse
Yard positions and dock assignments are tracked alongside in-building locations.