How to rebuild product variants and options in Magento

Moving from NCR Retail Online to Magento involves more than importing product names and prices. Variant structures, option rules, stock records, images, and customer-facing selections all need to be reconstructed in a system with a different catalog model. A careful rebuild protects search visibility, checkout accuracy, and inventory reliability.

Magento gives merchants several ways to represent product choices. Configurable products handle variations such as size and color, while custom options add selections that do not require separate inventory tracking. Grouped, bundle, virtual, and downloadable products solve other merchandising needs. Choosing the correct structure before importing data prevents expensive catalog revisions later.

The work is especially important for retailers migrating through an NCR Counterpoint partner or another implementation team. Product data should be mapped against the operational system that will remain authoritative, with clear rules for stock, pricing, fulfillment, and updates.

Audit the existing catalog before migration

Begin by exporting every product and documenting how customers currently select or customize it. Record parent products, child SKUs, option labels, prices, images, barcodes, supplier codes, tax settings, and stock quantities. Include discontinued items and inactive combinations so the migration team can decide whether they should be archived or omitted.

Separate true product variants from simple add-ons. A blue shirt in three sizes represents distinct inventory-bearing combinations. Gift wrapping, engraving, installation, and warranty upgrades may be better represented as custom options because they modify the purchase without needing a separate stock record.

Look for inconsistent naming as well. One system may use “Small,” “S,” and “Size Small” for the same attribute. Standardize values before loading them into Magento. Resolve duplicate SKUs, missing images, invalid characters, and products with variant prices that conflict with the pricing strategy.

Choose the right Magento catalog structure

A configurable product is usually the best choice when each customer selection corresponds to a separate simple product. The configurable item acts as the storefront parent, while associated simple products hold individual SKUs, quantities, weights, images, and other operational data. A customer can select attributes such as color and size, and Magento identifies the associated child item.

Customizable products are different. Magento custom options are suitable for choices such as monogram text, a preferred delivery window, or an accessory added to a base item. These options can change the price, but they generally do not create independently tracked inventory units. Using them for stock-sensitive variants can lead to inaccurate availability.

Bundles are useful when buyers assemble a product from several components, such as a computer package or gift hamper. Grouped products display multiple independent items together without combining them into one configurable selection. Document the intended customer experience before selecting a type, since changing product types after launch can require catalog restructuring.

Build attributes and variant relationships

Create global product attributes before importing products. Common examples include color, size, material, capacity, finish, and fit. Define the input type, storefront label, sorting order, and allowed values. Use controlled values instead of allowing free-form text, since consistent attributes support layered navigation, filtering, and product comparisons.

Only attributes used to define a configurable product should become variation attributes. A material description may be useful for filtering but may not belong in the customer’s selection process. Keep marketing fields, technical specifications, and fulfillment data separate from the attributes that generate child products.

After defining attributes, create the parent-child relationships. Each simple product should have a unique SKU and a complete combination of required values. For a product offered in four colors and three sizes, confirm whether all twelve combinations exist. If some combinations are unavailable, exclude them rather than creating empty child records that confuse shoppers.

Inventory architecture deserves special attention during this stage. Magento can manage stock at the simple-product level, but connected systems may send quantity, price, or order updates using different identifiers. Review these inventory differences before deciding which platform controls availability and how synchronization errors will be handled.

Map legacy fields to Magento data

A field-mapping document should connect every source value to a Magento destination. Typical mappings include product title to name, retail price to price, department to category, UPC to a custom attribute, and source SKU to SKU. Include transformation rules for units, currency, tax classes, image filenames, and status values.

For variants, map both the parent product and each associated simple product. The parent needs a meaningful description, category assignment, base imagery, and configurable attribute definitions. The child requires the exact attribute values, inventory quantity, weight where applicable, and any variant-specific images or pricing.

Use a staging environment for imports. Load a small representative group first, including products with two options, products with missing combinations, products with special pricing, and products with custom options. Review the result in the storefront and admin panel before processing the complete catalog.

Recreate pricing, media, and storefront behavior

Variant pricing needs a deliberate strategy. If all child products share a price, keep the pricing simple and consistent. If certain sizes, materials, or finishes carry premiums, configure price differences in a way that matches the source catalog and remains understandable at the product page. Validate special prices, tier prices, customer-group pricing, and scheduled promotions separately.

Images should be assigned at the correct level. Parent images can present the overall product, while child images should show the selected color or configuration. Check image roles, thumbnails, alt text, cropping, and filename conventions. A successful data import can still produce a poor shopping experience if variant selections do not update the gallery correctly.

Review storefront behavior on mobile and desktop. Confirm that unavailable combinations are disabled or hidden as intended, option labels are easy to understand, and the selected configuration remains visible in the cart and order confirmation. Test quantity limits, backorders, shipping calculations, and tax display for representative child products.

Search and navigation also depend on clean attribute data. Use consistent synonyms where appropriate, but avoid creating multiple attribute values for the same concept. Preserve useful legacy URLs through redirects when product pages are rebuilt, and verify that canonical tags and metadata do not point to obsolete addresses.

Test orders and synchronization

Functional testing should begin with the customer’s path, not with an import report. Select every major combination, add it to the cart, change the selection, remove it, and return to the product page. Confirm that the correct SKU, price, image, weight, and stock message follow the selected configuration.

Place test orders for available, low-stock, and unavailable child products. Check whether the order contains the parent name, selected attributes, and child SKU in a way that warehouse staff can understand. Then verify that the order reaches the operational system correctly and that the resulting stock adjustment returns to Magento.

Run negative tests as well. Attempt to purchase a disabled combination, submit an invalid custom option, use a quantity above the available amount, and apply a promotion to a product with a variant surcharge. These cases reveal gaps in validation that normal purchases may not expose.

Security and permissions should be part of the migration test plan. Limit catalog editing, import access, API credentials, and integration logs to the roles that need them. Review this security planning guide while setting up accounts, payment integrations, backups, and monitoring for the new Magento environment.

Prepare the launch and post-migration review

Freeze the source catalog for a defined period before the final migration, or establish a method for capturing changes made after the initial export. Communicate the cutoff to merchandising, warehouse, customer service, and store teams. A clear ownership schedule prevents a late price or stock edit from being lost.

Before launch, compare product counts, child SKU counts, option values, category assignments, prices, and inventory totals between the source and Magento. Spot-check high-volume products and products responsible for a large share of revenue. Resolve discrepancies rather than accepting them as normal migration noise.

After launch, monitor failed imports, integration queues, overselling warnings, product page errors, and customer search behavior. Review the first orders manually and compare them with warehouse and accounting records. Keep the old catalog export and mapping file as reference material so future corrections can be traced.

Use the first few weeks to refine labels, filters, images, and option instructions based on real customer behavior. A technically correct catalog may still need merchandising improvements, especially when Magento presents choices differently from the previous ecommerce platform.

Finalize a dependable Magento catalog

Rebuilding variants and options is a data-modeling project as much as a storefront project. The strongest migrations distinguish inventory-bearing child products from non-stock customizations, establish consistent attributes, and test integrations before customers depend on them.

Complete the mapping, load a controlled sample, validate the full purchase journey, and schedule the final catalog cutover with clear owners. Once the product relationships, stock rules, and security controls are verified, move the live catalog to Magento and monitor every early order closely.