Product catalogue: build your store’s source records
Build an online product catalogue with clear products, variants and categories. Use a record template, assign sources and check your first import.
- Published
- Last updated
A product catalogue is the organised product information a retailer uses to present and sell its range. An online catalogue connects each product to its sellable variants, approved facts and images, with references to current prices and availability.
Start with one product family before importing your whole range. The fictional jacket records below show how to separate shared information from each size-and-colour combination, assign an owner to each field and check the first import.
What a product catalogue contains
A digital product catalogue contains the source records behind the products customers browse and buy. Product catalogue and product catalog mean the same thing. A printed brochure or folder of product photos shows only part of that information.
Keep the following record groups:
- Product identity, including a stable internal ID and product name.
- Sellable variants, each with its own identity and purchase options.
- Category membership for browsing and merchandising.
- Product facts, such as colour, size and verified construction details.
- Media, with an image reference for the correct product or variant.
- Commercial references that connect each variant to its current price and sellable availability.
A product page combines these records into one storefront view. A category collection displays a selected group of products. A PDF catalogue is a fixed export, while a channel product feed sends selected fields to another service. Several views can use the same source records without becoming separate authorities for the product’s identity.
This distinction also changes product catalogue design. Agree on the records first, then decide how your site or exported catalogue displays them.
Separate products, variants and categories
A product is the shared family, a variant is a specific sellable choice and a category groups products for browsing. Keep those identities separate when one product appears in several places.
Consider the fictional Harbour jacket. Its shared description is, “A zip-front jacket available in navy and ochre, in sizes S and M.” The family has one parent product ID, 000042, and four sellable variants. Each variant needs its own identifier, stock reference and assigned image.
A stock keeping unit (SKU) is the retailer’s code for tracking a sellable item. In this example, JKT-NV-M identifies the navy medium jacket within the retailer’s systems. The parent ID 000042 groups all four variants and cannot tell a warehouse which size to pick.
A manufacturer’s product identifier comes from the manufacturer. Record its manufacturer part number (MPN) in a separate field, with the manufacturer’s name and the level it identifies. A family-level model number cannot distinguish variants unless the manufacturer actually assigns it that way.
A Global Trade Item Number (GTIN) is a GS1 trade-item identifier. GS1’s size-and-colour guidance requires a separate GTIN for each combination. Keep a supplied GTIN separate from your internal SKU. All identifiers below are fictional internal codes, and the example invents no GTINs.
A product category is a group of products with a shared purpose or characteristic. The Harbour jacket belongs to the store’s Jackets category and its Weekend clothing collection. Both memberships point to parent 000042. Adding the second membership creates another browsing route, without creating another jacket or a fifth variant.
Store navigation and an external shopping-feed taxonomy are separate structures. Keep the store’s category memberships, then map the same product to the channel’s accepted clothing category. A channel category describes classification, while Navy and M describe a purchasable variant. Use the product taxonomy guide when you need to design those structures.
Assign sources and owners before importing
Assign one authority for each field group before combining supplier files with your own store records. The authority decides which value can change, who approves it and where the accepted value comes from.
Field authority for the fictional jacket
| Field group | Source of the accepted value | Person or system authorised to change it |
|---|---|---|
| Supplier facts and manufacturer identifiers | Supplier specification and variant sheet | Product-data manager approves the supplier evidence |
| Internal parent IDs, variant IDs and SKUs | Retailer’s identifier register | Catalogue administrator assigns and maintains identities |
| Merchandising name and description | Retailer’s approved copy record | Merchandiser edits the published copy |
| Product and variant images | Approved media library | Content owner approves image rights and variant assignments |
| Current selling price | Retailer’s pricing system | Pricing manager changes prices in that system |
| Sellable availability | Inventory system and selling rules | Inventory controller maintains stock and availability rules |
Keep the original supplier assertion alongside its source reference. Publish the retailer-approved value only after resolving a conflict. If one sheet lists a jacket weight as 0.6 kg and another as 600 g, confirm both describe the same item before converting units.
If the supplier calls a colour Midnight and the merchandiser uses Navy, approve one store label and retain its mapping to the supplier’s variant. A disagreement about size or construction needs evidence from the correct supplier record. Leave the disputed specification unpublished until the product-data manager resolves it.
The catalogue can hold references to price and inventory records without owning their changing values. A copied stock figure is a snapshot. Decide which connection refreshes it and which system decides whether a customer can buy the variant.
Build a small product catalogue template
Build the first product catalogue template as a parent sheet and two variant sheets joined by stable identifiers. You can copy these tables into a spreadsheet without buying catalogue software.
These are fictional source records, not a platform-ready import file. Image and system references name example records. Replace them with your own approved records and map the columns to your destination’s required format.
Shared parent record
| Field | Fictional value | Requirement in this template |
|---|---|---|
| parent_product_id | 000042 | Required text identifier |
| product_name | Harbour jacket | Required |
| description | A zip-front jacket available in navy and ochre, in sizes S and M. | Shared approved copy |
| categories | Jackets; Weekend clothing | At least one approved store grouping |
| source_reference | supplier-sheet-J1 | Required evidence reference |
| destination_reference | harbour-jacket | Required mapping to the destination product |
| manufacturer_product_id | Empty | Optional until a verified identifier is supplied |
| shell_material | Empty | Optional unknown fact, excluded from published claims |
Sellable variant records
| parent_product_id | variant_id | sku | product_name | colour | size |
|---|---|---|---|---|---|
000042 | 000042-01 | JKT-NV-S | Harbour jacket | Navy | S |
000042 | 000042-02 | JKT-NV-M | Harbour jacket | Navy | M |
000042 | 000042-03 | JKT-OC-S | Harbour jacket | Ochre | S |
000042 | 000042-04 | JKT-OC-M | Harbour jacket | Ochre | M |
Variant source and destination references
| variant_id | source_reference | image_reference | commercial_reference | destination_reference |
|---|---|---|---|---|
000042-01 | supplier-sheet-J1:navy-S | harbour-navy-front.jpg | JKT-NV-S | harbour-jacket:navy-S |
000042-02 | supplier-sheet-J1:navy-M | harbour-navy-front.jpg | JKT-NV-M | harbour-jacket:navy-M |
000042-03 | supplier-sheet-J1:ochre-S | harbour-ochre-front.jpg | JKT-OC-S | harbour-jacket:ochre-S |
000042-04 | supplier-sheet-J1:ochre-M | harbour-ochre-front.jpg | JKT-OC-M | harbour-jacket:ochre-M |
Every variant inherits the parent’s description and category memberships. The repeated product name makes a variant row understandable on its own. A separate variant ID joins the final two tables, while the SKU connects the variant to price and inventory records.
In this fictional setup, both commercial systems use SKU as their matching field. The navy medium pricing record shows $129 including GST. Its inventory record shows three sellable units, with backorders disabled. These values are example snapshots, not permanent fields to copy from this article.
Format identifier columns as text before entering or opening data. 000042 must stay 000042, not become 42. CSV quotation marks alone do not stop a spreadsheet from interpreting a numeric-looking identifier as a number.
For this template, require a parent ID, variant ID, SKU, colour and size on every variant. Require its source, image and destination mappings before approving the family. Optional unknown specifications stay empty in the source sheet. The word Empty in the parent table explains a blank cell and is not a value to import.
If the destination requires a missing value, hold that row for resolution. A blank material field cannot become polyester because the photo looks like it. Set more detailed product attributes once the first record structure is working.
Import and check the first product family
Import one complete family into an unpublished preview or disposable test store, then check its saved records before expanding the range. You need permission to import products, approved images and a backup or export of any records the import could update.
Use your destination’s sample file to map the source sheets. For Shopify, its product CSV specification documents required headers and option dependencies. Its overwrite mode matches product handles, and an included blank optional column can clear an existing value. Keep unrelated fields out only after checking their dependencies.
- Assemble the parent record and its four variant rows. Resolve disputed facts with their field owners before creating the destination file.
- Validate the identifiers as text. Expect one parent ID, four unique variant IDs and four unique SKUs. Every variant must point to
000042. - Map the source fields to the destination format. Keep colour and size option positions consistent, and map image references to the image locations the importer accepts.
- Preview the small import with publication disabled. Check the expected product grouping and the overwrite setting before starting it. Stop if the preview shows four separate parent products.
- Run the import in the test destination and inspect the saved family. Expect one Harbour jacket with exactly four size-and-colour combinations, each present once.
- Select every variant and compare its SKU, image and commercial references with the source sheets. The navy medium selection must use
JKT-NV-Mand the navy image. In the fictional snapshot, it must show $129 including GST and three sellable units from the assigned systems. - Correct rejected rows using the reported error and their source records. Inspect the destination first to see which rows already exist, then retry with the documented matching behaviour.
- Export or reopen the saved records and repeat the count and relationship checks. Approve the family only when the intended values survive that check and the price and availability sources are correct.
Shopify’s documented import procedure includes an upload review before importing. It also warns that changing option values can replace variant IDs. Preserve the mapping between your internal identities and destination IDs when correcting an existing family.
Diagnose the first import before adding more products
| Symptom | Check | Corrective action |
|---|---|---|
| Duplicate Harbour jacket products | Compare the parent matching value on every row with the importer’s matching rules | Use one consistent parent mapping and resolve the unintended records before retrying |
| Orphaned variant | Compare the variant’s parent reference with the saved parent ID | Correct the reference or import the missing parent first |
| Approved copy replaced by supplier text or blanks | Compare included columns and overwrite behaviour with the field-authority table | Restore the approved value from its owner and remove the unauthorised update from the next import |
| Ochre image on a navy variant | Compare the saved variant ID, image assignment and row grouping | Correct the navy assignment and inspect both navy sizes again |
These checkpoints describe the results to expect from the example records. Use the saved destination records to decide whether your own import passes. For wider correction work after this first family, follow the data cleaning guide.
Use the catalogue for product discovery and buying
A catalogue supports buying when a customer’s request resolves to the correct sellable variant, with its current price and availability. Matching a product family alone is insufficient.
For the request “a navy jacket in medium”, search first finds the Harbour jacket in Jackets. The colour filter keeps the Navy variants, then size M selects 000042-02. Its SKU, JKT-NV-M, connects to the pricing and inventory records. The storefront or shopping assistant can then present the correct image and add that specific variant to the basket.
In the fictional snapshot, the chosen variant costs $129 including GST and has three sellable units. At purchase, the store must use the current price and selling rules. Stock held for another order or a later price change can alter what the customer can buy.
The navy image proves which image is assigned, not how many medium jackets remain. The family description lists available options but cannot prove every combination is currently purchasable. A category label also cannot establish waterproofing or another missing specification.
Hand over the accepted family with the following checks complete:
- Keep the parent ID and all four variant mappings intact when another system receives the records.
- Give each unknown fact to its named owner for product data enrichment, with the supplier evidence retained.
- Preserve image assignments and approved store categories when mapping records for another channel.
- Name the price and availability authorities, their refresh process and the person responsible for a failed update.
- Give the next importer the saved-record checks, so a successful file upload is followed by verification of the actual variants.
Use the accepted records to assess software requirements or prepare channel-specific listings. Keep 000042-02 mapped to the navy medium jacket wherever that variant is distributed.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.