Why SMBs Need a Better Product Catalog Solution
Managing a product catalog might seem simple when you have 20 items. But the moment your inventory grows to 200, 2,000, or 20,000 SKUs, spreadsheets start falling apart. Version conflicts, missing images, inconsistent descriptions, and pricing errors become daily headaches.
Traditional Product Information Management (PIM) systems solve these problems—but they come with enterprise price tags. Solutions like Akeneo, Salsify, or inRiver can cost anywhere from $30,000 to $150,000+ per year. For a small or medium-sized business, that’s simply not realistic.
This is where Airtable enters the picture. As a no-code relational database with a spreadsheet-like interface, it sits in a sweet spot between basic spreadsheets and full-blown PIM software. It’s powerful enough to handle complex product relationships, yet intuitive enough that your team can start using it within hours.
In this guide, we’ll walk through exactly how to set up, structure, and optimize an Airtable-based product catalog system for your business.
Understanding Airtable’s Strengths for Catalog Management
Relational Data Without the Database Expertise
Unlike Google Sheets or Excel, Airtable is a true relational database. This means you can link products to categories, categories to departments, suppliers to products, and images to variants—all without writing a single line of SQL.
For product catalogs, this is transformative. Consider a typical scenario:
- A single product has 5 color variants
- Each variant has 3 size options
- Each combination needs its own SKU, price, stock level, and image
In a spreadsheet, this creates a nightmare of duplicated rows. In Airtable, you create separate linked tables and let the relationships do the heavy lifting.
Visual and Collaborative by Design
Airtable offers multiple views of the same data:
- Grid view for bulk editing (like a spreadsheet)
- Gallery view for visual product browsing
- Kanban view for tracking product status (draft → review → published)
- Form view for collecting product submissions from suppliers
- Calendar view for launch date planning
Your marketing team sees the gallery view with images and descriptions. Your operations team sees the grid view with pricing and inventory. Same data, different perspectives.
Designing Your Product Catalog Base Architecture
Core Tables You Need
A well-structured product catalog base typically requires between 4 and 8 tables. Here’s the architecture we recommend after helping dozens of e-commerce businesses at Lueur Externe:
| Table | Purpose | Key Fields |
|---|---|---|
| Products | Master product records | Name, Description, Brand, Status, Launch Date |
| Variants | SKU-level details | SKU, Color, Size, Price, Weight, Barcode |
| Categories | Product taxonomy | Category Name, Parent Category, Slug |
| Images | Media assets | Image file, Alt text, Sort order, Variant link |
| Suppliers | Vendor information | Company, Contact, Lead time, MOQ |
| Price Lists | Channel-specific pricing | Variant link, Channel, Price, Currency |
Setting Up the Products Table
Your Products table is the hub of your catalog. Here’s a recommended field structure:
Products Table Fields:
├── Product Name (Single line text)
├── Internal Reference (Auto-number or Formula)
├── Short Description (Long text - Rich text enabled)
├── Full Description (Long text - Rich text enabled)
├── Brand (Linked record → Brands table)
├── Category (Linked record → Categories table)
├── Variants (Linked record → Variants table)
├── Tags (Multiple select)
├── Status (Single select: Draft / In Review / Active / Discontinued)
├── SEO Title (Single line text - Formula with character count)
├── SEO Description (Long text)
├── Created Date (Created time)
├── Last Modified (Last modified time)
└── Completeness Score (Formula - see below)
The Completeness Score Formula
One of the most valuable fields you can add is a completeness score. This formula checks whether key fields are filled in and returns a percentage:
IF(
AND(
{Product Name} != "",
{Short Description} != "",
{Full Description} != "",
{Category},
{Variants},
{SEO Title} != ""
),
"100%",
CONCATENATE(
ROUND(
(IF({Product Name} != "", 1, 0) +
IF({Short Description} != "", 1, 0) +
IF({Full Description} != "", 1, 0) +
IF({Category}, 1, 0) +
IF({Variants}, 1, 0) +
IF({SEO Title} != "", 1, 0)) / 6 * 100,
0),
"%"
)
)
This gives your team instant visibility into catalog quality—a feature that many expensive PIM systems highlight as a premium capability.
Building Product Relationships and Variants
The Parent-Variant Model
Most e-commerce platforms use a parent-variant (or configurable product) model. In Airtable, this translates to:
- Products table = Parent products (e.g., “Classic Cotton T-Shirt”)
- Variants table = Individual purchasable items (e.g., “Classic Cotton T-Shirt - Blue - Large”)
Each variant record links back to its parent product and contains:
- Unique SKU
- Specific attributes (color, size, material)
- Individual pricing
- Stock quantity
- Weight and dimensions (for shipping)
- Barcode / EAN / UPC
Handling Multi-Level Categories
Product taxonomy is critical for both navigation and SEO. Airtable handles hierarchical categories through self-referencing linked records:
- Create a Categories table
- Add a linked record field called “Parent Category” that links to… the same Categories table
- Add a lookup field to pull the parent category name for easy reference
Example hierarchy:
Clothing (Level 1)
├── Men's Clothing (Level 2)
│ ├── T-Shirts (Level 3)
│ ├── Shirts (Level 3)
│ └── Jackets (Level 3)
└── Women's Clothing (Level 2)
├── Dresses (Level 3)
├── Tops (Level 3)
└── Accessories (Level 3)
Automating Your Catalog Workflows
Built-in Airtable Automations
Airtable’s automation engine is surprisingly capable for a no-code tool. Here are catalog-specific automations worth setting up:
- New product notification: When a product’s status changes to “Active,” automatically notify your marketing team via Slack or email
- Low completeness alert: When a product is moved to “In Review” but has a completeness score below 80%, send it back to “Draft” with an automated comment
- Supplier follow-up: When a product has been in “Awaiting Supplier Data” status for more than 7 days, trigger a reminder email
- Image validation: When images are attached, check that alt text has been filled in
Integration with E-commerce Platforms
For SMBs running PrestaShop, WooCommerce, or Shopify, you’ll want to sync your Airtable catalog with your storefront. The most common approaches:
- Make (Integromat) – Visual automation platform with native Airtable and e-commerce connectors
- Zapier – Simpler automations for basic sync tasks
- Custom API scripts – Using Airtable’s REST API for complex bidirectional sync
- Airtable Sync – For pushing data to other Airtable bases used by partners or teams
A typical sync workflow looks like this:
- Product completed in Airtable (status = “Ready to Publish”)
- Automation triggers via Make
- Product data mapped to e-commerce platform fields
- Product created/updated on storefront
- Storefront ID written back to Airtable for future reference
At Lueur Externe, we’ve implemented this type of architecture for clients running PrestaShop stores, allowing their merchandising teams to manage all product information in Airtable while automatically pushing validated data to their live stores.
Real-World Example: A 3,000-SKU Fashion Brand
Let’s look at a concrete case study. A fashion brand with 3,000 active SKUs was managing their catalog across:
- 14 different Excel files
- A shared Google Drive with 12,000+ unorganized product images
- Email threads with suppliers for spec sheets
- Manual copy-paste into their PrestaShop back-office
The result? An average of 4.5 hours to onboard a single new product, frequent pricing errors, and SEO descriptions that were often missing entirely.
After migrating to an Airtable-based system:
- Product onboarding time dropped to 45 minutes (83% reduction)
- Pricing errors fell by 94% thanks to validation rules and lookup formulas
- SEO coverage reached 100% with mandatory field checks before publishing
- Image management became centralized with proper alt texts and variant associations
The entire migration took approximately 3 weeks, including data cleaning, base setup, team training, and automation configuration.
Pricing: What Does Airtable Cost for Catalog Management?
Here’s a realistic cost breakdown for an SMB scenario:
| Plan | Monthly Cost (per seat) | Records per Base | Best For |
|---|---|---|---|
| Free | $0 | 1,200 | Testing / Very small catalogs |
| Team | $20 | 50,000 | Most SMBs (up to ~10K SKUs) |
| Business | $45 | 125,000 | Growing brands with complex needs |
| Enterprise | Custom | 500,000 | Large operations |
For a team of 5 people managing a catalog of 5,000 SKUs, you’re looking at approximately $100/month on the Team plan. Compare that to dedicated PIM solutions starting at $500-$2,500/month, and the value proposition becomes clear.
Limitations to Be Aware Of
Airtable isn’t perfect for every scenario. Be aware of these constraints:
- Attachment storage limits: 20GB on Team plan, which can fill up quickly with high-resolution product images. Consider linking to external storage (Cloudinary, S3) instead.
- Record limits: If you have more than 50,000 SKU-level records, you’ll need the Business plan or consider splitting your base.
- No native version history for records: While you can see field-level history, there’s no “rollback” feature for entire product records.
- API rate limits: 5 requests per second per base. For large sync operations, you’ll need to implement queuing logic.
- Formula field complexity: Very complex formulas can slow down base performance with large datasets.
Best Practices for Long-Term Success
Data Quality Standards
- Define naming conventions early (e.g., “Blue” vs “Navy Blue” vs “blue”)
- Use single-select or linked records instead of free text wherever possible
- Implement the completeness score formula from the start
- Schedule monthly data audits
Team Adoption
- Create views tailored to each team’s workflow
- Lock down field configurations to prevent accidental changes
- Build a simple interface (Airtable Interface Designer) for non-technical users
- Document your base structure in a dedicated “README” table
Scaling Strategy
- Start with a simple structure and add complexity as needed
- Separate “reference data” (categories, brands, attributes) from “transactional data” (products, variants)
- Use Airtable Sync to share catalog data across departments without giving everyone edit access to the master base
- Plan your integration architecture before you need it
Comparing Airtable to Other No-Code Catalog Options
| Feature | Airtable | Notion | Google Sheets | Monday.com |
|---|---|---|---|---|
| Relational data | ✅ Native | ✅ Basic | ❌ Manual | ⚠️ Limited |
| Gallery view | ✅ | ✅ | ❌ | ⚠️ |
| API access | ✅ Robust | ✅ | ✅ | ✅ |
| Automations | ✅ Built-in | ❌ | ❌ | ✅ |
| Record capacity | 500K | Unlimited | ~5M cells | 500K |
| Image handling | ✅ Attachments | ✅ | ❌ Poor | ⚠️ Basic |
| E-commerce integrations | ✅ Extensive | ⚠️ Limited | ⚠️ Limited | ⚠️ Limited |
| Price (5 users) | $100/mo | $50/mo | Free | $72/mo |
For product catalog management specifically, Airtable remains the strongest no-code option thanks to its relational capabilities, visual views, and deep integration ecosystem.
Conclusion: Start Simple, Scale Smart
Airtable provides SMBs with a genuinely powerful no-code platform for product catalog management. It bridges the gap between chaotic spreadsheets and expensive enterprise PIM systems, offering relational data structure, visual collaboration, built-in automations, and extensive integrations—all at a fraction of the cost.
The key to success is thoughtful architecture from the start. Define your tables, relationships, and naming conventions before you import a single product. Use automations to enforce data quality. Build views that match how each team actually works.
If you’re ready to transform your product catalog management but want expert guidance on architecture, e-commerce integration, or no-code automation strategy, the team at Lueur Externe can help. With over 20 years of experience in web development, e-commerce (including certified PrestaShop expertise), and modern no-code solutions, we help SMBs build systems that scale.
Get in touch with Lueur Externe to discuss your product catalog project and discover how no-code tools can accelerate your e-commerce operations.