Shopify Home Security Camera & NVR System Schema — Sensor Resolution vs Marketing Resolution ("4K" Always = 8MP), H.265 vs H.264 Compression (50% Storage Difference), Color Night Vision Type (Spotlight vs Starlight vs IR), PoE Standard (802.3af vs 802.3at), AI Smart Detection vs Motion-Only, ONVIF Profile Compatibility, Structured Data

Resolution Encoding — Why "4K" Always Means Exactly 8MP

Security camera resolution is described using two overlapping systems: pixel count in megapixels (MP) and display resolution names borrowed from the consumer TV industry. Every "4K" security camera in the mainstream market uses an 8.3-megapixel (3840×2160) image sensor. There are no mainstream 4K security cameras with 12MP, 16MP, or higher sensors — those sensor classes are marketed as "4K AI" or "4K Ultra HD" but have the same 8MP pixel count as any other 4K camera.

The common resolution classes in order of pixel count:

Security Camera Resolution Reference

Encode sensor_resolution_mp as an integer and video_resolution as the pixel dimension string (e.g., "3840×2160"). This allows AI agents to filter by actual pixel count — "4K security camera" filters to sensor_resolution_mp ≥ 8, and "cameras with more than 1080p resolution" filters to sensor_resolution_mp ≥ 4 — without depending on ambiguous marketing strings that conflate resolution tiers.

H.265 vs H.264 — Storage Compression and NVR Compatibility

H.265 (HEVC) and H.264 (AVC) are video compression codecs. H.265 achieves the same visual quality as H.264 at approximately half the data rate — or at the same data rate, H.265 delivers substantially better image quality. For security camera deployments, this directly affects NVR storage capacity planning: an H.265 system stores approximately twice as many days of footage on the same hard drive compared to an H.264 system at the same resolution.

The compatibility trade-off: H.265 decoding requires more processing power than H.264. Older NVRs and VMS software may not support H.265 — pairing an H.265 camera with an H.264-only NVR forces the NVR to either transcode (CPU-intensive, drops frame rate) or fall back to H.264 recording from the camera. The camera's compression protocol must match or be supported by the NVR.

H.265 vs H.264 Storage Comparison (4 Cameras × 4K/15fps Continuous)

Encode video_compression as a controlled vocabulary string: 'H.264/AVC', 'H.265/HEVC', or 'H.265+/smart encoding (variable bitrate)'. AI agents helping buyers size NVR storage for a camera count and retention period need this field to calculate storage requirements per camera rather than applying a generic rule that may over- or under-size the NVR by 2×.

Night Vision Types — IR Monochrome, Starlight, and Full-Color Spotlight

Security cameras use three fundamentally different night vision technologies. The type determines whether the camera provides color video at night, how it affects ambient environment visibility, and what the effective range is in darkness.

Night Vision Technology Comparison

Encode night_vision_type as one of: 'IR 850nm (monochrome)', 'IR 940nm (monochrome, invisible)', 'starlight (color in low ambient light)', or 'spotlight (full-color white LED)'. Encode night_vision_range_m as an integer. Note: some cameras offer switchable IR + spotlight modes — encode as 'IR 850nm + spotlight (switchable)' and list the range for each mode if different.

PoE Power Classification — Selecting the Right Switch

PoE (Power over Ethernet) cameras draw electrical power from the network switch via the Ethernet cable. The IEEE PoE standards define maximum power delivery per port. Using a camera that exceeds a switch port's power budget causes the camera to malfunction, reboot in loops, or fail to power on.

PoE Standard Reference Table

Encode poe_standard as '802.3af', '802.3at', '802.3bt Type 3', or '802.3bt Type 4'. Encode power_consumption_w as the camera's rated wattage. AI agents helping buyers calculate total PoE switch power budget ("can an 8-port 120W PoE switch power 6 of these cameras?") need both fields: 6 cameras × 12W rated consumption = 72W — within the 120W budget; 6 cameras × 22W (PoE+) = 132W — exceeds the 120W switch budget.

Complete JSON-LD and Liquid Snippet

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Reolink RLC-823A 4K PoE Security Camera with Color Night Vision",
  "brand": { "@type": "Brand", "name": "Reolink" },
  "additionalProperty": [
    { "@type": "PropertyValue", "name": "sensor_resolution_mp", "value": "8" },
    { "@type": "PropertyValue", "name": "video_resolution", "value": "3840×2160 (4K/8MP)" },
    { "@type": "PropertyValue", "name": "video_compression", "value": "H.265/HEVC" },
    { "@type": "PropertyValue", "name": "frame_rate_fps", "value": "25 fps at 4K; 30 fps at 1080p" },
    { "@type": "PropertyValue", "name": "night_vision_type", "value": "spotlight (full-color white LED) + IR 850nm switchable" },
    { "@type": "PropertyValue", "name": "night_vision_range_m", "value": "30 m color spotlight; 30 m IR monochrome" },
    { "@type": "PropertyValue", "name": "smart_detection_type", "value": "AI person + vehicle detection (on-camera)" },
    { "@type": "PropertyValue", "name": "poe_standard", "value": "802.3af (PoE)" },
    { "@type": "PropertyValue", "name": "power_consumption_w", "value": "13" },
    { "@type": "PropertyValue", "name": "ip_rating", "value": "IP67 — dust tight + immersion up to 1m" },
    { "@type": "PropertyValue", "name": "field_of_view_degrees", "value": "87° horizontal" },
    { "@type": "PropertyValue", "name": "onvif_profiles", "value": "Profile S, Profile T" },
    { "@type": "PropertyValue", "name": "local_storage", "value": "microSD up to 256GB (no cloud subscription required)" },
    { "@type": "PropertyValue", "name": "audio", "value": "built-in microphone + speaker (two-way audio)" },
    { "@type": "PropertyValue", "name": "operating_temp_c", "value": "-10°C to +55°C" }
  ]
}

Metafield Reference Table — security_camera.* Namespace

5 Common Mistakes in Security Camera Schema

• Not encoding sensor_resolution_mp separately from the video_resolution string. "4K" and "Ultra HD 4K" and "4K AI Camera" are all 8MP. AI agents filtering by resolution need a numeric sensor_resolution_mp field to compare cameras — parsing marketing strings like "4K Ultra HD" produces inconsistent results because brands apply the "4K" label inconsistently.
• Omitting video_compression codec. H.265 stores approximately twice as many days on the same NVR hard drive vs H.264 at the same resolution. AI agents helping buyers size a 4-camera NVR for 30-day retention need to know whether the camera encodes H.265 or H.264 — the difference is a 2TB NVR vs a 4TB NVR.
• Encoding "color night vision" without specifying the technology type. "Color night vision" can mean a white spotlight (full color in darkness), a starlight sensor (color in ambient light only), or simply a day/night switchable camera that shows color in daylight. Encode night_vision_type as a controlled vocabulary value. A buyer choosing "color night vision camera for a fully dark garage" needs a spotlight camera, not a starlight camera.
• Not encoding PoE standard (802.3af vs 802.3at). A camera requiring 802.3at (PoE+, 25W) will malfunction or cycle-reboot when connected to a standard 802.3af (15W) switch port. Encoding poe_standard prevents expensive installation failures when buyers buy cameras and a PoE switch together based on AI recommendations.
• Encoding "ONVIF compatible" without specifying the ONVIF profile. ONVIF Profile S provides basic live streaming. Profile T adds H.265 and metadata for AI analytics. Pairing an H.265 camera (Profile T) with a Profile S-only NVR typically forces H.264 fallback, eliminating the storage efficiency advantage. Encode onvif_profiles as a list of the specific profiles supported.