Live in Rīga · 2,833 real orders processed

Turn live comments into paid orders

A customer types WOW/41/M/black on your live stream. CommentFlow reads it, prices it, sends a checkout link to Messenger, takes the payment and issues the VAT invoice — before the stream has even ended.

14-day pilot on your own live stream · No card required

Facebook Live Messenger Google Sheets BluOr Bank In-store till

No manual entry. Orders build themselves while you sell.

Three languages. Latvian, Russian and English, typos included.

Paid before packing. Checkout links go out in one tap.

Invoices on payment. Sequential, VAT-correct, LV or EN.

401 spellings mapped to 48 canonical colours — every one of them written by a real customer

The midnight spreadsheet

The stream ends at 22:40.
The real work starts at 22:41.

Without CommentFlow

  • Scroll back through 400 comments, copy them into a spreadsheet
  • Decode bleck, 4ernij, melns by hand — they all mean black
  • Message every customer a total, one conversation at a time
  • Chase transfers, tick names off a printed list
  • Type each invoice manually, hope the VAT adds up
  • Discover at packing time that two people bought size 41

With CommentFlow

  • Comments arrive as structured orders while the stream is still running
  • Spelling, language and size variants normalise automatically
  • Checkout links go out through Messenger in one tap
  • Card payments land in your own bank account, reconciled
  • VAT invoices generate on payment, in Latvian or English
  • Stock moves the moment an item is sold, in store or online

How it works

Four stages. One operator.

From a comment on a live video to a packed parcel and a filed invoice, without leaving the same screen.

1

Capture

Every comment reaches CommentFlow the moment it is typed — no scrolling back, nothing lost when the video ends.

  • Facebook Live — webhook straight from the Graph API
  • Messenger bot — orders placed in chat
  • Google Sheets — import a stream you already logged
  • In store — walk-ins typed into the till
2

Parse

A purpose-built engine reads how customers actually write — three languages, mid-sentence, with typos, several orders in one line.

  • 401 colour spellings collapse to 48 colours
  • Sizes — EU numeric, XS–XXL and Cyrillic
  • Multi-order comments split into separate lines
  • Anything ambiguous waits in the error queue
3

Collect

The customer gets a link, pays on their phone, and the paperwork writes itself. Your bank account, your merchant terms.

  • Checkout link delivered to Messenger
  • Mobile checkout in Latvian, Russian, English
  • Card payment through BluOr Bank
  • VAT invoice on payment — print or PDF
4

Fulfil

From paid to packed to posted, plus everything that happens over the counter — one ledger for both halves of the business.

  • Pack & ship queue with per-parcel codes
  • POS / till — cash, card, till close
  • Stock movement recorded on every sale
  • Venue reports — close a trip, get the PDF

What you get

Not a chat plugin.
The whole back office.

Everything a live seller needs between the comment and the courier — and everything the accountant asks for afterwards.

Live comment feed

Comments stream in as you sell, already matched to a product, a size and a price.

Multilingual parser

Latvian, Russian and English — including the misspellings your customers actually type.

Error queue

Whatever the engine can't read with confidence waits for one tap from an operator. Nothing silently vanishes.

Checkout & payments

Messenger checkout links, a mobile payment page in three languages, card payment via BluOr Bank.

Automatic invoices

Sequential numbering, 21% VAT, Latvian or English, generated the moment payment clears.

POS & till

Sell over the counter in cash or card, capture walk-in customers, close the till with a summary you can trust.

Venues & trips

Run a buying trip or a second location as its own venue, with its own catalogue, stock and closing report.

Finance analytics

Revenue trend, payment mix, margin by product, till performance — read from your own ledger, not an estimate.

Catalogue & stock

Products with photos, sizes, colours and cost prices. Every sale writes a stock movement.

Owner & operator roles

Staff run the stream and the till. Revenue reports and the closed-trip archive stay with the owner.

Your data, kept

An isolated database per account, verified daily backups, ten-second replication, a snapshot before every schema change.

Built for one hand

Mobile-first, dense and keyboard-fast. Designed to be used while a live stream is actually running.

Already in production

This isn't a prototype.
It runs a shop every week.

CommentFlow was built for WOW — World of Women SIA, a fashion retailer in Rīga selling through Facebook Live, a store on Lāčplēša iela and buying trips abroad. Every number below comes from that live system, not a demo dataset.

2,833Orders processed
703Customers
860Invoices issued
401Spellings mapped
49Till closes
2Countries, one ledger

Figures as at August 2026, from the live production database.
New accounts start empty — your numbers are your own.

Pricing

Priced per shop.
Not per comment.

Every plan starts with a 14-day pilot on one of your own live streams. If the orders don't come out cleaner than your spreadsheet did, you owe nothing.

Starter

€89/month

One operator running one stream at a time. Everything needed to stop using a spreadsheet.

  • Live comment capture & parsing
  • Error queue
  • Messenger checkout links
  • Automatic VAT invoices
  • 1 venue, 1 operator seat
  • Verified daily backups
Start a pilot
Most shops

Studio

€189/month

A stream, a store and a team. The full back office, including everything over the counter.

  • Everything in Starter
  • POS & till with cash and card
  • Catalogue, stock movements, cost prices
  • Finance analytics & margin
  • Up to 5 operator seats
  • Owner / operator permissions
Book a demo →

Scale

Let's talk

Several venues, buying trips, or a data history that needs bringing across.

  • Everything in Studio
  • Unlimited venues & trip reports
  • Historical data migration
  • Guided onboarding on a live stream
  • Custom parser vocabulary
  • Priority support
Talk to us

Prices in EUR, excluding VAT. Billed monthly, cancel any time.
Card payments require your own BluOr Bank merchant account — money moves between your customer and your bank, never through us.

FAQ

The questions sellers actually ask.

Do I need my own Facebook page and app?

You need your own page — that's where your audience is. To read comments the moment they're posted, CommentFlow connects to it through the Facebook Graph API with a page access token you authorise. If you'd rather not connect the API at all, orders can arrive through a Messenger bot or be imported from a Google Sheet after the stream.

How well does the parser really work?

It handles Latvian, Russian and English, mixed inside a single comment, with the typos people make on a phone at speed. 401 colour spellings resolve to 48 canonical colours; sizes cover EU numeric, XS–XXL and Cyrillic letters. One comment can contain several orders and will be split into separate lines.

It is deliberately conservative: when a comment is ambiguous it goes to the error queue for an operator instead of guessing. Recurring spellings from your own customers get folded into your vocabulary.

How do payments work, and who holds the money?

Customers pay by card or bank transfer through BluOr Bank, using your own merchant account. Funds move from your customer to your bank; CommentFlow never touches them. We generate the checkout, watch for confirmation and issue the invoice on payment. Other gateways can be added for Scale accounts.

We also sell in a physical store. Does that fit?

Yes, and it was built for exactly that. The POS and till handle cash and card sales, capture walk-in customers, keep a filterable sales history and produce a till close. Stream orders can be collected in store rather than posted. Stock moves on every sale, whichever channel it came from. CommentFlow works perfectly well for a shop that never streams.

Can I bring my existing orders and catalogue across?

Catalogue and order history import from Google Sheets or CSV during onboarding. Larger or messier histories are part of the Scale plan, where we do the migration with you and verify the totals against your own accounts before switching over.

Where does my data live, and what happens if something breaks?

Each account gets its own isolated database and storage volume — your ledger is never mixed with another shop's. Backups run daily and are integrity-checked before they replace the previous one; a corrupt download is discarded rather than trusted. Writes replicate every ten seconds, and a snapshot is taken before any schema change.

If your policy requires a specific hosting region, ask us — we'll confirm exactly where your instance sits before you sign anything.

Can my team use it without seeing the revenue?

Yes. Operators run the stream, the queue and the till. Venue revenue, margin reports and the closed-trip archive are restricted to the owner account.

What does onboarding actually involve?

A pilot on one real live stream. We set up your account, load your catalogue, connect your page and sit with you through the first stream. If your orders don't come out cleaner than your spreadsheet did, you walk away and owe nothing.

Free · no card required

Bring us your messiest stream.

Send a link to a live video you've already run. We'll parse the real comments from it and show you the orders it should have produced — before you commit to anything.

Or write to us directly: hello@commentflow.lv

We reply within one working day.