Collect the source data
For each item, collect the seller SKU, title, category, attributes, variants, images, price and status. Collect stock separately because it changes more often than descriptions. A stable seller SKU is a useful match key when the same identifier exists in your inventory system.
We review your access and a sample export first. A complete file may be enough for migration; ongoing updates may require an API connection. We check images, attributes and variants on a sample before moving the agreed catalog.
Resolve the differences between catalogs
The same item may have different titles and categories on Ozon and Wildberries. Sizes and colors may be separate listings or grouped variants. Images may be missing or unavailable for reuse. A successful import cannot be judged by row count alone.
Prepare a mapping of source ID, seller SKU, destination URL, parent product, variant, lead image, price and review status. Route duplicates and incomplete listings for an explicit decision.
Keep stock and pricing accurate
Choose one source of truth for stock and decide when an order reserves inventory. When several storefronts show the same stock, updates must account for orders from every channel. Test ordinary and problematic SKUs before enabling all categories.
Your site price can differ from marketplace prices because payment, delivery, advertising and support costs differ. Agree on pricing rules before importing amounts.
Reconcile fields before loading the catalog
Map the seller SKU, marketplace ID, category, attributes and variants across both sources. Identical SKUs do not always mean identical products, and the same product can use different SKUs. Resolve those conflicts manually before import; automatic SKU-only merging can hide part of your assortment.
Record a result for each source item: new product, variant of an existing product, archived item or exception with a reason. After import, compare the number of active source items against new products and variants. This reconciliation lets you accept the technical result without guessing from the catalog appearance.
Accept the result
Review totals for active SKUs, imported listings, merged duplicates and errors. Check several items from different categories for title, variants, price, images, stock and URL. Place a test order and compare stock against the source.
We can begin with a source audit and show how the unified catalog will look on your website before committing to launch.
Frequently asked questions
Does the ₽149,000 package include the store and catalog migration?
Yes, if a sample export confirms the agreed scope. The package includes the store, checkout, selected payment and delivery options, SKUs from the approved list, order notifications, statuses and website stock updates from one source. We record the list and exceptions before contracting; a different scope receives a separate estimate.
How will I know no products were lost during migration?
We record the active source SKUs, then provide a reconciliation for every item: new listing, variant or documented exception. We check categories, images, prices and a test order with you before acceptance.
Must marketplace sales stop during launch?
No. Your own website becomes an additional channel. If several channels sell the same physical stock, we agree on a separate synchronization design to avoid selling unavailable items.
Who will run the store after launch?
Under a separate agreement we can manage listings, prices, stock, replenishment planning, orders, customer inquiries, delivery, promotions and analytics. Responsibilities and reporting are agreed before work starts.