Product Data Checklist: What Your Developer Needs Before Building an Online Shop

Before anyone builds your online shop, they need your products written down in one place, cleaned up and consistent. For each item that means a title, a description, a price, a unique code (an SKU), its variants like size or colour, how many you have in stock, at least one clear photo, and the category it belongs to. Get that into a single spreadsheet and the build moves quickly. Hand over a WhatsApp catalogue and a few prices from memory, and the project stalls while someone chases the missing pieces.

This is for a Zimbabwe retailer moving off WhatsApp and Facebook orders into a proper shop. Below is exactly what "product data" means, the spreadsheet columns to fill in, and how to keep it consistent so the first batch goes live without delay.

TL;DR

• The one job: turn your products into clean, consistent rows in one spreadsheet before the build starts.
• Per item, you need: title, category, description, price, a unique SKU, variants, stock count, and at least one clear photo.
• Variants matter: every buyable combination (a size, a colour) gets its own row, SKU, price and stock, so items can sell out independently.
• Photos: good daylight phone photos are often enough to start; professional photography is a $100 per session add-on where images are your main selling point.
• Not covered here: how you get paid (see the payments guide) and how you charge for delivery (see the delivery guide). This article owns the catalogue itself.

What product data actually means

Product data is every fact your shop needs to display an item, take an order, and tell it apart from everything else you sell. At minimum that is a title, a description, a price, a unique SKU, any variants, a stock count, a category and a photo. If a product is missing any of those, it cannot go live cleanly, so the goal before a build is one spreadsheet where every row is complete. Clean data in, fast build.

The product spreadsheet: columns to fill in

This is the payoff. Set up one spreadsheet with these columns and fill a row for every sellable item. If a product comes in different sizes or colours, give each combination its own row.

Two habits keep this clean. Give every row a real, unique SKU, never leave it blank. And use one consistent name and spelling for each category, so "T-shirts" and "Tshirts" do not split into two menus.

Titles and descriptions that do the selling

Write titles the way a customer would search: the product, then the useful detail. "Cotton crew t-shirt" beats "Item 4" and beats a title stuffed with every keyword. Keep them short and specific.

For descriptions, plain and honest works. Say what it is, who it suits, and the details a buyer needs to commit: material, fit, dimensions, what is included, care or usage notes. You know your products better than any writer, so owner-drafted descriptions are the fastest route to launch. The build team will format them. If you would rather have longer, search-optimised copy written for you, that is a separate paid service, but a first launch rarely needs it.

SKUs: the code that ties everything together

An SKU (stock keeping unit) is a short unique code for each thing you actually sell. It is how your shop, your stock count and your orders all point to the same item without anyone guessing. You do not need special software. Build a simple pattern and stick to it, for example a product prefix, then the variant: TSH-RED-M, TSH-RED-L, TSH-BLU-M. The rules that matter: every sellable variant gets its own code, no two items share a code, and you never reuse an old code for a new product. Get this right on the spreadsheet and matching orders to stock stays simple once you are busy.

Variants: sizes, colours and anything that changes the item

A variant is a version of the same product that a customer chooses between, most often size or colour, sometimes material or pack size. The rule is simple: if two versions can sell out independently or carry different prices, each one is its own row with its own SKU and stock count. A small red shirt selling out should not hide the large blue one still on your shelf.

List the parent product once, then a row per buyable combination. If everything shares one price and you only track total stock, you can keep it lighter, but most clothing, footwear and multi-option sellers need per-variant rows. Decide this before the build, because retrofitting variants onto a shop that was set up for single items is slow.

Photos: what to gather and how good they need to be

Every product needs at least one clear photo, and your best sellers deserve two or three from different angles. Online, the picture does the work your shop assistant used to do, so a dark or cluttered image costs you sales.

You do not need a studio to start. Sharp phone photos in daylight, against a plain wall or sheet, are enough for most first shops. Name each file so it maps to the right row (tsh-red-m-01.jpg), keep the originals, and let the build team resize and compress them so pages stay light on mobile data. Where product images are your main selling point, or where you are shooting a large range and want consistency, professional photography is available as a $100 per session add-on. It is optional, not a requirement, and honest phone photos beat waiting months for a "perfect" shoot that never happens.

Stock and categories: the last two you cannot skip

Give every row a current stock count. Even a rough number lets the shop mark items out of stock automatically instead of taking orders you cannot fill, which is one of the fastest ways to lose a new customer's trust. Decide early whether you want stock tracked per variant or just a simple in-stock or out-of-stock flag, and tell your developer.

Categories are how customers browse. Group your products into a small, logical menu (Clothing, Footwear, Accessories) before the build, rather than dumping everything into one long list. Keep the names consistent, avoid twenty near-empty categories, and you will have a shop that is easy to shop.

What this checklist does not cover

This article owns the catalogue: the product data itself. Two neighbouring decisions sit just outside it and each has its own guide.

• Getting paid. How you actually collect money, from mobile options to on-site checkout, is a separate decision. See our guide on how to accept online payments in Zimbabwe.
• Delivery and shipping. How you charge for delivery, set zones and quote a price is its own piece of planning. That is why the spreadsheet captures rough weight or size per item, so the numbers are ready when you plan it. See planning delivery zones and shipping charges.

If you are still deciding whether to sell online at all, start with the broader overview of selling online in Zimbabwe, then come back here when you are ready to prepare the catalogue.

How this works with a TechTribe shop

TechTribe builds mobile-first shops for Zimbabwe businesses, and the cleaner your spreadsheet, the faster and cheaper the build goes. A scoped small online shop can be part of a Standard website at $550, while a larger catalogue with more variants, categories and custom features is a Premium build from $800 with a quote after we scope it. You can see what an ecommerce build involves before committing.

When we scope your shop, the first thing we look at is your product data. Bring the spreadsheet above, even half-finished, and we can tell you quickly whether your range fits a small shop or a custom build, where your data has gaps, and roughly how much loading it will take. That conversation is far more accurate than a guess based on "I sell about fifty things."

Your next step

You own your online shop the moment your products are clean, consistent and complete in one place. Before you ask anyone to build, open a spreadsheet, add the columns above, and fill a row for every item and every variant, with a photo named to match. That single file is the difference between a shop that launches in a couple of weeks and one that drifts for months waiting on missing prices and pictures.

When your catalogue is ready, or if you want us to sanity-check it first, get a quote for your ecommerce site and we will scope the build around the products you actually sell.

---

Author: Simon Updated: May 2026