Base Product vs. SKU

Generally, no. In a standard e-commerce structure, the price resides at the SKU level because different variants (like a larger size or a premium material) often have different costs. Even if all variants share the same price, it is best practice to assign it to the SKUs to ensure accurate transactional data.

No, they are different. An SKU is an internal identifier used by a business to manage inventory. A barcode (like a UPC or EAN) is a universal identifier used globally to identify a product across the entire supply chain. One SKU is typically associated with one unique barcode.

Grouping SKUs under a base product improves the customer experience by allowing them to see all options on a single page. It also boosts SEO by consolidating traffic to one URL rather than spreading it across multiple identical pages, and it simplifies data management in your PIM.

You should assign static, shared data like brand, material, and care instructions to the base product, while reserving variant-specific data like size, color, and weight for the SKUs. This hierarchy ensures that updates to the base product automatically reflect across all variants, significantly reducing manual data entry. It also helps PIM systems maintain a single source of truth for core product information.

An SKU is an internal identifier used for inventory management that follows your own business logic, while a GTIN or UPC is a globally unique standard used for external trade. SKUs are customizable and vary by company, whereas GTINs are assigned by GS1 and remain the same regardless of who sells the product. Most e-commerce systems map multiple SKUs to their respective GTINs to ensure accurate tracking across different sales channels.

You should create a new SKU whenever a product change affects the physical form, fit, or function, as this impacts inventory tracking and customer expectations. Minor updates like packaging design changes or description tweaks usually only require an update to the existing SKU records. Replacing an SKU entirely is necessary if the price point or manufacturing source changes significantly enough to require separate stock reporting and historical data.

A well-structured hierarchy prevents keyword cannibalization by allowing search engines to index a single authoritative parent page instead of dozens of near-identical variant pages. By consolidating customer reviews and backlinks onto the base product page, you build stronger page authority and a better user experience. This approach ensures that customers find the main product landing page quickly while still being able to select specific options like size or color via a clean interface.

You should create a new SKU when the product shares the same core design, material, and brand, but differs in specific options like size or color. If the material, primary function, or design changes significantly, it is better to create a new base product to maintain data integrity and avoid confusing customers during their search.

This structure enables the use of dropdown menus or color swatches on a single product page, preventing shoppers from having to browse dozens of individual listings for the same item. It simplifies navigation by grouping all relevant options together, allowing customers to find their preferred size or style without leaving the page.

No, inventory is almost exclusively managed at the SKU level because the SKU represents the physical item located in a warehouse. While some PIM or ERP systems can display an aggregate stock count at the base product level for reporting purposes, all actual sales and replenishments must be tracked against the unique SKU.

General lifestyle images or brand photos should be attached to the base product, while specific product shots, such as a close-up of a specific fabric color, belong to the SKU. This setup ensures that when a customer selects a specific variant on your website, the image gallery automatically updates to show the correct item.

A frequent error is placing variant-specific data, such as a specific color’s weight or a unique size dimension, at the base product level. This forces every version to share incorrect data. Another mistake is creating a new base product for every minor change, which clutters the catalog and confuses customers. Instead, use the base product for shared attributes like brand and material, while keeping unique identifiers like individual weights or prices strictly at the SKU level.