Setting Up Magento Kits and Bundles After an NCR Migration

Moving from NCR Retail Online to Magento is more than copying product names and prices. A retail catalogue that once relied on NCR Counterpoint or another back-office system may contain packaged goods, promotional sets, gift collections and products sold together at the point of sale. Magento can represent these relationships, but each type needs to be modelled correctly before inventory, pricing and fulfilment rules are imported.

The migration is also an opportunity to review how products are sold to Australian shoppers. A barbecue utensil set, wine glass collection or cookware bundle may have different stock, freight, GST and promotional requirements from its individual components. Careful planning prevents overselling and gives customers an accurate view of what they are buying.

Start with a product and inventory audit

Begin by exporting the relevant catalogue from the old platform and matching every kit or bundle to its component SKUs. Record the parent product name, child products, quantities, retail price, cost, tax treatment, images, descriptions and current stock source. If a “summer entertaining pack” contains six glasses and one serving jug, each item should have a clear SKU and an agreed relationship to the pack.

This audit should also identify duplicate products and retired combinations. Migration files often include old promotions, seasonal packs and discontinued variants that should not be recreated in Magento. A retailer serving customers in Sydney, Melbourne or Brisbane may also have different warehouse availability rules, so document whether stock is shared nationally, held by store, or synchronised with a central Counterpoint installation.

Before building products, decide where inventory is authoritative. Magento may manage salable quantities through its Multi-Source Inventory features, while a connected POS or ERP remains responsible for physical stock movements. If both systems update quantities independently, a bundle can appear available after one component has sold out. Establish a single ownership rule and test stock deductions from online order through to fulfilment.

Choose the right Magento product type

Magento’s bundle product is generally the closest match for a kit assembled from selectable components. It can allow shoppers to choose options, such as selecting a colour of tea towel or choosing between a small and large frying pan. Administrators can set required or optional selections, define minimum and maximum quantities, and display a fixed or dynamically calculated price.

A simple fixed kit may instead be better represented as a grouped product. Grouped products display related items together while allowing customers to adjust quantities for each item. This works well for a cookware collection where a buyer may want two saucepans and one stockpot, but it does not behave like a single packaged SKU in every operational scenario.

Configurable products suit one product with selectable variations, such as a drink bottle available in several colours and sizes. They are not a replacement for a multi-item bundle. Using the wrong type can create confusing URLs, inaccurate stock deductions and an order structure that the warehouse cannot interpret.

If the selling unit must always contain a defined set of components, a fixed bundle or custom extension may be more appropriate than a flexible bundle. Discuss the required behaviour with the Magento implementation partner before importing thousands of records. The product model affects catalogue navigation, checkout data, fulfilment, returns and reporting.

Build bundle data for Australian retail

For each Magento bundle, create a meaningful parent SKU and retain a mapping to the former NCR item number. Component SKUs should remain stable where possible, especially if they are used by barcode scanners, suppliers or accounting integrations. Store the quantity required for one kit and define whether the parent product carries its own price or derives the price from its children.

Australian pricing should be displayed in Australian dollars and checked for inclusive GST presentation. Retail customers commonly expect the price shown online to be the amount they pay, while business buyers may need tax invoices with GST clearly identified. Confirm that the bundle’s tax class and component treatment produce the correct result in cart, checkout, invoices and exports to the accounting system.

Product content also needs a commercial review. A collection inspired by barware products might include different glass capacities, materials and care instructions. Those details should appear in the bundle description without obscuring the exact contents. Include dimensions, total packed weight, country-of-origin information where relevant, warranty terms and whether items are dishwasher safe.

Shipping deserves particular attention. Magento may calculate freight from the combined dimensions and weight of child items, but the physical kit could be packed in a separate carton. Test delivery to metro Sydney, regional New South Wales, Perth and remote Northern Territory postcodes. Australia Post, couriers and local click-and-collect services may apply different rules, and bulky bundle packaging can change the freight charge substantially.

Recreate merchandising without losing clarity

A migrated bundle should be easy to understand from category pages, search results and mobile screens. Use a name that describes the customer benefit and contents, such as “Four-Piece Non-Stick Cookware Set”, rather than an internal promotion name. Show a primary image of the complete kit and add images of important components, packaging and size references.

Cross-sells and related products can preserve the merchandising logic of the previous store. A cookware set may link to replacement lids, trivets or utensils, while a glassware pack may be paired with a bottle opener. Products similar to cookware accessories can be used as related items when the connection is genuinely useful rather than simply filling a recommendation block.

Search engine handling should be planned before launch. Decide whether the old NCR URLs will redirect to the new Magento product pages, category pages or a relevant replacement. Preserve useful copy and metadata, remove obsolete references, and avoid creating separate indexable pages for every insignificant option. Use consistent attribute labels so shoppers can filter by material, capacity, colour, pack size and intended use.

Promotions require controlled testing. A percentage discount applied to the parent bundle may behave differently from discounts applied to individual children. Check coupon eligibility, catalogue price rules, loyalty pricing and clearance logic. A promotional pack advertised during Boxing Day or a January sale should not accidentally discount the same components twice.

Test orders, fulfilment and returns

Create test orders for every bundle pattern before the store goes live. Check that the selected components appear in the order confirmation, invoice, packing slip, customer account and warehouse feed. Confirm that inventory reduces by the correct quantity for each child SKU and that cancelling an order restores stock accurately.

Run separate tests for full shipment, partial shipment, backorders and store pickup. A customer in Adelaide may order a kit containing one available item and one delayed item, while a shopper in Canberra may select click and collect from a participating store. Magento’s status and fulfilment rules should communicate these situations clearly rather than presenting an apparently complete order that cannot be supplied.

Returns need a defined policy. If a customer sends back an entire kit, the warehouse may return all components to stock. If one saucepan from a set is damaged, staff need to know whether the individual component can be refunded, replaced or only accepted as part of the full kit. Configure credit memo behaviour and customer service procedures around the physical reality of the products.

Security and integration checks belong in the same testing cycle. Review API credentials, admin permissions, payment callbacks, tax calculations and connections to POS, warehouse and accounting systems. The former platform’s retail platform information may explain the original operating context, but the Magento build should rely on current integration documentation and a controlled staging environment rather than assumptions about legacy behaviour.

Launch with controlled catalogue governance

Use a staged migration rather than publishing every bundle at once. Import a small set of products, validate prices and stock, place real-world test orders, then expand by category. Keep a reconciliation file showing the old SKU, Magento SKU, bundle components, quantity, price and migration status. This makes it easier to investigate an order or stock discrepancy after launch.

Assign ownership for ongoing catalogue maintenance. Merchandising staff should manage descriptions and promotions, inventory teams should manage component availability, and technical administrators should control integrations and indexing. Changes to a child SKU can affect every bundle that contains it, so Magento should provide a reliable way to identify parent relationships before a product is renamed, archived or replaced.

Monitor the first weeks closely. Compare online sales with POS records, review abandoned carts caused by unavailable components, and inspect freight variances by state and postcode. Look for customer service contacts about pack contents, delivery timing and returns. These signals often reveal modelling problems that were invisible in a spreadsheet.

A successful migration leaves more than a functioning storefront. It creates a catalogue in which every kit has an accountable stock model, an accurate tax and freight outcome, clear customer content and a tested path from checkout to warehouse. The practical rule is simple: map each bundle to real component SKUs, test every operational consequence, and publish only when Magento, inventory systems and fulfilment staff agree on what one sale represents.