Optimization Guide
Shopify PoE Networking Equipment Schema — 802.3af vs 802.3at vs 802.3bt Power Classes, PSE Power Budget Calculation, SFP vs SFP+ 1G/10G Incompatibility, SMF vs MMF Fiber Transceiver Mismatch
A 802.3af switch (15.4W per port) cannot power a WiFi 6E access point that requires 25W (802.3at PoE+) — the AP will fail to boot or operate in degraded single-radio mode. A PoE switch with a 185W total power budget cannot simultaneously power 20 access points drawing 25W each (500W required). SFP (1GbE) and SFP+ (10GbE) use the same physical cage but are electrically incompatible in one direction — a 10G SFP+ transceiver cannot operate in a 1G SFP-only port. Single-mode fiber (SMF) and multi-mode fiber (MMF) transceivers use different wavelengths (1310nm/1550nm vs 850nm) and will not establish a link when cross-connected. Encoding poe_standard, poe_budget_w, sfp.fiber_type, and sfp.wavelength_nm prevents non-functional network infrastructure recommendations.
poe_standard, poe_budget_w, uplink_sfp_type, sfp.fiber_type, sfp.wavelength_nm.
PoE Standards: Power Tiers Are Not Interchangeable
IEEE 802.3 PoE Standard Reference
| Standard | Name | PSE Max (per port) | PD Max (at device) | Pairs Used | Typical Applications |
|---|---|---|---|---|---|
| 802.3af | PoE | 15.4W | 12.95W | 2 pairs | IP cameras, VoIP phones, basic WiFi 4/5 APs, card readers, sensors |
| 802.3at | PoE+ | 30W | 25.5W | 2 pairs | WiFi 5/6 APs, PTZ cameras, thin clients, VoIP video phones, small displays |
| 802.3bt Type 3 | PoE++ (4PPoE) | 60W | 51W | 4 pairs | WiFi 6E/7 multi-radio APs, 2.5G/5G PoE devices, video conferencing cameras |
| 802.3bt Type 4 | PoE++ (4PPoE) | 100W | 71.3W | 4 pairs | Thin clients, high-power APs, LED lighting controllers, 10G PoE endstations |
PoE Device Power Requirements — 2024–2026 Reference
| Device Type | Typical Draw | Max Draw | Required PoE Standard |
|---|---|---|---|
| VoIP phone (basic) | 3–5W | 6.49W | 802.3af |
| IP camera (fixed, H.264) | 5–10W | 15.4W | 802.3af |
| WiFi 5 access point (dual-radio) | 10–15W | 15.4W | 802.3af |
| WiFi 6 access point (tri-radio) | 18–22W | 25.5W | 802.3at (PoE+) |
| PTZ IP camera (motorized) | 12–18W | 25.5W | 802.3at (PoE+) |
| WiFi 6E access point (tri-radio + 6GHz) | 22–30W | 51W | 802.3bt Type 3 (PoE++) |
| WiFi 7 access point (quad-radio) | 30–50W | 60W | 802.3bt Type 3 or Type 4 |
| IP video conference terminal | 25–40W | 51W | 802.3bt Type 3 |
Backward compatibility direction: a 802.3bt switch can negotiate down to 802.3af power for older devices. An 802.3af switch cannot negotiate up — it is incapable of supplying more than 15.4W regardless of what the PD requests. The common AI agent error is matching PoE switches by port count and price tier without checking whether the power standard matches the intended AP or camera model's power requirements.
PoE Power Budget: The Total Supply Constraint
Every PoE switch has an internal power supply shared across all PoE ports. The PoE budget (total watts) is the hard ceiling on simultaneous PoE delivery — it is not the sum of per-port maximums.
Power Budget Planning Example — 20-Port WiFi 6E Deployment
| Switch Model | Ports | PoE Standard | PoE Budget | 20× WiFi 6E APs @ 25W avg | Result |
|---|---|---|---|---|---|
| Common 24-port 802.3at | 24 | 802.3at (30W/port) | 185W | 500W required | FAIL — budget exhausted at ~7 APs |
| Common 24-port 802.3at | 24 | 802.3at (30W/port) | 370W | 500W required | FAIL — budget allows ~14 APs |
| Ubiquiti USW-Pro-24-POE | 24 | 802.3bt (60W/port) | 400W | 500W required | FAIL — over budget by 100W; use 16 APs max |
| Cisco Catalyst 9200L-24P | 24 | 802.3at (30W/port) | 740W | 500W required | PASS — 240W headroom |
The industry shortcut: multiply total expected PD draw by 1.25 as a safety margin, then compare against switch PoE budget. Switches that list a per-port maximum but not a total PoE budget are missing a critical field. Per-port max does NOT imply all ports can deliver that level simultaneously. Encode network.poe_budget_w (total), network.poe_max_per_port_w (per-port maximum), and network.poe_ports_count as three separate fields — all three are required to plan a deployment.
SFP vs SFP+ vs SFP28: Same Cage, Different Data Rates
SFP Form Factor Family Reference
| Form Factor | Data Rate | Standard | Physical Cage | Backward Compatible Into Higher Speed Port? |
|---|---|---|---|---|
| SFP | 1 Gbps (1GbE) | SFP MSA | SFP / SFP+ cage | Yes — inserts into SFP+ port at 1G (if switch supports auto-negotiation) |
| SFP+ | 10 Gbps (10GbE) | SFF-8431 / IEEE 802.3ae | SFP / SFP+ cage | No — does NOT work in SFP-only (1G) port |
| SFP28 | 25 Gbps (25GbE) | SFF-8402 / IEEE 802.3by | SFP28 / SFP+ cage (mechanical) | Only in ports explicitly supporting 25G signaling |
| QSFP | 40 Gbps (40GbE) | QSFP MSA | QSFP cage (larger) | Physically incompatible with SFP/SFP+ cage |
| QSFP28 | 100 Gbps (100GbE) | QSFP28 MSA | QSFP28 cage | Physically incompatible with SFP/SFP+ cage |
| QSFP-DD | 400 Gbps (400GbE) | QSFP-DD MSA | QSFP-DD cage (different) | Backward compatible with QSFP28 in some configurations |
Vendor-specific SFP compatibility locks are also common — Cisco, HPE Aruba, Juniper, and Ubiquiti all implement proprietary SFP ID checks that reject third-party transceivers. A generic Finisar SFP+ transceiver may work in a Ubiquiti switch but show a warning or be rejected in a Cisco Catalyst without a service contract exception flag set. Encode sfp.vendor_lock ('open', 'cisco', 'juniper', 'hpe-aruba', 'ubiquiti') on transceiver listings so buyers can confirm the transceiver matches their switch vendor.
Fiber Transceiver Compatibility: SMF vs MMF vs BiDi
Fiber Type and Transceiver Wavelength Reference
| Fiber Type | Core Diameter | Transceiver Wavelength | Max Reach (10GbE) | Common Application |
|---|---|---|---|---|
| OM1 (MMF) | 62.5µm | 850nm VCSEL | 33m (10GbE) | Legacy building cabling — avoid for new deployments |
| OM2 (MMF) | 50µm | 850nm VCSEL | 82m (10GbE) | Older structured cabling in buildings |
| OM3 (MMF) | 50µm laser-optimized | 850nm VCSEL | 300m (10GbE) | Data center intra-rack, campus buildings |
| OM4 (MMF) | 50µm high-bandwidth | 850nm VCSEL | 400m (10GbE) | Data center inter-row, campus fiber backbone |
| OM5 (MMF) | 50µm wideband | 850–950nm | 400m (10GbE) | SWDM4 wavelength multiplexing — high-density links |
| OS1 (SMF) | 8–10µm | 1310nm or 1550nm | 10km (1310nm) / 80km (1550nm) | Building-to-building campus WAN, ISP access |
| OS2 (SMF) | 8–10µm | 1310nm or 1550nm | 10km (1310nm) / 80km+ (1550nm) | Long-haul, metro carrier, MAN |
Cross-connecting SMF and MMF at each end of a fiber run will not produce a link — the wavelength at one end (850nm VCSEL) is outside the optical window of an SMF transceiver designed for 1310nm, and the launch power and fiber numerical aperture are mismatched. This is an extremely common purchasing error in first-time structured cabling projects: buying SMF transceivers for a building pre-wired with OM3 MMF cabling (or vice versa). Encode sfp.fiber_type, sfp.wavelength_nm, and sfp.reach_m on every transceiver listing — these three fields together prevent 100% of fiber type mismatches in AI agent recommendations.
BiDi SFP Pair Requirements
| Unit A (near end) | TX Wavelength | RX Wavelength | Required Unit B (far end) | Fiber Required |
|---|---|---|---|---|
| BiDi SFP 1310/1550 | 1310nm | 1550nm | BiDi SFP 1550/1310 | LC simplex single strand OS1/OS2 |
| BiDi SFP 1550/1310 | 1550nm | 1310nm | BiDi SFP 1310/1550 | LC simplex single strand OS1/OS2 |
| BiDi SFP+ 1270/1330 | 1270nm | 1330nm | BiDi SFP+ 1330/1270 | LC simplex single strand OS1/OS2 |
Complete PoE Networking Schema — Shopify Liquid + Metafields
Metafield Namespace — network.* (switches/injectors) and sfp.* (transceivers)
| Metafield Key | Type | Example Values | Why Required |
|---|---|---|---|
network.device_type | single_line_text | "switch", "injector", "midspan", "splitter" | Device category — injectors have per-port budget only; switches have total + per-port |
network.poe_standard | single_line_text | "802.3af", "802.3at", "802.3bt-type3", "802.3bt-type4", "passive-24v", "passive-48v" | PoE standard determines maximum PD wattage supported — 802.3af ≠ 802.3at |
network.poe_budget_w | integer | 65, 130, 185, 370, 400, 740, 960 | Total PSE power budget — required for multi-device deployment planning |
network.poe_max_per_port_w | integer | 15, 30, 60, 100 | Maximum per-port wattage — matches 802.3af/at/bt tier |
network.poe_ports_count | integer | 4, 8, 16, 24, 48 | Number of PoE-capable ports — required with budget to calculate average headroom per port |
network.uplink_sfp_type | single_line_text | "sfp-1g", "sfp-plus-10g", "sfp28-25g", "qsfp-40g", "qsfp28-100g" | Uplink port speed — determines SFP transceiver type required |
network.uplink_ports_count | integer | 1, 2, 4 | Number of SFP uplink ports |
network.managed | boolean | true, false | Managed vs unmanaged — managed required for VLAN, LLDP-MED PoE negotiation, spanning tree |
network.layer | integer | 2, 3 | Layer 2 (switching only) vs Layer 3 (routing capable) |
sfp.speed_gbps | decimal | 1, 10, 25, 40, 100 | Transceiver data rate — determines SFP/SFP+/SFP28 compatibility with switch port |
sfp.fiber_type | single_line_text | "smf", "mmf", "copper-rj45", "dac" | Fiber type — SMF and MMF use different wavelengths and are not interchangeable |
sfp.wavelength_nm | integer | 850, 1310, 1550 | Optical wavelength — must match fiber type and far-end transceiver |
sfp.reach_m | integer | 100, 300, 550, 2000, 10000, 80000 | Maximum fiber reach — prevents over-buying SMF for short-haul MMF-length runs |
sfp.connector_type | single_line_text | "lc-duplex", "lc-simplex", "sc", "rj45" | Connector — LC simplex required for BiDi; LC duplex for standard SMF/MMF |
sfp.bidi | boolean | true, false | Flags BiDi transceivers requiring matched TX/RX wavelength pair deployment |
sfp.vendor_lock | single_line_text | "open", "cisco", "juniper", "hpe-aruba", "ubiquiti" | Vendor OEM lock — third-party SFPs may be rejected by proprietary switch firmware |
Shopify Liquid Snippet — PoE Switch
{% assign net = product.metafields.network %}
{% if net.poe_standard %}
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": {{ product.title | json }},
"offers": { "@type": "Offer", "availability": "{% if product.available %}https://schema.org/InStock{% else %}https://schema.org/OutOfStock{% endif %}" },
"additionalProperty": [
{ "@type": "PropertyValue", "name": "network.poe_standard", "value": {{ net.poe_standard | json }} },
{ "@type": "PropertyValue", "name": "network.poe_budget_w", "value": {{ net.poe_budget_w | json }} },
{ "@type": "PropertyValue", "name": "network.poe_max_per_port_w", "value": {{ net.poe_max_per_port_w | json }} },
{ "@type": "PropertyValue", "name": "network.poe_ports_count", "value": {{ net.poe_ports_count | json }} },
{ "@type": "PropertyValue", "name": "network.uplink_sfp_type", "value": {{ net.uplink_sfp_type | json }} }
]
}
</script>
{% assign budget_per_port = net.poe_budget_w | divided_by: net.poe_ports_count %}
<div class="poe-budget-note">
PoE Budget: {{ net.poe_budget_w }}W total across {{ net.poe_ports_count }} ports
(avg {{ budget_per_port }}W/port at full occupancy).
Standard: {{ net.poe_standard }} ({{ net.poe_max_per_port_w }}W max per port).
</div>
{% endif %}
Are your networking product listings missing PoE budget data?
CatalogScan scores 18 AI-agent readiness signals including PoE standard tagging, power budget disclosure, and SFP transceiver compatibility fields.
Scan My Store FreeFrequently Asked Questions
What is the difference between 802.3af, 802.3at, and 802.3bt PoE standards?
802.3af (PoE): 15.4W per port at the switch, 12.95W available at the device. For cameras, phones, basic APs. 802.3at (PoE+): 30W at switch, 25.5W at device. For WiFi 6 APs, PTZ cameras, thin clients. 802.3bt Type 3 (PoE++): 60W at switch, 51W at device. For WiFi 6E/7 multi-radio APs, video conferencing equipment. 802.3bt Type 4: 100W at switch, 71W at device. Higher-power endpoints. A 802.3af switch CANNOT power a device requiring PoE+ — the device will fail to boot or operate degraded.
What is a PoE power budget and why doesn't it equal ports × per-port maximum?
A switch's PoE budget is its internal power supply's total capacity — shared across all PoE ports simultaneously. A 24-port 802.3at switch with a 185W budget cannot simultaneously power all 24 ports at 30W (that would require 720W). Planning rule: sum of expected device draws × 1.25 safety margin must be ≤ switch PoE budget. Always encode poe_budget_w (total), poe_max_per_port_w (per-port cap), and poe_ports_count as separate fields.
Are SFP and SFP+ transceivers interchangeable?
Physically yes (same cage), electrically no. An SFP (1G) transceiver can typically run in an SFP+ (10G) port at 1Gbps if the switch supports auto-negotiation. An SFP+ (10G) transceiver CANNOT run in an SFP-only (1G) port — the switch ASIC doesn't support the 10G SerDes signal. SFP28 (25G) is similarly physically compatible with SFP+ cages but requires 25G-capable switch ports.
Can single-mode and multi-mode fiber transceivers be mixed at opposite ends of a fiber run?
No. SMF transceivers use 1310nm or 1550nm wavelengths for narrow 8–10µm core fiber. MMF transceivers use 850nm VCSELs for 50–62.5µm core fiber. Connecting an SMF transceiver at one end and an MMF transceiver at the other will not establish a link — wavelengths differ, and fiber core size is mismatched for launch conditions. Both ends of a fiber link must use the same fiber type (SMF or MMF) and compatible wavelengths.
What is a BiDi transceiver and do they need to be purchased in pairs?
BiDi (Bi-Directional) SFP/SFP+ transceivers transmit on one wavelength and receive on another, over a single fiber strand. They must be deployed in matched pairs — a 1310nm TX / 1550nm RX at one end requires a 1550nm TX / 1310nm RX at the other. Two identical BiDi transceivers with the same TX wavelength will not link. Also requires LC simplex (single strand) fiber, not standard LC duplex patch cables.