POS Product Variant Migration

A size or color is useful only when it still points to the correct sellable record. Review parent products, option names, variant combinations, and stock together.

Identify duplicate combinations, missing options, and legacy naming before loading the catalog. Confirm the receiving system’s current option requirements with representative samples.

• Style or parent ID → destination product grouping
• Size and color → agreed option names and values
• Variant SKU → individual sellable record
• Quantity → the same variant at the correct location

For an illustrative black shirt in small and medium, the test should produce one agreed style with two distinct sellable variants, each with its own identifier and stock.

• List every source variant under its parent before transforming labels such as S and Small.
• Keep intentionally missing combinations missing; two colors and three sizes do not prove that six variants exist.
• Verify the destination has the expected parent grouping and one sellable record for each approved SKU.
• Scan two similar variants and compare their own prices and store quantities, not just the parent total.

Use the migration checklist to assign the decision owner and acceptance evidence. Confirm inclusion in the written scope after a secure sample review.

Current vendor instructions inform this guide; account access and the selected workflow still need confirmation.

• Lightspeed R Series item import rules
• Lightspeed X Series product import rules