The best camera for a warehouse entrance may be the wrong camera for a long aisle or loading bay. Begin with the view and event you need, then compare equipment that can support that requirement.
An “AI camera” label is not a complete specification. Ask which features run on the camera, which need a recorder or processing device, and which require a licence. Then check how a usable result reaches the person responsible for the site.
Write a requirement for each important view
For a restricted doorway, the requirement might be to review an entry after closing. At a loading bay, it might be a clear record of a goods handover. At the vehicle gate, it might be a separate number-plate assessment. These are different tasks and should have separate acceptance criteria.
List the target distance, working hours, camera position and likely obstructions. If those details are still unknown, a site survey is more useful than choosing the highest-resolution model from a catalogue.
Use the warehouse coverage guide to settle placement and count. This buying checklist addresses which equipment and configuration should serve those views.
Compare the installed image, not only megapixels
Ask for a sample at the intended distance and framing. Check what is visible when a shutter is open, a truck is parked or stock occupies the foreground. Review the recording or export at the settings you will use.
A camera specification does not remove scene limits. Axis's analytics documentation identifies lighting, visibility, mounting and object size as considerations for its application. Other products need their own documented limits and tests; do not copy one manufacturer's settings into another system.
For a night requirement, test the relevant night conditions. Ask how the proposed lens and lighting serve the task rather than assuming that a broad “night vision” label settles it. Record conditions that were not tested.
Check the complete technical combination
| Decision | Evidence to request |
|---|---|
| Camera and lens | Exact model and the intended view at the required distance |
| Recording | Supported settings, storage calculation and playback/export result |
| Analytics | Named event, supported deployment path and licence scope |
| Integration | Camera or recorder stream, firmware and tested configuration |
| Operations | Alert recipient, escalation, maintenance and fault handling |
If you already have cameras, compare reuse with selective replacement. A brand name or stream protocol is insufficient to approve an AI Alerto deployment. PGAK's compatibility checklist sets out the information needed for technical review.
Include the network and power design in the quote. Confirm responsibility for switches, backup power, cable protection and the processing device where applicable. A camera price that excludes these items is not a complete project cost.
Ask for a pilot that can reveal a failure
Agree the required events before testing. Include normal authorised activity as well as the event that should trigger attention. Plan conditions such as a partially obstructed route or the required night view where safe and relevant.
Keep a manual event record. Compare expected events with actual alerts, including misses, unwanted alerts and delay. Log outages separately, because an unavailable stream is a different failure from an incorrect classification.
The pilot worksheet provides a consistent record. Do not choose a supplier solely from its best demonstration clip. A useful pilot produces a pass, a defined correction or a reason not to proceed.
Compare ownership costs and support
Request separate amounts for hardware, installation, licences, storage, integration, commissioning and ongoing support. Ask what changes if channels are added or a camera is replaced. Avoid assuming that a low initial purchase price gives the lowest cost over the period you intend to operate the system.
Clarify who reviews alerts and who handles physical incidents. Analytics can support that workflow; it does not supply an on-site responder by itself. Confirm maintenance access and the process for restoring a failed camera or service.
For an AI Alerto by PGAK assessment, prepare the warehouse city, existing camera and recorder details if known, and one priority event. The result should be a site-specific feasibility discussion, not an unsupported ranking of camera brands.