If you’re going to build a Shopify metafield comparison table for electronics products, the schema is the project. Get the metafield definitions right and the rest is plug-and-play. Get them wrong and you’ll be patching field names and recreating tables every time you add a sub-category. This page is the schema reference for an electronics catalog. The full setup walk-through lives at the parent Shopify comparison tables for electronics stores page.
Every metafield below uses the custom namespace, since that’s the namespace Shopify exposes by default. You can pick a different namespace if your store has organizational reasons to do so — SimplyCompare reads from any namespace.
Recommended metafield schema for electronics
Laptops and computers
| Display name | Metafield key | Type | Example |
|---|---|---|---|
| Processor | custom.processor |
Single line text | Apple M3 Pro 11-core |
| RAM (GB) | custom.ram_gb |
Integer | 18 |
| Storage (GB) | custom.storage_gb |
Integer | 512 |
| Display size (inches) | custom.display_inches |
Decimal | 14.2 |
| Display resolution | custom.display_resolution |
Single line text | 3024 × 1964 |
| Battery life (hours) | custom.battery_life_hours |
Integer | 22 |
| Weight (grams) | custom.weight_grams |
Integer | 1408 |
| Ports | custom.ports |
Multi-line text | 3× USB-C, 1× HDMI, MagSafe |
| Operating system | custom.operating_system |
Single line text | macOS Sequoia |
Wireless earbuds and headphones
| Display name | Metafield key | Type | Example |
|---|---|---|---|
| Driver size (mm) | custom.driver_size_mm |
Integer | 9 |
| Battery, buds (hours) | custom.battery_buds_hours |
Decimal | 6.5 |
| Battery, case (hours) | custom.battery_case_hours |
Integer | 30 |
| Noise cancellation | custom.noise_cancellation |
Single line text | Active (up to −26 dB) |
| Codec support | custom.codec_support |
Single line text | AAC, SBC, LDAC |
| Water resistance | custom.water_resistance |
Single line text | IPX4 |
| Bluetooth | custom.bluetooth_version |
Single line text | Bluetooth 5.3 |
Smart home and accessories
| Display name | Metafield key | Type | Example |
|---|---|---|---|
| Resolution | custom.resolution |
Single line text | 4K / 2160p |
| Field of view | custom.fov_degrees |
Integer | 130 |
| Storage type | custom.storage_type |
Single line text | Cloud + microSD |
| Smart home platforms | custom.platform_support |
Multi-line text | Google Home, Alexa, HomeKit |
| Power source | custom.power_source |
Single line text | Wired (USB-C) |
How those metafields flow into SimplyCompare
Once your metafield definitions exist and you’ve populated values on each product, the connection to SimplyCompare is automatic. Open the dashboard, create a new comparison table, select your products, and your metafields appear as available rows in the row editor. Drag them into the order you want, set display labels (e.g. “RAM (GB)” instead of custom.ram_gb), and you’re done.
From that point, every change you make to a metafield value flows through to every comparison table that uses it — no resync, no re-embed, no manual refresh.
Schema design tips for electronics catalogs
Use consistent units. Pick GB or MB for storage, hours or minutes for battery — and stick with one across your catalog. Mixing units forces shoppers to mentally convert and undermines the table.
Separate units from values when possible. Store custom.ram_gb as integer 16, not text “16GB”. Use the display label to add the “GB” unit. This keeps your data clean for sorting or filtering later.
Avoid free-text where you can avoid it. A free-text “battery” field invites typos and inconsistent formatting. An integer custom.battery_life_hours field forces consistency.
Plan for variant-level metafields. If your products have variants with different specs (e.g. a laptop with 16GB and 32GB RAM options), set the metafield definition to apply at the variant level rather than the product level. SimplyCompare can read either.
Frequently asked questions
Can SimplyCompare read metafields from a non-default namespace?
Yes. SimplyCompare reads from any metafield namespace you’ve defined. The custom namespace is the recommended starting point because Shopify exposes it by default in the metafield editor, but if you’ve organized your metafields under a brand-specific namespace, that works too.
How does SimplyCompare handle missing metafield values?
If a product has no value for a metafield that’s included in the comparison, SimplyCompare can either show the cell blank or hide that row for that product. The choice is configurable per table.
Can I add a new metafield and have it appear in existing tables automatically?
You’ll need to add the new metafield to each table’s row order in the SimplyCompare dashboard once. After that, any value updates flow through automatically.
Are there limits on how many metafields I can include in a single comparison table?
Practical limits matter more than technical ones. Tables with more than 12–15 rows become hard to scan, especially on mobile. For deep spec sheets, consider splitting into two tables (e.g. “Performance specs” and “Connectivity & ports”).
What if Shopify changes their metafield API?
SimplyCompare uses Shopify’s standard metafield interface. The interface is stable and changes are typically additive. We update the app as needed to stay current; no action is required from your side.
Schema right, comparison sorted
Get your electronics metafields right and the comparison tables write themselves. SimplyCompare connects to whatever you’ve set up, displays it cleanly, and keeps it in sync as you grow your catalog.