Ecommerce Website Development in Pune: Preparing Your Product Catalogue Data Before the Store Is Built

Ecommerce Website Development in Pune: Preparing Your Product Catalogue Data Before the Store Is Built

The fastest way to delay an online store is to start the build before the product data is ready. Ecommerce website development in Pune, or anywhere else, rests on a spreadsheet that most businesses have not yet created: one clean row for every product and variant, with a unique SKU, a title, a description, a price, attributes, images and category, in a form that can be imported in bulk. If that sheet exists when development begins, the store can be loaded, tested and launched on schedule. If it does not, the developer will spend weeks waiting for photographs, chasing sizes and reconciling three versions of the price list, and you will pay for that waiting.

This guide is for a retailer, distributor or D2C brand about to commission an online store on Shopify, WooCommerce or a custom platform. It walks through the catalogue data you need, how to structure SKUs and variants, how to prepare images and descriptions, the traps that break imports, and a practical timeline for getting the data ready in parallel with design. It is about building the store; it does not cover shipping, tax filing or payment operations.

Why catalogue data is the real critical path

When a store project is planned, the visible milestones are design approval, development and launch. The invisible one is data readiness. A store with fifty simple products can be loaded in a day. A store with five hundred products, each in several sizes and colours, with inconsistent names and photographs shot over three years, can take longer to prepare than to design.

Data quality also shapes the finished store in ways customers notice:

• Search and filters only work if attributes are consistent. "Navy", "navy blue" and "N. Blue" become three separate filter options.
• Product pages convert better when titles, descriptions and images follow one pattern. Our product page checklist for Indian online stores covers what each page should show.
• Category structure affects navigation and SEO. See our guide on site search and category navigation.
• Wrong variant data leads to wrong stock levels, and overselling is a customer-service problem, not a technical one.

Treat the catalogue as a deliverable with an owner and a deadline, the same as the logo or the domain.

Step 1: Decide what counts as a product and what counts as a variant

Before opening a spreadsheet, settle the model. A product is the item a customer thinks they are buying: a cotton kurta, a steel water bottle, a set of ceramic mugs. A variant is a specific version of that product: size M in blue, 750 ml in matte black. Each variant has its own SKU, price (sometimes), stock count and barcode.

Common mistakes:

• Listing each colour as a separate product when customers expect to switch colour on one page. This floods category pages with near-duplicates and splits reviews.
• Merging genuinely different items into one product with a variant dropdown, such as a phone case and a charger, because they share a brand. Customers do not search that way.
• Using variants for things that are not stock-keeping differences, such as gift wrapping or engraving. Those are usually options or add-ons, handled differently by each platform.

A reasonable test: if customers compare them side by side before choosing, they are variants of one product. If they choose between them as different things, they are separate products. Check platform limits as well, since each ecommerce platform has a maximum number of options per product and variants per product. Look up the current limits for your chosen platform before designing a catalogue with many combinations.

Step 2: Build a SKU scheme you can live with

A SKU (stock-keeping unit) is your own internal code for a variant. It appears in the inventory, orders, invoices, packing slips, marketplace listings and your accounting system, so it should be designed once and kept.

Good SKUs are:

• Unique. One code, one variant, never reused even if the product is discontinued.
• Readable. A person can tell roughly what it is: KRT-COT-NVY-M for a cotton kurta, navy, medium.
• Stable. They do not change when a product is renamed or moved to a new category.
• Free of spaces and special characters. Spreadsheets, scanners and platforms handle letters, digits and hyphens most reliably.
• Consistent in length and order. Category, product, attribute, size: always in the same sequence.

If you already have SKUs in a billing or ERP system, reuse them. The store should speak the same language as the rest of the business. If you sell on marketplaces as well, keep one master SKU and map marketplace codes to it, rather than inventing a second set.

Step 3: The master sheet, column by column

Create one spreadsheet, one row per variant, and fill these columns. Names vary by platform, and each platform publishes its own import template, so download the template for your platform early and align your sheet to it. The following are the fields almost every store needs.

Identity and grouping

• Product handle or parent ID: a code shared by all variants of the same product, so the importer knows they belong together.
• SKU: unique per variant.
• Barcode (EAN/UPC/GTIN) if you have one. Required for some feeds and marketplaces; leave blank rather than invent.
• Brand.
• Product type or category.

Display

• Title: see the section below.
• Short description: one or two sentences for listing pages.
• Long description: features, materials, dimensions, care, what is in the box.
• Tags or collections: how products are grouped for merchandising.

Commercial

• Price and, if applicable, compare-at (original) price.
• Cost price (internal; optional but useful for margin reports).
• Stock quantity and, if applicable, stock location.
• Weight and dimensions: needed for shipping calculation. Keep one unit, such as grams and centimetres, throughout.
• Tax category or HSN code: record it as an attribute so your accountant can configure invoicing; the tax treatment itself is a matter for your chartered accountant, not the catalogue.

Attributes (the filter fields)

• Colour, size, material, fit, capacity, pack size, and any category-specific attributes such as fabric or power rating. Use a controlled list for each. Decide the allowed values in advance: "Navy", never "navy blue".

Media

• Image file names or URLs, with the first image as the main one.
• Alt text for each image (see below).

SEO fields

• Page title and meta description, or a rule for generating them.
• URL handle: short, lowercase, hyphenated.

Step 4: Write titles and descriptions to a pattern

Choose a title formula and apply it to every product. For example: Brand + product type + key attribute + variant detail, such as "Aarav Cotton Straight Kurta, Block Print". Short, specific, no capital-letter shouting, no keyword lists. A shopper scanning a category page should be able to tell products apart from titles alone.

For descriptions, write for a person first. A useful structure is:

1. One or two lines on who the product is for and what it does.
2. Key features as a short bullet list.
3. Specifications: material, dimensions, weight, capacity, care instructions, what is included.
4. Anything that prevents a return: sizing notes, colour variation warnings, compatibility.

Do not copy manufacturer or marketplace descriptions word for word. Duplicate text across many sites gives search engines no reason to rank yours, and manufacturers' text is often written for a different market. If you have hundreds of products, prioritise: write careful descriptions for your best sellers and top categories first, and use a clean templated description for the long tail, improving it over time. Do not generate hundreds of near-identical descriptions in bulk for the sake of volume; thin, repetitive pages help neither shoppers nor search results.

Step 5: Prepare images before development starts

Photography is usually the longest lead-time item. Decide early what you need per product:

• A main image on a clean background.
• Additional angles, a close-up of texture or detail, and an image showing scale or use.
• For variants, an image per colour at minimum.

For consistency, agree specifications: aspect ratio (a single ratio across the store, such as square or 4:5, looks more professional than a mixture), minimum resolution, background, and file naming. A good file name is the SKU plus a number: KRT-COT-NVY-01.jpg. It makes mapping images to rows automatic and helps you find the right file in a year.

Compress before uploading. Large uncompressed photographs slow product pages, and speed matters for both shoppers and search. Modern formats such as WebP are widely supported, and most platforms will convert and resize on upload, but starting with sensible file sizes still helps. For help planning shoots, see our guides on brand photography for ecommerce and photography costs in India.

Write alt text for every image: a plain description of what the image shows, such as "Navy cotton kurta with white block print, front view". It helps screen-reader users and gives search engines context. Describe, do not stuff keywords.

Step 6: Structure categories and navigation

Sketch your category tree on paper before entering anything. Aim for a hierarchy two or three levels deep: broad category, sub-category, and perhaps a type. Each product should live in one primary category and may appear in extra collections such as "New arrivals" or "Gifts under a stated price".

Rules that avoid headaches:

• Use the names customers use, not internal jargon. Check what your shoppers type into search and what appears in your Google Search Console queries.
• Avoid very deep trees. If a shopper needs five clicks to reach a product, reorganise.
• Keep category names unique and meaningful. "Accessories" is too broad to be useful; "Phone cases" is clear.
• Decide filters per category. Shoes need size and colour; mugs need capacity and material. Do not offer filters that most products leave blank.

Step 7: Clean the data before you hand it over

Run through the sheet with these checks. Most of them take minutes in a spreadsheet and save days in the importer.

1. Duplicate SKUs. Sort by SKU and look for repeats, or use a duplicate-highlighting rule.
2. Blank required fields. Price, SKU, title and at least one image.
3. Inconsistent attribute values. Filter each attribute column and merge variants of the same word.
4. Text encoding and special characters. Curly quotes, ampersands and non-English characters can break CSV imports. Save as UTF-8.
5. Number formats. Remove currency symbols and thousands separators from price cells; use plain numbers.
6. Hidden formatting. Leading or trailing spaces, line breaks inside cells, and merged cells all cause trouble. Unmerge everything.
7. Image mapping. Every row that needs an image has a file that exists and a name that matches.
8. Stock realism. Do not enter placeholder stock to make products appear available.

Import a small batch of ten to twenty products first, check how the pages and filters look on a test version of the store, and only then run the full import. That cycle usually finds problems you would not see in the spreadsheet.

Migrating from another platform or marketplace

If you already sell on a marketplace or an older website, an export is the starting point but rarely the finish. Exports often carry marketplace-specific titles stuffed with keywords, mixed units and missing attributes. Use the export as raw material and clean it into the master sheet rather than importing it directly.

If you are moving from one store platform to another, also plan URL redirects from old product and category addresses to the new ones, so existing search rankings and bookmarks continue to work. Our Shopify and WooCommerce migration checklist lists the steps, and the principles in migrating a website without losing SEO apply to stores as much as to any other site. Preserve customer, order and review data where the new platform allows it, and tell your developer early if you need historical orders moved, because it affects the plan.

Timeline: running data prep in parallel with design

A realistic project runs catalogue preparation alongside design instead of after it. The pattern below uses relative weeks; the real durations depend on catalogue size and how many people are working on the data.

• Before kick-off: decide platform, product and variant model, SKU scheme, category tree and attribute lists.
• While design is in progress: complete the master sheet for the first batch of products, commission or finish photography, and write descriptions for priority products.
• During development: run the first test import, review product pages, fix data issues, and complete the remaining catalogue in batches.
• Before launch: final import, stock sync, spot checks on every category, and a review on phones.
• After launch: improve descriptions and images for best sellers using search and sales data.

If the sheet is not ready by the time development reaches the product templates, say so early. A developer can build with dummy products, but the design and filters should be reviewed with real ones.

Who should own the catalogue

Nominate one person on your side as the catalogue owner. They are the single point of contact for product questions, they approve the master sheet, and they decide what happens when a supplier changes a specification. Developers should not be guessing whether a missing weight is zero or unknown.

After launch, define how new products will be added and by whom. A documented procedure (fill the template, check the list, import or add manually, review the live page) avoids the slow decay in data quality that most stores suffer.

Where this fits in the wider build

Catalogue data is one input to the project. The decisions around platform, features and integrations are covered in our overview of ecommerce website development in Pune, and the comparison of Shopify, WooCommerce and custom builds will help you choose the platform that suits your catalogue size and variant complexity.

Govindani Infotech Pvt. Ltd. builds online stores from our office at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009. Our ecommerce website service includes help structuring the catalogue and import, and our website creation service covers the surrounding site. If you would like us to review a sample of your product sheet before a build begins, message us on WhatsApp or use the contact page.

Frequently Asked Questions

What product data do I need before building an online store?

For every variant: a unique SKU, title, description, price, stock quantity, weight and dimensions, category, attributes such as colour and size, and at least one good image. Having these in a clean spreadsheet before development starts is the single biggest factor in launching on time.

How should I structure SKUs for an ecommerce website?

Use unique, readable, stable codes without spaces or special characters, in a consistent order such as category, product, colour and size. Reuse your existing billing or ERP codes if you have them, and never reuse the code of a discontinued variant.

What is the difference between a product and a variant?

A product is what the customer thinks they are buying, such as a kurta. A variant is a specific version of it, such as size M in navy. Each variant has its own SKU and stock count but shares one product page.

How many products should I launch with?

Launch with the products you can present well: accurate data, good images and real stock. A smaller, complete catalogue serves customers better than a large one with thin pages. Add the rest in batches after launch.

Can I use manufacturer descriptions for my products?

You can use the facts, but rewrite the wording. Identical text appears on many sites and gives search engines little reason to prefer yours, and manufacturer copy is often written for a different audience. Start with your best sellers and improve the rest over time.

Related reading: Syncing Stock Between Your Shop, Billing Software and Online Store Without Overselling.