• Online Stores · OpenCart

Attribute schema: forty fields with only four filled in don't make a catalog

Attributes are usually added on a “why not” basis: the platform allows it, a manager created the field, a supplier sent the data. A year later a category has forty fields, only four of them actually filled in, and filtering by the rest shows nothing. An attribute schema solves the opposite problem: not how many fields you can have, but which ones this category really needs, so that they get filled in and people search by them.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Focus
online stores, mostly OpenCart
after a free audit
Price
Guarantee

days after project sign-off

online stores, mostly OpenCart
Focus
Timeline

to 40 working days

free catalog review
Start
Warranty

days from the date the acceptance act is signed

within 2 hours
Reply
under a written contract
Terms
What's included

Complete list of work and what you get as a result

  • an attribute set for each category group, not a single list for the whole catalog
  • mandatory and optional fields separated, with an explanation of why
  • value types: a number with a unit of measurement, a value from a reference list, yes or no
  • reference lists of allowed values where they are needed
  • a check against what people actually search for in your categories
  • marketplace requirements taken into account, if you pass data to them
  • a list of attributes worth removing as unnecessary
  • rules for new categories, so the schema doesn't sprawl
  • short instructions for the people who add products
When this service isn't right

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

  • filling in attributes for you
  • inventing attributes that aren't in your data sources
  • promises of higher sales
  • moving the catalog to another platform
  • unifying different spellings of values: that is separate work
Who it's for

Situations where this service delivers results

Scenario 1 of 4

A catalog with empty attributes

The fields exist, the values don't. A filter on such an attribute either finds nothing or hides half the products, and the buyer concludes the assortment isn't there.

We'll review your situation in a free audit

Free catalog review

We look not at the number of fields but at how full they are: that is what shows which attributes are alive and which only take up space.

What we measure

  • How many attributes a category has and how many are filled inThe most telling pair of figures. The gap between them is the real problem with the schema.
  • Which attributes people actually filter byIf analytics shows the filter is used on three fields out of twenty, the rest are candidates for removal.
  • Whether numbers are numbersPower, weight and volume have to be numbers with a unit of measurement, otherwise a range filter is impossible.
  • How different the categories areThe number of dissimilar groups determines how many separate field sets will have to be designed.
  • What marketplaces requireIf you pass data to marketplaces, their mandatory fields have to be in the schema from the very start.
  • Who will fill them inA schema with no people behind it will stay on paper. The number of mandatory fields has to be manageable.

What you get

  • attribute fill rates for key categories, in figures
  • a list of candidate fields for removal
  • a draft schema for one or two categories as an example
  • an estimate of the work broken down by stage

Timeline: 2–4 working days

Why is it free

A schema can't be proposed without seeing the fill rates: two stores with the same assortment can have entirely different ones.

What's next

You get the figures and a sample schema. What to do next is your decision, and the document stays with you.

Short form: your contact and site URL

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points
  • 01

    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.

  • 02

    Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • 03

    Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • 04

    Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • 05

    Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • 06

    Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • 07

    Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • 08

    We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • 01

    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.

  • 02

    Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • 03

    Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • 04

    Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • 05

    Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • 06

    Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • 07

    Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • 08

    We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

  • Number of category groupsA schema is made not per category but per group of similar ones. The more dissimilar groups, the more separate field sets.
  • Whether reference lists of values are neededA list of allowed values keeps the filter manageable, but it has to be drawn up for each attribute separately.
  • Marketplace requirementsMapping your schema to a marketplace's fields is separate work, better done right away than by reworking the schema later.
  • State of the existing dataIf attributes are scattered across descriptions, you first have to understand what is there at all. This affects the timeline more than the number of categories does.
  • How many fields to make mandatoryThe more mandatory fields, the fuller the catalog and the more work for your managers. It is a balance, and you set it.
  • Whether rules for new categories are neededWithout them, the schema lasts until the first new product group. It is a small but necessary part of the work.
Cases

Tasks and results in numbers — all metrics measured by us

a sample of 41 Ukrainian online stores, of which 39 responded and a product page was checked on 30

Task
Check how complete the stores' product cards are: whether there are attribute filters, comparison and displayed ratings — all of which grow out of the quality of the product data itself.
Solution
An external measurement of the home page and one product page taken from the sitemap: traces of features in the HTML, plus product, price and attribute markup. It records whether a trace is present, not the quality of the implementation.
Result
Measured on 17 September 2026, 35 stores: filter by attributes: 9 sites out of 25; product comparison: 10 sites out of 25; rating markup: 3 sites out of 25.

Pancer Protection

an online store of tactical and military gear with a catalog of over 50,000 SKUs

Task
Hold an oversized assortment of tactical gear (body armor, clothing, footwear, backpacks, comms, optics) in a single store with detailed filtering by attributes — without losing page response speed.
Solution
A store on OpenCart 3 (chameleon theme + NeoSeo modules) behind Cloudflare. Two language versions. Full local-store JSON-LD markup: Store, Place, GeoCoordinates, PostalAddress, OpeningHoursSpecification, ContactPoint, WebSite, SearchAction. At checkout: LiqPay, card online, cash on delivery, cash on collection, bank transfer and online installments (dataLayer events). Binotel telephony, eSputnik email marketing, Google sign-in, GTM, GA4, Google Ads.
Result
54,302 products and 635 categories — the figure is confirmed by two independent methods: a sitemap index of 32 product files gives 110,096 URLs across two languages, and a cross-check through OpenCart search gives 54,501–54,600 items (a 0.4% discrepancy). A catalog of 54,000 SKUs returns the first response in 0.41 s and the full HTML in 0.51 s at 422 KB. Nine JSON-LD types on the home page. Five payment methods, including LiqPay and online installments. Measured 31 July 2026.

Did not find your case?

Describe how it works on your side — we will tell you whether “Product attribute schema” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Total duration:7–30 days

  1. Checking fill rates

    2–4 working days

    We count how many attributes each category has and how many of them are actually filled in. We look at what users filter by.

  2. Grouping categories

    1–3 working days

    We combine categories into groups with similar needs. A schema is made per group, otherwise the number of sets becomes unmanageable.

  3. Designing the schema

    3–10 working days

    For each group we define the set of fields, the value types and which of them are mandatory. Disputed decisions go to you.

  4. Reference lists and units

    2–8 working days

    We draw up lists of allowed values and standardize the units of measurement, so the filter stays manageable and numbers are comparable.

  5. Implementation

    3–12 working days

    We load the schema into the catalog, move existing values into the new fields and remove the attributes judged unnecessary.

  6. Rules and handover

    1–3 working days

    We set out the rules for new categories and hand over instructions for the people who add products. Then the 30-day warranty from the date the acceptance act is signed applies.

Technologies & integrations

What we build on and what it connects to

Stack

  • OpenCart
  • WooCommerce
  • PostgreSQL
  • MySQL
  • MariaDB
  • Python
  • SQL
  • TypeScript
  • Git

Integrations

  • 1C
  • BAS
  • XML/YML price feeds
  • CSV exports
  • Google Merchant Center
  • Rozetka
  • Prom
A schema per category group or one shared field list

How this option differs from the alternative

Fill ratefewer fields, but they are filled in
Filtershows a manageable list of values
Manager's workclear what to fill in for this category
Selling on marketplacesfields are mapped to the marketplace's requirements
Launch complexityhigher: the schema has to be designed
What we need from you

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

  1. a catalog export with the existing attributes
  2. which categories bring the most revenue
  3. access to analytics to see what people filter by
  4. whether you pass data to marketplaces, and to which ones
  5. who will fill in the new fields and how much time they have
  6. who on your side accepts the work

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

How is this different from normalizing attributes?

They are two different steps. An attribute schema decides WHICH fields a category needs. Normalization brings different spellings of values to a single form in the fields that already exist. The schema comes first: there is no point tidying up values in a field that should never have existed.

How many attributes should a category have?

As many as your managers will actually fill in, and no fewer than the filter needs. That is usually noticeably fewer than you have now. Forty fields with four filled in are worse than eight filled in completely: in the second case the filter works and the buyer sees the assortment.

Will you remove our attributes?

Only the ones you approve. We show fill-rate figures and data on what people filter by, and propose a list of candidates for removal. The decision is yours: sometimes a field is empty not because it is unnecessary but because nobody has got around to filling it in yet.

What about marketplace requirements?

Build them into the schema from the start. Marketplaces have their own mandatory fields, and if your schema doesn't match them, every export needs manual rework. Taking this into account at the design stage is cheaper than reworking the schema a year later.

How long does it take?

12 to 40 working days. What usually takes longest is not the design but the decisions on your side: which fields to make mandatory. That directly affects your managers' workload, so it is not something to rush.

Can the schema be done for only part of the catalog?

Yes, and for large stores that is the better approach. We start with the categories that bring the most revenue: the effect shows sooner there, and on a small volume it is easier to check whether the schema is convenient in practice.

Who decides that a field is mandatory?

You do. Every mandatory field is your managers' time on every new item. We show what the filter gains and what marketplaces require, but the balance between completeness and workload is set by the owner.

Will this affect sales?

Not directly, and we don't promise it. The schema makes filtering and comparison possible, which buyers use to narrow their choice. How much that affects sales depends on the assortment and prices, and we won't quote percentages.
Demo

Your catalogue on a phone screen

This is how your store can look on a phone: a collection banner, popular products and a cart one tap away. Tap “Add to cart” and the counter in the header updates, just like in a real store.

  • Collection bannerThe first screen shows what is new, not a logo.
  • Product cardsPhoto, price and a button — no extra page to open.
  • One-tap cartThe counter in the header updates instantly, like in a real store.
Stores in the portfolio

This is a demo interface, not a client's store. Live projects are in the portfolio.

SHOP
New collectionAutumn / WinterExplore
PopularAll products ›
  • Essentials Hoodie1 290 ₴
  • Urban Backpack1 490 ₴
  • Classic Cap690 ₴
  • Basic Tee590 ₴
  • Street Sneakers2 390 ₴
  • Active Shorts890 ₴

Let's count how many of your fields are actually filled in

The catalog review is free: we show field fill rates in figures and a sample schema for your category.

From measured cases54,302 products and 635 categories

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.