A smartphone in Shopify can have up to 3 option types: storage, color, and network band. Take 2 storage sizes, 5 colors, and 2 network variants and you get 20 rows under one product handle (as of November 2026). Electronics product data for upload teams is wider, more precise, and more decision-heavy than apparel or home goods, and the decisions need to be settled before data entry begins, not midway through.
Key takeaways
- Electronics products carry more fields per product than most other categories, including technical specifications that an upload team enters verbatim from the source you provide
- Variant structure must be decided before data entry begins: which 3 attributes become Shopify option types, and whether different storage sizes carry different prices
- Model numbers often differ from marketing names; a clear mapping table prevents duplicate product entries and mid-job pauses
- Compatibility data for accessories goes into metafields or prefixed tags, not the standard product fields
- A complete electronics data brief covers a master model list, variant mapping decisions, a tech specs table, compatibility scope, and image file naming rules
Why electronics product data takes more preparation
An upload team filling in an apparel product needs a title, size and color variants, weight, and a description. An upload team filling in a consumer electronics product needs all of that, plus:
- A model number and a marketing name, which are often different and cannot be used interchangeably in Shopify
- Technical specifications: processor, RAM, storage capacity, screen size, resolution, battery life, connectivity (Wi-Fi generation, Bluetooth version, 5G bands)
- Compatibility data for accessories: which case fits which handset, which charger fits which port
- Regulatory information: CE marks, FCC IDs, country certifications, as printed on the packaging
Supplier files for electronics are dense. A file with 40 handsets and 12 accessories can have several hundred rows, with each row carrying 20 or more fields that all need checking before they go into Shopify. The difference from apparel is not only the number of fields: it is the type. Clothing fields are mostly words. Electronics fields include specifications where a wrong number has a real consequence for a buyer.
Core electronics product data for upload teams
These are the fields an upload team fills at the product level (the same value for every variant of that product):
| Field | What to supply | Notes |
|---|---|---|
| Title | Brand and model name and key spec (e.g., "Pixel 9 Pro 256GB Obsidian") | Agree the naming template before the job starts |
| Description | Key features, screen size, processor, battery, connectivity summary | Source from your brand content, not the supplier file alone |
| Vendor | Brand name (Google, Samsung, Apple) | Used for filtering and collection rules in Shopify |
| Product type | Category label your store uses (Smartphone, Wireless Earbuds) | Agree a consistent list upfront; a product can have only one |
| Tags | OS type, age range, compatibility tags if used | Agree tag format and prefixes in the brief |
| Weight | Retail-packaged weight in grams (or kilograms), for shipping rates | Use the boxed weight, not the device weight alone |
Variant-level fields (each row under the product handle gets its own values):
| Field | What to supply |
|---|---|
| SKU | Unique per variant; agree whether to use your internal SKU or the supplier part number |
| Barcode (GTIN/EAN/UPC) | One per variant; different storage sizes or colors often carry different barcodes |
| Price | Per variant if prices differ by storage size; otherwise one price at product level |
| Inventory quantity | Opening stock per variant per location |
For a broader checklist of fields across all product categories, the Shopify product data entry checklist covers the core fields an upload team verifies on receipt.
Variant structure: storage, color, and network band
Shopify allows up to 3 option types per product and up to 2,048 variants per product (as of November 2026). For mobile phones, the three most common option types are:
- Storage (64GB, 128GB, 256GB, 512GB, 1TB)
- Color (product color name, as branded by the manufacturer)
- Network (Unlocked, AT&T, Verizon, T-Mobile) if you sell carrier-locked variants
Before data entry starts, the merchant needs to decide:
- Do you sell carrier-locked phones? If yes, network band goes in as the third option type.
- If not, two option types (storage and color) leaves the third slot open for a future attribute.
- Do different storage sizes carry different prices? If yes, the price field gets filled per variant row rather than at the product level.
A common problem: supplier files list the same handset under multiple model numbers, one per carrier variant, and an upload team receiving the file without a mapping decision will often ask whether these are separate Shopify products or variants of one product. Settling this in the brief before the job starts is faster than raising it midway through entry.
Compatibility and technical specifications
Compatibility data is specific to accessories: a phone case fits certain handset models, a charger fits certain connector types, a screen protector fits certain screen dimensions. This data does not go into Shopify's standard product fields. The two main approaches are:
Tags: "Compatible: iPhone 15" or "Fits: USB-C" as prefixed tags. Quick to filter and fast to bulk-edit, but difficult to query programmatically and not ideal for displaying a structured list on the product page.
Metafields: A compatible_devices metafield (a list of text values or product references) gives structured compatibility data that themes and apps can display on the product page. The upload team enters these as text if the merchant specifies the values in the brief.
Either way, the merchant supplies the compatibility scope. An upload team will not make compatibility decisions from a supplier file alone: the risk of assigning the wrong compatible model to a case or charger is too high.
Technical specifications go into the product description as formatted text, or into metafields if the store displays a spec comparison table on product pages. Supply them in a consistent format. The upload team enters them as given; they do not convert units or confirm specs against a third-party source. Shopify's product details help page covers the standard product fields and their limits (as of November 2026).
Model numbers: what to send your upload team
The model number disambiguation problem is specific to electronics. A supplier file for smartphones will often include:
- A manufacturer model number (SM-G991BZBGEUB, for a Samsung Galaxy S21 5G Phantom Gray UK variant)
- A marketing name (Galaxy S21 5G)
- A region code or carrier code embedded in the model number
A merchant selling through Shopify typically wants the marketing name as the product title, with the model number stored in a separate field (a metafield, the SKU, or a tag) for internal reference and filtering. Without a mapping table from the merchant, an upload team either has to pause on every product or guess, and guessing across 40 handsets creates errors that take longer to correct than the original job.
A model number mapping table is a two-column spreadsheet: supplier model number on the left, the display title it maps to on the right. For a 40-handset catalog, this takes about 30 minutes to build once and saves several hours of correction work during entry.
For a complete electronics upload job, a data brief covers:
- Master model list with marketing name, model number, and storage/color/network variant breakdown
- Variant structure decision (which 3 attributes become option types, or 2 if network is not used)
- Tech specs table, in the format and units the product page will display
- Compatibility scope for accessories (compatible devices per SKU)
- SKU convention (internal vs. supplier part number)
- Image file naming convention (style code and color code, so the upload team can match images to variant rows)
For the broader preparation guide before sending work to a team, what to send your upload team covers the standard file and brief requirements across all product categories. For first-time launches where product setup decisions run across the whole catalog, the new product range launch checklist is a good starting point for electronics ranges.
Our Shopify product data entry service handles the full electronics data job, from checking the brief to entering every product field. For what a team handles specifically in this category, our electronics product upload service describes the data work by industry.
Frequently asked questions
How many variant options can a Shopify product have?
Shopify allows up to 3 option types per product (for example, storage, color, and network band) and up to 2,048 total variants (as of November 2026). Most consumer electronics products stay well under this limit. A product sold in 4 storage sizes, 5 colors, and 2 carrier variants gives 40 rows, which is fine. Products needing more than 3 option types require a third-party app.
Should compatibility data go in tags or metafields?
Tags work well for basic compatibility filters involving a small number of device types. Metafields work better for structured data that your theme or an app will display on the product page, such as a "compatible with" list. The upload team can handle either approach; specify which one you want, and the value format, in the brief before the job starts.
What if our supplier file has different model numbers for the same product?
Provide a model number mapping table: supplier model number on the left, the Shopify display title on the right. A model number mapping table prevents duplicate product entries and mid-job holds reliably. Without it, an upload team will pause on every ambiguous model and wait for a decision from you.
Do we need to send spec sheets for every product?
Yes. An upload team enters technical specifications verbatim from the source you provide. They do not research specs from a third-party database or confirm figures from memory. A complete spec sheet per model is the preferred input. If you only have a supplier catalog, that works too, as long as the specs are readable and attributed to the correct model number.
Can the upload team handle both handsets and accessories in one job?
Yes. Accessories need compatibility data in addition to the standard fields, so the brief needs a compatibility scope alongside the core product data. For jobs that mix handsets and accessories, a combined model and compatibility table covers both and reduces the number of questions during entry.
