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.