Catalog variations with no SKU set. SKU-less items break inventory, reporting, and cross-channel parity.
At a glance
A real-time count of catalog item variations that have no SKU assigned. A SKU is the stable identifier that ties a variation to inventory counts, per-item reporting, purchase orders, and any external system (a 3PL, an ERP, a marketplace listing). A variation with no SKU is a blind spot: it still sells, but it is hard to reconcile, hard to reorder, and impossible to match across channels. For a merchant running both POS and online, SKU-less items are where cross-channel parity quietly breaks.
| What it counts | COUNT(item variations WHERE sku IS NULL OR sku = '') across the active catalog, at the variation (catalog_object_id) level. Square stores the SKU on the item variation, not the parent item. |
| Why SKU matters | The SKU is the join key. Inventory on-hand counts, Top Products by Revenue, purchase orders, and marketplace listings all key off it. A missing SKU degrades every one of those downstream. |
| VAT / tax treatment | n/a, this is a catalog-health count. |
| Refunds / orders | n/a. A SKU-less variation can still be ordered and sold; the gap is in reporting and reconciliation, not in checkout. |
| Channels / sources | Catalog-wide. The Square Catalog is shared across POS, Square Online, and Invoices, so a missing SKU affects every surface. SKU-less items are most damaging for merchants who sync inventory across channels or to external systems. |
| Currency / unit | number (count of variations with no SKU) |
| Time window | RT (real-time, polled from the Square Catalog API every 5-15 minutes) |
| Alert trigger | > 5, threshold-based |
| Roles | owner, operations |
Calculation
Calculated automatically from your Square Online 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 US homeware merchant on Square: a retail store plus a Square Online storefront, with inventory also pushed to a marketplace. Catalog of 1,420 active variations. Snapshot taken on 12 Apr 26 at 14:00 UTC.| Catalog segment | Variations | Notes |
|---|---|---|
| Active variations | 1,420 | All non-archived item variations |
| Variations with a SKU | 1,388 | Healthy, fully identified |
| Variations missing a SKU (this card) | 32 | Above the > 5 threshold |
| Of those 32: recently added, never finished | 18 | New items where setup was rushed |
| Of those 32: legacy POS quick-items | 11 | Items created at the register on the fly |
| Of those 32: a top-50 seller | 3 | The dangerous slice |
- Three SKU-less variations are top sellers, and those are the urgent ones. A flat count of 32 missing SKUs is a catalog-hygiene task; the three that are top-50 sellers are an active reconciliation problem. Those items are moving real volume that cannot be cleanly tied to inventory counts or pushed reliably to the marketplace. Cross-reference Top Products by Revenue to find them first.
- Register quick-items are the usual culprit. Square POS lets staff create an item on the fly at checkout to ring up something not yet in the catalog. Those quick-items rarely get a SKU, so a POS-heavy account accumulates SKU-less variations over time. This is an operational discipline signal as much as a data one.
- Missing SKUs are where cross-channel parity silently fails. When inventory or listings sync to a marketplace or a 3PL, the SKU is the match key. A SKU-less variation either fails to sync or matches the wrong record, which is how a unified-commerce setup develops POS to Online Inventory Drift and oversells. Fixing SKUs is upstream of fixing parity.
Sibling cards merchants should reference together
| Card | Why pair it with Items Missing SKU |
|---|---|
| Top Products by Revenue | Cross-reference reveals which SKU-less variations are actually selling. A missing SKU on a dead-stock item is hygiene; on a top seller it is urgent. |
| POS to Online Inventory Drift | Missing SKUs are a common root cause of drift, the variation cannot be matched reliably across surfaces or external systems. |
| Total Catalog Items | The denominator. Missing SKUs as a share of the catalog is the cleaner health read than the raw count. |
| Total Item Variations | SKU is set at the variation level, so this is the correct denominator for SKU coverage. |
| Square Inventory vs Marketplace Listings | Marketplace sync keys off SKU. SKU-less variations are the ones that fail to list or mismatch. |
| Online-Only SKUs | A related catalog-parity view; online-only items still need SKUs to be tracked properly. |
Reconciling against Square
Where to look in the Square Dashboard: Square Dashboard, Items, Item library. Add the SKU column to the item list (or export the catalog to CSV) and filter or sort for blank SKU values. Square’s catalog export is the most reliable way to audit SKU coverage at scale, the exported sheet has one row per variation with its SKU, so empty cells are your missing-SKU set. Other Square Dashboard views that look like the same number but aren’t:- Items, Item library, item count: counts parent items, not variations. SKU is a per-variation field, so item-level counts understate the gap.
- Items, item editor, single item: shows one item’s SKU at a time, useful for fixing but not for counting.
- Reports, Item sales: aggregates sales per item and can show a “no SKU” bucket, but only for items that sold in the window, not the full catalog.
| Reason | Direction of divergence |
|---|---|
Variation vs parent count. We count at the variation (catalog_object_id) level. A parent item with three variations, two missing SKUs, counts as 2 here but might read as 1 “item with a SKU issue” in a parent-level view. | Vortex IQ usually higher |
| Archived items. Archived variations are excluded here. A catalog export including archived items will show more blank SKUs. | Vortex IQ lower than a full export |
| Whitespace SKUs. A SKU of a single space or a placeholder string is technically non-empty. We treat blank and whitespace-only as missing; a raw export might not. | Vortex IQ slightly higher |
| Auto-generated SKUs. Some merchants let a tool backfill SKUs; if that ran between snapshots, the count drops. | Self-corrects on next sync |
| Sync lag. The most recent ~5 minutes of catalog edits may not be in our index. | Self-resolves within minutes |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
| Marketplace listings (Square Inventory vs Marketplace Listings) | SKU-less variations are the ones missing from marketplace listings | Marketplaces require a SKU to list and to sync stock. The count of variations that fail to list should overlap heavily with the SKU-less set. Fixing SKUs upstream usually clears both. |
| 3PL / ERP inventory feed | SKU-less variations cannot be matched to the external system | Any external inventory master joins on SKU. Missing SKUs are exactly the records that drop out of an ERP or 3PL reconciliation. |
Known limitations / merchant FAQs
Why does a missing SKU matter if the item still sells? Checkout does not need a SKU, but everything downstream does. Inventory on-hand tracking, per-item reporting, purchase orders, 3PL and ERP reconciliation, and marketplace listings all join on SKU. A SKU-less variation sells fine but becomes a blind spot the moment you try to count it, reorder it, or match it to another system. It is the seed of POS to Online Inventory Drift and failed marketplace syncs. Where do all these SKU-less items come from? Two main sources. First, register quick-items: Square POS lets staff create an item on the fly to ring up something not in the catalog, and those almost never get a SKU. Second, rushed catalog adds: a new product imported or created in a hurry where the SKU field was skipped. POS-heavy merchants tend to accumulate the former; fast-growing catalogs accumulate the latter. The card counts 32 but my item list shows fewer. Why? Most likely a variation-vs-parent difference. Square stores the SKU on each item variation, and this card counts at the variation level. A single parent product with several variations can contribute multiple missing SKUs while appearing as one row in a parent-level item view. Export the catalog to CSV (one row per variation) to see the true count. Does an archived item with no SKU count? No. Archived variations are excluded, the card focuses on the active catalog you are actually selling and syncing. If you want to clean up archived items too, use Square’s full catalog export, which includes them, rather than this card. Can I just auto-generate SKUs to clear the alert? You can, and Square and various tools support bulk SKU backfill, but do it deliberately. An auto-generated SKU clears the count, but if it does not match the SKU your 3PL, ERP, or marketplace already uses for that product, you have created a new mismatch instead of fixing one. For items that exist in an external system, align the SKU to that system’s identifier rather than inventing a fresh one. Why is the threshold set at 5? A handful of SKU-less items is normal churn (a quick-item rung up yesterday, a new product mid-setup). The> 5 trigger is tuned to surface a genuine hygiene problem rather than routine activity. If your operation requires zero tolerance (heavy marketplace or 3PL reliance), tighten the threshold in your Vortex IQ workspace settings.
What’s the action playbook when this card breaches?
Three steps: (1) sort the SKU-less list against Top Products by Revenue and fix the top sellers first, (2) check whether the breach traces to register quick-items, if so the durable fix is staff process plus periodic catalog cleanup, (3) for any variation that exists in an external system, set the SKU to match that system’s identifier so the fix also clears downstream marketplace and inventory mismatches.