The manufacturer's website with a catalog of products
The development of the manufacturer's website begins not with the layout, but with the nomenclature: how many series are in the products, how many sizes are there in each, and in what form are the characteristics. The structure of the catalog, the deadline, and the estimate depend on these three answers. Next comes the usual work: a product card with parameters and a passport, a filter by what is really chosen, a request for calculation instead of a basket. 25–45 working days from the approved TK. We name the amount after a free analysis of the nomenclature — it is a guess for him.
50% down payment, 2 rounds of edits, 30 day warranty
Metrics measured by us on live sites of corresponding scale.
after a free audit
Price
30
Guarantee
days after project sign-off
2
Measured manufacturer sites
live projects, measurements 31.07–01.08.2026
164
Site map without duplicates
addresses, 164 unique
208
The first response from the server
ms on the product catalog, 244 ms on the main one
106
Bilingual catalog
items were deployed in 230 addresses
25–45
Term
working days from the approved TK
50%
Conditions
down payment, 2 rounds of edits, 30 day warranty
Who it's for
Situations where this service delivers results
Scenario 1 of 5
Dealers are behind your models
The article is typed, and on the first page there is an intermediary catalog with your same line and its application form. The site returns this request to itself: address for the model, text parameters, your sales contact. In the analysis, we show exactly which models this has already happened.
We'll review your situation in a free audit
Scenario 2 of 5
The nomenclature exists, there is no machine type
The list lives in the technologist's head, in the price, and in the completed PDF, and all three sources are slightly different. Until the specifications are tabulated, the filter will not be assembled - so the first step is to check the list with your technical person, not the design.
Scenario 3 of 5
The buyer asks for a calculation, not a "buy" button
Equipment and materials are shipped according to the contract, with agreement on the volume and term. The basket is superfluous here: a form with a substituted series and standard size, a passport file and clear terms of delivery are required. The manager receives a request with parameters.
Scenario 4 of 5
One series, hundreds of standard sizes
Here the main thing is decided: the type size is a separate card or a variant within the series. The answer depends on the number of addresses, the type of filter and the amount of filling. Decisions are made before the design: redoing the structure after layout means redoing everything.
Scenario 5 of 5
The dealer network is growing, but there are no conditions on the website
A potential partner is looking for someone to write to and can't find one. A separate section with terms of cooperation, application and direct contact of the sales department captures this in one screen - and at the same time separates the dealer scenario from the retail one.
Cases
Tasks and results in numbers — all metrics measured by us
Ukrainian manufacturer of non-combustible wall panels
Task
Lay out the technical products in such a way that the designer and the tender buyer take the parameters themselves, without calling the manager.
Solution
Catalog on Next.js with product cards, calculator and full set of structured company data. Service sections are closed in robots, counters are set at the start-up stage.
Result
Zero duplicates: the sitemap has 164 entries and exactly the same number of unique addresses. The product catalog gives the first answer in 208 ms, the main one in 244 ms (median of two measurements); HTML is loaded in 429 ms with a weight of 528 KB. There are eight types of machine data — Organization, PostalAddress, Country, QuantitativeValue, SearchAction, WebSite, ImageObject, EntryPoint. The stack declared in the portfolio coincided with what the site gives. Measurement 01.08.2026.
B2B supplier of professional equipment for chocolate production
Task
Lay out the line of equipment according to performance and technical parameters in two languages and collect requests for calculations from the site.
Solution
A catalog site with a separate page for each item, a calculation request form, an expanded page for calculation conditions, GTM, GA4 and call tracking.
Result
The bilingual catalog of 106 items was expanded to 230 addresses: the map is compiled with an index of four files, 106 products and 9 content pages for each language. Measurements 07/31/2026: server responds in 351.4 ms, HTML is loaded in 490.4 ms at 297.6 KB. The shipping and payment page lists six payment methods—more than any other project we've measured. There are only three types of structured data: WebSite, SearchAction, ImageObject. Separately, a discrepancy was recorded - in the portfolio, the stack is indicated as WordPress, and the site uses Shop-Express CMS 8x.
What's included
Complete list of work and what you get as a result
Product catalog: series, subdivisions, product card with parameters and photo - the buyer reaches the desired size without a call
Filter according to the characteristics that are really chosen - power, size, material, performance, and not all the fields in a row
Passports, certificates and drawings in files on a card: the designer takes them himself and does not write you a letter
Invoicing request form with transfer to mail and CRM - cartless scenario for products shipped under contract
Section for dealers: terms of cooperation, application form, direct contact of the sales department
Technical SEO: CNC for models, canonical, unique title with article number, site map without duplicates
JSON-LD micro-markup: Organization, Product, QuantitativeValue, BreadcrumbList — parameters are given by machine, not by image
GTM and GA4 analytics with the events of loading the passport and sending the request - you can see which series is driving the appeal
Transfer: access, written instructions for adding the product, going through the administration with your responsible person
Terms of work: 50% down payment, two rounds of edits at the design stage, 30 calendar day warranty after acceptance
When this service isn't right
What's not included — so there are no surprises at delivery
Extracting characteristics from paper catalogs and scans in excess of the agreed volume
Technical copywriting of product descriptions
3D visualization and renderings of products
Hosting, domain, compliance certificates
Promotion, advertising and dealing with the dealer network after the launch
Process steps
Transparent stages with approval at every step
Total duration:25–45 days
1
Analysis of nomenclature and TK
3-5 working days
We compare the list of products with your technologist, decide the fate of the standard size, collect the characteristics in one table. The output is a TK, based on which the estimate is calculated and the work is accepted.
2
Directory structure and prototype
3-5 working days
Series tree, fields of the product card, set of characteristics for the filter, path to the calculation request. We agree to the design — after the layout, it is already a rework of everything.
3
Design
5-9 working days
Home, series section, product card, dealer section, request form. Here we fix the target weight of the page: in the manufacturer's website we measured, the HTML weighs 528 KB.
4
Site assembly
8-13 working days
Layout, catalog, filter by parameters, calculation form with transfer to CRM, dealer section, roles in admin, service pages.
5
Filling of products and documentation
4-8 working days
Cards, specifications, photos, files of passports and certificates. We check the number of cards with your list and double-check the site map before launch, not after.
6
Analytics, testing, transmission
2-5 working days
GTM and GA4 with the events of loading the passport and sending the request, micro-markup, measurements of the first server response, the passage of admin with your person, transfer of accesses.
Free analysis of the nomenclature and the current site
For the manufacturer, the main question is not "what design", but "how to put the products on the site so that they are found by their characteristics." Therefore, the audit begins with the nomenclature, and not with the layout.
What we measure
How many items actually and how they are groupedWe analyze your list: series, standard sizes, execution. The structure of the catalog and the volume of work depend on whether the typeface is a separate card or a variant inside the card.
In what form are the technical characteristicsA table in Excel, a catalog in PDF, passports of products - all these are different sources in terms of labor intensity. From the table, the characteristics fall into the filter, from the PDF they must first be extracted.
The status of the existing site, if anyHow many addresses are in the sitemap and how many of them are unique, the first response from the server, the weight of the HTML, what types of structured data are given. On the manufacturer's site we measured, there were 164 addresses without a single duplicate - this is a guideline for a normal state.
Who is your visitor: dealer or end customer?It depends on whether the main thing on the card is the price and the basket or the technical passport and the form of the calculation request. It is possible to mix both scenarios on one card, but this is a separate amount of work.
Which is already indexed under your brand nameLet's see what pages the search for the brand name and models returns, whether the dealer's catalog is in the output instead of your site.
What you get
The scheme of the product catalog: series, subdivisions, depth, which characteristics go into the filter.
Measurements of the existing site with a list of defects found, if the site already exists.
An estimate of the amount of work by stages with an explanation of what exactly pulls the amount up.
A 30-40 minute conversation with your technologist or product manager.
Timeline: 3–5 working days: we analyze the product range longer than a regular site
Why is it free
Because without analyzing the nomenclature, the amount would be fictitious: the difference between a catalog of 60 items and a catalog of 600 standard sizes is not in percentages, but in times. The document is yours in any case.
What's next
After the audit, we give an estimate with a breakdown by stages and calendar dates. If it turns out that you don't need a new site, but a catalog reconstruction on the existing one, let's say it directly.
Short form: your contact and site URL
Contract, act and 30-day warranty
Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.
Sole proprietor & bank transfer
The contractor is a registered sole proprietor. Payment by invoice with closing documents.
Rights & access — yours
Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.
Client portal instead of email chains
During the project you get access to a portal: contracts, invoices, acts and project status in one place.
European clients
Among our work — projects for Norway, Bulgaria, Moldova and Spain.
Verifiable numbers
Every case in the portfolio comes with a link to a live site and a technical measurement.
Audit first, then pricing
There is no price list on the site intentionally: the scope of the same work differs multiples between clients.
We say "no" when unsure
If the task isn't ours or the deadline is unrealistic — we tell you upfront.
Did not find your case?
Describe how it works on your side — we will tell you whether “Development of the manufacturer's website” fits and what it means in your situation. No brief and no call: one question, one answer.
What affects the price
Why two seemingly identical tasks are priced differently
The depth of the nomenclatureSixty items and six hundred type sizes — the difference is not in percentages, but in times. We count not the pages, but the cards after deciding the fate of the font size.
The view in which the characteristics existExcel or accounting downloads fit into the filter almost without manual work. The Verstan PDF is analyzed semi-automatically. Scanning of the paper catalog is done by hand, and this is a separate stage.
Who is your buyer on the siteThe dealer needs conditions, documents and a sales contact, the end user needs parameters and calculations. One scenario is cheaper than two: you can combine them on one card, but this is work, not a tick.
Volume of documentationA series passport is just a file. A passport for each standard size with its own values in the table is already a storage and binding system, and it takes time.
Language versionsThe second language adds not a translation of the interface, but a second set of cards, characteristics and meta-data, which must then be maintained. This is a constant expense, not a one-time expense.
Communication with the accounting systemOne-time export of the range is cheaper than constant exchange. And the exchange does not correct the accounting: if there is a resort in the database, the site will show it neatly and quickly.
Technologies & integrations
What we build on and what it connects to
Stack
Next.js — the directory is given as ready-made HTML, so the characteristics are visible even without JavaScript; limitations: the template is managed by the developer, not the content manager
TypeScript — types in attribute fields catch inconsistencies even before assembly; limitation: the entry threshold for a third-party contractor is higher
PostgreSQL - type sizes are structured, the filter is collected from fields, not from text
WordPress is an alternative when the directory is managed by your marketer himself; limitation: on hundreds of sizes, the filter is kept on plugins
nginx and HTTP/2 — parallel rendering of photos and PDFs; limitation: speed removes technical loss, but does not create demand for products
HTTPS with HSTS and Cloudflare — the browser doesn't warn against you; limitation: the certificate encrypts the channel and does nothing else
Integrations
Google Tag Manager
GA4
Google Maps
reCAPTCHA
Telegram bot for applications
KeyCRM
Uspacy CRM
1C / BAS — export of the nomenclature
eSputnik
The manufacturer's website against the card on the marketplace and the dealer's catalog
How this option differs from the alternative
Marketplace / dealer catalogOur approach
Who describes your productsMarketplace: retail site template. Dealer: His text, often from an older version of the lineupyou: parameters, performance, passport and certificate in the fields of the card
Technical documentationMarketplace: there is no space for passports. Dealer: Will mail on requestfiles on the card, available without registration and without correspondence
Request by model article numberMarketplace: your model is next to the competitor's analogues. Dealer: he is in the issueown CNC address and unique title for each model
A scenario without a shopping cartMarketplace: Buy button only. Dealer: the application goes to him, not to youcalculation form with substituted series and standard size
What can be seen about the demandMarketplace: aggregated marketplace reports. Dealer: don't see anythingGA4 and Passport Download Events: It's clear which episode is being watched
What we need from you
We can't start without this — best to prepare in advance
1The list of products divided into series and standard sizes is in a table, even a draft.
2Technical characteristics in machine form: Excel, CSV or download from the accounting system.
3Photo of products from 1,200 px on the long side, preferably on a uniform background.
4Documentation files: passports, certificates, drawings - in the form in which you issue them to buyers.
5The answer to the question to whom you sell from the site: dealers, end buyers or both.
6One person from the technical side with the right to confirm the correctness of the characteristics.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ
Most frequently asked questions — with concrete answers
We have 400 font sizes, is that 400 pages?
Not necessarily. The typeface can be a single card or a variant within a card series. The first option gives more addresses for requests with a specific article, the second - a more compact catalog. We choose by analysis: we see if your buyer really dials the article. The main thing is not to mix both approaches in the same directory, this is where duplicate addresses come from. And immediately a fair limit: cleaning duplicates does not add traffic, it stops scattering it, and the number of pages in the index after cleaning may even drop for a while.
Do we even need a basket?
Often not. If the products are shipped according to the contract or through dealers, the basket interferes: the buyer must request a miscalculation and pick up the passport of the product, and not issue a payment. In the catalog of the equipment we measured, it is done just like that - a request form, and next to it on the conditions page, six calculation methods are listed for those who are already ready to pay. Just don't get confused: an account on the site does not make you a supplier for a legal entity. Then, all the same, the contract, postponement and availability according to the volume.
The characteristics are only in the PDF catalog - what to do?
First extract them into a table. This is a separate stage, and its complexity is determined by the file itself: the layout with equal tables is sorted almost automatically, the scan of the paper catalog is done by hand, line by line. That's why we ask you to send the files themselves during the analysis, and not to describe them in words: you can see from the files whether it's two days of work or two weeks. Without a machine view of the characteristics, the filter will not be collected - a set of pages with pictures will be obtained.
Will they find us by the model name?
No one guarantees a position, and we will not. Technically, we cover everything: your own CNC address for the model, a unique title with an article number, parameters in HTML text instead of a picture, Product markup. But the sitemap does not guarantee indexing - Google writes it directly, and the real number of indexed pages is visible only in your Search Console, which we do not have access to by default. The manufacturer's most frequent problem is not in optimization at all: in issuing its models, dealer sites are behind it. This can be seen in the analysis in half an hour.
How long does development take and what does the deadline depend on?
25–45 working days from the approved TK. Nomenclature analysis 3–5 days, structure and prototype 3–5, design 5–9, assembly 8–13, product and documentation pouring 4–8, analytics with testing and transfer 2–5. The deadline is not counted from the signature, but from the date when we received the specifications in machine form: until then, only the design moves.
Who will add new products after launch?
Your product manager through admin. At the show, we go through the addition of the product using a live example: card, characteristics, documentation files, appearance in the filter and on the site map. If the nomenclature is updated in batches, we set up import from your table or export from accounting - this is a separate volume of work. And the limit here is this: the exchange does not correct the accounting. If there is a resort in the system, the site will show it neatly and quickly.
Where to put passports and certificates?
Files on the product card, next to the characteristics, without registration and without correspondence with the manager. Numerical parameters are duplicated with the QuantitativeValue markup, so that the power or dimensions are given by machine. Just don't expect the position markup: it doesn't raise the site and doesn't force the search to show the extended snippet — it decides for itself. And you can mark only what is actually on the page: markup the non-existent is a risk of manual sanctions.
Is a second language necessary if we are thinking about exporting?
Technically, this is not a duplication of pages, but a second set of cards, characteristics and meta-data that must be maintained further. In the hardware catalog we measured, the two language versions gave 230 addresses from 106 items. But the translation of the interface is not yet a market entry: it requires local payment, delivery, support and prices, the site closes only the storefront. And the machine translation of the technical catalog does more harm than good — the buyer sees that they are not being talked to seriously.
How to understand that the site is working if the transaction is closed with an invoice?
We measure what precedes the bill: sending a calculation request, uploading a passport, viewing a series page. We put these events in GTM and GA4 at the launch stage, not after complaints. Next, a fair margin: GA4 shows a trend, not an accounting truth. Blockers, consent mode, and browser restrictions on cookies eat up part of the data, so you have to compare the numbers with real deals deliberately - by hand, based on the dates of the requests.
Send the product list and any file with specifications.
In response, there is a diagram of the catalog with a division into series and standard sizes, measurements of your site, if there is one, and an estimate of the works by stages with dates. If you need a rebuild of an existing directory rather than a new site, let's say so in the first email.
From measured casesZero duplicates: the sitemap has 164 entries and exactly the same number of unique addresses
There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.