OZON: prices and stock for Shop-Script

A store and Ozon live apart. An item sells in the store — on Ozon it is still in stock, and an order arrives for something you no longer have. A price changes in the store — on Ozon the old one stays. The seller either fixes stock by hand in the evenings, or pays for a large integration in which prices and stock are just one of a dozen and a half features.

This plugin does that one job, and does all of it: the stock and the price of every product variant go to Ozon on their own, with your markup, rounding and safety buffer. It does not pull Ozon orders into the store and does not create product cards — you have already created them, it only keeps them current.

Visible before sending, not after

The main screen is a table of what will go to Ozon for every variant: the product and its SKU, the stock in the store and the stock Ozon will get, the store price and the price Ozon will get after markup and rounding, the crossed-out price, what was sent last time and when. A row that will not go says why: "the variant has no SKU", "the SKU is not in the Ozon account", "the card on Ozon is archived", "the product is not published in the store".

Tabs with counters: "All variants", "Ozon accepted", "Not sent yet", "Ozon rejected", "Not on Ozon", "Duplicate SKU". Search by SKU and product name. The tab, the search and the page live in the URL, so a working selection can be bookmarked.

Trial mode

The plugin installs with trial mode on: it computes everything and shows the finished table, but sends nothing to Ozon. Markup, rounding, safety buffer and matching are checked on your own products and your own numbers — before the first real upload, not on a live listing. One checkbox in the settings turns it off when the table looks right.

Matching by SKU

Ozon knows a product by the seller's SKU — the offer_id field. The "Match with Ozon" button pulls the list of cards in your account and sorts the assortment out: what was found, what is missing on Ozon, which variants share a SKU and which have none. Duplicates are a quiet disaster — two variants with one SKU would silently overwrite each other's stock — so the plugin does not upload them and shows them on their own tab. That SKU can be mapped to the variant's SKU field, the variant id or the product id, whichever matches your account.

Stock

Stock is taken across the whole store or from one chosen warehouse, when Ozon trades from stock the storefront does not share. A safety buffer is subtracted: that many units are never shown on Ozon, so the last one is not sold twice. There is a stock ceiling and a separate value for products with no stock accounting — Ozon has no "unlimited", it needs a number.

The rule "take off sale below N" sends zero: the product stops selling, but the card stays alive with all its history and reviews, and sales resume as soon as stock is back.

Prices

The store price goes to Ozon with a percentage markup that usually covers the marketplace fee and delivery. Rounding: to the ruble, to ten rubles, or to a nine-ending price. A negative markup is allowed too, if you sell cheaper on Ozon.

The crossed-out price is taken from the product's compare-at price or computed from the selling price plus a percentage — and since Ozon rejects a row when the gap between the two is too small, the plugin checks that gap itself, before sending. A price floor is set separately: the marketplace may not push the product below it in its own promotions.

On a schedule

Uploads run on their own, from every half hour to once a day. Each run covers as many products as the hosting can take, starting with those not refreshed for the longest, so the queue is worked through over several runs. Ozon limits how often it may be called — one stock change per product per half minute, ten price changes per hour — and the plugin respects those limits and does not waste them: a value Ozon already knows is not sent again.

What will go and what will not is visible in the table before the run. How to enable the schedule on your hosting is written right in the workplace, with no need to go looking through the documentation.

The log

What the store sent and what it heard back: stock, prices, matching, trial runs, connection checks — with the time, the source (a button or the schedule) and the number of accepted and rejected rows. Ozon's errors are translated into plain language instead of codes, so when a price on Ozon is not the one you expected it is immediately clear whose side the problem is on.

Settings

Client-Id and Api-Key. What to match by. The Ozon warehouse for stock — the "Check the connection and find out warehouse numbers" button shows its number, which is not available anywhere in the Ozon account UI. Stock: source, safety buffer, ceiling, value for untracked products, take-off-sale threshold. Prices: markup, rounding, crossed-out price, floor, VAT rate. Published products only. Trial mode. Schedule: on/off, interval, products per run.

What you need

An Ozon seller account and a Seller API key with product and price permissions. Product cards must already exist on Ozon and their offer_id must match what is selected in the plugin settings. Stock upload needs a seller warehouse — the FBS or realFBS schemes; under FBO stock is Ozon's own and there is nothing to upload. The plugin only talks to api-seller.ozon.ru.

Compatibility

• Shop-Script 9.4.1 and newer, Webasyst 2.0 interface; the older 1.3 interface is supported as well;
• localization: Russian, English;
• dark backend theme supported: colors come from the backend theme variables;
• checked down to 390 px screen width — on a phone the table and the buttons work the same way as on a desktop;
• the storefront is not affected: the plugin lives in the backend only and changes nothing in the products themselves.

Support

Questions and suggestions — via the developer's feedback form.