A warehouse management structure is the set of roles, reporting lines and team groupings that decides who directs the work, who does it, and who answers when it goes wrong. Most warehouses, whatever their size, settle into the same basic shape: a manager at the top, supervisors or team leaders running the floor, and operatives doing the picking, packing, receiving and despatch. What changes is the number of sites, shifts and clients, and that is what this guide works through.
Some clarity on the term first. This guide is about people and organisation. It isn’t about the steel frame of a building, the racking design, or a data warehouse schema. When we say structure, we mean who reports to whom, how teams are grouped, and which responsibilities belong to which job.
Start with the job titles, because the official picture is more structured than most people expect. The Health and Safety Executive publishes Warehousing and storage: A guide to health and safety (HSG76), which covers the safety side of warehouse work and is the document to check when you decide who owns each safety duty. For general management, our guide to how to manage a warehouse covers day-to-day running, so this piece stays on structure and roles.
The roles a warehouse needs
Den National Careers Service warehouse manager profile lists the core duties: tracking stock levels and storage space, overseeing loading and unloading, planning deliveries, arranging staff shift rotas, and overseeing recruitment and training, with health and safety checks alongside them. The same profile says warehouse workers can move into a team leader or assistant manager job before becoming a manager. That ladder is what most structures are built on.
The Office for National Statistics makes the same split in its occupational codes. Its SOC 2020 unit groups put managers in storage and warehousing under 1242, elementary storage supervisors under 9251, and warehouse operatives under 9252. The codes don’t prescribe a structure, but they do treat supervising storage work as a separate job from doing it.
| Role | Typical focus | KPIs to watch |
|---|---|---|
| Operations or general manager | Site performance, budget, client and board reporting | Order fulfilment rate, cost per order, site margin |
| Warehouse manager | Stock, space, staff, safety and standards on one site | Stock accuracy, despatch on time, safety incidents |
| Shift manager | Running one shift and handing over to the next | Shift output, backlog at handover |
| Team leader or supervisor | Directing a team, briefings, allocating work | Picks or moves per hour, error rate, attendance |
| Inventory controller | Stock records, counts, adjustments, expiry checks | Stock accuracy, count variances, aged stock |
| Goods-in and despatch leads | Receiving and loading, dock schedule, carrier cut-offs | Receipts put away on time, late despatches |
| Health and safety lead | Risk assessments, inspections, training records | Near misses, overdue inspections, training completion |
| Warehouse operative | Picking, packing, moving stock, following task instructions | Individual accuracy and pace against standard |
No site has every row, and smaller operations often combine roles. An owner-run business might give goods-in and despatch to one lead and the stock record to a supervisor. The test is simpler than any org chart: every responsibility in that table should have a named owner, even if one person holds three of them. Our WMS for warehouse managers page shows what the manager’s role looks like inside the system.
Mathew Buttar, who spent nearly 25 years in warehouse operations before moving into go-live work at Clarus, puts the manager’s core job bluntly. Knowing your stock and how you control it is the “number one job”, and the rest of the structure depends on it. If nobody owns the stock record, picking, invoicing and cycle counts all run on guesswork.
Team leaders and supervisors
The clearest public description of the supervisor role comes from the Skills England standard for transport and warehouse operations supervisor, ST0647. It describes the warehouse operations supervisor as the person who directs stowing, supervises goods receipt and despatch, runs stock control and checks, and leads a team by setting objectives, allocating work, holding daily briefings and debriefings, appraising staff and managing team KPIs. Use that list as a checklist for what the role must own, whatever the job title says. A level 3 warehouse operations supervisor apprenticeship is advertised on Find an apprenticeship, og CILT UK, which runs logistics careers and qualifications, lists Level 3 and Level 5 certificates in logistics, supply chain and operations management.
How the hierarchy and reporting lines work
Who does a warehouse manager report to? The public job profiles don’t say. The Prospects warehouse manager profile describes supervising warehouse staff and working with customers, suppliers and transport firms, but it leaves the reporting line out, and so does the National Careers Service profile. In practice the manager usually reports to an operations, site or general manager, and in a small owner-run business the owner may fill that seat. Map your own line in your own chart rather than copying someone else’s.
How many supervisors per team?
There is no reliable published ratio, and anyone quoting one is guessing. Set the number by workload instead. Ask how many people one supervisor can brief, observe and coach within a shift once their own paperwork and exceptions are counted. Then check the answer against shift length and the number of zones or sites that supervisor covers.
Mathew Buttar’s view is that being on the floor matters as much as watching the screen. A system that records every task lets a supervisor see who is falling behind without walking the whole site. It can’t show what someone is doing between scans, so supervision still means being there.
Functional, shift and zone-based structures
Most warehouses group their teams in one of three ways, and many mix them. The right choice depends on how different the tasks are, how many hours the operation runs, and whether storage conditions or product rules change across the building.
| Structure | How teams are grouped | Works well when | Watch out for |
|---|---|---|---|
| Funksjonell | By task: goods-in, picking, packing, despatch, inventory | Tasks differ widely and volumes are steady | Handoffs between functions. A goods-in backlog can hold up picking, because space has to be cleared first. |
| Shift | By time: early, late, nights, weekends | The operation runs long hours or has carrier cut-offs | Handover losses and different standards from one shift to the next |
| Zone | By area: ambient, chilled, mezzanine, returns, quarantine | Storage conditions or product rules differ by area | Uneven workload between zones, and cover gaps when someone is off |
A zone is more than an address. Mathew Buttar’s example is gluten-free product that must not sit beneath a product that could contaminate it if a stack splits, so a zone is really a rule about where stock is allowed to go. Zones also shape routes. In Clarus, pick routes follow a walk sequence set against each location, so the way you divide the floor also decides the order people walk it (how picking logic works in Clarus).
How 3PL warehouses split account management and operations
A third-party logistics warehouse runs two jobs at once: operating the floor for each client, and managing each client as a commercial account. Many 3PLs split these into two groups that work closely together. The operations side includes the warehouse manager, shift managers and team leaders. The account side includes account managers or client services staff, who handle onboarding, client questions and reporting, and a billing or invoicing role that turns activity into charges.
Client rules are where the two sides meet. Mathew Buttar notes that different end customers of the same 3PL account can demand different remaining shelf life on what they receive. Someone has to own that client rule set and agree it with the floor before the first order goes out. Give that job a name on the chart. Without it, operations and account teams end up arguing about who promised what.
Visibility is the other pressure point. Clarus’s client access feature lets a 3PL’s clients see stock levels and order status without phoning the warehouse, which takes a steady stream of enquiries off the operations team. Mathew Buttar describes clients who can check their stock in a portal, or receive a daily stock report by email, rather than asking for it.
Billing needs its own owner too. When charges depend on activity, someone has to check the record before an invoice goes out. St John’s Hall Storage, a 3PL, shows what the work looks like when the floor and the invoice aren’t linked. Its Managing Director had spent around four days at each month end checking invoices that had been re-keyed from the WMS into the accounts package. That re-keying is gone, Clarus saves the equivalent of about two staff members on site across picking and invoicing, and invoicing time is down by 90% (read the St John’s Hall story).
Multi-site structure: what stays central and what stays local
When a business runs more than one site, the question is which responsibilities move up to group level. As a rule of thumb, group functions own what must be the same everywhere: client onboarding standards, finance, system configuration, group-wide reporting and training design. Site managers own what depends on the building and the people in it: daily scheduling, staff, safety on the floor and local exceptions.
Adding a site is partly a systems question. Clarus supports multi-warehouse and multi-site working from a single environment. Mathew Buttar has described setting up a new warehouse in minutes once the data is in place, with two caveats: a site that uses full scanner-based working takes longer, and the speed depends on having the data ready. Plan the people side with the same care. Each new site needs its own super users, people who understand why the system is configured the way it is.
How a WMS changes the structure
If you’re new to the category, what a WMS is sets out the basics. The short version for structure is that a warehouse management system doesn’t remove the supervisor’s job, but it changes what that job spends its time on. Three changes matter most.
Fewer admin roles. A paper pick list needs a second person to check the picks against it. Mathew Buttar describes that as two people’s worth of labour to confirm one pick was right. Scanning takes much of that check out of the process. It doesn’t take all of it. A picker can still scan the right location, the right pallet and the right product, then take the wrong item from the pallet next to it. Scanning reduces errors; it doesn’t guarantee them.
Data-driven supervision. Every task is held as a line in the system, so a supervisor can see what moved, from where to where, when, and who did it. Our guide to tracking warehouse operator activity covers how to use that record. Two limits apply. The record shows what was done in the system, not everything that happened on the floor. And Clarus doesn’t include a labour management tool that tells you whether your team’s hours are efficient, so you’ll still need your own standards for that.
Super users, not just a training day. Mathew Buttar’s implementation approach identifies at least two super users in the team. They understand why the system is set up as it is, they run user acceptance testing, and they become the on-site reference after go-live. That is what keeps a structure working when someone leaves. A standard project, with proper support on both sides, is aimed to go live within 12 weeks. For pricing and plan context, see our WMS-kostnad page, and if you’re comparing systems, our best WMS buyer’s guide sets out what to check.
KPIs at each level
Measure each level on what it can change. Operatives can influence their own accuracy and pace, so individual measures suit them. Stock accuracy belongs to the inventory controller and the warehouse manager, and despatch timing belongs to the despatch lead and the shift manager. Measuring a team leader on a company-wide figure they can’t move only produces blame. The roles table above lists a starting set for each level.
Example org charts: small, medium and multi-site
The table below sets out three illustrative shapes that show how responsibilities group as a business grows. They are not benchmarks, and we haven’t given headcounts because we don’t have a sourced basis for them.
| Level | Small single site | Medium single site | Multi-site group |
|---|---|---|---|
| Top | Owner-manager | Warehouse manager reporting to a director | General or operations manager over site managers |
| Floor supervision | One team leader per shift | Shift managers and team leaders | Site managers, each with their own shift managers |
| Specialist roles | Goods-in and stock control combined | Separate inventory controller and H&S lead | Central inventory, H&S and training leads |
| Admin and client | Owner handles invoices and queries | Admin role for invoicing and client queries | Central client services and billing team |
| Rapportering | Weekly review with the owner | Daily site KPIs to the warehouse manager | Site KPIs rolled up to group reporting |
Read the table from top to bottom. On a small site, one person holds several boxes. As volume and sites grow, each box gets its own owner, and the coordination work moves up to whoever sits above the sites.
Snakk med en lageransvarlig
If you’re reviewing who owns what in your operation, and want to see how a purpose-built WMS fits the way your team is organised, Clarus is worth a conversation. We work with 3PLs and distributors across the UK to implement warehouse management software that fits the way you operate, not the other way around.
Ta kontakt med teamet vårt å snakke gjennom dine krav.