"The spreadsheet said 40 units left, but that was every color combined."
One shared quantity meant nobody could tell which specific size and color was actually about to sell out.
BoldBellowsReal linked records, not compressed text
Give every Ecwid variant its own Airtable record
A basic connector usually flattens size, color and stock into a single row, or worse, one quantity shared across every combination a product has. We model each product, option and combination as its own linked record, keyed to Ecwid's own IDs, so a stock count always points at the exact variant it describes.
View Pricing
From $400, paid once.
No monthly connector fee.
- Every combination is its own addressable record
- An orphaned link surfaces, never a silent gap
- Variation Matrix Draft is usually testable within a week
What an Ecwid combination clears before it becomes an Airtable record
- Product and combination read as separate entitiesnever flattened into one row
- Every record keyed to Ecwid product and combination IDsnever a mutable option label
- A missing parent or option link is surfacednever left as a silent orphan
- Stock stays tied to the variant it describesnever collapsed into one parent count
- A fixed build fee, quoted before work startsnothing billed monthly for the matrix itself
01The one-cell-for-everything trap
A dozen variants don't fit in a single field
A basic connector usually writes one Airtable row per Ecwid product and jams every size, color and stock count into a delimited text field or a single shared quantity. That works until someone actually needs to know which specific combination is running low.
"Two combinations had the same option text in different languages, and Airtable treated them as one."
Nothing anchored a record to Ecwid's actual combination ID, so a text match quietly merged two separate variants.
"A product got restructured, and half its combinations just vanished from the base."
Nothing detected the broken parent link, so a real product change looked like data quietly disappearing.
A catalog base is only useful if a single row answers a single question. Once ten variants share one cell, every question needs someone to manually decode it first.
Same products, same combinations. The difference is whether Airtable shows every variant as its own row, or a dozen variants crammed into one.
Before
- A single field hides which combination is low
- Matching text can merge two real variants
- A broken parent link looks like missing data
After
- Every combination is its own linked record
- A shared text label never merges two variants
- A broken link surfaces, never hides silently
02How it works
How a combination earns its place as a linked record
The event is qualified against the current catalog state first, its business meaning is translated into normalized fields second, and only a confirmed, evidence-backed write commits third.
Details behind why every combination gets its own record
- A webhook payload is a pointer, not the record itself. Ecwid keeps the notification compact on purpose, so the matrix always fetches the current product or combination before deciding what belongs in Airtable.
- Nothing about a webhook tells you who made the change. A merchant editing options by hand and a bulk import through the REST API trigger the identical notification, so the matrix never assumes a low-volume origin and skips validating it.
- Airtable's linked-record fields hold a genuine relationship, not a formatted string. That's what lets a parent product and its combinations stay separately addressable instead of every variant getting flattened into one delimited cell.
03Inside the matrix build
How the matrix grows from Draft to Governed
The product-combination split and schema-safe upsert ship with Variation Matrix Draft. Option normalization and a catalog change trail join at Variation Matrix Linked. Stock-location links and scheduled reconciliation complete the model at Variation Matrix Governed.
Variation Matrix DraftVariation Matrix LinkedVariation Matrix Governed
Product-combination model Variation Matrix Draft
Creates separate linked records for a parent and each sellable variant.
Schema-safe upsert Variation Matrix Draft
Updates by Ecwid IDs rather than a mutable option name.
Option normalization Variation Matrix Linked
Stores size, color and custom selections without column sprawl.
Catalog change trail Variation Matrix Linked
Records option additions, removals and SKU changes over time.
Stock-location link Variation Matrix Governed
Relates quantities to their applicable fulfillment location.
Orphan detector Variation Matrix Draft
Surfaces a combination whose parent or option link is missing.
Scheduled reconciliation Variation Matrix Governed
Sweeps for a combination the live feed missed the first time.
Thirty-day launch review Variation Matrix Governed
We stay attached through the first month of real catalog changes before calling the base finished.
04Who it's for
Built for catalogs where a variant deserves its own row
Catalog managers maintaining variants, buyers reviewing replenishment needs, operations analysts joining orders to SKUs, and product leads who need a real audit trail when an option changes.
Catalog manager maintaining variants
Needs proof that every size and color is its own addressable record, not a guess from a shared field.
Buyer reviewing replenishment needs
Wants a stock number tied to the exact combination running low, not a total that hides the detail.
Operations analyst joining orders to SKUs
Wants stable IDs to join against, not a label that can drift between two languages or storefronts.
Product lead auditing option changes
Needs a change trail for who added or removed an option, and when it happened.
05Compare
Where a one-row-per-product export actually breaks down
Exporting an Ecwid product to a single Airtable row takes minutes. Keeping every size and color individually addressable, and catching a broken parent link before it looks like missing data, is where that shortcut runs out of road.
| What actually decides the outcome | Manual spreadsheet export | A basic connector | BoldBellows build |
|---|---|---|---|
| How a variant is stored | One column per option, typed by hand | A delimited string inside one field | YesIts own linked record, tied to its parent |
| How it's matched | A product name, checked manually | Whatever text field the connector happens to see | YesEcwid product and combination IDs |
| A shared stock count | Split up manually, if anyone notices | Left as one number across every variant | YesTied to the exact combination it describes |
| A broken parent link | Looks like the row is simply gone | Silently drops the orphaned record | YesSurfaced as a named exception to review |
The duplicate-language trap
Two combinations display the same option text in different storefront languages. The matrix re-reads Ecwid's own combination ID rather than trusting the visible label, so the two stay distinct records.
The stock-model switch trap
A parent product switches from unlimited stock to tracked combination stock. The matrix keys off Ecwid's own IDs rather than the stock model in effect at the time, so the switch updates existing records cleanly instead of corrupting them.
PricingClear, one-off packages
Turn every variant into its own record
Variation Matrix Draft, Linked and Governed differ mainly in how much of the option and stock-location model gets built as real linked records. Select a package below to see the exact price and timeline for your catalog. Variation Matrix Draft opens at $400.
View Pricing
Pricing
Build your Ecwid to Airtable price
Pick a package, answer three short questions about trigger scope, identity and failure policy, and your price and turnaround move as you choose.
06The process
Proving the matrix links cleanly before you launch
Variation Matrix Draft covers one Ecwid store and one Airtable base, and the product-combination split is normally in testable shape within the first week. Variation Matrix Linked needs extra rounds to prove option normalization holds up against a catalog that's already messy. Variation Matrix Governed takes the longest, since we deliberately restructure a product mid-test to confirm the orphan detector actually catches the broken link — that single scenario is usually what pushes the build toward thirteen days. If a seasonal catalog refresh is coming up, tell us the date and we'll sequence the build around it.
Map your real catalog structure
We look at how your products, options and combinations actually relate to each other in Ecwid today.
Design the table schema
You approve the linked-table structure, the field names, and exactly how an orphan should be handled.
Build the matrix
The qualification logic, the linking rules and the orphan-detection path all get assembled around your real Airtable base.
Deliberately stress the schema
We feed it a restructured product, a duplicate option label and a stock-model switch to see where a weaker design would have quietly broken.
Walk the base with your team before we step back
A real product moves through the full matrix while your catalog manager watches, then we hand over the runbook.
Three things to have ready
- Someone on your team who can grant Ecwid app access at the store-owner level.
- Airtable administrator access to the base this should write to.
- A few real products with multiple combinations already active.
07Security and ownership
A table-by-table grant, not a key to the whole catalog.
Each table this build writes to carries its own narrow Ecwid permission, agreed before the first record is created. Orders, customers, discounts and storefront settings sit entirely outside what the matrix can see or touch.
Authorization is scoped per table, not per store
Writing to the combinations table never implies a grant that could touch orders, customers or pricing anywhere else.
Named fields only, agreed on before launch
Every field allowed into a linked record is listed up front; anything Ecwid sends outside that list gets discarded, not stored.
Credentials never appear inside a viewable base
The keys that authorize a write live in a separate secured store — no table, record or log ever displays them.
A resend corrects the row it belongs to
Linking runs off the product and combination IDs together, so a repeated delivery updates that exact record instead of appending a duplicate.
Troubleshooting logs stop at IDs and outcomes
A support log shows which combination moved and why, never a copy of pricing or anything a customer entered.
The finished base is yours outright
Every table, field mapping and linking rule stays in your Airtable workspace — nothing about this build is licensed back to us.
08In their words
What BoldBellows clients say
Verified reviews from teams who use BoldBellows automations every day, from ecommerce catalog management to operations and fulfillment.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
09FAQ
What catalog managers ask before the matrix ships
Still unsure? We reply in plain English.
We already have Zapier writing Ecwid orders into Airtable. What does this actually add?
A single trigger step can copy a field when a product changes, but it can't split a product's combinations into their own linked records, and it has no way to detect when a parent link goes missing after a restructure. Building that structure in is the entire point of this service.
Could this accidentally overwrite something we already have set up in Airtable?
No. The build writes only inside the tables named in your data contract, using the field list you approved. An existing table, view or automation outside that scope is never touched.
We've been selling through Ecwid for a while already. Can our existing catalog be brought into the matrix too?
Yes. A one-time historical import walks your current catalog and creates the same linked structure the live sync would have built, then hands off to live events from that point forward.
Is our Airtable seat cost part of the quote?
It isn't. The number on this page is a single build fee. Whatever plan you already pay Airtable and Ecwid for keeps running unchanged, billed the same way it always has been.
What if Ecwid restructures how combinations work, or Airtable changes its linked-field behavior?
Every endpoint and field this build depends on is written down in your handoff. If either platform changes one, reconciliation surfaces a named, visible failure — the matrix never keeps writing against a definition that's gone stale.
How does this actually stop a combination from getting a duplicate record?
Every write claims the pairing of Ecwid's product ID and combination ID before it touches anything. A repeated delivery finds that same pairing and updates the existing linked record instead of creating a second one. It is also the answer to ecwid to airtable, sync ecwid orders to airtable and ecwid airtable integration.
Next stepStop crushing variants into one field
Give each combination the record it deserves
Show us a real product with a handful of combinations and tell us which fields your team actually needs to see. We'll turn that into a fixed quote before any build work starts. Pricing begins at $400 for Variation Matrix Draft.
- From $400, paid once
- Every variant is its own linked record
- An orphaned combination is flagged, not dropped
- Stock stays tied to the exact variant it describes