A single gateway for working with marketplaces: stock, prices, and orders in 1C, with support for multiple legal entities and FBS/FBO.
22.10.2025 Ready-made 1C modules do not fit every case: custom changes are needed when there are multiple legal entities.
A single control point (1C) reduces workload and makes oversight easier.
Automating stock, pricing, and orders is critical for stable marketplace sales.
Using a standard solution with customization provides flexibility and scalability without losing support. Reading time: 10 min.
A large B2B trading company in electronics and accessories approached our partners.
It sells its products to wholesale buyers, develops a retail network, and accepts preorders on the website.
At the start of the project, accounting was handled in 1C:Trade Management 11, warehouse operations in WMS, and financial accounting in 1C:Accounting. In 2024, the client decided to enter marketplaces - Wildberries, Ozon, and Yandex Market.
The market was growing rapidly, competitors were already using this channel, and the company's turnover through traditional B2B channels was stagnating.
It was not enough just to "launch"; we had to do it quickly and with minimal operating costs while keeping accounting systems orderly.
Before the marketplace integration was implemented, the business faced a number of problems:
Inability to scale sales quickly.
The company planned to sell hundreds of item master records across several marketplaces.
Each marketplace requires its own export format, separate authorization, and configurable listings.
Marketplace out-of-the-box solutions could not account for the company's specifics: multiple legal entities, different warehouses and prices, and requirements for product labeling and traceability.
Disconnected accounting systems. 1C:Trade Management and WMS were maintained separately, and the interfaces differed.
Order data from the website and wholesale inquiries
came into the system with delays, which meant stock could not be updated in time in 1C.
Adding another channel without automation threatened total chaos.
Lack of transparency in stock and pricing.
Marketplaces require accurate stock data and up-to-date prices.
Manual uploads can cause errors: employees forget to update the price, send an incorrect stock level, the item goes negative, and the marketplace blocks the seller.
High requirements for order processing speed.
Marketplaces work like this: the seller must confirm the order, pick it, pack it, and ship it to a pickup point within 24 hours.
With manual order processing, this is hard to maintain, especially with dozens of orders a day.
These problems required a comprehensive solution: without organizing the processes, entering marketplaces risked chaos and fines.
To launch sales on marketplaces, we created a single gateway between 1C and the marketplaces.
Our partners reviewed standard 1C marketplace integration modules. In 1C:Accounting versions starting from 3.0.114 and in 1C:Trade Management 11.5, there are built-in tools for Wildberries, Ozon, and Yandex Market. They allow catalog, stock, and order exports, but by default they work with one legal entity and one warehouse.
In our case, there were several legal entities, so we chose the 1C-Rarus FBS/FBO module, which supports multiple organizations, warehouse units, and FBS/FBO schemes. The module is built on the 1C platform, so it can be extended without losing support.
To ensure error-free product export, we cleaned up the item master: each product received a unique SKU, a valid barcode, attributes, and labeling. We used the FBS module's item matching mechanism: the system automatically matched products by SKU and barcode, and created cards for new items based on marketplace data.
For each marketplace (Wildberries, Ozon, and Yandex Market), our partners registered accounts and obtained Client ID, Secret Key, and API keys. In the module, we configured: the organization selling the goods; the operating model (FBS) and label size for shipping documents; minimum stock levels (when stock is above 50 in 1C, we export 100 units to improve search ranking; if stock is below 50, we export the actual quantity); price types: retail, wholesale, and discounts; and warehouse-to-marketplace mapping.
Flexible settings allow one item to be sold at different prices and from warehouses belonging to different legal entities.
Our partners configured scheduled jobs:
Fast updates - every 15 minutes, the module sends current stock levels to marketplaces via API.
This mode minimized the risk of selling something that was already out of stock.
Full export - the entire catalog with updated prices is exported twice a day.
Order synchronization - every 5 minutes, the module checks for new orders and updates their statuses.
Thanks to automation, employees no longer track stock manually, and prices and availability are always up to date.
For each marketplace, we designed an end-to-end business process: Internal shipment creation.
The module automatically creates a "Picking Order" document (internal order) for the warehouse when a marketplace order is received. Picking and packing.
Warehouse staff see the list of items, pick them, and label them in accordance with Chestny Znak requirements.
The FBS module supports handheld data terminals (HDTs), allowing labeling codes to be scanned and recorded automatically in 1C.
Printing the label and completing the shipping document.
The system generates a label barcode (100x150 mm or 58x40 mm, depending on the setting) and prints several waybills at once. Order transfer to the marketplace.
After packing, the "Sales" document is sent to the marketplace automatically.
Employees track the status (accepted, delivered, canceled) directly in 1C. Returns and claims.
When an order is returned, the system creates a return document, uploads the sold-items report, and automatically allocates the marketplace commission.
This process allows employees to use the familiar 1C interface to handle online orders without switching between marketplace dashboards.
Our partners ran a pilot on a limited assortment (50 SKU) and confirmed that the exchange works correctly. They then trained warehouse staff, accounting staff, and sales managers. They learned to manage stock, track order statuses, and print shipping documents.
The company sells on behalf of four organizations.
Our partners set up order allocation rules: each legal entity is responsible for its own region and assortment, and the module automatically selects the appropriate organization based on the warehouse and item.
This solution was critical, since standard modules do not support work with multiple legal entities.
Following these steps made it possible to build a reliable and scalable marketplace operations system that takes both the client's specifics and marketplace requirements into account.
As a result of the integration, we achieved significant improvements:
Revenue growth and expansion into new channels.
Within three months, the client launched sales on Wildberries, Ozon, and Yandex Market.
The number of orders increased 12x, and turnover grew by 40%. Three more marketplaces are planned to be connected during 2025.
In the traditional setup, when marketplace orders were entered into 1C manually, picking one order took 20-30 minutes.
After automation, all documents (order, picking, sales, label printing) are generated automatically.
Order assembly now takes 12-15 minutes, and the logistics team can ship up to 500 orders a day without additional staff. Fewer errors and fines.
Automatic stock and price updates reduced cancellations due to out-of-stock items by 80%.
Properly configured scheduled jobs and automatic validation of details almost completely eliminated incorrect submissions, reducing penalties from marketplaces.
Transparency for accounting and logistics.
All order documents (orders, sales, returns) are created in 1C and linked to financial accounting.
Accounting can quickly see marketplace commissions, amounts due, and reconcile reports using standard 1C tools.
Flexibility in assortment management.
The company learned to quickly add new products, change prices, and manage promotions.
There is no need to keep separate spreadsheets for each marketplace anymore - everything runs from 1C.
The project went through five key stages:
Business process analysis and module selection.
We studied marketplace requirements, assessed the capabilities of standard modules, and chose a solution that supports FBS/FBO, multiple legal entities, and API.
Data normalization and item master setup.
We cleaned up the master data and added missing barcodes, attributes, and labeling.
We configured the stock and price export rules. Module integration and adaptation.
We configured API keys, created rules for assigning orders to legal entities, and set up scheduled jobs for exporting stock, orders, and prices. Pilot project and refinements.
We ran a test on a limited assortment and verified catalog export, order processing, and label printing.
Based on the pilot results, we adjusted processes and fixed errors.
Scaling and staff training.
After a successful pilot, we connected the remaining product groups and marketplaces.
We trained employees to work with the module, created instructions, and set up support.
Completing these stages in sequence made it possible to minimize risks and gradually extend the project to the full assortment and all marketplaces.
During the project, we encountered several typical challenges:
Different departments used different names for the same item and different barcodes.
This meant the module could not link the ordered item to the product card in 1C.
We created a unified item master and introduced a rule: every new product must have a unique SKU and a valid barcode.
To process legacy data, we built a matching program that automatically merged identical items.
Working with multiple legal entities.
Standard modules exported data on behalf of a single legal entity.
We expanded the module by linking the legal entity to the warehouse and product category. Now, when an order comes from a Moscow warehouse, it is automatically issued under the Moscow legal entity, while an order from a regional warehouse is issued under another one. Order processing speed.
Initially, orders came in batches, and staff could not process them fast enough.
Our partners configured scheduled jobs so the system checks for new orders every five minutes, and every two minutes during peak hours. Labeling and Chestny Znak.
For products with mandatory labeling, individual codes must be specified.
We connected handheld data terminals (HDTs) so employees could scan codes and send them automatically to 1C.
The integration module supports this processing, which helped avoid errors when transferring codes to marketplaces. Returns and claims.
Returns were handled through the FBO module: when a return report is received, the system automatically creates return documents, allocates the commission, and writes off the goods.
This eliminated delays in returns and reduced the number of manual operations.
Overcoming these challenges made the solution reliable and allowed sales to scale without quality loss.
Using 1C marketplace integration based on a standard module customized to the client's needs delivered several clear advantages: a single point of sales management.
All operations are performed in 1C: from catalog export to printing shipping documents.
Employees do not waste time learning each marketplace's dashboard, and managers get reporting in a single interface. Lower operating costs.
Automation reduced labor costs for order picking, document printing, and stock updates.
The need for additional staff decreased. Error reduction.
The system checks availability and prices before export, and the "minimum stock" flag prevents selling out-of-stock goods.
Scanning labels reduced the risk of fines for violations. Flexibility and scalability.
The module is easy to configure for new marketplaces.
As early as 2025, according to the plan, the client will connect SberMegaMarket.
Examples from other companies show that expanding integration to new marketplaces brings hundreds of additional orders.
is aiming for similar results. Simplicity in accounting and control.
Accounting sees sales reports and accrued commissions in 1C and prepares sales and return documents correctly.
This simplifies reporting and makes it possible to pass inspections without issues.
These advantages gave the client a stable, transparent, and flexible marketplace sales management system that scales without losing efficiency.
"When the client set the goal of entering marketplaces, we fully understood the risks."
At first glance, it seems simple: upload products, get orders, and that's it.
In practice, you run into bureaucracy, different data formats, multiple legal entities, and strict picking deadlines.
During the process, we found that ready-made integrations are often designed for small businesses: they cannot work with multiple legal entities and warehouses.
For example, we added automatic legal entity selection by warehouse and separated minimum stock levels for different product groups."
The project is moving forward. In the coming months, the client plans to:
Launch the FBO model (Fulfillment by Operator).
This will make it possible to store part of the goods in marketplace warehouses and expand the delivery geography.
We integrate marketplace sales and returns reports so accounting automatically receives commission and logistics data. Pricing automation.
Create a module for dynamic price changes based on stock levels, shelf life, and competitor activity.
Integration with CRM and the loyalty system.
Link marketplace order data to the customer profile in CRM to offer personalized discounts and mailings.
Mobile apps for pickers.
Develop a mobile interface based on 1C or third-party solutions so a picker can confirm assembly, scan labels, and print a label directly from a smartphone. Training programs and support.
Prepare a series of webinars and video guides for new employees and counterparties.
These plans will help expand reach and improve marketplace performance in the future.
