Case Study

Nahid’s World — we turned a perishable-food brand into a nationwide desk they run every day.

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.

nahidsworld.comCustom PHP + MySQLStore · POS · Collect · Accounts
Nahid's World desktop homepage

44,000+

Orders already on the platform

4

Sales channels in one desk

COD first

Payment culture

Nationwide BD

Market

The factory

One ticket from first message to deposit.

01
04
B

SmartB path

Intake

Ticket

Four 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.

Desk

Order

POS, collect, or landing

Counter stock becomes a Direct Order. Sourced fish becomes Collect → Call → Convert. A mango landing still posts into Orders.

Last mile

Delivered

Assign, ride, or courier

Ready-to-assign pool. Own riders + gonahid inside Dhaka. SA Paribahan for frozen, Steadfast bulk for grocery.

Money

Deposit

Accounts on the day of sale

COD collection → deposit. Sale income from the order. Customer credit is a ledger, not a rumour.

Compare

How much of the work lived in one system.

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

Old desk Platform

How the desk helps

POS, landings, WhatsApp, reports, accounts — one scroll.

01 · WhatsApp

All-in-one WhatsApp order

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.

  • Website, Messenger, WhatsApp, and hotline all create a ticket
  • Mobile lookup before a second promise
  • Convert to a normal order when the fish is confirmed

02 · POS

How POS helps the counter and the phone

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.

  • Direct order when stock is on the counter
  • Collect POS when fish still has to be sourced
  • Credit, COD, bKash, and bank on the same ticket

03 · Landing

How a landing page helps a season

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.

  • Seasonal page without a deploy
  • Quick checkout on the same catalog
  • Campaign traffic does not skip operations

04 · Reporting

Backend order reporting the owner can filter

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.

  • Channel mix: website, WhatsApp, Messenger, tele-sales, B2B
  • Status-change dates, not only created_at
  • Bulk print, Steadfast export, Excel out

05 · Accounting

Accounts start on the day of the sale

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.

  • Assets, income, expense, loans on one dashboard
  • COD collection → deposit closes the rider loop
  • Credit outstanding is a ledger, not a notebook
How to order page listing website, Messenger, WhatsApp, and hotlineWeight-aware catalog the POS and the website shareAmrapali mango landing page with campaign copy and order CTAPublic storefront that writes into the same order bookShipping rules for own fleet, SA Paribahan, and Steadfast

Desktop storefront

Captured from the live shop at 1440.

Homepage · CMS banners + categories
Homepage · CMS banners + categories
Fish catalog · weight + price filters
Fish catalog · weight + price filters
How to order · four official channels
How to order · four official channels
Landing · seasonal campaign page
Landing · seasonal campaign page
Shipping · fleet, SA Paribahan, Steadfast
Shipping · fleet, SA Paribahan, Steadfast
dpanel · staff enter the operations desk
dpanel · staff enter the operations desk

Before / after

The sales desk is now a queue the whole team can finish.

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.

Start a project