A website for a business with many products

What a catalogue site has to do

Buyers of industrial products often arrive knowing what they need, such as a specific grade, material or standard, and want to confirm quickly that you can supply it. A catalogue site works when it answers these in order:

1. Do you make or supply what I need? Clear categories, and a product page for each item.
2. Is it the right specification? Properties, grades, sizes and standards, set out in a table that can be read on a phone.
3. Can I see the documents? A published data sheet, so the buyer does not have to ask for it.
4. How do I ask for a quote? A phone number and a WhatsApp link within one tap, on every page.

How the pages are organised

• Categories group products the way buyers think about them, not the way the factory does.
• Product pages are built from one template. The layout is shared; the content on each page, meaning its specification, its applications and its documents, is specific to that product. A page that repeats another with only the name changed does not help the buyer, and Google’s spam policies also single out large numbers of near-duplicate pages made to catch search phrases.
• Application pages explain where a product is used and what to choose. They answer the question a buyer has before they know which product they need.
• Enquiry routes are the same everywhere: call, WhatsApp, and a form that opens WhatsApp with the details filled in.

Two catalogue sites already live

I designed and built both of these and help manage them. The figures below are counts of content, taken from each site’s own sitemap on 9 October 2026. They show scale and structure; they are not traffic, ranking or sales results.

Samrat Poly Resins (samratpolyresins.in), an industrial manufacturer in Doraha, Ludhiana, English only.

• 302 URLs in the sitemap
• 51 products, each with a published data sheet
• 40 application guides

Samrat FRP Traders (samratfrptraders.com), an FRP materials trader in Biratnagar, Nepal, in Nepali and English.

• 676 URLs across two languages (338 each)
• 51 products in 9 categories
• 62 application guides

The Work page shows how each site looks and what it contains.

What this offer does not include

The packages publish your products as pages with specifications, documents and enquiry routes. Unless your written proposal says otherwise, they do not include: online payments or a shopping cart, customer accounts or price-on-request logins, a searchable or filterable product database, an assistant that answers product questions, or links to your stock or ERP software. Those need a backend, and they change the price and the upkeep; frontend, backend and what your site needs explains why.

What fits which package

A range of around twenty products with a few supporting pages fits Essential’s 20 to 30 pages. With fifty or more products and application guides, you are in the page counts of Growth (70 to 100) or Complete (100 to 200). Growth and Complete also include agreed SEO implementation, which for a catalogue means page titles, descriptions, headings and internal links planned across the whole structure. Essential is frontend only and includes none of it.

The pricing page lists exactly what each package includes.

What I need from you

For each product: the name, the specification, the applications, any standards it meets and the data sheet if you have one. For the business: the contact details, the areas you supply, and the photographs you are allowed to publish. The guide to what to prepare before a website project lists the rest.

If you also sell through a marketplace

Many suppliers get their first enquiries from a marketplace listing. A website of your own does a different job: your full range in your structure, your documents, your proof. The note on whether you need your own website or an IndiaMART listing, or both is a short decision guide, and how to organise a product catalogue website shows the structure I use, with a worked example.

Questions people ask

Can customers buy online?

A catalogue site is built for enquiries and quotation requests. Online payments, a shopping cart, customer accounts, price-on-request logins and links to stock or ERP systems are not part of any package unless they are agreed in your written proposal. The note on frontend, backend and what your site needs explains what each involves.

How many products can a site hold?

The package sets the number of published pages, and each product with its own useful content is one page. Essential covers 20 to 30 pages, Growth 70 to 100 and Complete 100 to 200.

Do you need the data sheets from me?

Yes. Specifications, data sheets and photographs are facts about your products, and only you can confirm them. I can plan how they are presented, but I cannot invent them.

Can the site be in more than one language?

Yes. Each language is a full set of content that someone has to write and check. One of the sites below runs in Nepali and English.

Where do quote requests go?

The enquiry form on a package website builds a message and opens WhatsApp with it, and phone links start a call. Nothing is stored on a server. Storing requests, e-mailing them or feeding a stock system is backend work and would have to be agreed in your written proposal.

Related Craft Notes

• Frontend, backend and what your site needsA backend is not a sign of a better website. It is extra machinery that stores data and runs rules. Here is when a business site needs one and when it does not.
• What to prepare before a website projectMissing material, rather than design or code, is a common reason a website is held up. Gather these items first and the project can move at the speed of the build.
• Images that load fast on a business sitePhotographs are usually the heaviest thing on a business page. Sizing them for the screen, reserving their space and describing them well makes a site faster and easier to use.
• How to organise a product catalogue websiteA catalogue works when a buyer can get from a need to the right product in a few clicks. This is a practical structure, with a worked example and honest limits for sites without a search engine of their own.
• Own website or IndiaMART listing: do you need both?A marketplace listing and your own website do different jobs. This is a plain framework for deciding what each should do for your business, and when the website matters more.
• What pages a business website needsA page earns its place by answering a question a visitor really has. Here is the core set, the pages that depend on your business, and a test for pages you can leave out.
• Titles, headings and links: a page checklistSearch engines and readers use the same few signals to understand a page. This checklist shows what to write for each, with examples of weak and clear versions.
• Catalogue website or online store: which one?Many businesses ask for an online store when they need a catalogue that brings in enquiries. The difference is who completes the sale, and it changes the cost, the risk and the provider you need.
• How a quote request should work on a catalogue siteA catalogue site succeeds when a buyer can ask for a quote in a minute and you receive what you need to answer it. This note covers the fields, the routes and the follow-up.