AutoProbaho

Illustrative scenario

Online retailer: from inbox orders to an automated order hub

A Bangladeshi online retailer typically sells through three doors at once — its own website, a Facebook page with WhatsApp follow-up, and a marketplace like Daraz — and each door delivers orders in a different shape. This scenario shows how such a retailer could pull all of them into one automated order hub built on n8n, without replacing the shop platforms it already uses.

Book a free consultation Interactive demonstration

Illustrative scenario (anonymised)

E-commerce

A Dhaka-based online retailer of fashion and home items selling through a WooCommerce website, a Facebook page with WhatsApp follow-up and a Daraz store, with orders copied into Excel and couriers booked by hand.

Three sales channels, one overworked Excel sheet

The retailer sells fashion and home items through a WooCommerce website, a busy Facebook page where customers order in the inbox and confirm on WhatsApp, and a Daraz store. A small team copies each order into a shared Excel sheet, checks stock in another sheet, books the courier on the courier's portal, and messages the customer a tracking number by hand. Cash-on-delivery amounts arrive from couriers days later in a statement that someone reconciles line by line.

As volume grows, orders are missed in the inbox, the same item is sold twice across channels, courier bookings carry typos in the address, and the COD statement never quite matches the sheet. Return handling is a chat thread. Nobody can say, without a weekend of work, which channel or product is really making money.

Interactive demonstration

Before

  • Orders from website, Facebook inbox and Daraz copied into one shared Excel sheet
  • Stock checked in a separate sheet; items sold twice across channels
  • Courier booked manually on the courier portal; tracking sent by hand
  • COD statements reconciled line by line, days later
  • Returns handled in chat threads with no link to the original order

After

  • Every order lands in one hub via webhook, API or a structured form
  • One stock position per SKU synced to website and marketplace
  • Courier booked by API; tracking sent automatically over WhatsApp/SMS
  • COD statements imported and matched; only exceptions need a person
  • Returns logged against the order; channel and product dashboard

Implementation process

  1. Audit

    Trace one order per channel

    We follow a website order, a Facebook order and a Daraz order from first message to settled cash and write down every copy-paste and portal login involved.

  2. Design

    Order model, states and exception rules

    One order structure with clear states — new, confirmed, booked, delivered, returned, settled — plus rules for what the automation may do alone and what needs a person.

  3. Build

    Intake first, then courier and stock, then reconciliation

    Order intake goes live first for all channels, courier booking and stock sync follow, and COD reconciliation and returns come last.

  4. Migrate & train

    Open orders, SKU list and team training

    Open orders and the SKU list are loaded from the sheets; the team is trained on the hub and the structured form in Bengali.

  5. Go-live & improve

    Parallel run, then switch, then monthly tuning

    The hub runs alongside the sheet for a short period, then replaces it; monthly reviews add channel reports and refine exception rules.

This is an illustrative, anonymised scenario composed from typical situations in this kind of business — not a published client result.

What AutoProbaho builds

  • Order intake hub on n8n

    Website orders arrive by webhook, Daraz orders through its seller API, and Facebook or WhatsApp orders are captured by a short structured form the team fills in — all landing as one normalised order in a central database.

  • Stock sync across channels

    One stock position per SKU; when an order is confirmed on any channel, availability is updated on the website and the marketplace so an item is not sold twice.

  • Courier booking and customer notification

    Confirmed orders are booked with the chosen courier partner through its API, the consignment number is stored on the order and sent to the customer over WhatsApp or SMS automatically, with delivery status updated as the courier reports it.

  • COD reconciliation and returns

    Courier statements are imported and matched to orders automatically; unmatched lines are flagged for a person, returns are logged against the original order, and a dashboard shows channel and product performance.

Expected business outcomes

  • No order lives only in an inbox

    Every order, whichever channel it came from, exists as one record with a status.

  • One stock truth across website and marketplace

    Availability updates from a confirmed order rather than from a weekly correction.

  • Courier bookings without re-typing

    Address, phone and COD amount go to the courier exactly as the customer gave them.

  • COD statements reconcile themselves, mostly

    People handle only the exceptions the automation could not match.

Frequently asked questions

No. In this scenario the shop platforms stay as they are; n8n connects to them through webhooks and APIs. The hub sits behind them and keeps orders, stock and delivery status in one place.

Related solutions

Related services

Related industries

Case Studies

Copying orders from an inbox into Excel?

Book a free consultation. We will trace one order from each of your channels to delivery and settlement and tell you honestly which step to automate first.

Book a free consultation Open the consultation calendar