Case study · Web application
Case Study: A Catalogue and Admin Platform for an International B2B Alloys Manufacturer
An international manufacturer of precious-metal alloys needed one platform to present its products to buyers worldwide and manage that content itself. We built it as a single repository: a Next.js 16 site with product categories, product pages, industry pages, quality information, downloads and a gallery, plus an admin panel, backed by a Go REST API on PostgreSQL and Redis. Everything runs in containers behind Nginx, with only the web ports exposed.
By Web Your Vyavsay team · Published
Drafted with AI assistance. Claims are checked against the sources listed below and reviewed by our team.
What the business needed
- A catalogue that buyers can browse by product category and by the industry they work in.
- Detailed product pages, quality information and downloadable documents for technical buyers.
- An admin the team can use to add and update products and categories without a developer.
- Pages that load quickly and can be found through search in many countries.
What we built
| What it does | |
|---|---|
| Public website (Next.js 16, React 19) | Home, products by category and product detail, industries, quality, downloads, gallery and contact pages |
| Admin panel | Sign-in, product and category management for the team |
| API (Go with Fiber) | A REST API that serves the catalogue and handles admin changes |
| Data (PostgreSQL and Redis) | Products and content in PostgreSQL, with Redis alongside it |
| Delivery (Nginx and Docker) | Nginx in front of the site and API, serving uploaded files; only ports 80 and 443 are exposed |
Why this stack
Next.js renders the catalogue on the server, so product pages arrive complete for buyers and search engines. A separate Go API keeps the business logic fast and independent of the front end, and running everything in containers behind one reverse proxy keeps the server’s exposed surface small.
What other manufacturers and exporters can take from it
- Organise the catalogue the way buyers search: by product and by application or industry.
- Give technical buyers downloadable specifications and quality documents on the product page.
- Let the sales team update products themselves, so the website never lags behind the price list.
Frequently asked questions
Why use Next.js for a B2B catalogue?
It renders pages on the server, so product details are in the HTML that buyers, search engines and AI tools receive, and it handles large catalogues with category and product routes cleanly.
Why a separate Go API instead of doing everything in Next.js?
A separate API keeps business rules in one place that other channels, such as a mobile app or an ERP integration, can reuse later, and Go handles that work efficiently.
Can the sales team update products without a developer?
Yes. The admin panel lets the team manage products and categories directly.
Does a manufacturer need a custom platform rather than a website builder?
Not always. A website builder is enough for a small brochure site. A custom platform pays off with large catalogues, technical documents, several languages or integration with internal systems.