Skip to main content
Metrics type: Supporting Metrics • Category: Ecommerce Platform
Variants with a populated SKU. Below 95% breaks marketplace + 3PL integrations.

​
At a glance

Percentage of active variants with a populated SKU string. Below 95% breaks marketplace integrations (Amazon, eBay), 3PL feeds, and inventory-management apps that key off SKU.

​
Calculation

Calculated automatically from your Shopify data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A UK homewares brand on Shopify, ~2,400 active variants. Snapshot 12 May 26. The card reads 90.0%, 5 ppt below the 95% alert threshold. Six things to notice:
  1. The alert is firing. Coverage <95% means downstream integrations have gaps: Amazon will reject 240 variants on next feed sync; the 3PL won’t receive SKUs for those variants and pickers will see “unnamed item” labels.
  2. Most missing SKUs are recent additions. Drill-down typically shows 70-80% of the missing-SKU variants were added in the last 30 days. The team adds products fast and forgets to populate SKU. Audit the product-creation workflow.
  3. Some are intentional. Bundle variants, gift cards, and digital products often don’t need SKUs by some teams’ conventions. If those are the missing 240, the threshold is misconfigured; tune to exclude productType IN ('Gift Card','Digital','Bundle').
  4. Marketplace impact is silent. When a Shopify-Amazon-Connector pushes an inventory feed, missing-SKU variants are silently dropped. The brand may not realise 240 variants are invisible on Amazon until a customer asks why a product disappeared.
  5. 3PL impact is loud. When the 3PL receives a fulfilment instruction with a missing SKU, the picker can’t find the SKU label on the shelf. Either the order delays, the picker substitutes, or the warehouse calls customer-service. All friction.
  6. Action: bulk-fix via Shopify import/export. Export all variants, populate SKU column based on a naming convention (e.g. [product_handle]-[colour]-[size]), re-import. Coverage rises to ~100% in minutes. Worth doing as a quarterly hygiene action.

​
Sibling cards merchants should reference together

SKU Coverage is the catalogue-hygiene canary. Companions:

​
Reconciling against the vendor’s own dashboard

Where to look in Shopify Admin:
Shopify Admin → Products → All products filtered by SKU is empty
The most direct equivalent. Count of matching products / total active products = coverage. Should match this card to within sync-lag tolerance. Other Shopify Admin views:
  • Bulk editor (Products → Bulk actions → Edit products): shows SKU column for bulk fix.
  • Apps like Stocky, Inventory Planner: typically refuse to track variants without SKUs; their dashboards show how many are excluded.
Why our number may legitimately differ from Shopify Admin: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

Why does coverage matter? Five downstream consumers depend on SKUs:
  1. Marketplaces (Amazon, eBay, Etsy): require SKU to list; missing-SKU variants are silently dropped.
  2. 3PL / fulfilment partners: pick orders by SKU; missing-SKU variants cause pick failures.
  3. Inventory-management apps (Stocky, Inventory Planner, Cogsy): track stock by SKU; missing-SKU variants don’t appear in forecasts.
  4. Accounting / ERP integrations (Xero, NetSuite, QuickBooks): post sales by SKU; missing-SKU variants accumulate as “unknown product” entries.
  5. Bulk catalogue feeds (Google Shopping, Meta Catalog): require SKU as the unique identifier for ad serving.
Why do new variants come in without SKUs? Default Shopify product creation doesn’t require SKU. Two patterns:
  1. Manual creation by content team: marketing-focused contributors think in product names, not SKUs. Easy oversight.
  2. App-imported products: some apps create variants without populating SKU (relying on Shopify variant ID). These are typically the worst offenders.
Action: mandate SKU as required field via Shopify product-template customisation, or review at end-of-week. What’s a healthy coverage threshold? For most brands, 99-100% should be the target. The 95% alert threshold is a “wake up” signal; persistent operation at 95-98% indicates process gaps. Should I exclude gift cards and digital products? Yes if your business policy doesn’t track them by SKU. Configure exclusions in Nerve Centre → Catalogue → SKU Coverage Filters. Defaults exclude productType IN ('Gift Card'). My SKU strings have prefixes / suffixes; does that matter? For coverage purposes, no; non-empty string suffices. For downstream consumers, format matters. Example: a 3PL may require alphanumeric only (HOMEWARES-001); some marketplaces require ASIN-format (12-char alphanumeric). Audit per-channel SKU naming policies. Why are some variants showing twice? Duplicate SKUs are a separate problem from missing SKUs. This card measures presence, not uniqueness. Pair with a duplicate-SKU report (on roadmap) to find variants with the same SKU; they confuse downstream systems just as much as missing ones. Subscription products, do they need SKUs? Yes. Recurring orders create line items with SKUs; if missing, the recurring billing has no product reference. Subscription apps like ReCharge, Bold, or native Shopify Subscriptions require SKUs. Action playbook to fix coverage:
  1. Bulk export all active variants to CSV.
  2. Identify missing SKU rows (filter on empty SKU column).
  3. Apply naming convention in CSV: e.g. {handle}-{option1}-{option2}.
  4. Bulk import the CSV; Shopify updates SKUs in batch.
  5. Verify coverage rises to ~100% on this card.
  6. Process change: make SKU a required field in your product-creation checklist; consider a Shopify Function to enforce it server-side.

​
Tracked live in Vortex IQ Nerve Centre

SKU Coverage is one of hundreds of KPI pulses Vortex IQ tracks across Shopify and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.