RELATIONAL OPTION DATASETS

Spreadsheet-driven 3D swatches, SKUs, and pricing

Hardcoding finish swatches, part SKUs, and price surcharges inside individual 3D meshes or UI components turns catalog updates into engineering tickets. Aircada stores product permutations in structured spreadsheet datasets that bind directly to 3D materials, part visibility, and pricing rules without engineering tickets.

Spreadsheet-driven 3D swatches, SKUs, and pricing

Stop hardcoding swatches and surcharges across 3D scenes

When a configurable product offers 40 fabric textures, 12 metal finishes, and 8 hardware upgrades, scattering option labels, texture references, and price adjustments across disconnected storefront UI arrays and 3D scene nodes quickly leads to out-of-sync prices and broken checkouts.

Aircada centralizes product permutations inside structured option datasets. Instead of editing 3D logic or waiting on a developer every time a seasonal color launches or a material surcharge changes, your team updates a single table row and lets Aircada propagate the change across the 3D viewport, storefront option selectors, and Shopify or headless checkout pricing.

In production deployments like Cinch Gaming, separate structured option tables drive front and back controller shells, face buttons, thumbsticks, D-pads, rear paddles, textured grips, build speeds, and engraving tiers from one clean catalog source.

STRUCTURED OPTION TABLES

One table row drives 3D materials, thumbnails, and SKU codes

Every dataset pairs a typed column schema with validated option rows. When a shopper picks a finish or part, Aircada resolves the linked texture, font, or 3D sub-model, updates the 3D scene immediately, and emits the selected row's label and SKU to your storefront UI.

Automatic unique row ID generation, row counting, and schema validation on every save
Verifies linked media assets (textures, thumbnails, fonts, and 3D sub-models) and clears broken references cleanly
Serialized per-dataset write queues prevent conflicting edits during rapid table updates
Immediate cloud flush whenever a Studio browser tab moves to the background so work is never lost
Custom walnut and brushed brass modular desk organizer beside a structured Dataset Row Schema UI card showing row ID, finish, material asset, and upcharge
TWO-WAY PRICING SYNC

Keep option tables and checkout pricing rules in lockstep

Option sets inside an Aircada pricing model bind directly to a source dataset. Whenever you add a seasonal finish row or revise a surcharge column, Aircada synchronizes the linked option set, validates the versioned pricing manifest, and updates the matching checkout connector fields automatically.

Two-way synchronization keeps dataset rows and pricing option sets aligned without manual copy-paste
Built-in manifest validation catches missing or malformed option references before publishing
Auto-generates checkout connector fields for every synced option set so checkout payloads stay accurate
Separates clean published pricing manifests from transient Studio editing state
Three espresso machine housings in sage green, matte black, and brushed steel beside a Two-Way Pricing Sync UI card
LIVE LOCAL-TO-BROWSER SYNC

Edit catalog tables locally and watch the 3D scene refresh live

For engineering and merchandising teams managing large catalogs in Git, Aircada's CLI and local development server watch option tables on disk and stream updates straight into the running browser session with zero page reloads.

Timestamp-based reconciliation automatically pushes newer local edits and pulls newer Studio edits
Content-hash change detection prevents sync echo loops during rapid batch updates
Atomic file writes protect local catalog files from partial saves or crashes
Live browser refresh updates 3D swatches, option lists, and prices instantly while testing
Anodized cobalt-blue CNC-milled aluminum bicycle stem beside a live sync UI card showing active dataset and pricing refresh

How option tables, pricing models, and storefront checkout stay synchronized

Each dataset enforces a typed column schema so selecting a single row can swap a 3D finish or sub-model, update the storefront swatch thumbnail, pass the exact manufacturer SKU into the order payload, and recalculate the active price through two-way pricing dataset sync.

Option dataset layers and runtime behavior
LayerHow It Is StructuredWhat It Controls
Product Option TableTyped column schema + validated option rowsStores option IDs, display labels, manufacturer SKUs, price adjustments, colors, fonts, and linked 3D or image assets.
Linked Pricing ManifestValidated, versioned pricing definitionBinds option sets to source datasets alongside base prices, surcharges, and cross-option or quantity rules.
Checkout Connector SyncAuto-generated option fields per option setMaps each synced option set straight into Shopify or headless cart submission without hand-wiring every field.
Local Cache & Cloud StorageBrowser cache + queued cloud persistencePreloads datasets locally for fast storefront startup while queuing atomic saves and validating timestamps in Studio.

When to use tabular option datasets

Replace brittle hardcoded arrays whenever product options share structured attributes or pricing rules.

Multi-material furniture & cabinetry

Manage dozens of wood veneers, powder-coat colors, and fabric grades in one table where each row maps to a 3D finish and tier surcharge.

Seasonal colorway & swatch refreshes

Add or retire seasonal color palettes in the dataset table without rewiring 3D scene logic or shipping new storefront code.

Component SKU & part-number lookup

Store manufacturer part numbers alongside visual 3D options (as Cinch Gaming does across controller shells, thumbsticks, and buttons) so checkout receives exact component codes.

Git-versioned catalog workflows

Pull, batch-edit, validate, and sync structured option tables and pricing manifests through the Aircada CLI alongside your storefront repository.

Responsibility Tiers

  • 1 Native Aircada layer
  • 1 Aircada Configuration layer
  • 1 Custom Implementation layer
  • 1 External layer

Responsibility Boundaries Across Product Option Datasets

How Aircada's dataset runtime, Studio table configuration, and external ERP catalogs divide responsibilities.

Dataset registry, write-queued persistence, pricing sync & live CLI hot-reload

  • Native Aircada
  • Browser caching, write-queued cloud persistence, broken media reference cleanup, two-way dataset-to-pricing synchronization, manifest validation, and checkout connector field generation.

Table schema definition, row population & option-set binding

  • Aircada Configuration
  • Defining dataset columns, uploading swatch and material assets, populating option rows in Studio or via the CLI dataset workflow, and linking tables to pricing option sets.

Automated ERP / PIM import scripts

  • Custom Implementation
  • Optional build or webhook scripts that transform external ERP or PIM product spreadsheets into Aircada option tables via the CLI sync workflow.

Master SKU pricing governance & warehouse inventory counts

  • External
  • Merchant ownership of wholesale and retail price schedules, tax rules, and live stock availability inside Shopify or external ERP systems.

Frequently Asked Questions

Can merchandising teams update swatches and pricing in tables without breaking live configurators?
Yes. Whenever datasets and pricing models synchronize, Aircada validates all option references against its manifest validator and checks linked media assets automatically. Missing fields or broken asset references are flagged immediately before changes publish to your live storefront.
Can our developers manage option tables as files in Git instead of only in the browser UI?
Yes. Option tables and pricing manifests serialize to clean, version-controlled files managed through the Aircada CLI. During development, Aircada's local file watcher reconciles edits by timestamp, prevents sync loops with content hashing, and hot-reloads changes straight into the browser.
Do large option datasets slow down initial 3D viewer load times?
No. Active datasets preload efficiently during startup and cache locally in browser storage so repeat visits load immediately. Cached tables only re-fetch when a dataset's updated timestamp changes after a catalog edit.
Do we have to connect every spreadsheet option to our checkout payload by hand?
No. When a dataset syncs to an option set in your pricing model, Aircada automatically generates and updates matching checkout connector fields for each option set. That keeps 3D selections, live pricing, and Shopify or headless order payloads aligned from a single table.
NEXT STEP

Structure your product catalog as live 3D datasets

Send us your current finish matrix or option spreadsheet and we will show you how it maps directly to 3D materials and live checkout pricing.

CONNECTED CAPABILITIES

Related capabilities

Explore the adjacent capabilities and integrations that pair with this workflow.

Live dynamic pricing and wholesale quantity breaks
DYNAMIC PRICING
CAPABILITY

Live dynamic pricing and wholesale quantity breaks

Explore
One-click multi-SKU 3D kits and bundle checkout
commerce and ordering
CAPABILITY

One-click multi-SKU 3D kits and bundle checkout

Explore
Live 3D cart thumbnails and verified design IDs
commerce and ordering
CAPABILITY

Live 3D cart thumbnails and verified design IDs

Explore
Automated 3D assembly BOMs and pick-list specs
ORDER BOM & LINE-ITEM EXTRACTION
CAPABILITY

Automated 3D assembly BOMs and pick-list specs

Explore

Sean Chenoweth
WRITTEN BY
Sean Chenoweth
Co-founder, Aircada
Published Updated