How to sell software license keys on BigCommerce — the right way
Software licenses are close to a perfect ecommerce product: no warehouse, no shipping, no returns pallet. And yet stores get license delivery wrong constantly — keys sent hours later by a human, spreadsheets that run dry mid-promotion, or worse, the same key sold twice. This guide walks through doing it properly on BigCommerce.
Step 1: Set up licenses as digital products
In BigCommerce, a software license is a digital product: no shipping requirement, no inventory location, delivered electronically. Create each license SKU the way you would any product — name, price, imagery, category — but pay attention to two fields that will matter later:
- SKU naming. Your SKU is how any fulfillment automation decides which vendor and which product a key must come from. Pick a convention (vendor prefix, product family, seat count) and hold to it.
- Variants for seats and terms. A "5-device / 1-year" license and a "10-device / 2-year" license are different vendor SKUs. Model them as variants with distinct SKUs, not as free-text options.
Step 2: Choose your delivery model — this is the decision that matters
There are three ways stores deliver license keys, in ascending order of maturity:
- Manual fulfillment. A human sees the order, logs into a vendor portal, provisions or copies a key, and emails it. Fine for your first ten orders. It does not survive weekends, promotions, or employee vacations.
- Key-list apps. You pre-purchase keys in bulk, upload them as a list, and an app hands one out per order. Better — delivery is instant — but you've traded fulfillment labor for inventory risk: capital tied up in keys, lists that run out silently, and a database of plaintext keys waiting to leak. We compare the models in depth in key lists vs. on-demand provisioning.
- On-demand provisioning. The order webhook triggers a live API call to the vendor or distributor, which mints a key for exactly what was bought. Nothing pre-purchased, nothing to run out of, nothing sitting in plaintext. This is how KeyVolt works.
Step 3: Wire delivery into the customer experience
Where the key shows up matters as much as how fast. Email alone is fragile — spam filters eat keys, and business buyers forward them around until nobody knows which key belongs to whom. Aim for:
- Email plus account. Deliver in the order confirmation and in the customer's store account.
- The B2B buyer portal, if you sell to businesses. BigCommerce B2B Edition gives each client company a portal with order history — license keys belong right there, next to the orders that bought them. More on this in selling digital products with B2B Edition.
Step 4: Plan for the unhappy paths
License fulfillment fails in ways physical fulfillment doesn't, and your process needs answers for each:
- Vendor API is down. Does the order retry automatically, or does it silently vanish? Insist on retries plus an alert when retries are exhausted.
- Refunds. Digital goods can't be "returned" — decide your policy up front and state it on the product page.
- Wrong SKU mapping. The most common real-world failure: an order routes to the wrong vendor product. Test every SKU mapping before launch, and again whenever the catalog changes.
Launch checklist
- Every license SKU follows your naming convention and maps to a vendor product
- Delivery is automated end-to-end (place a real test order and time it)
- Keys appear in the customer account, not just email
- Failed provisioning alerts a human and can be replayed
- Refund policy is written and visible
- You are authorized to resell every product in the catalog
Selling software on BigCommerce is a genuinely good business — high margin, no logistics, global by default. The stores that win treat license delivery as a product feature, not an afterthought. And if your catalog needs more than an app can offer — ERP-driven pricing, custom checkout logic, a storefront built around your operation — that's BigCommerce development work worth doing once and properly.