Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
E-commerce & Commerce 6 min read

Omnichannel retail operations: a step-by-step guide

One stock pool, one order record and one returns policy across shop, website, marketplace and social channels. A practical sequence for getting there.

E
EncryptTechBD · 0 comments
Woman looking into a shop window on a city street
Photo: Daria Nepriakhina / StockSnap

Omnichannel is not five channels running in parallel. It is one promise kept in five places: the same stock, the same price logic, the same order record and the same returns policy, whether the customer walks in, orders from the website, buys through a marketplace or sends a message on Facebook.

Most retailers start with the channels and then try to reconcile them. The sequence below starts with the data and the operating rules, which is the order that survives growth. It is written for a retail business in Bangladesh with a shop or two, a website, and social or marketplace orders.

Prerequisites

  • A named owner for the channel mix, usually the operations or commercial lead.
  • A product master with a unique SKU for every sellable variant.
  • An honest view of current stock accuracy, including the shop floor.
  • Access to the POS, e-commerce, marketplace and accounting systems, or the people who administer them.
  • A budget for integration, training and at least one full stock count.

Step 1: Define the channel promise

Decide what each channel is for. A shop may be a showroom, a pickup point and a returns desk. The website may carry the full catalogue while the shop carries a curated range. A marketplace may be a clearance channel. Write the promise for each: which products, which prices, which delivery options and which returns route. If the promises conflict, the integration will encode the conflict.

Step 2: Clean the product master

Every sellable item needs one SKU, a variant structure for size or colour, a barcode where available, dimensions, weight and a tax category. Images and descriptions should be shared, not maintained separately per channel. Duplicate SKUs are the most common reason stock counts disagree after an integration. Merge them before you connect anything.

Step 3: Choose the inventory model

  • Pooled inventory. All channels see one stock figure. It maximises availability but risks overselling if counts are wrong.
  • Allocated inventory. Each channel gets a reserved quantity. It protects key accounts but can leave stock stranded.
  • Hybrid. Pool most stock, reserve a buffer for the shop or a key marketplace, and set safety stock by velocity.

Pick the model explicitly and write the safety-stock rule. "The system will handle it" is not a rule.

Step 4: Write the order routing rules

When an order arrives, where does it ship from? Common rules include nearest stock, a dedicated online warehouse, the shop with the highest availability, or a split shipment when no single location can fulfil the order. Decide what happens when stock is wrong, when a location is closed, and when the customer chooses pickup. Test each rule with a real order before launch.

Step 5: Connect the systems

Integrate the POS, e-commerce platform, marketplace connectors and accounting ledger. Use an order service that holds the canonical order and publishes status changes to every channel. Keep the integration idempotent: a repeated webhook must not create a second order or a second stock deduction. Log every sync with a transaction ID so support can trace a failure.

Step 6: Standardise statuses and exceptions

Define a small set of statuses that every channel maps to: received, confirmed, picking, packed, shipped, delivered, cancelled, returned and refunded. Then define the exception states: payment pending, stock short, address unclear, delivery failed and customer unreachable. Each exception needs an owner and a maximum age. Without this, the team spends its day translating between systems.

Step 7: Fix payments and reconciliation

Accept the payment methods your customers actually use, including cash on delivery, cards and mobile financial services. Store the provider reference on the order, reconcile settlements daily, and keep refunds linked to the original payment. A channel that cannot refund cleanly will create a support queue that outlasts the campaign that produced it.

Step 8: Make returns work across channels

Decide whether a customer can return an online order in a shop, and whether a shop purchase can be returned by courier. Define the inspection step, the restocking rule and the refund timing. Returned stock should go to a quarantine or inspection location before it re-enters available inventory. Publish the policy in the same language on every channel.

Step 9: Set fulfilment SLAs and train staff

Agree cut-off times, packing standards and delivery promises by location. Train shop staff on picking online orders, scanning and handing over to the courier. Give them a way to report a stock discrepancy without editing the count silently. If staff are measured only on shop sales, online orders will always lose.

Step 10: Measure and iterate

Review the same scorecard every week: stock accuracy, order accuracy, cancellation rate, delivery time, return rate and settlement differences. Fix the worst-performing location or channel first. Expand the catalogue or the channel mix only after the basics are stable.

Evidence to keep

  • Product master export with one row per sellable SKU.
  • Inventory model and safety-stock rule, signed by the business owner.
  • Order routing matrix by channel and location.
  • Status map and exception owners.
  • Daily reconciliation and weekly stock-count record.

Common mistakes

  • Connecting channels before deduplicating the product master.
  • Showing shop stock online without a safety buffer.
  • Letting each channel keep its own order status vocabulary.
  • Treating returns as a customer-service issue rather than an inventory process.
  • Measuring the online team and the shop team on conflicting targets.
  • Launching all channels on the same day.

Metrics

  • Stock accuracy by location.
  • Order accuracy and cancellation rate.
  • Time from order to handover.
  • Return rate and refund cycle time.
  • Unreconciled payments by channel.

Where this fits in our work

Omnichannel operations depend on an order and inventory layer that sits above the individual channels. Our Commerce Systems division builds that layer and connects the till, website and marketplace; the pricing page explains how the work is phased. For the year-by-year view, read omnichannel retail operations, year by year.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes