Warehouse Surveillance Blueprint: Camera Layout, PoE & 30-Day Storage

A warehouse security camera system has to answer more than “was somebody there?” It may need to show which pallet moved, what happened at a loading dock, and who used an employee entrance. Those are different views, and one wide camera rarely does all three well.

Start with the evidence you need, not the camera count. Use overview cameras to follow activity and dedicated views to capture details at entrances, dock positions and handling points.

This blueprint is an illustrative design exercise, not a completed customer case study. The quantities and bitrates below are planning assumptions, not a promise of coverage, retention or compatibility. The cover image is an illustration, not a NorthStar installation photograph. Final selection requires a site survey, current product specifications and day/night commissioning.

1. Define the warehouse zones and evidence targets

Before placing cameras on a drawing, mark the racks, doors, dock positions, pedestrian routes and secured inventory. Include rack heights and the highest expected pallet stack: an empty warehouse can look covered until inventory blocks every useful sightline.

Zone Question the footage must answer Starting view Survey concern
Receiving and shipping docks Which shipment moved, and through which bay? Dedicated view of each handling area plus an overview Open-door glare, trailers blocking views, forklift movement
Rack aisles Who entered the aisle, and where did they stop? Fixed views along or across each aisle Tall racks and pallets hide cross-aisle activity
Open staging floor Where did an item or person move next? Wide-area overview or fisheye Detail decreases toward the edges and at long distances
Employee and visitor doors Who crossed this specific entrance? Dedicated face-level approach view Backlighting, hats, door swing and reachable hardware
High-value inventory area Who accessed the restricted stock? Focused view of the access point and handling area Privacy boundaries, tampering and blocked shelves
Exterior dock apron What happened before a vehicle reached the bay? Separate exterior overview Headlights, weather, lighting and camera power at night

For each location, write an acceptance target such as “recognize the person entering this doorway on playback” or “follow a pallet from the staging lane to dock 2.” Avoid vague targets like “cover the whole warehouse.” Test the target using recorded footage, not just the live preview.

2. Match camera style to the job

Fisheye for open-area context—not every aisle

A 12MP AI fisheye dome camera is a candidate for an unobstructed staging or intersection area. It can provide broad context, but its megapixels are spread across a wide scene. It should not be treated as a replacement for dedicated entrance or aisle detail views.

Confirm the mounting geometry, image detail at the farthest target, and fisheye dewarping support in the selected recorder or VMS. Verify live view, recorded playback and exported evidence: the operator's screen and exported file may not behave the same way. Racks remain physical obstructions regardless of resolution.

Vandal domes for reachable entry and handling points

The 4MP AI vandal dome camera listing specifies a 2.8mm fixed lens, IK10 impact rating and IP67 protection. It is a candidate for entry or handling locations where the housing may be reachable. A fixed wide lens still needs a distance check; it does not guarantee a useful face image across an entire dock.

IK10 describes an impact test, not immunity to a forklift strike or deliberate obstruction. Protect the mounting and cable entry too. See turret versus dome cameras for glare, cleaning and tamper considerations.

Dedicated dock views for difficult light

An open loading door can place a bright yard behind a dark person. Check the selected camera's wide dynamic range capability and actual playback under that condition. Aim away from a direct view of the brightest opening where practical, and test moving subjects rather than judging a stationary scene.

At night, nearby walls, reflective wrapping and dust can affect infrared images. Check lighting, shutter settings and motion blur with a person walking and a forklift traveling at the site's normal operating speed. Keep the test controlled and follow the warehouse's safety procedures.

3. Build a camera and equipment schedule

The example below assumes a warehouse with six aisle views, four dock handling views, two entry views and four unobstructed overview locations. It is not a camera-per-square-foot rule. A different rack layout may need more dedicated views and fewer overview cameras.

Camera IDs Quantity Role Illustrative recording assumption
C01–C06 6 Fixed aisle views 4MP, H.265, 15 fps, 4 Mbps each
C07–C10 4 Dock handling views 4MP, H.265, 15 fps, 4 Mbps each
C11–C12 2 Dedicated entrance views 4MP, H.265, 15 fps, 4 Mbps each
C13–C16 4 Open-area fisheye overview views 12MP, H.265, 15 fps, 8 Mbps each

The 4MP and 12MP bitrates are budget inputs, not measured output from these products. Confirm the requested resolution/frame-rate combination and codec on the exact model, then measure day and night traffic. Busy scenes, sensor noise and compression settings change the result.

Your equipment takeoff should also list:

  • Exact camera model, lens, mount and junction box for every ID.
  • Cable route, measured length, switch port and required PoE standard.
  • Recorder/server model, incoming bandwidth limit, drive configuration and usable storage.
  • VMS recording channel count, existing licenses and any licenses included with the server.
  • UPS load and runtime requirement, rack space, patching and surge protection where applicable.
  • Operator workstation, export method, permissions and support handover requirements.

Start with the camera catalog, PoE switches and VMS servers. These are selection resources, not a prevalidated warehouse kit.

4. Calculate PoE and network capacity separately

PoE has two limits: power available on each port and the switch's total power budget. Meeting one does not meet the other.

For illustration, if twelve devices required 10W each and four required 20W each, their combined specified demand would be 200W. Reserving another 25% gives a 250W planning budget, provided the switch also meets each device's port requirement. These wattages are hypothetical; use manufacturer maximum requirements and the switch's published power accounting, including cable losses where relevant.

Do not add a high-power injector merely because a camera has a high megapixel count. A 60W Gigabit Hi-PoE injector is only a candidate when a specific device needs it and its power negotiation, standard and connector are compatible. A “60W” label alone does not establish compatibility.

Use standard Ethernet distance limits when planning copper runs; fiber to a remote switch may be preferable to stretching a long run. Isolate camera traffic appropriately, restrict remote access and document addressing. See the PoE switch buying guide.

For our recording assumptions:

  • Twelve fixed cameras × 4 Mbps = 48 Mbps.
  • Four fisheye cameras × 8 Mbps = 32 Mbps.
  • Total continuous recording payload = 80 Mbps.

Budget additional capacity for network overhead, live viewing, playback, exports and growth. An illustrative 2× payload allowance is 160 Mbps, not a universal uplink requirement. Gigabit may be sufficient for this example; larger or more demanding deployments require a fresh calculation. Check the recorder's incoming bandwidth limit independently of the switch uplink speed.

5. Size 30-day recording from bitrate

Assume continuous recording for all sixteen cameras. Using decimal terabytes:

Storage (TB) = total bitrate (Mbps) × 86,400 × retention days ÷ 8,000,000

Group Total bitrate Raw video storage for 30 days
Twelve fixed views 48 Mbps 15.552 TB
Four overview views 32 Mbps 10.368 TB
Whole system 80 Mbps 25.920 TB

An illustrative 10% reserve brings that to 28.512 TB of usable planning capacity, before any additional growth allowance. RAID parity and spare drives affect the raw capacity you must purchase. Formatting and recorder reservations must also be checked. Decimal TB and binary TiB are different display units, not extra physical storage losses to count twice.

At the assumed constant bitrate, a 10TB configuration is below the raw 25.92TB requirement. A recorder being “16-channel” does not mean it meets this retention target. Check drive bays, supported capacity, recording throughput and feature compatibility; compare NVR recorders with a suitably sized server.

For a Wisenet WAVE configuration, verify the required recording channels and existing entitlements. The catalog offers PRO-04, PRO-08 and PRO-16 bundles. Do not order another sixteen licenses if the selected server already includes the needed licenses. Confirm fisheye behavior and exact camera compatibility before committing to the platform.

Read the NVR storage and bandwidth guide and Wisenet WAVE server guide for the next planning checks. Retention must be recalculated from actual recorded bitrate after commissioning; motion-only recording is not a guaranteed substitute for sufficient storage.

6. Commission against the evidence targets

  1. Walk each aisle with racks stocked to their expected height. Record occlusions and adjust coverage.
  2. Test faces at entrances and handling activity at docks in daytime and after dark.
  3. Review moving subjects for blur and open-door scenes for lost detail.
  4. Verify fisheye dewarping in live view, playback and exported files.
  5. Measure per-camera bitrate and peak PoE behavior with IR and other high-load features active.
  6. Confirm recording schedules, time synchronization, overwrite behavior and disk-health alerts.
  7. Recalculate storage from measured traffic, then review oldest available footage once the retention window has elapsed.
  8. Test an evidence export with the customer's authorized operator, and document access permissions and retention responsibilities.

What to send with a warehouse quote request

Send a floor plan with rack heights, dock and door locations, cable distances, lighting conditions and the evidence target for each view. Add the required retention period, existing recorder or VMS, license inventory and anticipated expansion.

Do not send access credentials or sensitive operational drawings through an ordinary enquiry. If your layout is confidential, ask how to share it securely first. The contact page is the starting point for discussing the layout and requesting an equipment quote.

For compliance-sensitive bids, use the NDAA documentation checklist. Warranty and delivery terms are available on the dedicated warranty and shipping and returns pages.

Frequently asked questions

How many cameras does a warehouse need?

Count evidence targets rather than square feet. Racks, dock positions, entrances and handling areas need distinct views. The sixteen-camera schedule in this guide is illustrative, not a universal coverage recommendation.

Can one fisheye camera cover several warehouse aisles?

A fisheye can show broad activity in an open area, but it cannot see through racks or pallets. Use dedicated aisle and entrance views where recorded detail matters, and verify dewarping in playback and exports.

How much storage does this sixteen-camera example need for thirty days?

At the assumed combined 80 Mbps, continuous recording uses 25.92 decimal TB over thirty days. An illustrative ten percent reserve gives 28.512 TB of usable planning capacity, before growth allowances. Size raw drives separately for RAID and recorder reservations, then validate actual bitrate.

Does every warehouse camera need a 60W PoE injector?

No. Select power equipment from the exact device's required PoE standard and maximum demand. High resolution alone does not establish a need for a 60W injector; negotiation and connector compatibility must also be verified.

Is this a completed NorthStar warehouse case study?

No. It is a hypothetical planning blueprint with explicit camera, bitrate and storage assumptions. It contains no customer installation results or guaranteed coverage claims.