Intake
TicketFour channels, one ticket
Website, Messenger, WhatsApp, and the hotline still exist. Each now opens a Collect Request or a checkout order — not a private chat.
Case Study
Natural food, Bangladesh, nationwide. Fish is often sourced after the customer asks. Price is per kg. Most people pay after they inspect. We built the store, collect desk, POS, landings, reporting, and accounts around that flow — so a first WhatsApp becomes a packed invoice, a rider, and a deposit.

44,000+
Orders already on the platform
4
Sales channels in one desk
COD first
Payment culture
Nationwide BD
Market
The factory
SmartB path
Intake
TicketWebsite, Messenger, WhatsApp, and the hotline still exist. Each now opens a Collect Request or a checkout order — not a private chat.
Desk
OrderCounter stock becomes a Direct Order. Sourced fish becomes Collect → Call → Convert. A mango landing still posts into Orders.
Last mile
DeliveredReady-to-assign pool. Own riders + gonahid inside Dhaka. SA Paribahan for frozen, Steadfast bulk for grocery.
Money
DepositCOD collection → deposit. Sale income from the order. Customer credit is a ledger, not a rumour.
Compare
Process comparison — old desk vs the platform. Not a client KPI claim. The bars show where the work sat.
Operations coverage
WhatsApp / social intake
14% → 94%
Counter + phone POS
18% → 92%
Campaign landing pages
10% → 88%
Order book + reporting
16% → 95%
Accounting from the sale
12% → 90%
Dispatch + last mile
22% → 91%
Four channels, written down
Share of that channel that created a shared ticket — not a private chat.
Website checkout
WhatsApp + Messenger
Hotline 09639-203050
Walk-in / tele POS
How the desk helps
01 · WhatsApp
Customers still message Facebook, WhatsApp, or the hotline. That does not change. The desk does: one Collect Request holds name, mobile, zone, item, and weight. Statuses — Call, Followup, Collecting, Converted — are shared, not trapped in one person’s chat.
02 · POS
Walk-in and tele-sales used to bypass the shop. POS writes a Direct Order or a Collect Request in the same catalog the website uses — weight, zone, subzone, customer credit, and payment proof. The packing desk sees the ticket the cashier just made.
03 · Landing
Hilsha, mango, dates — campaigns used to wait on a developer. Landing pages are CMS screens: story, products, WhatsApp CTA, one-page checkout. Marketing ships a slug. The order still lands in Orders, not a form inbox.
04 · Reporting
One order book: website, POS, converted collect requests. Filter by channel, POS vs ecommerce, paid / unpaid / credit, created vs delivered date. Summary report and Excel replace a month-end reconstruction from chats.
05 · Accounting
Cash, bank, and MFS sit next to the order. Sale income can post from the order or collect request. Customer credit is deposit, usage, refund, settlement — a balance with history. Month-end is a report, not a rebuild.





Desktop storefront






Before / after
BeforeMessage sits in one person’s WhatsApp
AfterCollect Request or POS ticket in shared admin
BeforeWho calls the customer back is unknown
AfterCall → Followup is a visible status
BeforePrice argued in comments
AfterOne Set Price screen + history
BeforeRider assigned on the phone
AfterAssign Parcel pool + gonahid
BeforeCOD in personal wallets
AfterCash / MFS / bank ledger + deposit
BeforeCredit lives in someone’s head
AfterCustomer credit balance + settlement
Every fish and every taka attaches to a request or an order. Website, landing checkout, WhatsApp collect, or POS — all become Orders. Ready to assign → rider or courier → delivered → cash collected → deposit. Informal side channels are the old operation leaking back in.
Ready for the system your business has been waiting to run?
Bring the dream product. We’ll make a plan.