How should you prepare products, SKUs and variants for your store?

Before sending a product folder to your web designer, decide what the customer can actually buy. A product is the main item; an option describes a choice such as colour or capacity; a variant is a specific allowed combination. An SKU is the business's internal reference for a sellable item. Those concepts should not be mixed with a marketing title or a supplier barcode.

A useful handover has an approved product list, a row for each offered version, matching image references and a person responsible for price and stock. It makes the designer's task a controlled import and review rather than a guessing exercise. Keep sensitive supplier costs and unrelated internal notes outside the public-content file.

References: Shopify: product variants · Shopify: using SKUs to manage inventory

Imagine a hypothetical desk organiser offered in two colours and two sizes. Four combinations are possible, but perhaps the large green version is not sold. The catalogue should contain the three real variants, not generate a fourth simply because two option lists were supplied.

The codes below are illustrative internal SKUs, not real Biaway products or barcodes. Each row describes one distinct item. A shared parent reference lets the implementer group the variants under one product page while keeping their operational details separate.

Scroll the table sideways to read every column.

Give the designer the field names, units and approval status before populating hundreds of rows. A blank value should have a clear meaning: unknown, not applicable or awaiting confirmation. It should never silently become a zero price, free delivery, unlimited stock or a feature claim.

Use a compact handover with three linked sheets or equivalent structured records. The format is an editorial planning suggestion, not a requirement of every platform.

• Product record: stable parent reference, approved Arabic and English names, category, factual description and product-level documents.
• Variant record: parent reference, allowed option values, SKU, current price, stock treatment, weight and other necessary fulfilment data.
• Asset and approval record: exact image filenames, which variant they show, permission/source information, missing facts and the owner who approves publication.

Shopify's SKU guidance distinguishes internal SKUs from barcodes and recommends unique identifiers for effective inventory tracking. Choose a simple consistent scheme the team can use, or preserve an established scheme rather than renaming everything for the new website. Confirm how any existing inventory tool identifies products before changing codes.

Arabic and English descriptions should point to the same underlying sellable item when they are translations. Do not create a second stock pool merely because the title changes language. Likewise, stock held at separate real locations is an operational quantity question; it does not necessarily make the physical product a new variant.

Record what 'out of stock' should do: prevent ordering, allow an explicitly approved preorder, or trigger another supported behavior. Never infer the rule from an empty spreadsheet cell. Any preorder promise or replenishment date must be confirmed by the business.

References: Shopify: using SKUs to manage inventory

An internal worksheet is not automatically a platform-ready import file. The implementer should map its fields into the current platform format, preserve a backup and test a small representative set. Shopify's CSV documentation shows that import columns and product grouping have specific meanings; use the current format rather than treating any spreadsheet as interchangeable.

Choose a simple item, an item with several options and one with a genuine exception. Check names, prices, images, option selection, stock behavior and order details. Open both languages on a phone and verify that choosing a variant shows the correct image and price. If a field is mapped incorrectly, fix the small test before repeating it across the catalogue.

1. Approve a short sample containing the main catalogue patterns.
2. Map the business fields to the chosen platform's import fields.
3. Import into the agreed safe review environment and record warnings.
4. Compare the rendered product and order details with the approved source rows.
5. Resolve discrepancies, then approve the complete import and retain the source file.

References: Shopify: product CSV import and export

Consider a hypothetical Saudi Arabia retailer preparing stock for collection in Hofuf and Mubarraz within Al Ahsa, deliveries to Dammam and Khobar, and shipments to Riyadh and Jeddah. The same sand, small organiser should remain the same product identity wherever the customer is located. Destination-specific availability, shipping or collection rules should be documented separately from its Arabic and English names.

If one real collection location lacks a variant, do not imply that the entire catalogue is unavailable everywhere. Give the implementer the actual stock-location model and confirm what the selected platform can represent. This example is a planning exercise, not evidence of Biaway stockrooms, retail branches or nationwide merchant delivery. Biaway can prepare the website configuration online from approved business data.

Biaway's ecommerce catalogue reviewed on 16 October 2026 lists SAR 700 one-time setup and up to 25 products, including supplied SKUs and basic product options. It does not, by itself, define every possible relationship between products, variants and complex customisations. Send the real combination count and sample data before approving the quotation; obtain written confirmation of the included work.

Close the handover by asking staff to identify and fulfil several sample items using the delivered order information. If 'blue medium' could refer to three unrelated products, the record is not ready. Also name the person who will add future products, approve prices and correct data. A clean first import is only useful if the team can maintain the same discipline after launch.

References: Biaway: ecommerce product setup scope

Prepared with AI assistance, with platform and accessibility claims checked against the primary sources below at publication. The planning frameworks are Biaway’s editorial recommendations. Examples labelled illustrative are not client stories or measured results. Platform features and requirements can change.

• Shopify: product variants
• Shopify: using SKUs to manage inventory
• Shopify: product CSV import and export
• Biaway: ecommerce product setup scope