1688-to-Ozon sourcing and listing automation
Auto Ozon Skill
A local pipeline for Codex, Claude Code and Hermes: sources products on 1688, prices them for Ozon and drafts a Russian listing
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- After explicit enablement it publishes new product listings to Ozon
- It calculates and writes prices based on its own logistics and exchange-rate estimates
Install
Manual install
pnpm dlx ozon-master@0.1.2 init --agent allInstalls, initializes the Ozon MCP and local skill pointers for Codex, Claude Code and Hermes.
This is third-party code. Review the repository files before installing.
What it does
The project runs eight steps from sourcing to listing: collects a product from 1688 by keyword, image, ID or the official similar-item search, normalizes it into one CanonicalProduct, picks an Ozon category and groups SKUs, prices it through the CEL logistics provider using rates, packaging data and commission, reads the current Ozon category attributes and dictionaries, fills them by script and agent within confirmed facts only, builds and validates a draft items[] payload, and finally submits it to Ozon. The agent itself writes the Russian copy and picks the category without calling an external text LLM, a separate image-generation key is only needed if photo generation is explicitly requested. Publishing to Ozon is blocked until the seller explicitly enables it for a specific store, separately from the general setup, and even then it does not proceed without checking config hashes, the draft hash and a daily limit.
Who it is for. For Ozon sellers who source products on 1688 and want to automate the path from finding a supplier to a ready but reviewable listing.
Good fit when
- You need a pipeline from 1688 sourcing to an Ozon listing with logistics-based pricing
- You want Russian listing copy without a separate language-model key
- You are fine with publishing only after explicitly enabling it for a specific store
Not a fit when
- You have no 1688 or Ozon Seller account, or are not ready to solve CAPTCHAs manually
- You need logistics providers other than CEL: only that one is implemented
- You need stock management, rollback or archiving of listings: step 8 does none of that
Example request
Source ten mugs on 1688 for my Ozon store and prepare draft listings without publishingLimitations
The README is in Chinese. It needs Node.js 20+, pnpm, Chrome or Playwright Chromium, and for the bundled Ozon MCP also Python with uv. CEL logistics rates are a manual snapshot with no verified date, explicitly flagged needs_review rather than an official current tariff. The project does not bypass 1688 CAPTCHAs or verification, a visible browser and a human are needed when the anti-bot triggers. Automated tests use fixtures and a fake Ozon transport, real publishing is not covered by the test suite.
How to disable. Run setup publishing disable --store-id <Client-Id> --actor <name> to turn off publishing for a store, and delete the project to disable the pipeline entirely.
Security check
- After explicit enablement it publishes new product listings to Ozon
- It calculates and writes prices based on its own logistics and exchange-rate estimates
README in short
The Chinese README describes the eight steps from 1688 sourcing to Ozon publishing, the feature set (account and risk-control handling, market selection, category and attributes, pricing, drafting, publishing with retries), installation via pnpm dlx ozon-master, a bundled Ozon MCP for reading products and orders, current production boundaries (CEL logistics only, 1688 facts outrank agent estimates) and safety rules around CAPTCHAs, secrets and publishing.
FAQ
Does the pipeline publish listings on its own?
No, publishing is blocked until the seller explicitly enables it for a specific store with a separate command, and is further checked against config and draft hashes.
Is a language-model key needed for the copy?
No, the calling agent itself writes the Russian copy and picks the category, a separate key is only needed for image generation and only on explicit request.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail