Are kits and bundles different from variants?

Yes. A bundle is a SKU that decomposes into multiple component SKUs at order time (a gift basket sold as one item, fulfilled as three). Variants are different versions of the same product. Both are first-class.

Is bulk import supported for catalog setup?

Yes. CSV import covers products, variants, prices, stock, images, and categories. The importer validates before commit and reports errors per row, so a 10,000-line spreadsheet does not fail at line 9,000 with no recovery.

E-commerce · Catalog & Variants

Catalog & Variants

SKUs, variants, kits, bundles, and bulk imports.

Start free trial Back to E-commerce

Catalog & Variants flow within the CloudIP E-commerce module — input, processing, and outcome.

A clean catalog is the foundation of every commerce decision: what to list, what to price, what to count. CloudIP catalog supports variants, kits, bundles, and bulk import — and the same record drives POS, online store, and channels.

Variant matrices, color and size grids, and unit conversions are first-class.

What you get

Inside Catalog & Variants

Specifics that distinguish CloudIP Catalog & Variants from the alternative.

Variants

Color, size, and other axes with per-variant pricing and stock.

Kits and bundles

Sell kits as one SKU; deplete component SKUs at fulfillment.

Bulk operations

CSV and Excel import; bulk edit price, category, and tags.

Channel SKU mapping

Map channel-specific SKUs to your master catalog.

How it works

Catalog & Variants on the CloudIP platform

Where this capability lives, who runs it, and what it shares with the rest of the system.

Catalog & Variants runs as part of the CloudIP E-commerce module on the same multi-tenant infrastructure as every other capability you use. There is no separate console to log into and no separate billing line: product catalog software is provisioned the moment your tenant is created and stays in lockstep with the rest of the platform as it grows.

Operators interact with product catalog software through the E-commerce interface they already know — the same record screens, the same audit trail, the same role and permission model. Behind the scenes, variants handles the heavy lifting, while channel sku mapping keep the experience consistent across teams. Configuration changes are versioned, exportable, and reviewable, so the way you run product catalog software today is reproducible tomorrow.

Because Catalog & Variants reuses the platform's user database, every action is attributable, every record has a stable ID, and every export honours the tenant's data residency choice. That means product catalog software reports tie out to the rest of the books, audit logs, and operational dashboards without an integration step in between.

Catalog & Variants fits inside CloudIP E-commerce alongside the other e-commerce capabilities — they share the same data model, so improvements in one tend to compound across the others. If you are evaluating CloudIP specifically for product catalog software, the rest of E-commerce comes along at no extra cost.

FAQ

Common questions about Catalog & Variants

Yes. Variant axes are arbitrary; each combination has its own SKU, price, weight, and stock. The catalog UI handles up to a few thousand variants per product gracefully; very large variant matrices may use bundles or dynamic options instead.