Charopis is an engine for product-description drafts in e-commerce. Generation takes about a minute. Publishing is not automatic: an operator reads, edits, and only then approves the copy in the store.
📋 Project metrics
- Start: 14 May 2023 (Initial Repo)
- Status: Production deployment (skladmuzyczny.pl)
- Role: Full-Stack Developer / Architect
- Goal: Shorten time-to-market for new products
🚀 Product journey
- Proof of Concept (Postman) — API called manually to test prompts and content quality.
- MVP (React UI) — simple split-screen UI; operator verified the text and copied it to the CMS.
- Automation (Playwright) — automated entry into the store panel without copy-paste.
- Production (Native API) — native communication with SOTE and Shoper APIs delivered stability and speed.
🎯 Business problem
In the music industry, descriptions must be precise (wood type, pickup type, tone characteristics). Writing such content for thousands of SKUs caused losses and blocked online sales.
❌ Pains and operational challenges
- Time loss: Tedious writing instead of store growth and customer service.
- No quality guarantee: Hard to keep high quality at scale.
- Instability and inconsistency: Uneven structures hurt the professional image.
- Bottleneck on new deliveries: Hundreds of products waited for publication because copywriting was the bottleneck.
- Duplicate content: Copying producer descriptions hurt SEO — unique content was needed.
💡 Why it works (product approach)
- Deep industry context: Converts technical data into benefits language with proper musical terminology.
- Human-in-the-loop: Operator reviews the draft in the CMS, eliminating hallucinations and protecting quality.
- Security and onboarding: Kinde (SSO) simplifies access management and secures login.
- Multi-platform integrations: Native support for SOTE and Shoper APIs enables scaling across platforms.
📈 Business impact (ROI)
| Metric | Before Charopis | With Charopis | What it actually means |
|---|---|---|---|
| Draft | 30-60 minutes of writing from scratch | about 1 minute of generation | The engine produces a draft, not a finished description |
| Review | Writing and editing in one step | Manual review of the draft | Time to publish depends on the operator |
| Bottleneck | Copywriting blocked new SKUs | Drafting no longer blocks intake | Pace is limited by human approval, not by AI |
“Charopis took the unbearable extra work off our shoulders. Today we can’t imagine working without this system.”
🛠️ Architecture & tech stack
- Logic: Express.js + Bull.js + Redis (task queues with retries)
- Interface: Next.js / React (responsive operator panel)
- Auth: Kinde (SSO)
- LLM orchestration: Openrouter
- Integrations: SOTE API, Shoper API (native CMS connection)
- Infra: Docker Compose + Dokploy (own VPS management)
🚀 Next steps
- Visual monitoring of task progress (queue UX)
- Extensions to import fields not natively supported by e-commerce APIs
- Many other product ideas that are hard to summarize in a few words
Artefacts
- Site: https://charopis.pl