Pobedit Trading House

Task and context

An existing WordPress website for a carbide supplier was rebuilt with Next.js and Payload CMS. Engineers and purchasing teams need to find parts, check specifications and submit parameters or drawings for a quote. Staff need a maintainable catalogue and structured enquiries.

The solution

Catalogue and documents

Nested categories, name and number search, specifications, galleries and drawing previews support product selection.

Rod configuration

Customers choose a type, grade, dimensions and quantity and combine multiple line items. Prices appear when a matching price list is available; otherwise a quote is required.

Clearance items

CMS-managed products include quantities, prices, stock and documents. Selected items can be submitted in one enquiry.

Content management

Products, home page content, contacts and documents are edited in Payload CMS. Field labels and links to public pages guide staff.

Enquiry follow-up

New accepted enquiries with an email address can receive a confirmation message. Referral context accompanies the request for the team’s follow-up.

How it works

1. Select

   Find a product in the catalogue or search and review its specifications.

2. Configure

   Set the carbide grade, dimensions and quantity, then add the required configurations to the order.

3. Request

   Review the items, enter contact details and attach a drawing if needed. Submit after consent and CAPTCHA.

4. Follow up

   The server passes the request to the CRM. New accepted requests with an email address can receive confirmation; a manager handles the final terms.

How the parts connect

The website is the customer-facing entry point; Pobedit CRM is the team workspace. A server integration passes website enquiries to the CRM, where a manager continues the conversation.

The outcome

Company information, technical products, estimates and enquiries are brought together. Customers can move from product selection to a request, while the team maintains the content and handles incoming enquiries.

Under the hood

Next.js + Payload CMS

Public pages and content management share one project. Staff maintain products through forms rather than source-code changes.

Server-side enquiries

Request checks and the CRM integration run on the server, with submission status shown to the visitor.

URLs and SEO migration

Legacy addresses and metadata are handled during the platform change. Canonical, Open Graph and sitemap describe pages for search and sharing.

Scope and limits

The site creates technical enquiries, not automatically paid orders. Calculations depend on available price lists, and confirmation delivery depends on email services. A manager handles final terms and fulfilment.