• Online Stores

Shop under Rozetka: own site from which the correct feed is issued

The online store under Rozetka is a site where mandatory characteristics are placed in separate fields under the category of the site, and not in a paragraph in the description. You start the catalog once, and the same line of data goes to the platform as a feed: name, attributes, channel price, balance. Refusal of moderation is given by the data, not the engine, so we put validation before sending. The term is 25–50 working days, the amount is named after a free audit of the catalog.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Shops with a connected platform were measured
2 live stores of garden tools, measurement 07/31/2026
after a free audit
Price
30
Guarantee

days after project sign-off

2
Shops with a connected platform were measured

live stores of garden tools, measurement 07/31/2026

1,300
Catalog of more of them

unique addresses, about 1,213 cards, 1,120 with the manufacturer's article number

4,236
Duplication in the site map

records for 1,300 addresses — 3.3 copies per address

547.2
The first response from the server

and 625 ms; HTML weight 252.6 and 350.4 KB

not found in any of the two: in one Organization and ContactPoint, in the second zero blocks
Marking Product / Offer
25-50
Term

working days from approval of technical specifications

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

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

Free audit of the catalog according to the requirements of the marketplace

The feed is rejected not because of the site, but because of the data: there is no mandatory characteristic, the price is different, the balance is outdated. The audit shows how many of your items will be moderated as is, and how many need to be supplemented — and it is this proportion that determines both the deadline and the estimate.

What we measure

  • Mandatory characteristics by categoryHow many items already have the full set of attributes required by the site in its category. The main multiplier of work, and it can be calculated only by your export.
  • Comparison of categoriesDo your categories fit clearly on the site tree. Each one-to-many case is a line in a manual correspondence map.
  • Status of descriptions and imagesThe length and content of the descriptions against the requirements, the resolution of the images, third-party inscriptions and watermarks on the photo.
  • Source of balances and pricesWhere does the availability come from and how quickly does it arrive? Outdated feed balance is the most expensive mistake: cancellation, wasted click and negative seller rating.
  • Technical status of the current siteSpeed, sitemap, markup. For reference, in the garden tool store we measured with Rozetka connected, the sitemap weighed in at 1.18MB and contained 4,236 entries at 1,300 unique addresses—3.3 copies per address.
  • Channel crossingWhat will happen to your pages when the same product appears on the site, and which part of the assortment should not be given there. We have this conversation before launch, not after.

What you get

  • Catalog document: share of feed-ready items and list of what's missing.
  • Map the matches of your site tree categories.
  • Evaluation of works on the addition of characteristics in a separate line.
  • Conversation for 30–40 minutes on the document.

Timeline: 3-5 working days

Why is it free

Because the readiness of the catalog for the feed is a figure that can be calculated, and without it the estimate will be a guess. The document remains yours regardless of whether we make a store or not.

What's next

After the audit — the amount and term by stages with dates, contract, invoice, report. If it becomes clear from the numbers that it is more profitable for you to start with a storefront on the site, we will say so.

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

  • Proportion of items with full attributesThe main lever. A catalog of 500 items, where the characteristics are already laid out as fields, and a catalog of 500 items, where they are hidden in the description with solid text, are different projects under the same name. We calculate the share at the audit, before talking about the amount.
  • How many site categories you occupyEach category has its own set of mandatory fields. One category — one match map and one set of validation rules; fifteen categories - fifteen, plus cases when your category splits into several others.
  • Status of descriptions and imagesPhotos on a uniform background without inscriptions and descriptions of the required length go to the feed as is. A photo with a superimposed logo or descriptions in a PDF-price with a picture is a manual work for each item, and it is displayed on a separate line, and not hidden in the total.
  • Source of balances and pricesAccounting system API is one job. Uploading a file once a day is another. Residues in the head of the owner of the warehouse is the third, and you have to start with the account, not with the site.
  • Processing of orders from two channelsPicking up orders from the account in the site administration is a separate volume that depends on what exactly the API of the site gives. Without it, the manager keeps two journals, and this is the shortest way to double the sale of the last unit.
  • The state of what already isA store from scratch is calculated more transparently than someone else's modification: in someone else's code, half the time is spent on analyzing how prices and balances are arranged there.
Who it's for

Situations where this service delivers results

Scenario 1 of 4

You trade from the platform's office and you don't have your own website

A storefront on the platform is a rental: the rules, commission and visibility change without your participation, and the buyer remains the buyer of the platform. This channel does not replace its website, it adds a second one — with a domain and customer contacts. A fair margin: The feed opens up a product outlet, but doesn't make your price competitive.

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

Complete list of work and what you get as a result

  • A catalog in which mandatory characteristics are entered in the fields under the category of the site - the position goes to moderation without manual revision in the office
  • A one-to-many case mapping of your site tree categories - otherwise the product part just has nowhere to go
  • Feed generator with validation before sending: an item with incomplete attributes is not included in the download
  • A report on rejected items after each regeneration — what exactly did not pass and which field to fill in
  • A separate price field for the channel with a markup rule: the commission does not eat up the margin, and the retail price of the site remains independent
  • Balances from the accounting system as a single source at once for the site and for the feed, without a second availability log
  • Separation of assortment: a mark that goes to the site, and that is sold only on its website
  • Orders from both channels in the same admin - the manager works with one journal, the write-off is from the same balance
  • Payment and delivery on your own website: online card, cash on delivery, non-cash account, carriers, self-delivery
  • Product pages with Product and Offer markings, CNC, canonical and a site map without duplicates — so that the site has a chance in the search on its own
  • Transfer: access, written instructions for your processes, passing the admin check with the live order manager
  • Terms of work: 50% advance 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

  • Registration and moderation as a seller on the site
  • Completing the characteristics throughout the catalog is evaluated by a separate line
  • Management of the seller's rating and work with reviews on the site
  • Advertising inside the marketplace
  • Hosting, domain, acquiring
Process steps

Transparent stages with approval at every step

Total duration:25–50 days

  1. Catalog audit and technical task

    2-5 working days

    We count the share of items ready for the feed, look at the site categories and the source of the balance. The output is a TK, based on which the estimate is calculated and the work is accepted.

  2. Data Model and Category Correspondence Map

    4-7 working days

    The tree of your categories falls on the tree of the platform, mandatory characteristics become fields, we agree on the rule of the channel price. It is expensive to redo it after layout, so we agree in writing.

  3. Assembly of the store

    8-14 working days

    Design and layout, catalog with filters, shopping cart and checkout, admin roles, payment, delivery and return pages, Product and Offer markup.

  4. Importing the catalog and adding attributes

    4-10 working days

    Mapping of price fields, test filling, comparison of the number of cards using two methods. In parallel, empty mandatory characteristics are closed - the longest and least predictable part.

  5. Feed generator and validation

    3-6 working days

    Compilation of XML according to the requirements of the site, checking of the scheme, the rule for filtering out incomplete items, the regeneration schedule in cron, the report on rejected items.

  6. Trial export and analysis of deviations

    2-4 working days

    The first feed to the office, collection of reasons for failures, data corrections, repeated regeneration. Here it becomes clear how honestly we calculated readiness for the audit.

  7. Testing, transfer, launch

    2-4 working days

    End-to-end processing of orders from the site and from the site, reconciliation of balances between channels, measurements of TTFB and HTML weights, passing of administration with your manager, transfer of accesses.

Did not find your case?

Describe how it works on your side — we will tell you whether “Online store under Rozetka requirements” fits and what it means in your situation. No brief and no call: one question, one answer.

Cases

Tasks and results in numbers — all metrics measured by us

online store of the official seller of garden tools with connected Rozetka

Task
Sell ​​tools of a well-known brand in Ukraine and at the same time keep export at the site: catalog with filters by type and series, cards with characteristics, calculation of delivery in the basket.
Solution
OpenCart 3.x under nginx with HTTP/2 and HSTS, two language versions with x-default. Four payment methods, including payment in installments, two carriers, a feedback module, a connected platform.
Result
Measurement 07/31/2026: 1,300 unique addresses in the sitemap — about 1,213 cards and about 70 categories, with 1,120 cards bearing the manufacturer's article directly in the address. TTFB 625ms, full HTML load 752.5ms at 350.4KB. Defects found: sitemap weighs 1.18MB and contains 4,236 entries for the same 1,300 addresses — 3.3 copies per address; from the markup on the main page, only Organization and ContactPoint, no Product.

online store of garden tools for private buyers with delivery to the site at the checkout

Task
Sell ​​irrigation systems, lawnmowers, trimmers and hand tools to private gardeners, with marketplace logistics among the delivery options.
Solution
OpenCart 3.x. Five payment methods — from card to cashless with and without VAT — and four carriers, including the site's delivery service. The layout is optimized for page weight.
Result
Lightest HTML among batch stores - 252.6KB, TTFB 547.2ms, full load 676.7ms; 66 out of 69 images (96%) are slow to load. The found state, not our work: /sitemap.xml gives HTTP 200 with a body of zero bytes, the backup feed is 404, so it was not possible to calculate the volume of the directory from the outside; of JSON-LD blocks is zero, the names of carriers are presented only as pictures without alt.
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 export module exists only under three; the limitation is conscious and fixed in the TK before the start
  • PHP and MySQL are a limitation: the generation of a large feed from the admin system rests on the timeout, so we transfer it to the console task
  • nginx
  • XML feed with schema validation - limitation: validation catches structure and empty fields, but not that the characteristic is filled with the wrong value
  • cron for scheduled regeneration - limitation: there is always a window between runs in which the price on the site is already out of date
  • Accounting system API for balances
  • JSON-LD Product / Offer

Integrations

  • Rozetka
  • Rozetka Delivery
  • XML feed to marketplaces
  • Google Merchant Center
  • LiqPay
  • WayForPay
  • monobank
  • postpaid
  • non-cash settlement
  • Nova Poshta
  • Ukrposhta
  • 1C / BAS
  • Google Tag Manager
  • GA4
Your site as a feed source against trading only from the cabinet

How this option differs from the alternative

Where does the product card live?in your base, a copy of the feed goes to the site
Channel pricea separate field with a commission markup rule
Data about the buyeryours: domain, contact, order history
Risk of stoppingtwo channels, the fall of one does not stop sales
Start speed25-50 business days plus attribute replenishment
Where does the demand come from?your SEO and advertising on your own domain, more slowly and cumulatively
What we need from you

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

  1. Catalog download in machine form - CSV or XML with name, article number, price, balance and characteristics in separate columns.
  2. A list of the platform categories in which you plan to trade.
  3. The pricing rule for the channel taking into account the commission is your decision, we just sew it into the field.
  4. Access to the seller's account or decide who opens and moderates it.
  5. Access to the hosting, domain and accounting system, where the balances will come from.
  6. One person from your side with the right to make decisions on the assortment and prices.

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

Sales are already coming from the site - why do you need your own website?

To have a channel that belongs to you. You rent a storefront on the site: the commission, display rules, and delivery procedure change without your participation, and the buyer remains a site buyer after the purchase — you have no contact with him. A smart scheme is not "instead of", but "together": the catalog lives with you, the site receives a feed from the same source. And immediately a fair limit — its domain gains visibility for months, while the storefront gives views from the first day.

Why is the feed rejected and what do we do before the first download?

The reason is almost always in the data: there is no mandatory characteristic for the category, the description does not meet the requirements, there is a third-party inscription on the photo, the price differs from the website. Therefore, the validation is done before the shipment: the item with incomplete attributes is not included in the export, and you receive a report with a list of fields that need to be closed. Our recommendation at the start is not to give the entire catalog at once, but to go through one category in its entirety and look at the real reasons for refusals, while there are dozens, not thousands.

Should the price be the same on the site and on the site?

Usually not, and that's why we introduce a separate price field for the channel with a markup rule - the commission takes a significant part of the check, and there is no reason to include it in the retail price of the site. One caveat: the sites compare your price to the price on your own site, so the rule should be a conscious decision with a ceiling, not a "plus percentage" formula with no upper limit.

Will the site not take away my search traffic?

In part, it will be taken away - marketplaces are strong in issuing, and it is pointless to fight with them for general requests such as "buy a trimmer". Therefore, the site should take what the platform does not provide: detailed pages of categories for narrower queries, selection and comparison, local queries, articles. This is a slow strategy and it would be dishonest to sell it as fast.

We have a lot of duplicates in our sitemap - will this harm the feed?

No to feed, yes to search. In the garden tool store we measured with Rozetka connected, the sitemap weighed 1.18 MB and contained 4,236 entries at 1,300 unique addresses: 3.3 copies per address, because the product was indexed under several category paths. Signals diverge across copies instead of coming together on a single page. It is treated with a canonical address for the product and a clean sitemap. The limit is also fair: cleaning duplicates does not add new traffic, it stops spraying it, and the number of pages in the index will first drop - this is the normal course of events.

How can a manager work with orders from two channels?

In one place. Orders from the office are pulled into the site admin, the manager keeps a single journal, and the balance is debited from the same source. Two separate magazines is a direct path to selling the last unit twice, and the platform counts the backorder against the seller's rating. Technically, the scope of this part depends on what exactly the site's API returns, and we call it post-audit.

We take the remains to the BAS - how will they get to the site?

Through API exchange: the accounting system remains the source of truth, the site takes availability from there, the feed takes it from the site. One chain instead of two parallel ones. What does not work here: if there is a re-sort or open write-offs in the accounting, the site will simply quickly and accurately show inaccurate data. And there is always a window between exports - in the case of mobile residues, it is shortened to hours, not reduced to zero.

How long does development take and why is the fork so wide?

25-50 working days from approval of technical specifications. Site and feed generator - estimated part: build 8-14 days, feed with validation 3-6. Extends the deadline for filling in mandatory characteristics, because this is work for each position in each category of the site. If the catalog is already structured and the attributes lie in columns, the term runs along the lower limit.

Send a catalog download - let's count how many items will be moderated as is.

In 3-5 working days, we will return the document: the share of ready items, a map of correspondence of categories, a list of what needs to be supplemented, and an assessment of this work in a separate line. Next - the amount and term by stages.

From measured casesMeasurement 07/31/2026: 1,300 unique addresses in the sitemap

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.