Warehouse and Logistics Camera Design: Rack Aisles, Docks and Shipping

Warehouse camera systems: 9:16 corridor mode in rack aisles, placement at docks and packing stations, matching video with WMS events and checking clock drift.
Technical summary
Technology
IP cameras, corridor mode (9:16), WDR, NTP, VMS bookmarks, WMS/barcode integration
Topic
Area-based camera design for warehouse and logistics spaces
Level
Intermediate
Prerequisites
  • The DORI / pixel density concept
  • The warehouse layout plan and process flow
  • Basic VMS knowledge
In this article9 sections

A customer says “a box was missing”, the warehouse manager asks for the recording, and the operator spends three hours scrolling through the wrong camera’s footage. In a warehouse, what’s expected from cameras isn’t general security but process evidence: which pallet was loaded from which dock onto which vehicle, was the box intact when it left the packing station, which forklift movement caused the damage on the rack. Here we treat the warehouse camera system separately as rack aisles, docks, packing stations and the outdoor yard, and give decisions on camera type, mounting, lighting and matching video with WMS events, with their criteria. If handheld terminals are used in the same rack aisles, test operator routes separately for Wi-Fi design in warehouse and rack areas.

The question first, then the camera

A project that starts the design with a camera list ends with blind spots on site. The right start is writing down which question the recording is expected to answer. In logistics, these questions are more or less the same in every warehouse:

  • Missing/wrong shipment disputes: reaching footage taken while the order was packed and loaded onto the vehicle within minutes.
  • Damage liability: showing whether the pallet was damaged at goods receiving, on the rack or during loading.
  • Loss and shrinkage: narrowing down the time window in which a count discrepancy occurred in a high-value product zone.
  • Workplace safety incidents: reviewing forklift–pedestrian contacts and rack collisions after the fact.

Each question needs a different image level. In a shipping dispute, the box label must be readable; for rack damage, seeing the forklift’s movement is enough. If you cover the whole area with the same resolution and lens without making this distinction, you lose twice. The budget swells, and detail at the critical point is still missing.

Area-based design table

The table below is a starting template based on the pixel density references in the IEC 62676-4:2014 table. Verify the values on site, with the chosen lens and under real lighting.

Field Purpose Target level Camera type
Rack aisle Observing movement and damage Observation (~62 px/m) Fixed, corridor mode
Inside the loading dock Pallet and vehicle door Recognition (~125 px/m) Fixed, high WDR
Outside the dock / docking Tracking vehicles and trailers Observation, separate camera for plates Fixed or LPR
Packing station Product, label, packing Identification (250 px/m and above) Ceiling type, narrow angle
Goods receiving Condition of the incoming load Recognition Fixed, varifocal
Outdoor yard and perimeter Detection, entry–exit Detection / observation Bullet, thermal (long runs)

Recording requirements also vary by area. What’s sought in an area to be reviewed is continuous, consistent footage; raw frame rate comes second.

Field Recording mode Frame rate (starting point) Note
Packing station Continuous 12–15 fps Tagged with WMS events
Dock Continuous 10–15 fps Marking with a door-open sensor
Rack aisle Continuous or motion 8–12 fps Event-based in a warehouse without a night shift
Outdoor yard Continuous 10–12 fps Together with analytics alarms

Operations set the retention period: look at how many days after the fact disputes arrive and at notification periods in contracts. Justifying this period under KVKK is a separate task; it’s covered separately in the camera recording retention period guide.

Corridor mode and mounting in rack aisles

In a narrow, long rack aisle, a standard 16:9 image spends most of its pixels on the rack faces and the ceiling. Many manufacturers offer a corridor mode that rotates the image 90 degrees to produce a 9:16 portrait frame (Axis calls this feature “Corridor Format”). The camera is also physically mounted rotated by 90 degrees; the sensor’s long side is aligned along the aisle, and with the same resolution more pixels remain at the far end of the aisle. A free gain.

Points often corrected in mounting:

  • Position: The camera is placed on the aisle axis, preferably on the ceiling or column at the head of the aisle, in line with the axis. A camera looking at an angle from a side column leaves one face of the rack blind.
  • Height: Mounting very high shows top-rack pallets and forklift forks well, but detail of pedestrians and labels on the floor is lost. Mounting very low, the forklift mast and load block the image. Just above rack height, at a point that doesn’t clash with sprinklers and light fittings, is a good starting point.
  • Range: If a single camera can’t deliver observation level at the far end, cameras are placed facing each other at both ends of the aisle. Distance is halved; the area a forklift blocks from one side is visible from the other.
  • Lighting: In warehouses, aisle lighting is often motion-activated. When the light goes off the camera switches to IR, and back to color when it comes on; these transitions leave brief blackouts in the recording. Be sure to check in the night test. If needed, discuss keeping minimum lighting on with facility management.

You can find the effect of mounting height and tilt angle on face visibility, with calculations, in the camera mounting height and angle article.

Loading docks and vehicle docking area

The dock is the hardest imaging condition in a warehouse. When the door opens, the inside is dim and the outside is daylight; the camera has to work with two different exposures in the same frame. Here a camera with true multi-exposure-based WDR is chosen, and the survey is done with the door open, at the hour when the sun hits the dock most directly. The WDR dB value on the datasheet isn’t a decision criterion on its own. Take a test recording in the same scene.

What must be seen inside the dock is the inside of the trailer door and the pallet crossing the dock leveler. The camera is placed in the upper inside corner of the door, looking into the trailer at a slight angle. A camera mounted above the door, exactly on the trailer axis, is constantly blocked by the forklift mast; shifting it a few degrees to the side often solves the problem.

In the outdoor docking area, the goal is to track the vehicle and trailer. If plate reading is wanted, don’t expect it from the overview camera; a separate plate camera is placed at the entrance gate. The outside-dock camera records the vehicle queue, driver movement and seal checks at observation level. If a door open/closed sensor or the dock control panel output is connected to the VMS as an event, searches such as “all intervals when dock door 7 was open” become possible.

Detail imaging at the packing station

Most dispute reviews revolve around the packing and shipping station. The goal is to show the product being placed on the table, going into the box, the box being closed and the label being applied in a single, uninterrupted image.

  • The camera is placed directly above the table, with a ceiling-type or short-arm mount; staff heads and bodies shouldn’t block the image.
  • The field of view is limited to the table surface. Example calculation: with 2560 pixels of horizontal resolution, a 1.6 m wide table gives about 1600 px/m; the product and box surface are clearly visible. If you want to read the barcode from the image, the barcode module width also goes into the calculation. In most cases, linking the scanner event to the video is more reliable than trying to read the barcode from the camera.
  • Table lighting shouldn’t cause reflections on glossy packaging; choose a diffuse fitting.
  • If there are several tables, the table number matches the camera name one to one. The integration works through this match.

Matching video with WMS events

The step that really increases the recording’s value is writing WMS or barcode scanner events onto the video timeline. The operator doesn’t watch hours of footage; they search by order number. A typical flow: the scanner or WMS produces an event (order scanned, box closed, dock assigned), and a middleware service matches this event with the relevant table or dock camera and sends it to the VMS as a bookmark or external event.

The format of the event sent to the VMS varies by manufacturer; common fields are usually:

{
  "source": "WMS",
  "event": "PACK_CLOSE",
  "order_no": "SO-2026-118734",
  "station": "PACK-04",
  "camera": "CAM-PACK-04",
  "timestamp": "2026-11-10T14:32:07+03:00"
}

This matching works if all systems use the same time source. Cameras, the NVR/VMS and the WMS server are tied to the same NTP server. On a Linux-based middleware service, you verify synchronization with these commands:

chronyc tracking
chronyc sources -v

On Windows servers, the equivalent is the w32tm /query /status command. A common integration fault isn’t a code error but clock drift. At a fast packing station, even a few seconds of drift opens footage of the wrong box. Check camera clocks periodically through the VMS. For API-based integration and ERP/MES connections, see the camera API and ERP integration service page.

Forklift traffic and fire load

A warehouse is an environment where cameras get physically damaged. A forklift mast and high loads hit cameras mounted low; a camera on a column is placed above the protection barrier. The cable route runs along the rack axes, through a cable tray at a height the forklift forks can’t reach. A hanging cable will one day snap.

Three topics are checked for fire safety. First, cameras and cable trays mustn’t obstruct the spray pattern of sprinkler heads; clearance requirements of the standard the fire design is based on (for example EN 12845 or NFPA 13) are checked with the fire consultant. Second, the fire performance class of cables inside the warehouse must comply with the facility specification. Third, the recorder should sit in a separate, protected technical room, not inside the storage area. Otherwise the recording most needed is lost in the fire.

If you want to catch forklift–pedestrian proximity events with analytics, camera angle and zone design follow different criteria; the topic is covered separately in the forklift–pedestrian proximity analytics article. For facilities that also include production lines, the factory camera system design guide complements this article.

Check order before commissioning

  • Are the question to be answered and the target image level written down for each area?
  • Were corridor mode and facing placement considered in rack aisles?
  • Was the dock survey done with the door open and at the hardest lighting hour?
  • Are packing station cameras named one to one with the table number?
  • Are cameras, the VMS and the WMS tied to the same NTP source, and is drift monitored?
  • Were cameras and cable trays checked for sprinkler and forklift impact risk?
  • Is the recorder outside the storage area, in a protected room?

For a design that covers the site survey, area-based camera plan and event integration together, see the scope on the warehouse and logistics camera systems page.

Frequently asked questions

How do you calculate how many cameras a warehouse needs?

The number of cameras comes from area-based goals. The required image level is set for each rack aisle, dock, packing station and goods receiving point, then the field-of-view width that achieves this level with the lens and resolution is calculated. The areas that increase the count most are long aisles and docks with many doors.

Does every camera have corridor mode?

No. Corridor mode (9:16 portrait image) is available from many enterprise camera manufacturers but varies by model. Before choosing, check the datasheet for image rotation or corridor format support and the resolutions supported in this mode.

What infrastructure is needed to integrate cameras with the WMS?

You need a WMS or scanner system that produces events, a middleware service that matches events to cameras, and a VMS that accepts external events or bookmarks. All components using the same NTP source is a prerequisite; if the clock drifts, the integration opens the wrong footage.

Should warehouse cameras use continuous or event-based recording?

Use continuous recording in areas subject to dispute reviews, such as packing stations and docks. In rack aisles with no night-time activity, motion- or analytics-based recording can reduce storage needs; the decision depends on the review scenarios.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles