What most often delays an online store launch is product data, rather than design or development. Inconsistent names, missing photos, prices changing during entry, and undecided options all mean messages back and forth and waiting, sometimes even rebuilding a completed product page.
You can prepare product information before choosing a team to build the store. Organized data helps define product counts, variants and required images when estimating scope. Start with the product list, then review the gaps with our team.
One spreadsheet for all products
Use a simple spreadsheet: product name, category, price, options, and short description. An Excel or Google Sheets file is enough. Everyone should work from one file rather than separate copies in email and WhatsApp messages.
An organised spreadsheet makes adding products in bulk easier. Most online store platforms support importing products from a file, saving manual entry one product at a time and reducing errors.
Essential spreadsheet columns
- Product code (SKU): A fixed code for each product or option, useful later for inventory and linking orders.
- Product name: In the wording customers search for, rather than the internal warehouse name.
- Category: The main category and subcategory, if any, with consistent names across all rows.
- Price: In Saudi riyals, specifying whether VAT is included, and the sale price if applicable.
- Short description: Two or three lines explaining the product’s main features.
- Detailed description: Specifications, dimensions, materials, and use or care instructions.
- Weight or dimensions: If shipping fees will be calculated using them.
Standardise formatting before entry
Check the spreadsheet for duplicates and inconsistent wording. A product entered under slightly different names will appear as two products in the store. Standardise category, size, and colour names, and agree on one number format.
If you sell to customers in Saudi Arabia, write names and descriptions in Arabic first, then add English if the store is bilingual. Do not rely on unreviewed machine translations for descriptions, because incorrect product descriptions lead to returns and many questions.
Search and filter data
Consider how customers search for your products. Do they choose by type, size, age group, or material? Each attribute customers will filter by needs its own spreadsheet column, with consistent values across all rows.
If you write the material as “cotton”, “cotton fabric”, and “Cotton” in different rows, customers will see three different filter options and miss some products. Prepare a list of allowed values for each attribute before filling the spreadsheet, and stick to it.
Also add the search terms customers use if these differ from the product’s official name. These terms help store search and make descriptions closer to customers’ language.
Images
Photograph products against a consistent background with similar lighting, and name each image after the product or its code. Consistent photos make the store clearer and more professional, and help customers compare products on category pages.
What do you need for each product?
- A clear main image showing the whole product against a consistent background.
- Additional photos from different angles and a close-up of important details such as material or texture.
- A photo for each colour or option that looks different, so customers see what they will actually receive.
- A photo showing scale when needed, such as the product in someone’s hand or beside a familiar object.
Image sizes and filenames
Agree on one aspect ratio for all product images, such as square, so product cards do not appear at different sizes on category pages. Do not upload huge photos straight from the camera; they slow the store on mobile, where many customers browse.
Name image files so they link to the spreadsheet, for example the product code followed by the image number. This simple naming method saves considerable time when matching images to products, especially if you have many.
If existing photos have different backgrounds and lighting, decide before implementation whether to reshoot, edit the current images, or start with them and replace them later. Deciding early is better than discovering inconsistency after launch.
Options and inventory
Define options such as size and colour, and whether each has a different price or stock level. These details affect how the product page is built and how customers choose before adding to the cart.
Types of options
- Options that do not change the price: Such as shirt colours, where every colour has the same price.
- Options that change the price: Such as pack size or capacity, each with its own price.
- Options with separate stock: The small size may be available while the large is sold out, so the store needs to know the quantity for each option.
- Optional extras: Such as gift wrapping or printing the customer’s name, which may need a text field for their request.
In the spreadsheet, put each option on a separate row linked to the parent product, with its price, quantity, and code if different. This most closely matches how most platforms import options.
Who manages inventory after launch?
Before implementation, decide who will update quantities and whether another system tracks inventory, such as accounting or warehouse software. If inventory is managed elsewhere, you may need an integration or a clear update process to avoid selling unavailable products. If your data is spread across several systems, the article on migrating data to a new system explains how to clean it before migration.
Also decide what happens when a product sells out: does it disappear, appear as unavailable, or allow preorders? These are simple decisions that affect the customer experience and your team’s work.
Once this data is complete, discussions about store scope and cost become much more accurate. You can read what determines the cost of an online store, and review what we prepare in our service for Online store design.
Frequently asked questions
Do all products need to be ready before starting?
Not necessarily. A sample representing your different product types can be used to build product and category pages, then the rest can be added using the same spreadsheet. The sample should cover every type of option you sell.
Who writes product descriptions?
This is agreed before implementation. You know your products and specifications best, so the basic information usually comes from you. The wording can then be organised for clarity and consistency.
Do I need a SKU for every product?
It is not mandatory in every store, but is very useful if you have inventory or multiple options, or plan to connect the store to another system later.
What about payment and shipping methods?
These are reviewed based on your business accounts and available providers, such as mada, Apple Pay, and shipping companies. If you want to discuss your particular store, Contact us.