Eofferix takes supplier price lists, maps the fields to Ozon requirements and runs recurring exports: it updates prices, descriptions and photos, creates new products and hides outdated ones.
After registration, the free plan lets you work with small catalogs.
Short on time to learn the settings? We can connect your price list to Ozon and hand over a ready-to-use profile.
Any configuration that can export a product catalog.
Price lists and catalogs in XLS, XLSX and CSV.
Supplier price lists in XML and YML.
Price lists maintained in online spreadsheets.
Files attached to incoming emails.
Product data exported through a supplier’s API.
Price lists and catalogs hosted on an FTP server.
Files shared by link from cloud storage.
Set up the source, rules and connection once. Eofferix then repeats data preparation and delivery on your update schedule.
Upload a file, provide a link, connect FTP or collect email attachments. XML, YML, JSON, CSV, XLS, XLSX and 1C exports are supported. Multiple suppliers can first be combined in a unified catalog.
About data sources
Identify the SKU, price, stock, name and images in your price list. For product cards, map categories and required attributes. Add markups, rounding and product filters here too.
How to fill Ozon fields
Enter your seller Client ID and API key in the profile. Choose to send product cards or update only prices and stock. The Excel template remains a separate option for manually uploading a file to Ozon.
How to connect Ozon
Review the data checks and messages before delivery. After the first verified run, save the profile and set a schedule. Run history and errors are available in the service.
How to run an export
These are real Eofferix screens with demonstration data, shown in Russian.
Connect Ozon Seller API and export products automatically.
If you prefer to hand over the fields, API and processing rules, send a sample price list and tell us what needs updating in Ozon.
Service usage is billed separately under your selected plan. Service plans · Done-for-you terms
Eofferix can merge price lists and catalogs from several suppliers into one unified catalog, normalize products and then export that data to Ozon. If you have one supplier now, start with a separate processing profile for that source.
XML, YML, CSV, XLS or XLSX without manual rebuilds before every update.
offer_id, SKU, barcode, name, category, price, stock, description, images and required Ozon attributes.
Scheduled runs for prices, stock or a full product file.
Items without required data are skipped before delivery.
Sign up, connect your sources and configure recurring delivery of product cards, prices and stock to Ozon. After registration, the free plan is available - try it and evaluate the automation.
How to merge 1C, spreadsheet, and supplier data before sending to Ozon.
How direct delivery of product cards, prices and stock to Ozon works.
Where to enter Client ID, API key and export scope.
Filter example before publishing to a storefront or marketplace.
Practical check for required media.
Yes. Eofferix has a dedicated Ozon profile for sending product cards, prices, stock and publication actions through Ozon Seller API. The seller enters Client ID and API key in the profile, and the service validates data before delivery. The Ozon Excel template remains a separate workflow for manual file upload.
No. For one supplier, a profile is enough: source, processing rules and export to Ozon. A unified catalog is useful when you need to merge several sources, remove duplicates and choose the final data for export.
XML, YML, JSON, CSV, XLS, XLSX and CommerceML from 1C are supported. If the structure is custom, it can be parsed as a separate source and then mapped to Ozon fields.
Yes. A price list can be fetched from FTP or FTPS and used as a recurring source. This works when the supplier updates a file on its server and you need to pick up the latest version automatically.
A spreadsheet can be connected as a source if the service can access it by link or a supported loading method. Then it is processed like a table price list: structure, fields and rules are configured in the profile.
The minimum set depends on the scenario. Prices and stock need product identifiers and update values. Product cards add category, name, attributes, description, images and required Ozon attributes.
You can select working images, normalize links or files, resize and convert them. Products without required images can be filtered out before delivery.
It depends on the selected workflow. You can leave the card unchanged, update stock, or configure archiving and unarchiving through Ozon API for matched products. Direct product deletion should not be treated as the default scenario.
API export sends prepared data to the seller account automatically through Ozon Seller API. The Excel template only prepares a file in Ozon format: you download it and upload it manually in the seller account. Both workflows can start from the same supplier source.
Yes. A separate profile can send only product identifiers, prices and stock. Product cards, descriptions and images are not changed during that run.
Both are possible. A one-time file can be checked manually, but Ozon work usually relies on a saved profile: it repeats the same transformations and can run on schedule.
Yes. If a supplier sends a file by email, configure an IMAP source: the service will find the message, take the attachment and continue processing through the profile rules.
Yes. You can use full or partial 1C export, including CommerceML. After import, fields and sections are mapped to the structure needed for Ozon delivery.
Yes. Rules can apply markup, discount, rounding, final supplier price logic and other transformations. This avoids manual editing before every delivery.
Yes. Filters can use category, required fields, price, stock, brand, product group or other conditions. Only products that pass the rules go into the export.
Run the profile on a sample or test set first and review the output file, skipped products and errors. After checking, send the result through API or use the file for manual upload.
