AI Product Description Generator for Marketplaces

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
AI Product Description Generator for Marketplaces
Medium
~3-5 days
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1361
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1189
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

Development of AI Product Description Generation System

Manual copywriting for a catalog of 10,000 products takes 3–4 months. An AI system reduces this to a week, generating up to 10,000 descriptions per day — 50–100 times faster than manual work. We use GPT-4o, asynchronous batch processing, and adapters for Wildberries, Ozon, Amazon. In one project for an online store with 15,000 SKUs, we reduced the copywriting budget by an order of magnitude and cut the time to launch on marketplaces from 3 months to 2 weeks.

Why Automation of Descriptions Is Critical for E-commerce

Manual writing does not scale: when the assortment grows from 1,000 to 10,000 SKUs, copywriting costs multiply, and timelines reach 3–4 months. An LLM-based system solves this: once the architecture is developed, you get an unlimited stream of SEO-optimized texts for any platform. LLMs guarantee a consistent style and eliminate typical errors — typos, duplication, mismatched attributes.

What Problems Does the AI Generator Solve?

High cost and long timelines. Manual writing has a high cost per description, and for a catalog of 10,000 products it takes months. Our system reduces cost by an order of magnitude: cost per description becomes negligible, and time drops to 2 seconds.

Inconsistent quality. Different copywriters write differently, harming brand perception. The LLM generator uses a single prompt and rules for each platform, ensuring uniformly high quality for all products.

Limited SEO optimization. Copywriters rarely consider all key queries and search engine requirements. The system automatically generates meta tags, titles, and descriptions optimized for the specific marketplace.

System Architecture

Core Generator Code (GPT-4o)
from openai import AsyncOpenAI
from dataclasses import dataclass
from typing import Optional
import asyncio

client = AsyncOpenAI()

@dataclass
class ProductData:
    name: str
    category: str
    brand: str
    sku: str
    attributes: dict          # {color: "red", size: "M", material: "cotton"}
    images: list[str] = None  # URL изображений
    price: float = None
    target_audience: str = ""

@dataclass
class GeneratedDescription:
    title: str              # SEO заголовок
    short_description: str  # 150–200 символов (превью на маркетплейсе)
    full_description: str   # HTML с форматированием
    bullet_points: list[str]  # 3–7 ключевых преимуществ
    seo_keywords: list[str]
    meta_description: str   # 160 символов для SEO

class ProductDescriptionGenerator:
    def __init__(self, platform: str = "general"):
        self.platform = platform
        self.platform_configs = {
            "wildberries": {"max_title": 60, "max_desc": 4000, "bullet_count": 5},
            "ozon": {"max_title": 100, "max_desc": 6000, "bullet_count": 7},
            "amazon": {"max_title": 200, "max_desc": 2000, "bullet_count": 5},
            "general": {"max_title": 80, "max_desc": 3000, "bullet_count": 5},
        }

    async def generate(
        self,
        product: ProductData,
        tone: str = "professional",
        language: str = "ru"
    ) -> GeneratedDescription:
        config = self.platform_configs.get(self.platform, self.platform_configs["general"])

        # Если есть изображения — используем GPT-4 Vision
        if product.images:
            return await self.generate_from_images(product, config, tone, language)
        else:
            return await self.generate_from_text(product, config, tone, language)

    async def generate_from_text(
        self,
        product: ProductData,
        config: dict,
        tone: str,
        language: str
    ) -> GeneratedDescription:
        attributes_str = "\n".join([f"- {k}: {v}" for k, v in product.attributes.items()])

        response = await client.chat.completions.create(
            model="gpt-4o",
            messages=[{
                "role": "system",
                "content": f"""Ты — эксперт по написанию продающих описаний для {self.platform}.
                Тон: {tone}.
                Язык: {language}.
                Ограничения: заголовок до {config['max_title']} символов,
                описание до {config['max_desc']} символов,
                {config['bullet_count']} буллетов преимуществ.

                Создай описание товара. Верни JSON с полями:
                title, short_description, full_description (HTML),
                bullet_points (массив), seo_keywords (массив), meta_description."""
            }, {
                "role": "user",
                "content": f"""Товар: {product.name}
                Бренд: {product.brand}
                Категория: {product.category}
                Характеристики:
                {attributes_str}
                ЦА: {product.target_audience or 'не указана'}"""
            }],
            response_format={"type": "json_object"}
        )

        data = json.loads(response.choices[0].message.content)
        return GeneratedDescription(**data)

    async def generate_from_images(
        self,
        product: ProductData,
        config: dict,
        tone: str,
        language: str
    ) -> GeneratedDescription:
        """Используем Vision для анализа фото товара"""
        import base64

        image_contents = [
            {"type": "image_url", "image_url": {"url": url}}
            for url in product.images[:3]  # Максимум 3 изображения
        ]

        response = await client.chat.completions.create(
            model="gpt-4o",
            messages=[{
                "role": "user",
                "content": [
                    {"type": "text", "text": f"""Проанализируй изображения товара и создай описание.
                    Платформа: {self.platform}. Тон: {tone}. Язык: {language}.
                    Дополнительные данные: Категория: {product.category}, Бренд: {product.brand}.
                    Верни JSON: title, short_description, full_description, bullet_points, seo_keywords, meta_description."""},
                ] + image_contents
            }],
            response_format={"type": "json_object"}
        )

        data = json.loads(response.choices[0].message.content)
        return GeneratedDescription(**data)

How the System Processes Catalogs from CSV/Excel

For loading products from CSV, we use batch processing: process_product_catalog reads the file, splits it into batches of 20 products, and generates descriptions in parallel via asyncio. Errors are handled with return_exceptions — a failure on one product does not stop the entire flow.

import pandas as pd
import asyncio

async def process_product_catalog(
    catalog_path: str,
    platform: str = "wildberries",
    batch_size: int = 20
) -> pd.DataFrame:
    df = pd.read_csv(catalog_path)
    generator = ProductDescriptionGenerator(platform=platform)
    results = []

    for i in range(0, len(df), batch_size):
        batch = df.iloc[i:i+batch_size]
        tasks = []

        for _, row in batch.iterrows():
            product = ProductData(
                name=row["name"],
                category=row["category"],
                brand=row.get("brand", ""),
                sku=row.get("sku", ""),
                attributes={k: row[k] for k in row.index if k not in ["name", "category", "brand", "sku"]}
            )
            tasks.append(generator.generate(product))

        batch_results = await asyncio.gather(*tasks, return_exceptions=True)
        for j, result in enumerate(batch_results):
            if isinstance(result, GeneratedDescription):
                row_data = batch.iloc[j].to_dict()
                row_data.update({
                    "generated_title": result.title,
                    "generated_short_desc": result.short_description,
                    "generated_full_desc": result.full_description,
                    "generated_bullets": " | ".join(result.bullet_points),
                    "seo_keywords": ", ".join(result.seo_keywords),
                })
                results.append(row_data)

    return pd.DataFrame(results)
Parameter Manual Copywriting AI System
Throughput 50–200 descriptions/day 1,000–10,000 descriptions/day
Cost per description (at 10,000 volume) High Significantly lower
Time for 10,000 SKU catalog 3–4 months 1–2 weeks
SEO optimization Depends on copywriter Built-in rules for each platform
Multilingual Needs translator Generation in any language

Adaptation for Platforms

For each marketplace (Wildberries, Ozon, Amazon), we provide separate formatter classes. They handle character limits, structure requirements, and keywords. Example formatters:

class WildberriesFormatter:
    def format(self, desc: GeneratedDescription) -> dict:
        return {
            "наименование": desc.title[:60],
            "описание": desc.full_description[:4000],
            "характеристики": "\n".join(desc.bullet_points),
        }

class OzonFormatter:
    def format(self, desc: GeneratedDescription) -> dict:
        return {
            "name": desc.title[:100],
            "description": desc.full_description,
            "short_description": desc.short_description,
            "keywords": desc.seo_keywords,
        }

How Is SEO Optimization Ensured?

The system uses SEO rules for each platform: character limits, keywords, title structure. The prompt receives category, brand, and attributes, enabling relevant descriptions. Additionally, we apply few-shot and chain-of-thought techniques to improve quality. For Wildberries, the system automatically inserts popular queries into the title and meta description.

What Is Included in a Turnkey System Development?

  1. Architecture and code — core generator, support for text and images (GPT-4 Vision), batch CSV/Excel processing.
  2. Marketplace integration — adapters for Wildberries, Ozon, Amazon, direct API upload.
  3. Documentation — API description, instructions for adding new platforms, model card.
  4. Team training — 2 online sessions for configuration and operation.
  5. 2-week post-launch support — bug fixes, prompt fine-tuning.

Timeline and How We Work

Stage Duration
Analysis and design 2–4 days
Generator development 5–10 days
Marketplace API integration 5–10 days
Testing and refinement 3–5 days
Deployment and training 2–3 days

Cost is calculated individually after analyzing your catalog and integration requirements. Our team has specialized in AI solutions for e-commerce for over 5 years and has completed over 30 projects. We guarantee quality: each description undergoes validation against platform SEO rules.

Contact us to evaluate your project. Get a consultation on architecture and a preliminary timeline estimate.

Generative AI Development: From Prompt to Production API

We often receive a task "generate a product image" — on the surface it seems simple. But behind this lies a choice between dozens of models, configuring the inference pipeline, manually solving consistency issues, integrating into the product backend, and answering why the model generates hands with six fingers in staging but not in production. Let's break down the directions we work with.

Image Generation: From Prompt to Production API

The current landscape includes FLUX.1 [dev/schnell/pro] from Black Forest Labs and Stable Diffusion 3.5. FLUX.1 [schnell] takes 4 steps instead of 20–50 for SDXL — 5–12 times faster — while maintaining higher quality. On an A100 80GB — 1.2–1.8 s per 1024×1024 image at batch_size=4.

A typical deployment issue: FLUX.1 [dev] requires 24+ GB VRAM in fp16. On A10G 24GB it fits tightly; at batch_size>1 — OOM. Solution: torch_dtype=torch.bfloat16 + enable_model_cpu_offload() from diffusers, or quantization via bitsandbytes to NF4 — minimal quality drop, memory consumption drops to 12–14 GB.

ControlNet and IP-Adapter are key tools for production tasks where controllability is needed. ControlNet with Canny/Depth/Pose maps provides structural control. IP-Adapter (especially IP-Adapter-FaceID) allows transferring character identity to generations — this is the foundation for personalized content. More about ControlNet can be found on Wikipedia.

Case study: e-commerce photography. A retailer with 8000 SKUs needed lifestyle photos for each product. Pipeline: product segmentation (Segment Anything Model 2) → background removal → inpainting with FLUX.1 [dev] using product image as IP-Adapter reference → upscale via RealESRGAN_x4plus. The generation cost is negligible compared to professional photography, providing huge savings. Throughput — 200 images/hour on 2× A100. Our extensive experience from 30+ projects ensures we select the optimal model for your task — an evaluation can be obtained upfront.

Why Is Model Selection Only Half the Battle?

Fine-tuning for a Specific Style or Character

Dreambooth and LoRA are the standard for adapting to a specific visual style or object. LoRA trains in 2–4 hours on 20–30 reference images on a single A100. Rank 16–32 is usually sufficient for style; rank 64+ is needed for precise face reproduction.

A common mistake: training LoRA too long — the model overfits to references, losing the ability to vary. Sign: at cfg_scale=7, all images look like copy-paste of references. Solved by early stopping (usually 1500–2000 steps for 20 images) and prior_preservation_loss.

For deeper customization — full fine-tuning via diffusers + accelerate with FSDP on multiple GPUs. But that already takes 40–80 hours of training and requires a truly large dataset (1000+ images).

Comparison of Image Generation Approaches

Model Speed (1024×1024, A100) Quality (CLIP score) Controllability (ControlNet, IP-Adapter) VRAM (fp16)
Stable Diffusion 3.5 2.0–3.5 s 0.28–0.31 via ControlNet (allowed) 16–20 GB
FLUX.1 [schnell] 0.8–1.2 s 0.30–0.33 limited (no ControlNet) 12–14 GB (4‑step)
FLUX.1 [dev] 3–5 s (50 steps) 0.32–0.34 via IP-Adapter, ControlNet (adapter) 24+ GB
Midjourney (API) 5–10 s (queue) 0.31–0.33 prompt + style reference not required

Video Generation: Which Models Are Best?

Model Availability Duration Resolution Controllability
Sora (OpenAI) API (limited) up to 60 s 1080p prompt, image-to-video
Wan2.1 (Alibaba) open weights up to 81 frames 720p prompt, I2V, V2V
CogVideoX-5B open weights 6 s 720p prompt, I2V
Kling 1.6 API up to 30 s 1080p prompt, I2V
Mochi-1 open weights 5.4 s 480p prompt

Open-weight video models still lag behind commercial ones in stability and length. Wan2.1 is the best choice for self-hosting: 14B parameters, runs on 2× A100, delivers acceptable quality for short clips.

The main pain of video generation is temporal consistency: the character changes clothing color at the third second, objects "drift." Partial solution — generation with motion_bucket_id and noise_aug_strength in Stable Video Diffusion, or using I2V (image-to-video) instead of pure text-to-video. As noted in VideoPoet research, consistency is achieved by training on long sequences.

AnimateDiff remains a working tool for short loops and motion effects on top of SD/FLUX. Not Sora, but deployable locally and predictable.

Music and Audio Generation

AudioCraft from Meta (MusicGen + AudioGen) is a production-ready stack for music generation. musicgen-large (3.3B) generates 30 s of music in ~8 s on A100. Control via text prompt and melody conditioning — you can specify a melody by humming.

Stable Audio Open from Stability AI is an alternative with length up to 47 s, better structural control (intro/verse/chorus). Deployment is similar: diffusers + FastAPI.

For voice-over and dubbing — ElevenLabs API or self-hosted XTTS v2 (see Speech AI service). For sound design and foley — AudioGen.

3D Generation: Current Practical State

3D generation has not yet reached the same maturity as 2D. But for specific tasks, tools are already working:

TripoSG and Shap-E — text/image-to-3D. Shap-E from OpenAI generates simple 3D meshes in seconds, but geometry is rough. TripoSG gives more detailed results but requires post-processing (remeshing, UV unwrapping).

Wonder3D and Zero123++ — 3D reconstruction from a single image. They work by generating multi-views (6–8 views) and then 3D reconstruction via NeuS or instant-ngp.

Gaussian Splatting (3DGS) — not generation, but reconstruction from a series of photos/videos. For product cards and real estate it's already production: 50–200 photos → 3DGS model in 15–30 min on RTX 4090 → interactive 3D viewer in browser.

What Infrastructure Is Needed for Generative AI Deployment?

Critical for generative models:

  • Task queue — Celery + Redis or Ray Serve. Synchronous HTTP for image generation is unacceptable with >5 concurrent requests.
  • Caching — similar prompts yield similar results. Semantic cache via embeddings (faiss + sentence-transformers) can reduce GPU load by 20–40%.
  • Quality monitoring — CLIP score for text-image alignment, FID for evaluating generation distribution. Integrate into MLflow or Weights & Biases.
  • Storage — generated images immediately to S3/MinIO, not on the inference server disk.

What's Included in the Deliverables

We take the project turnkey — from model selection to deployment and monitoring. The result includes:

  • Model (or API integration) with performance benchmarks (latency p99, throughput).
  • Pipeline documentation (prompt engineering guide, model card, dependency versions).
  • Integration with your backend (REST/gRPC, queues).
  • Configured monitoring (dashboards, alerts for quality drift).
  • Training workshop for the team (2–4 hours).
  • Warranty support for 3 months after launch — as part of our quality certificate.

We have completed 30+ projects in generative AI — this gives us the right to guarantee results.

How Is the Generative AI Development Process Structured?

  1. Analysis (1–2 days): audit of current architecture, clarification of use case, selection of models and success metrics. We evaluate the project free of charge.
  2. Proof of Concept (1–3 weeks): quick prototype on your data — to see real quality, not blog demos.
  3. Design (1–2 weeks): pipeline architecture, infrastructure (GPU cluster/API), A/B testing plan.
  4. Implementation and fine-tuning (4–12 weeks): development, LoRA/full fine-tuning, integration with queue and cache.
  5. Testing (1–2 weeks): load tests, metric validation, edge-case verification (negative scenarios).
  6. Deployment and monitoring (1–2 weeks): production deployment, monitoring setup, documentation.
What We Verify at the Proof of Concept Stage
  • Alignment of expectations and actual generation quality (CLIP score, user study).
  • Inference speed at different batch sizes and GPU types.
  • Likelihood of toxic/incorrect generations — checking safety filters.
  • Scalability: will the model handle peak load.

Timeline Estimates

Integration of a ready API (DALL·E 3, Midjourney API, Stability API) — 1–2 weeks. Self-hosted pipeline with fine-tuning — 6–12 weeks. Full platform with UI, queues and monitoring — 3–6 months. The specific cost is calculated individually after analyzing your scenario.

Contact us — order a consultation, and we will select the optimal architecture for your project. Get a preliminary cost and timeline estimate for free.