Overview

Draft note (delete before publishing): Everything in [brackets] is a placeholder. Swap in the real merchant name, location, category, and metrics. Don't publish invented numbers — confirm each figure with the merchant first.

[Merchant Name] sells [product category] in [city / market], across [website, Instagram, WhatsApp, marketplace]. By early [year], they had a good problem and a bad symptom: demand was growing, and they kept running out of their best sellers.

The problem: four answers to one question

Like a lot of growing stores, [Merchant Name] sold in several places at once. Each channel tracked stock a little differently:

• The website said one number.
• The team answered DMs from memory.
• The marketplace listing lagged a day behind.

So "is this in stock?" had no single answer. The result was predictable — they oversold items they didn't have and sat on items they thought were gone. [Add a concrete example: e.g. "During [campaign], they sold [N] units of a product with [M] in stock."]

The switch

[Merchant Name] moved to Stella over [timeframe], following a staged cutover so they never stopped selling. (Link to the 7-day playbook if relevant.) The key change wasn't a new storefront — it was a single source of truth for inventory that every channel now reads from.

On top of that, they set low-stock rules: when a SKU dropped below [threshold], Stella [flagged it / triggered a reorder / paused promotion]. [Confirm exactly what was configured.]

The results

[Pull a real quote from the merchant here — keep it specific, not generic praise.]

After [timeframe] on Stella:

• Stockouts on top sellers dropped by [X]%. (confirm)
• Time spent manually reconciling inventory fell from [hours/week] to [hours/week]. (confirm)
• [Add one more outcome the merchant actually cares about — revenue, fewer refunds, faster restocks.]

Why it worked

None of this was about a smarter chatbot. It was about giving the store one reliable backend so the numbers stopped disagreeing — and then letting simple rules act on those numbers automatically. That's the whole thesis of a commerce backend.

Want results like [Merchant Name]'s? Book a demo.