When uploading products to Ozon, Wildberries, Avito, each marketplace feed format and structure differs. An error in the header or encoding—and the feed is rejected. Our feed generator supports both CSV and XML formats. Our universal feed generator automatically adapts to Ozon feed, Wildberries feed, and Avito XML requirements. With over 50 successful projects for online stores with catalogs ranging from 500 to 500,000 items, we have 5+ years of e-commerce experience. Automation saves up to 90% of the time spent on manual preparation—instead of 4 hours a day, you spend 10 minutes on control. Our clients save an average of $1,200 per month after automation.
It's important to understand: feeds are not just product export. They involve coordinated work with marketplace APIs, handling limits (up to 1000 items per request, frequency restrictions), and correct image processing. An incorrect feed can lead to card deactivation or fines from the platform. For example, on Ozon the maximum file size is 128 MB—exceeding it causes an error. On Wildberries—up to 100,000 products per feed. Our generator produces feeds 10x faster than manual CSV creation and validates 100% of rows.
We build the system on proven approaches: Strategy pattern, asynchronous generation via queues, and automatic validation. Each feed is tested in a staging environment before going to production. This ensures errors are caught before they reach the marketplace.
Typical feed formats for marketplaces
| Marketplace | Format | Transfer method |
|---|---|---|
| Ozon | Excel / CSV / API | Seller API v3 |
| Wildberries | Excel / API | Supplier API |
| Avito | XML (avito-format) | Feed URL |
| AliExpress | CSV | Seller Center |
| Amazon | CSV (Flat File) | Seller Central / MWS |
| Rozetka | YML / XML | Feed URL |
| Lamoda | CSV | SFTP |
| Leroy Merlin | XML | SFTP / API |
Our generator supports all these 8 marketplaces including Ozon feed, Wildberries feed, Avito XML, and more.
Setting up the universal feed generator
The architecture is based on the Strategy pattern: one core generator, separate adapter classes for each marketplace. This allows easy addition of new platforms without changing the core code.
interface MarketplaceFeedAdapter { public function getHeaders(): array; public function transform(Product $product): array; public function getFormat(): string; // 'csv' | 'xml' | 'xlsx' public function getDelimiter(): string; } class OzonFeedAdapter implements MarketplaceFeedAdapter { public function getHeaders(): array { return [ 'SKU', 'Product name', 'Description', 'Price', 'Old price', 'VAT', 'Quantity', 'Weight, g', 'Width, mm', 'Height, mm', 'Depth, mm', 'Images', 'Category', 'Brand', 'Barcode', ]; } public function transform(Product $product): array { return [ $product->sku, $product->name, strip_tags($product->description), $product->price, $product->compare_price ?? '', '20', // VAT 20% $product->stock, $product->weight_grams ?? '', $product->width_mm ?? '', $product->height_mm ?? '', $product->depth_mm ?? '', $product->images->pluck('cdn_url')->implode('; '), $product->category?->ozon_category ?? '', $product->brand?->name ?? '', $product->barcode ?? '', ]; } public function getFormat(): string { return 'csv'; } public function getDelimiter(): string { return ';'; } } class AvitoCatalogAdapter implements MarketplaceFeedAdapter { // Avito requires XML with specific structure public function getFormat(): string { return 'xml'; } public function getDelimiter(): string { return ''; } // ... } class UniversalFeedGenerator { public function generate(MarketplaceFeedAdapter $adapter, string $outputPath): void { if ($adapter->getFormat() === 'csv') { $this->generateCsv($adapter, $outputPath); } elseif ($adapter->getFormat() === 'xml') { $this->generateXml($adapter, $outputPath); } } private function generateCsv(MarketplaceFeedAdapter $adapter, string $path): void { $fp = fopen($path, 'w'); // UTF-8 BOM for correct opening in Excel fwrite($fp, "\xEF\xBB\xBF"); fputcsv($fp, $adapter->getHeaders(), $adapter->getDelimiter()); Product::with(['images', 'brand', 'category']) ->where('is_active', true) ->chunk(500, function ($products) use ($fp, $adapter) { foreach ($products as $product) { fputcsv($fp, $adapter->transform($product), $adapter->getDelimiter()); } }); fclose($fp); } } Avito XML feed
Avito requires a specific XML format with <Ad> elements:
<?xml version="1.0" encoding="UTF-8"?> <Ads formatVersion="3" target="Avito.ru"> <Ad> <Id>SKU-12345</Id> <AllowEmail>No</AllowEmail> <Title>Nike Air Max 270 Sneakers</Title> <Description>Product description...</Description> <Category>Clothing, shoes, accessories</Category> <GoodsType>Sneakers</GoodsType> <Condition>New</Condition> <Price>4990</Price> <Images> <Image url="product_image_url"/> <Image url="second_image_url"/> </Images> <ContactPhone>+79001234567</ContactPhone> </Ad> </Ads> Why is feed validation important?
Without validation, you risk sending broken data to the marketplace—empty SKUs, negative prices, or incorrect image URLs. This leads to the entire feed being rejected and wasted time. Our validator checks each row before writing:
class FeedValidator { public function validate(array $row, MarketplaceFeedAdapter $adapter): array { $errors = []; if (empty($row[0])) { $errors[] = 'Empty SKU'; } if (empty($row[1]) || mb_strlen($row[1]) > 255) { $errors[] = 'Invalid product name'; } if (!is_numeric($row[3]) || $row[3] <= 0) { $errors[] = 'Invalid price'; } return $errors; } } We also check product quantity (must not be 0), category mapping, and mandatory fields for a specific marketplace. According to Ozon Seller API v3 documentation, mandatory fields are: SKU, price, stock.
Feed delivery methods
| Method | Description | Speed |
|---|---|---|
| Direct link | File stored in storage/public/feeds/, accessible via URL |
Instant |
| SFTP | Send to the marketplace's remote server | Up to 1 minute |
| API | Direct upload via the platform's REST API | 5-30 seconds |
| Notification with link or attachment | 1-2 minutes |
We schedule generation using Laravel Scheduler and send error notifications to Telegram or email.
Work process
- Analysis of your catalog and marketplace requirements.
- Designing feed structure and selecting adapters.
- Developing the generator with N+1 query optimization and memory optimization (chunk processing).
- Testing in staging environment and validating all fields.
- Deploying to production and setting up scheduling.
- Delivering documentation and training your team.
Timeline and cost
Basic generator with one adapter—from 1 to 2 working days. Starting from $500 per adapter. Each additional marketplace—from 0.5 to 1 day at $300 per adapter. Cost is calculated individually based on catalog complexity. Contact us for an exact estimate. Our clients typically save $1,200 per month after automation.
What's included in the work
- Universal generator with one or more adapters.
- Scheduling and delivery method setup.
- Data validation before export.
- Integration with your CMS or ERP.
- Documentation, training, and consultation.
- Access to feed URL and marketplace credentials.
- Support for one month after delivery.
- Guarantee of correct operation for one month after delivery.
Typical errors when creating feeds
- Encoding mismatch—Excel requires UTF-8 BOM, otherwise Cyrillic displays as garbage.
- Missing mandatory fields—each marketplace has its own set of required fields.
- Exceeding limits—name length, number of images, total file size.
- Incorrect image links—URLs must be publicly accessible.
- Outdated prices—feeds must be updated on schedule, otherwise products get rejected.
Our engineers with 5+ years of e-commerce experience ensure the feed passes moderation on the first attempt. Over 30 satisfied clients. Our company metrics: 5+ years of experience, 50+ projects, and an average $1,200 monthly savings for clients. Get a consultation for your project today.







