• Online Stores

Online electronics store: characteristics, comparison, warranty

The development of an online electronics store does not begin with design, but with characteristics: diagonal, memory capacity, power, energy consumption class should lie in separate fields. Otherwise, neither the filter nor the comparison of models will be collected - and it is precisely with them that the buyer of equipment chooses. On July 31, 2026, we took metrics from a home appliances and electronics store: 4,000 products, 8,358 sitemap addresses, first server response 995.7ms with 132KB HTML. There are no prices on this page on purpose: first, let's see what is being collected from your data.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
The size of the hardware store
4,000 products and 170 categories, 8,358 addresses in the site map
after a free audit
Price
30
Guarantee

days after project sign-off

4,000
The size of the hardware store

products and 170 categories, 8,358 addresses in the site map

995.7
The first answer is there

ms with an HTML weight of 132 KB

126.3
Fastest response in our sample

ms — a difference of 8 times on a similar class of sites

four at once, including two different GA4 streams
Analytics counters found
free data and site audit, 2-4 working days
Before the estimate
30–50
Development period

working days from the approval of the TK

Who it's for

Situations where this service delivers results

Scenario 1 of 5

The price from the distributor is there, and the characteristics are inside the text of the description

The price, article number and name are in columns, and the diagonal, memory capacity and power consumption class are in a solid paragraph in the description. For the store, it's a catalog without a filter: the buyer flips through the pages instead of narrowing down 400 refrigerators to four. We get the characteristics from the descriptions and break them down by attributes — a separate stage with its own term.

We'll review your situation in a free audit
What's included

Complete list of work and what you get as a result

  • Catalog by type of equipment and brand with a filter by characteristics, not by words in the description - the buyer narrows the selection himself, without a manager
  • A card with technical characteristics in separate fields, equipment and warranty conditions is what is read in this niche before the "buy" button
  • Comparison of models by characteristics: the main tool for choosing equipment, summarized in one table instead of two open tabs
  • Installments and payment in installments at the checkout next to the usual payment by card — so that a lump sum is not a reason to think
  • Block of compatible accessories and consumables in the card of the main product based on the compatibility table
  • Delivery: Nova Poshta with branch selection at checkout, Ukrposhta, courier, self-delivery — the manager no longer asks for the branch number
  • Technical SEO: CNC, canonical, unique title, sitemap without duplicate language versions, hreflang with x-default
  • JSON-LD micro-markup: Store, Product, Offer, BreadcrumbList — so price and availability are machine-readable
  • Analytics: One GA4 flow through Tag Manager instead of multiple conflicting counters, cart events, and purchases
  • Transfer: access, written instructions, passing the administration with your manager on a live order
  • Terms of work: 50% advance payment, two rounds of edits at the design stage, warranty period of 30 calendar days after acceptance
When this service isn't right

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

  • Writing technical reviews and comparative articles
  • Service accounting of repairs and warranty claims as a separate system
  • Filling characteristics manually beyond the agreed volume
  • Post-launch advertising
  • Hosting, domain, acquiring

Free pre-development audit

The hardware store wins on comparing models and loses on slow delivery. The audit shows two things: what of your data is already being collected into characteristics and where the current site is losing customers. Both numbers are needed to name the amount, not to guess it.

What we measure

  • Characteristics in the dataHow many items have the diagonal, memory capacity, power and power consumption class in separate fields, and how many - only in the text of the description. Without fields, neither the filter nor the comparison will come together, and this is where the biggest line of the estimate hides.
  • The unity of the names of characteristicsIs the same characteristic named the same in different cards of the same category: "diagonal" vs. "screen size", "W" vs. "W". Model comparison only works on a single dictionary.
  • Volume of the catalog and duplication in languagesWe count the addresses in the site map and cross-check with standard search. In the measured hardware store, the map gave 8,358 addresses with a real catalog of 4,000 products and 170 categories — each page is present twice.
  • Recoil speedFirst server response, full load and HTML weight. A benchmark from our measurement in this niche: 995.7 ms to the first byte with a light markup of 132 KB - the server is slowing down, not the page.
  • AnalyticsHow many counters are there and whether they are duplicated. In the same store, we counted four ad-analytics counters, including two different GA4 streams, a typical reason why the numbers in the reports do not match.
  • Installments, payments and guarantee blockWhat is connected now and whether the warranty and service conditions are described in human language and markup. In tech, warranty is part of the purchase decision, not a formality in the footer.

What you get

  • A document with numbers: the volume of the catalog, addresses in the site map, speed, HTML weight, a list of counters, payments and deliveries.
  • An estimate of how many characteristics will have to be obtained from the descriptions in order to assemble the filter and comparison — for each category separately.
  • List of analytics findings: duplicate streams, dead counters, non-existent events.
  • A 30-40 minute conversation on the document, where we answer questions and show what is critical and what can wait.

Timeline: 2-4 working days from the moment we received the price and website address

Why is it free

Because in electronics, the difference between "there is a price" and "there are characteristics" is measured in weeks of work, and you can see it only by opening the file. Calling the amount before that would mean either overinsurance and overestimating, or underestimating and then rewriting the estimate. The audit is cheaper for us than both options. The document remains with you in any case - even if we do not make the store.

What's next

After the audit - the amount and term by stages with calendar dates, contract, invoice, act. If it turns out from the numbers that you don't need development right now, let's say it straight: four such cases are listed below on this page.

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.

What affects the price

Why two seemingly identical tasks are priced differently

  • The state of the characteristics in the priceThe file, where the diagonal, the amount of memory and the power lie in separate columns, is filled in a day. The same characteristics within the text of the description have to be obtained and checked for each category - in this niche, this is the longest line of the estimate.
  • Number of data sourcesOne distributor price or five different downloads with their own field names and their own units. Each additional source is a separate mapping and a separate reconciliation on duplicate items between suppliers.
  • Depth of model comparisonComparing 8-12 fields within one category takes several days of work. End-to-end comparison between categories requires a single dictionary of characteristics for the entire catalog, and this is another volume.
  • Installments and methods of paymentEach provider has a separate connection, a test order for real money and the display of conditions in the product card. You draw up the contract and the keys: from our side, this term is not accelerated.
  • Language versionsThe second language doubles the number of addresses and requires hreflang with x-default. In a measured hardware store, this is 8,358 addresses with 4,000 products — and the same number of lines that need to be kept clean.
  • Volume of photos and contentThe manufacturer's photos are usually suitable and do not add anything to the deadline. A catalog where there are no photos or they were taken on a phone in the sales hall entails separate work with the content.
Process steps

Transparent stages with approval at every step

Total duration:30–50 days

  1. Brief and terms of reference

    3-5 working days

    We analyze the assortment, equipment groups, warranty conditions and a list of payments. The output is a TK, based on which the estimate is calculated and the work is accepted.

  2. Analysis of the price and set of characteristics

    4-7 working days

    Let's see what is already in the fields in the data, and what is inside the descriptions. Together with you, we record the characteristics by which the buyer actually chooses a model in each category — this list becomes both a filter and a comparison table.

  3. Prototype catalog, cards and comparisons

    3-5 working days

    Category tree, card fields, equipment and warranty block, checkout steps with installments. We agree with the design: redoing the structure after layout is expensive.

  4. Design

    5-8 working days

    Home, category with filter, product card, comparison screen, cart, checkout. Here we fix the target weight of the page so as not to repeat the 132 KB markup with a one-second server response.

  5. Assembly of the store

    8-13 working days

    Theme layout, catalog and attribute filter, comparison module, accessory compatibility table, payments and installments, admin roles, warranty and return pages.

  6. Catalog import and specification

    5-8 working days

    Mapping of price fields to attributes, extraction of characteristics from descriptions, reduction of names and units to a single dictionary, reconciliation of the number of cards using two methods, schedule of updating prices and balances.

  7. Integrations, analytics, transmission

    2-4 working days

    Payments and deliveries, one flow of GA4 through Tag Manager, JSON-LD, sitemap with hreflang, end-to-end running of the order from the cart to the TTN, speed measurements, passing the admin with the manager.

Did not find your case?

Describe how it works on your side — we will tell you whether “Development of an online store for electronics and household appliances” fits and what it means in your situation. No brief and no call: one question, one answer.

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 the critical module does not yet have a build for 4.x; we fix the version in the TOR on the brief, and not at the stage of integrations
  • OCFilter — filter by characteristics; limitation: reads attributes, not the text of the description, so everything that lies in the description will not get into the filter
  • Model Comparison Module - Limitation: Only compares identically named characteristics within a category
  • MySQL - we look at the indexes under the filter separately: the box ones are no longer enough after several thousand items
  • PHP
  • nginx, HTTP/2
  • HTTPS + HSTS

Integrations

  • LiqPay
  • WayForPay
  • Privat24
  • monobank "Purchase in installments"
  • "Payment in installments" of PrivatBank
  • Visa/Mastercard
  • postpaid
  • non-cash settlement
  • Nova Poshta
  • Ukrposhta
  • Meest Express
  • Google Tag Manager
  • GA4
  • Google Ads
  • Meta Pixel
  • Telegram
  • Viber
Your hardware store vs. a showcase on the marketplace

How this option differs from the alternative

Filter by characteristicsyour set of fields in each category changes according to the assortment
Comparison of modelsyour table according to the characteristics that you consider crucial
Installments and paymentsany provider you have contracted with
Sales commissionno, just hosting and domain
Technical sidesitemap, markup and speed are your responsibility and our work
What we need from you

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

  1. Price with characteristics in separate fields or agreement to work on bringing them to this appearance.
  2. A list of characteristics by which the buyer really compares models in each category - what you need is an understanding of the niche, not a technical form.
  3. Terms of warranty and service: you prepare the text, legally this is your area.
  4. Contracts with installment providers, if you connect it: the keys are issued to you, not to the contractor.
  5. Photos of products - usually photos of the manufacturer are suitable.
  6. One person with the right to approve the directory structure and set of 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 the characteristics in the text of the description - is this a problem at all?

The problem is purely technical. In OpenCart, the characteristic in the attribute field and the same characteristic in the description are different entities: the filter and comparison read the attributes, they do not see the description. Therefore, "we have everything on the card" and "we will collect the filter" are not the same thing. We get the characteristics from the descriptions and map them to the attributes during import. How long it will take is only visible after we open your file: in a price of 4,000 items, one category can be laid out perfectly, and the next one - a solid paragraph.

How many characteristics to display in the comparison?

Our recommendation is 8-12 fields per category, and no more. A longer table does not help to choose: a person scrolls it sideways on the phone and closes it. Take the characteristics by which the buyer really sifts out the models — diagonal, memory capacity, power, energy consumption class — and leave the complete list in a separate block on the card. And the main condition: within one category, the characteristic must be called the same everywhere. "Diagonal" in one card and "screen size" in another will give two different rows in the table.

Install the installment plan for the entire catalog?

No, and it is not economy on our part. Each provider takes a commission from the order, and on low-margin items, it eats up the profit completely. The mechanism works where the lump sum is large relative to the buyer's income: refrigerator, laptop, washing machine. On an accessory for a couple of hundred hryvnias, the installment plan does not add anyone who would not otherwise have bought it, but it adds a commission. Therefore, we connect by product groups, not globally. You conclude the contract with the bank, the keys are also issued to you - the contractor will not do this on your behalf.

We have four analytics counters and the numbers in the reports don't match

So it will be as long as there are four of them. In the hardware store we measured, there was a Tag Manager, two different GA4 streams, and an advertising tag at the same time. Two streams on the same site count events in parallel and give different numbers, and no one knows which one is correct. We reduce it to a single flow through Tag Manager, we clearly describe the events of the cart and purchases. A fair limit: the counter doesn't improve anything by itself, it just lets you see. Blockers and restrictions on cookies are not going anywhere, so GA4 shows a trend, not a cash register - you need to consciously reconcile it with accounting.

Why does the site map have twice as many addresses as products?

Because each page exists in two languages ​​and receives two addresses. Measured example: 8,358 addresses in the map with a catalog of 4,000 products and 170 categories. This is not a bug in itself - it becomes a bug when the hreflang with x-default is configured carelessly: then the search engine reads the versions as separate documents, and your pages compete with each other for the same query. The fix doesn't add traffic, it stops spraying it. And I warn separately: after cleaning, the number of pages in the index may drop for some time, this is the expected course of events.

The first response is almost a second - is this normal for an appliance store?

No. In our measurement, the hardware store gave the first response in 995.7 ms with an HTML weight of 132 KB: the markup is light, the server and requests to the database slow down. For contrast, the fastest store in the same sample is responsible for 126.3 ms. The 8x difference is project-specific engineering, not a platform property, and is treated by a separate speed job without rewriting the store. Be honest about the limit: speed does not make an offer attractive. A fast site will simply give a person a reason to leave sooner if the price is higher than the market.

How long does development take and what does the deadline depend on?

30–50 working days from approval of technical specifications, seven stages. The two longest are building the store (8–13 days) and bringing the characteristics to a single set for each category (5–8 days). If the price is structured, the term runs along the lower limit. If the characteristics lie in the texts of the descriptions, it is a separate line of the estimate and separate days, and we call them before the start, not in the middle of the work. Delays that occur most often on your part: agreeing on the set of characteristics and the text of the warranty terms.

Will the store be included in Google's product listing and on marketplaces?

We close the technical part: JSON-LD with Product and Offer, site map without duplicates, feeds to the feed. Without a correct product feed, there are no products in the product distribution at all - this is not "fewer impressions", it is zero impressions in this block. But no one guarantees items, and we will not. In a product listing, the buyer sees you next to everyone else, and if you're more expensive without explaining why, the feed will simply show that comparison sooner. Merchant Center also has its own content requirements, and working with them is not included in site development by default.
Related services

What's usually ordered together with this task

Send the price and tell us what characteristics you choose the model for.

In response, what from your data is collected in the filter and comparison already now, what will have to be obtained from the descriptions, and the work plan by stages with dates.

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.