Why Digital Product Inventory Matters (Even When Nothing Ships)
When you're running multiple digital products—ebooks, courses, templates, software licenses—it's easy to lose track of what you actually have, what's selling, and what needs updating. Unlike physical inventory, digital products don't run out. But they do become stale, broken, or forgotten.
An inventory system for digital products isn't about stock levels. It's about knowing your complete product catalog, tracking version history, monitoring performance, and catching products that need maintenance before they hurt your reputation.
If you're managing a portfolio like Archieboy Holdings does—30+ properties across publishing, tools, and AI workflows—you need a way to see the whole picture without logging into 30 different dashboards.
What a Digital Product Inventory System Actually Does
A solid inventory system for digital products tracks:
- Product metadata — title, description, category, platform, URL, status (active/archived/draft).
- Version history — what changed, when, and why. Essential for courses and software that update regularly.
- Performance metrics — sales, downloads, revenue, customer feedback, refund rate.
- Dependencies — which products link to or bundle with others; which rely on third-party services.
- Maintenance flags — broken links, outdated content, expired credentials, compliance issues.
- Ownership and responsibility — who created it, who maintains it, who has access.
The goal is simple: one place to see all your digital products, their status, and their health. No more surprises.
The Three Layers of a Digital Product Inventory
Layer 1: The Core Inventory (Spreadsheet or Database)
Start here. This is your source of truth—a single record for every product you offer.
A spreadsheet works for 5–15 products. Use columns like:
- Product Name
- Category (Ebook, Course, Template, Software, etc.)
- Platform (Gumroad, Teachable, your own site, etc.)
- Product URL
- Launch Date
- Current Status (Active, Archived, Beta, Discontinued)
- Last Updated
- Monthly Revenue (approximate)
- Owner / Maintainer
- Notes
For 20+ products or complex dependencies, move to a lightweight database. Airtable, Notion, or a simple SQLite table works better than a spreadsheet because you can link records, filter by status, and generate reports without manual updates.
The key: update this weekly. Make it a 15-minute Friday ritual.
Layer 2: Version and Change Tracking
Digital products change. Courses get new modules. Software gets bug fixes. Ebooks need updated links. Without a change log, you won't remember what changed or when—and you'll repeat mistakes.
For each product, keep a simple changelog:
- Version number or date
- What changed (e.g., "Fixed broken module 3 link", "Updated pricing", "Added new chapter")
- Who made the change
- Why (bug fix, feature request, compliance, etc.)
Store this in a dedicated tab in your inventory sheet or in a document linked from your database. For software, use GitHub releases or a changelog file. For courses, keep a document in your course platform's admin area.
This sounds tedious, but it saves hours when a customer asks, "Has this been updated recently?" or when you need to debug why something broke three months ago.
Layer 3: Performance and Health Dashboard
The inventory tells you what exists. The dashboard tells you how it's performing and what needs attention.
At minimum, track:
- Sales and revenue — monthly earnings by product, trend over time.
- Customer engagement — downloads, course completion rate, software usage (if applicable).
- Refund and complaint rate — flag products with unusually high refunds or negative feedback.
- Technical health — broken links, outdated third-party integrations, expiring licenses or credentials.
- Last maintenance date — if a product hasn't been touched in 12 months, it probably needs a review.
You don't need a fancy BI tool. Google Sheets with IMPORTRANGE formulas, Zapier connecting your sales platform to a database, or a simple Python script pulling from your APIs all work. The point is to automate the data pull so you see trends without manual work.
Building Your Inventory System: Step by Step
Step 1: Audit Your Current Products (Week 1)
List every product you currently sell or maintain. Include beta products, archived products, and anything you might resurrect. Don't overthink it—just get them all in one place.
For each, note:
- Where it lives (which platform, URL)
- Who built it
- When it was last updated
- Approximate monthly revenue
Step 2: Choose Your Tools (Week 1)
For a small portfolio (5–10 products): a Google Sheet is fine. Add a second sheet for version history and a third for monthly metrics.
For a growing portfolio (10–30 products): use Airtable or Notion. Set up a "Products" table, a "Versions" table (linked), and a "Monthly Metrics" table. This lets you filter, search, and generate reports without formula hell.
For a large, complex portfolio: consider a lightweight database (SQLite, PostgreSQL) with a simple web interface. Tools like Archieboy Holdings use internal dashboards to monitor their entire portfolio—you might eventually need something similar.
Step 3: Define Your Metadata Standard (Week 1–2)
Agree on what fields every product must have. This prevents chaos later. Example:
- Product Name (required)
- Category (required, controlled list: Ebook, Course, Template, Software, etc.)
- Status (required, controlled list: Active, Beta, Archived, Discontinued)
- Platform (required)
- URL (required)
- Owner (required)
- Launch Date (required)
- Last Updated (required)
- Monthly Revenue (optional)
- Notes (optional)
Use dropdown menus and validation rules to keep data clean. This matters more than you think—messy data makes dashboards useless.
Step 4: Set Up Automated Metrics (Week 2–3)
Connect your sales platform (Gumroad, Stripe, your own API) to pull revenue and transaction data. Use Zapier, Make, or a simple script to push data into your inventory system daily or weekly.
Start with revenue and download counts. Add engagement metrics (course completion, software logins) once you have the basics working.
Step 5: Create a Maintenance Schedule (Week 3)
Assign someone (or yourself) to review the inventory every Friday for 15 minutes. Check:
- Are all statuses current?
- Have any products not been updated in 12 months? (Flag for review.)
- Any broken links or customer complaints?
- Any products underperforming or ready to archive?
Document your findings in a simple "Inventory Review" log. Over time, this log becomes a goldmine for understanding which products are worth your time.
Common Mistakes to Avoid
Mistake 1: Letting the inventory get stale. If your inventory is out of date, it's worse than useless—it's misleading. Set a calendar reminder to review it weekly. Make it a team ritual, not a chore.
Mistake 2: Tracking too much data. You don't need 50 columns. Start with 10–15 essential fields. Add more only if you actually use them. Complexity kills adoption.
Mistake 3: Not linking inventory to actual sales data. An inventory that shows "Monthly Revenue: $500" but doesn't connect to your actual Stripe or Gumroad account is just a guess. Automate the data pull.
Mistake 4: Ignoring archived products. Keep them in your system with a clear "Archived" status. You might want to resurrect them, and you'll want to know why you killed them in the first place.
Mistake 5: Treating inventory as a one-time project. It's not. It's an ongoing system. Build it to be lightweight and easy to maintain, or it will rot.
A Real-World Example: Multi-Site Publisher
Imagine you run 5 author-focused websites, each with 3–4 digital products (courses, templates, ebooks). That's 15–20 products across different platforms.
Without an inventory system, you're logging into each site separately to check sales, update content, and catch broken links. With a system, you see everything in one dashboard:
- "Advanced SEO for Authors" course (Teachable) — last updated 3 months ago, $2,400/month, 87% completion rate. ✓ Healthy.
- "Book Launch Checklist" template (Gumroad) — last updated 18 months ago, $150/month, no recent sales. ⚠️ Needs review.
- "AI Writing Tools Guide" ebook (your site) — last updated 2 weeks ago, $800/month, link to OpenAI docs broken. ⚠️ Fix link this week.
You spot issues before customers complain. You know which products are worth promoting and which are dragging down your time. You can make decisions based on data, not guesses.
Tools That Help (But Aren't Required)
- Airtable — best for small-to-medium portfolios. Flexible, visual, integrations with Zapier.
- Notion — good for teams. Slower than Airtable but easier to customize and share.
- Google Sheets + Apps Script — free, powerful if you know basic scripting. Good for pulling data from APIs.
- Zapier or Make — connect your sales platform to your inventory system without coding.
- Metabase or Superset — if you need advanced dashboards and have technical resources.
Start Small, Scale Smart
You don't need a perfect system on day one. Start with a spreadsheet. List your products. Track revenue. Review it weekly. Once you've done that for a month, you'll know what else you need.
Many publishers start with a simple sheet, then graduate to Airtable when they hit 15–20 products. If you're managing a large portfolio with complex dependencies, you might eventually need something custom—but most teams can get 80% of the value from a well-maintained Airtable base or Notion workspace.
The key is consistency. A mediocre system you actually use beats a perfect system you abandon after two weeks.
If you're already tracking multiple products across platforms, a digital product inventory system will likely save you 5–10 hours a month in manual checking and reduce customer-facing issues. That's worth the setup time.