• Online Stores

Online store of garden equipment and spare parts

The development of an online store for garden equipment rests not on equipment, but on spare parts: two hundred lawn mowers and trimmers is a small catalog, and details for them - tens of thousands of pages. That's why we design a garden equipment store from the nomenclature: first we count how many addresses the catalog will give together with spare parts and how many nesting levels are needed for the buyer to reach his knife or filter. The second lever is the season: before the peak, the directory should have already been bypassed by the search engine, and not just flooded.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Niche stores were measured
3 living stores of garden equipment and tools, measured on 07/31/2026
after a free audit
Price
30
Guarantee

days after project sign-off

3
Niche stores were measured

living stores of garden equipment and tools, measured on 07/31/2026

from 8,690 unique addresses to 59,189; in one, it was not possible to count from the outside
Distribution of catalogs
547.2-840.5
The first response from the server

ms on the same engine

252.6–454.5
Weight of the HTML page

KB

30–50
Term

working days from the approval of the TK

we call after a free audit of the directory
Cost
50%
Conditions

advance payment, 2 rounds of edits, 30-day warranty period

Who it's for

Situations where this service delivers results

Scenario 1 of 4

Technicians have two hundred items, and they ask about spare parts

The call "are there knives for this model?" the manager closes it manually, because on the website the details are in a separate list without connection with the equipment. Linking parts to models brings this answer to the catalog: the buyer walks in from his lawnmower and sees compatible items. The fair limit of the mechanism: the binding does not add demand and does not work until the articles and characteristics in the cards are brought to order - no filter will do this for you.

We'll review your situation in a free audit
Cases

Tasks and results in numbers — all metrics measured by us

the official online store of garden tools of the world brand

Task
Sell ​​a full range of garden tools — watering systems, lawn mowers, secateurs, battery-powered equipment and accessories — with a detailed catalog, specifications and delivery across Ukraine.
Solution
Store on OpenCart 3.x with nginx with HTTP/2 and HSTS. Eight payment methods and four delivery services, including delivery through the marketplace. Two language versions with x-default, upload to the site, feedback module.
Result
8.57 MB Sitemap: 33,493 records for 8,690 unique addresses — about 3.85 copies per address. Of them, there are 81 category nodes and 8,609 sheet pages, the catalog is about 8,600 cards. TTFB 789.4 ms including redirect to the language branch, HTML weight 323.9 KB. Found: only one of the two announced language versions was included in the sitemap.

online store of garden tools for private buyers

Task
Sell ​​irrigation systems, lawn mowers and trimmers, battery and hand tools with a selection of kits for various tasks.
Solution
Shop on OpenCart 3.x using nginx with HTTP/2. LiqPay, cards, payment by details and cashless settlement with or without VAT; four carriers, including marketplace shipping. Layout optimized for weight: almost all images with delayed loading.
Result
TTFB 547.2ms, full HTML load 676.7ms at 252.6KB - the lightest page among the stores in the batch; 66 of 69 delayed loading images. Defect found: /sitemap.xml gives HTTP 200 with an empty body, sitemap feed — 404, so it was not possible to measure the volume of the directory from the outside.

online store of an official seller of garden equipment and spare parts

Task
Maintain a catalog of machinery and spare parts with deep nesting, filters by engine power and type, and up-to-date balances.
Solution
OpenCart 3.x store with spare parts catalog up to four levels deep, eight payment methods and four delivery options. The sitemap is declared in robots.txt and divided into submaps.
Result
Commodity sub-maps: 18 files of 3,000 addresses plus 1,321 — a total of 55,321 commodity addresses; categorical 3,868, total 59,189. TTFB 840.5 ms, full load 997.4 ms with an HTML weight of 454.5 KB. The six types of JSON-LD are the richest markup of the batch.
What's included

Complete list of work and what you get as a result

  • Equipment catalog with a separate branch of spare parts and consumables — depth of nesting under your nomenclature, not under the theme template
  • Linking spare parts to models: the buyer enters from his machine and sees compatible parts, the manager does not answer this manually
  • Filter by power, engine type, working width and tank capacity — what makes the models really different
  • Price import with field mapping and schedule update of balances: during the season, the price changes more often than the manager has time
  • Checkout with payment by card, installments, post-payment and non-cash invoice with VAT - for all three types of buyers
  • Delivery: Nova Poshta, Meest Express, Ukrposhta, delivery through the marketplace, self-delivery — with the choice of branch in the order
  • Technical SEO: CNC, canonical on the filter combination, site map with submaps — so that a large catalog does not eat itself with duplicates
  • JSON-LD micro-markup: Store, Organization, Product, BreadcrumbList — so that store data does not conflict with each other
  • Analytics: GTM, GA4, cart and purchase events - configured before seasonal advertising starts, not after
  • Transfer: access, written instructions, passing the administration with your manager on a live order
  • Terms: 50% down payment, two rounds of edits at the design stage, warranty period of 30 calendar days
When this service isn't right

What's not included — so there are no surprises at delivery

  • Compilation of explosion diagrams and tables of compatibility of spare parts, if they are not in the manufacturer's data
  • Service accounting of repairs as a separate system
  • Filling the catalog manually beyond the agreed volume
  • Advertising in the post-launch season
  • Hosting, domain, acquiring
Process steps

Transparent stages with approval at every step

Total duration:30–50 days

  1. Catalog audit and technical task

    3-5 working days

    We calculate the volume with spare parts, analyze the price and the current site, fix the list of payments and carriers. The output is a TK, based on which the estimate is calculated and the work is accepted.

  2. The structure of the catalog and the diagram of binding spare parts

    4-6 working days

    Category tree with parts branch, set of characteristics for filter, model-part relationship rule by compatibility table or by articles. We agree to the design.

  3. Design

    5-8 working days

    Home, category, equipment card, details card, shopping cart, checkout. Here we fix the target weight of the page: in the measured niche stores, HTML weighs from 252.6 to 454.5 KB.

  4. Assembly of the store

    8-12 working days

    Theme layout, catalog and filter, shopping cart and checkout, admin roles, payment, shipping and return pages. In parallel, we are preparing a site map scheme with submaps.

  5. Import of equipment and spare parts

    5-9 working days

    Mapping of price fields, filling in batches through the console, binding of parts to models, comparing the number of cards using two methods, schedule for updating prices and balances.

  6. Integrations, analytics, markup

    3-5 working days

    Payment and carriers, marketplace feed, GTM and GA4 with cart and purchase events, JSON-LD, sitemap declared in robots.txt.

  7. Inspection for the season, transmission, start-up

    2-5 working days

    End-to-end running of the order from the shopping cart to the TTN, measurements of the first response and weight of HTML on the category page, passing the admin check with the manager, transfer of accesses.

Free pre-season audit

In garden equipment, the error in the estimate is almost always in the spare parts: there may be two hundred items of equipment, and tens of thousands of parts for it. The audit gives an exact figure before we agree on the money and the term.

What we measure

  • Catalog volume including spare partsWe count on the site map and cross search. In the hardware and parts store we measured, the product subcards yielded 55,321 addresses — 18 files of 3,000 plus 1,321.
  • Depth of nestingHow many levels are needed for the buyer to reach the desired detail. In the hardware and spare parts store we measured, the catalog is expanded to four levels of nesting — otherwise, knives, filters, and fittings that differ in size fit into one pile.
  • Site map statusDoes she exist at all? In one of the three measured niche stores, /sitemap.xml gives an HTTP 200 with a body of zero bytes, and the backup feed is 404: formally the file exists, but in fact the search engine receives zero addresses. In the neighboring store, the opposite extreme is 33,493 records for 8,690 addresses.
  • Speed ​​under seasonal loadThe first response and the weight of HTML. Measured benchmarks of the niche: from 547.2 ms on a light catalog to 840.5 ms on a catalog of 55 thousand product addresses.
  • Checkout and carriersHow many payment and delivery methods are connected. In two of the three measured niche stores, there are eight payment methods and four carriers, in the third - five and four; all three carriers have marketplace delivery.
  • Mobile shareIs there a viewport and how heavy is the category page on the phone - during the season, most orders come from there.

What you get

  • Document with numbers: parts catalog volume, category depth, sitemap status, speed, HTML weight.
  • An estimate of how many nesting levels your nomenclature needs.
  • List of technical findings of the current site.
  • Conversation for 30–40 minutes on the document.

Timeline: 2–4 working days, up to 5 in the season

Why is it free

Because the number of spare parts is a number that cannot be guessed from the outside, and it determines both the term and the amount. It is faster to calculate it than to argue about a fork. The document is yours regardless of who will make the store.

What's next

After the audit, the amount and term by stages with calendar dates taking into account the season, then the contract, bill and act.

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 an online garden equipment store” 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

  • How many addresses will the catalog give with spare partsThe main lever. In the measured niche stores, the range is from 8,690 unique addresses to 59,189 - these are different projects in terms of the term and scope of work, although outwardly both are "garden equipment stores". We calculate the number at the audit using two methods, because a guess here costs weeks.
  • Price sourceMachine CSV or XML with SKU, price, balance and specifications is a field mapping. PDF from the manufacturer or a photo of the price - manual disassembly, a separate stage and a separate line of the estimate.
  • Compatibility tableThere is a table "model - detail" - binding is done by import. None - we collect according to the manufacturer's articles and selectively check by hand; on tens of thousands of items, it noticeably moves the upper limit.
  • Category depth and filterThe spare parts catalog has four levels of nesting — not "more menu items", but a separate structure with canonicals on the filter combination. Without them, the filter will generate thousands of almost identical addresses, and this is a degradation, not an improvement.
  • Number of payments and carriersEvery payment method and every carrier is a connection, a test order, and a reconciliation item. Eight checkouts and four delivery services, as in measured niche stores, is a tangible volume, not a tick.
  • SeasonWorking on a peak date means a tight approval schedule on your part. We can speed up our part, but not the speed of browsing the directory by the search engine - no contractor affects it.
Technologies & integrations

What we build on and what it connects to

Stack

  • OpenCart 4.x is set by default, this is a branch that is being developed
  • OpenCart 3.x — when you need a module without assembly under 4.x; minus is accepted consciously
  • PHP Supported Versions - In the three measured niche stores, the core is at PHP 7.3.33, unsupported as of 2021
  • MySQL — we look at indexes on tens of thousands of items, otherwise the category will take a long time to assemble
  • nginx, HTTP/2, HTTPS + HSTS — the channel is encrypted, but the certificate itself does not make the store safe
  • OCFilter — filter by characteristics; we close the combinations with canonicals
  • Console import in batches: from 10,000 items, the admin drops after a timeout
  • Sitemap-index of submaps of 3,000 addresses: one file of the map weighs megabytes

Integrations

  • LiqPay
  • monobank "Purchase in installments"
  • Privat24
  • payment by details
  • non-cash payment with and without VAT
  • cash on delivery
  • Nova Poshta
  • Meest Express
  • Ukrposhta
  • Rozetka Delivery
  • Rozetka site
  • Google Tag Manager
  • GA4
  • Google Ads
  • Google Reviews
  • Telegram
  • Viber
Catalog with reference to models against a flat price

How this option differs from the alternative

How the buyer finds the itemfrom your equipment model to the list of compatible items
Wrong orderscompatibility is fixed in the data, the manager does not check each one
Indexingsubmaps of 3,000 addresses, duplicates closed with canonicals
The manager's work in the seasonthe question "will it fit" closes the catalog
Launch datelonger: structure and binding are separate steps
What we need from you

We can't start without this — best to prepare in advance

  1. The price of the equipment and separately the price of spare parts — even if the second comes from the manufacturer with a different file.
  2. Table of compatibility of spare parts with models, if there is one; without it, we make the binding according to articles.
  3. List of characteristics for the filter: power, engine type, width of capture, tank volume.
  4. Agreements with carriers and payment providers - API keys are issued to you.
  5. Photo of equipment; for spare parts, a photo of the manufacturer is usually enough.
  6. One person with the right to approve the structure of the catalog before the start of the season.

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 ten times more spare parts than equipment — will the store pull it out?

It will drag on, but this is already a large catalog with its own rules. The equipment and spare parts store we measured gives 55,321 product addresses and 3,868 category addresses — a total of 59,189, collected from 18 subcards of 3,000 addresses plus 1,321 in the nineteenth. The first server response there is 840.5ms, the slowest of the three niche stores we measured, and that's a direct result of volume. On such catalogs, console import works in batches: the admin on tens of thousands of items falls off after a timeout.

How will the buyer find a part for his model?

Because of the attachment to the model: comes from his lawnmower - sees compatible knives, filters, candles. If there is no compatibility table, we collect connections according to the manufacturer's articles, and this is a longer job. The second way is the depth of categories: in a measured store of equipment and spare parts, the catalog is expanded to four levels, because fittings and knives differ by a trifle such as thread or mounting size. The limit is fair: neither binding nor filter will save if there are no characteristics in the cards — the data must first be put in order.

We have a season - when does it start?

30-50 working days before the peak, and this is the lower estimate: the term is calculated from the approved TOR, not from the first conversation. On top of that, add the time it takes for a search engine to crawl the directory — a sitemap does not guarantee indexing or positions, and no one speeds up this part. If there are less than two months left until the peak, it is fairer to close the bottleneck of the current store - speed, site map or checkout - and make a complete replacement after the season.

The site map seems to be there, but there are no pages in the search - why?

Check that it actually gives addresses. In one of the three niche stores we measured, /sitemap.xml returns an HTTP 200 with a body of zero bytes, and the fallback feed is 404: the file formally exists, the address is zero, and the directory size from the outside is not counted at all. The opposite extreme in the same niche is 33,493 card entries for 8,690 unique addresses, meaning that each card is repeated almost four times under different category paths. Both conditions are visible on the audit in half an hour.

Is it possible to sell in parallel on the marketplace?

Yes, an XML feed from the same catalog: prices and availability are pulled from the same source, so there is no difference between the site and the platform. In all three measured niche stores, the platform is connected — both as a sales channel and as a delivery method at the checkout. The limit: the feed opens the channel, but does not make your price competitive - in commodity distribution you are compared to everyone at once.

How many payment methods do you really need?

Two of the three measured stores have eight niches — from card and installment purchases to cashless with VAT and cash on delivery; in the third five, and the shop is open. It is not logos that should be counted, but segments: a private gardener, a private gardener, a VAT company. Each additional gateway is a fee and an additional line in the reconciliation, so we determine the list during the audit.

How to keep stock relevant in the season?

Scheduled import — daily or hourly, depending on how fast the warehouse moves; if there is an exchange with the accounting system, we draw prices and balances from there. Be honest about the limit: the exchange does not fix the account. If there is a re-sort or unclosed write-offs, the site will quickly and accurately show inaccurate data, and between downloads there is always a window in which the last unit can be bought twice.

Why is there no price on the page?

Because the estimate in this niche depends on one number - how many addresses the catalog together with spare parts will give, and it is impossible to guess it from the outside. The difference between the stores we measured is almost 100%: 8,690 unique addresses versus 59,189. Therefore, first, a free audit in 2-4 working days, and already according to its figures, the amount and term by stages. The document remains yours regardless of who will make the store.

Send the price of the equipment and separately the price of spare parts

In 2-4 working days we will return with the numbers: how many addresses your directory will give, how many levels of nesting are needed, what about the sitemap and speed. After that - the amount and term by stages.

From measured cases8.57 MB Sitemap: 33,493 records for 8,690 unique addresses

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

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.