Shopify Software Licence Product Import: Keys and Variants

A software developer imports their product catalogue to a new Shopify store: a security suite with three licence tiers (1 PC, 3 PC, Family), three platforms (Windows, Mac, iOS), and two term options (1 year, lifetime). The import completes. One product appears in Shopify admin. It has one variant. All the licence configuration data (tiers, platforms, terms) is in the description as a paragraph. When the first customer purchases, the fulfilment app tries to deliver a licence key but cannot determine which key pool to draw from, because the variant SKU says "auto-2847" rather than anything that identifies the licence configuration.

A shopify software licence product import differs from a standard digital or physical product import in three specific ways. The variant structure is three-dimensional and functional, not just descriptive. The SKU convention is operational, not cosmetic. And the product description has no physical attributes to draw from (no materials, dimensions, or colours), so AI generation must work from pure benefit and outcome language.

Why Software Licence Variants Are Structurally Different#

Physical products use variants to describe appearance and size: Colour, Size, Material. These are descriptive dimensions that let customers select what they want before purchase. Software licence variants are functional dimensions that determine what the customer can actually do with the product after purchase: how many devices they can install on, which operating system is supported, and how long the licence lasts.

This distinction matters for the import file because Shopify's variant options appear to customers as selectors on the product page. A clothing product with "Colour: Blue, Size: M" shows a colour swatch and a size selector. A software product with "Platform: Windows, Devices: 3 PC, Term: 1 Year" shows three dropdowns. Each combination routes to a different SKU, a different key pool, and potentially a different price.

Most software developers manage their products in a CRM, billing platform, or spreadsheet that does not use Shopify's row-based variant structure. Their export might have one row per product (not one row per variant combination), or might use columns like "Platforms Supported: Windows, Mac, iOS" rather than separate option rows. Importing this directly produces a single-variant product that loses all the licence dimension data.

The import file for a software licence product requires one row per variant combination. A security suite with 3 tiers, 3 platforms, and 2 terms produces 18 rows (3 × 3 × 2), all sharing the same product Handle, each with a distinct set of option values and a distinct SKU that encodes the configuration.

The SKU Convention That Makes Automated Delivery Work#

The SKU on each software licence variant is not an arbitrary identifier. It is the routing key that licence delivery apps use to match a purchased variant to the correct activation key pool.

When a developer sets up their licence delivery integration, they configure a mapping between variant SKUs and key pools: "all variants with SKU containing 3PC-WIN" draw from the Windows 3-device key pool. When an order arrives, the app reads the purchased variant's SKU, matches it against the mapping, draws the next unused key from the correct pool, and delivers it to the customer by email.

A variant SKU that does not encode the licence configuration breaks this routing. Auto-generated SKUs ("SKU-001", "SKU-002") have no semantic meaning the delivery app can parse. Human-readable descriptive SKUs with no consistent structure ("Windows_3pc_1yr", "WIN-3-YEAR") require manual mapping configuration for every product variant. This is manageable for 5 products and unmanageable for 50.

The import file should use a consistent SKU format that encodes the licence configuration as a hyphen-separated compound identifier: PRODUCT-TIER-PLATFORM-TERM. For a security suite (abbreviated AVSUITE): AVSUITE-1PC-WIN-1YR, AVSUITE-3PC-WIN-1YR, AVSUITE-FAM-WIN-1YR, AVSUITE-1PC-MAC-1YR, and so on across all 18 combinations. Importier carries these SKUs through the import exactly as written. They appear on every variant after the import completes.

How Importier Handles the Three-Way Variant Matrix#

Importier's Smart Variant Detection reads the option columns and groups product rows by Handle, building the variant matrix automatically. For a software licence import file with Option1 Name (Platform), Option2 Name (Devices), and Option3 Name (Term), Smart Variant Detection identifies the 18-row group under each product Handle and constructs the 3×3×2 variant matrix before committing to Shopify.

The Import Review step shows the full matrix (every variant combination with its SKU and price) before anything is written to Shopify admin. This is where structural errors in software licence import files surface before they become live problems:

• Missing combinations: if the developer forgot to include Windows/Family/Lifetime in the spreadsheet, the 3×3×2 matrix appears as a 3×3×1 in the review, missing an entire term tier.
• Duplicate SKUs: if the same AVSUITE-3PC-WIN-1YR SKU appears on two different rows, the review flags it. Duplicate SKUs in the live product create the same routing conflict in the delivery app.
• Option value inconsistency: "1 PC" on one row and "1PC" on another creates two separate Devices options in Shopify instead of one. The review matrix makes this visible.

1. 01
   Build the import spreadsheet with one row per variant combination. Every row for the same product shares a Handle. Columns

   Handle, Title, Option1 Name (Platform), Option1 Value (Windows / Mac / iOS), Option2 Name (Devices), Option2 Value (1 PC / 3 PC / Family), Option3 Name (Term), Option3 Value (1 Year / Lifetime), Variant SKU, Variant Price, Body (HTML).
2. 02
   Apply a consistent SKU convention across every row

   PRODUCT-TIER-PLATFORM-TERM. For a security suite: AVSUITE-1PC-WIN-1YR, AVSUITE-3PC-MAC-LIFE, AVSUITE-FAM-IOS-1YR. The SKU must encode enough information for the delivery app to route correctly without any additional lookup.
3. 03
   Upload to Importier. In the column mapping step, map your Platform, Devices, and Term columns to Option1, Option2, and Option3 respectively. If your spreadsheet uses different names (Licence Tier, Operating System, Duration) the mapping step translates them; Shopify stores the value you map to Option1 Name as the visible option label.
4. 04
   Check the Import Review matrix

   verify all 18 combinations appear (or your expected count), confirm SKUs are unique across all rows, confirm prices are correct per combination. For software with tiered pricing (Family licence costs more than 1 PC, Lifetime costs more than 1 Year), verify the price on each row reflects the correct tier.
5. 05
   Generate AI descriptions

   enter the software's core benefits (what problem it solves, which threat categories it blocks, what the lifetime licence means for ongoing cost), the target customer (home user vs small business), and any key performance claims (scan speed, false positive rate) as enrichment context. Importier generates from this context, not from physical attributes that do not exist.
6. 06
   After the products are live, configure the licence delivery app to map your SKU pattern to the correct key pools. A consistent PRODUCT-TIER-PLATFORM-TERM format makes this a one-time configuration per product family rather than per-variant manual assignment.

Writing Software Product Descriptions Without Physical Attributes#

Most AI description tools are optimised for physical products. They look for colour, material, dimensions, weight, and care instructions. A software product has none of these. A prompt for "Antivirus software for Windows, 3 PC licence, 1 year" with no additional context produces a generic output that restates the option values: "This 1-year antivirus licence covers up to 3 Windows PCs."

Importier's AI engine generates from enrichment context, not just from the product options. For a software licence import, the merchant enters what the software actually does: specific threat categories blocked (ransomware, phishing, zero-day exploits), measurable performance claims (99.9% detection rate in AV-TEST, 0.2 second scan time), target customer (home user, family, small office), and what the purchase decision comes down to for most buyers.

The Benefits-First description style generates copy that leads with outcomes: what the customer can do that they could not do before, what they no longer need to worry about, what they get that a free alternative cannot provide. For software, this converts better than a feature list because the buyer cannot hold or see the product. They are buying confidence, and the description has to create it.

“A software description that opens with "protects your family's devices from ransomware, phishing, and privacy leaks without slowing them down" communicates value. A description that opens with "3-device Windows antivirus licence" communicates a spreadsheet cell.

For enterprise or SMB software where the buyer is a procurement officer or IT manager, Importier's Technical Specification style shifts to a more formal format: compliance certifications, deployment model (cloud vs on-premise), admin console features, integration support (Active Directory, MDM platforms), and SLA terms. The same product can carry both description styles: consumer storefront and B2B catalogue.

According to Shopify's guide to selling digital products, software and licence products on Shopify require a digital fulfilment method configured separately from the product listing itself. The import establishes the product structure and variant data; the delivery configuration (key pools, download links, email templates) is set up in the fulfilment app after the products are live. Getting the variant SKU structure right at import time is what connects these two systems.

Platform Compatibility as Structured Metafields#

Beyond the three variant dimensions (platform, devices, term), software products often carry additional structured data that belongs in metafields rather than in variant options: minimum OS version requirements, processor architecture (ARM vs x86-64 for Mac silicon compatibility), file download size, and compatibility flags (compatible with latest OS version: yes/no).

Importier's Computer Software category from Shopify's Standard Product Taxonomy activates the relevant metafields for software products: platform compatibility, licence type (perpetual, subscription, trial), and file format. These metafields feed structured data to Google Shopping and AI shopping agents. A query for "lifetime antivirus licence compatible with Mac M1" can match a product that has the platform and licence type metafields populated, and will not match a product whose only platform reference is in the description text.

The shopify-digital-products-import article covers the broader category of digital products including e-books, fonts, and downloadable files. Software licences specifically benefit from the Computer Software taxonomy category and the three-way variant structure, which general digital products typically do not need.

According to Shopify's product variants documentation, each Shopify product supports up to three option types with up to 100 variant combinations. A software product with 4 platforms, 4 licence tiers, and 4 term options would produce 64 combinations, within the 100-variant limit but only just. A fifth platform or tier pushes to 80 or 100. Planning the option dimensions at import time avoids discovering this ceiling after the products are live, which would require a product restructure (combining options or splitting into multiple products) rather than a simple edit.

Key Takeaways for a Shopify Software Licence Product Import#

Software licence products require specific import decisions that general product imports do not. Getting them right at import time prevents manual rework in both the Shopify admin and the licence delivery integration.

• One row per variant combination: a software product with 3 platforms, 3 licence tiers, and 2 terms needs 18 rows under the same Handle. Each row carries one combination with its own SKU and price. Do not consolidate options into a single-variant product.
• SKU convention is operational, not cosmetic: the variant SKU is what the delivery app uses to route keys. Use a consistent compound format (PRODUCT-TIER-PLATFORM-TERM) that encodes enough information to route without a separate lookup table. Set this before the import and carry it through.
• Enrichment context drives software descriptions: software products have no physical attributes. Enter the specific threats blocked, performance claims, target customer profile, and what distinguishes the product from free alternatives as enrichment context. The Benefits-First style generates from this context.
• Computer Software taxonomy metafields populate structured data: activating the category in the import brings in platform compatibility, licence type, and file format as metafields that Google Shopping and AI shopping agents can read. Description text cannot substitute for these.
• Check the variant matrix in Import Review before committing: missing combinations, duplicate SKUs, and option value inconsistencies are visible in the review matrix. Fixing them in the source file takes two minutes; fixing them in live Shopify products takes significantly longer.

Import your software licence catalogue with the correct variant structure and delivery-ready SKUs at importier.app.