PRODUCT DATA AND RULES

Product Data & Rules

Manage structured swatch and SKU datasets, enforce buildability rules, and drive made-to-measure dimensions and modular assemblies from one deterministic rule layer.

Product Data & Rules

What product data and rules do in configurable 3D commerce

Product data and rules form the deterministic layer inside Aircada's configurable commerce platform that binds catalog swatches, SKUs, compatibility constraints, custom dimensions, and modular connections directly to a live 3D product scene. Every option a buyer selects is validated against manufacturing rules before it reaches pricing or checkout.

High-combination catalogs break down when incompatible hardware pairings, unbuildable dimensions, or hardcoded swatch lists reach checkout. Storing every SKU and constraint inside frontend code turns routine seasonal finish updates into engineering tickets.

CAPABILITY

Spreadsheet-driven 3D swatches, SKUs, and pricing

Manage material swatches, finish tiers, SKUs, and upcharges in structured option tables with two-way pricing synchronization and live local-to-browser updates.
Spreadsheet-driven 3D swatches, SKUs, and pricing
CAPABILITY

Conditional product rules and part compatibility

Prevent invalid custom builds with reactive 3D action-trigger links, cross-option compatibility dependencies, validation gates, and arithmetic logic operators.
Conditional product rules and part compatibility
CAPABILITY

Snap-together modular 3D product assemblies

Build connected 3D product systems with port-to-port vector snapping, chain relaxation, axis rotation locks, and anchors for lighting and tracks.
Snap-together modular 3D product assemblies

Separate catalog data from storefront code

Merchandising teams maintain hundreds of finishes, part SKUs, and option surcharges inside structured option datasets in Aircada Studio. Those tables bind directly to 3D materials, part visibility, and pricing tiers with automated reference validation before publication.

When a product requires cross-option dependencies, conditional product rules hide incompatible choices, auto-adjust dependent components, and block unbuildable combinations live in both the 3D viewport and option UI.

Support made-to-measure sizing and modular assemblies

Standard 3D mesh scaling stretches woodgrain textures and distorts corner bevels. For enclosures, signage, or furniture sold by dimension, parametric product sizing rebuilds geometry and arc-length UVs in the browser so textures and hardware proportions stay accurate at every measurement.

For multi-unit builds such as shelving, cabinetry, or rack systems, modular system builders snap connected units port-to-port along exact mechanical joints as buyers add, swap, or reorder modules.

RULE ARCHITECTURE

How catalog data drives valid 3D builds

One deterministic source of truth connects merchandising tables to 3D geometry and checkout.

1

Import swatches, SKUs, and option metadata

DATASETS

Organize finishes, part codes, dimensions, and surcharges in structured option datasets without writing frontend arrays.

2

Enforce cross-option buildability live

CONSTRAINTS

Apply conditional product rules to restrict invalid pairings and update dependent parts automatically.

3

Rebuild custom sizes and modular chains

GEOMETRY

Drive parametric product sizing and modular snap-chain assemblies directly from validated inputs.

4

Pass structured specs to pricing and checkout

HANDOFF

Feed resolved SKUs, dimensions, and part lists straight into live pricing and store checkout.

Proven across high-combination production catalogs

Every rule stays synchronized with live pricing, Shopify or headless checkout payloads, and shop-floor assembly specs. Cinch Gaming runs this rule layer across 50,000+ custom controller builds, and engineering teams can extend custom storefront bindings through the Aircada SDK when needed.

Product data and rules capability selector for buildable 3D catalogs
Operational ProblemAircada CapabilityWhat Your Team Receives
Updating hundreds of swatches, part SKUs, and surcharges requires engineering ticketsProduct Option DatasetsStructured tabular datasets bound directly to 3D materials, part visibility, SKUs, and pricing tiers with automated reference validation.
Shoppers submit incompatible part combinations that the factory cannot buildConditional Product RulesVisual cross-option compatibility logic that restricts invalid pairings, updates dependent parts live, and prevents unbuildable checkout payloads.
Made-to-measure products stretch woodgrain textures and warp rounded cornersParametric Product SizingBrowser-rebuilt parametric geometry with arc-length UVs so bevels, hardware proportions, and textures remain accurate across custom dimensions.
Chained modular products float apart instead of aligning at exact mechanical jointsModular System BuildersPort-to-port 3D snap-chain assemblies with real-time position alignment as shoppers add, swap, or reorder connected modules.

Technical Glossary

Product Option Dataset
A structured table of finishes, part SKUs, prices, and display labels inside Aircada Studio that drives 3D materials, part visibility, and checkout metadata without code changes.
Deterministic Rule Layer
Explicit compatibility, dependency, and dimension logic that produces the same valid product configuration and SKU output every time a buyer selects a given set of options.
Parametric Geometry
3D product geometry regenerated mathematically from buyer-entered width, height, or depth measurements with arc-length UVs so textures and corner bevels never stretch.
Snap-Chain Assembly
A modular 3D system where individual units connect through defined mechanical ports, recalculating alignment and overall dimensions automatically as parts are added or removed.

Frequently Asked Questions

Can merchandising teams update swatches, SKUs, and pricing without writing code?
Yes. Teams manage finish swatches, part SKUs, and pricing tiers inside structured tabular datasets that bind directly to 3D materials, part visibility, and pricing rules. Aircada validates dataset references automatically before changes publish, while upstream ERP or PIM exports into those datasets remain controlled by your catalog workflow.
Do we need custom JavaScript for every part compatibility rule?
No. Cross-option dependencies, conditional visibility, and automatic option adjustments are authored visually inside Aircada Studio and enforced deterministically in the 3D scene and UI. Aircada handles buildability constraints, parametric bounds, and snap-chain alignment natively, while real-time warehouse stock checks or ERP-specific order routing remain outside the 3D rule layer.
How is parametric product sizing different from scaling a standard 3D mesh?
Standard axis scaling stretches woodgrain or fabric textures and deforms circular holes and corner fillets into ovals, whereas Aircada rebuilds parametric geometry and arc-length UVs cleanly for the shopper's selected dimensions. Browser-side parametric generation handles dimensional primitives and enclosures with exact measurements passed to checkout, while sculpted organic shapes continue to use dedicated variant meshes.
Does this replace Shopify's variant limit for catalogs with thousands of combinations?
Yes. Instead of pre-generating thousands of static store variants for every finish and part combination, Aircada resolves option datasets and compatibility rules in the browser and passes validated SKUs and line-item properties at checkout. Shopify only stores your base products or individual component SKUs.
Can modular assemblies enforce overall size limits and per-unit compatibility?
Yes. Snap-chain builders combine port-to-port 3D alignment with conditional rules so you can cap total assembly length, restrict end-cap or connector pairings, and pass every module's SKU and position into the final order payload.
Sean Chenoweth
WRITTEN BY
Sean Chenoweth
Co-founder, Aircada
Published Updated