Suppliers
We connect a supplier to your store by their price feed: the program reads the feed on a schedule and keeps prices, stock and new items in sync. Below — which feeds we work with, what we need from you and which cases count as hard.
XML, YML, CSV, Excel · from $35 per supplier · answer within a day
What we can read
The format decides the price of the connection, not whether it is possible. XML, YML and CSV are the standard $35; Excel costs more, because those workbooks almost always have to be unpicked separately.
XML
The most common case: a link the supplier refreshes themselves. We read it straight from the URL, nothing to upload by hand.
from $35
YML
The Yandex.Market dialect, the same one Rozetka and Prom use. Categories, brands and pictures already have their place in it.
from $35
CSV
Any delimiter and encoding. We tell the program which column is the SKU, which is the price and which is the stock — once, at setup.
from $35
Excel
XLS and XLSX, including the workbooks suppliers send by e-mail. Several sheets and merged header cells are fine.
from $70
No feed at all
Only the supplier site. Then the data is collected from the pages of that site, and the price depends on how the catalogue is built — we name it after we look.
above $70
How it behaves afterwards
Feed size
The ceiling is set by your hosting memory, not by the program: parsing costs roughly three times what the file weighs. At 128 MB that is a feed of about thirty thousand items, at 256 MB twice as much. Excel is the most expensive — the workbook is read whole. We look at your feed and your hosting and tell you whether it fits, before any payment.
Items gone from the feed
Hidden in the store, not deleted: the card, its URL and its statistics survive until the item comes back.
New items
Added to the category you mapped. Categories the supplier has added since setup wait for your confirmation.
Scheduled updates
The capability is there — a cron job. How often it actually manages a full pass is decided by your hosting: time and memory limits differ everywhere, and where they are tight the program does less per pass and takes longer. Starting an update by hand always works.