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

Courier integration cost for online stores in Bangladesh

What drives the cost of connecting an online store to Bangladeshi couriers, a scope-based calculator and the vendor questions that prevent surprises.

E
EncryptTechBD · 0 comments
Clothing on hangers in a retail store
Photo: Artificial Photography / StockSnap

Connecting an online store to a courier looks like a small development task: send an order, receive a tracking number. In practice it is three jobs joined together. The store must create a parcel the courier accepts, keep the delivery status in sync, and reconcile the cash the courier collected against the orders it delivered.

That is why quotes for the same store can differ widely. One supplier prices a one-way push to a single courier. Another prices a multi-courier workflow with cash-on-delivery reconciliation and an exception queue. This guide explains the cost drivers, gives you a calculator that uses your own numbers, and lists the questions that expose an incomplete proposal.

What a courier integration actually covers

  • Serviceability and rate check: whether the destination is covered and what the delivery will cost.
  • Parcel creation: recipient, address, item description, weight, declared value and cash-on-delivery amount.
  • Label and pickup: a printable label, a pickup request and a handover record.
  • Status synchronisation: pickup, in transit, delivered, returned and cancelled states mapped to your order.
  • Exceptions: failed pickup, wrong address, refused parcel, lost parcel and return to origin.
  • Money: cash collected, courier fees, adjustments and remittance to your bank or wallet.

What drives the cost

The number of couriers is the first driver, but it is not the only one. Each additional courier adds authentication, address formats, status names, label layouts and settlement rules. A courier with a documented API is a different job from one that only offers a merchant panel.

  • API maturity: official API, sandbox, webhooks and stable identifiers, or manual exports and screen automation.
  • Order volume: batch creation, rate limits and peak handling become design constraints at higher volume.
  • Sales channels: website, marketplace and social orders may need different mapping and duplicate controls.
  • Cash on delivery: expected collection, rider handover and remittance need a reconciliation layer.
  • Returns: reverse pickup, inspection and restocking add states and exceptions.
  • Address quality: free-text addresses create failed deliveries and manual correction work.
  • Multi-warehouse: pickup location, stock allocation and cut-off times multiply per site.
  • Support: someone must own the error queue after launch.

A scope-based cost model

Ask every vendor to price the same lines. This makes proposals comparable and shows what they have omitted.

  1. Discovery: map the order flow, courier accounts, statuses, settlement files and exception owners.
  2. Courier connector: one unit per courier, including authentication, rate check, parcel creation, label and cancellation.
  3. Orchestration layer: routing rules, retries, duplicate protection and a single internal status model.
  4. Store integration: order events, stock, customer data and admin controls.
  5. Tracking: webhook receiver, signature check, status mapping and customer notifications.
  6. COD reconciliation: expected versus collected, fees, remittance and an exception queue.
  7. Testing: sandbox cases, failure injection, peak-volume test and a real pilot.
  8. Monitoring and support: alerts, logs, a runbook and a monthly support allowance.
  9. Contingency: an agreed amount for API differences found during build.

Price each line as a range or as person-days multiplied by a blended rate. A single total hides whether the vendor has included reconciliation, which is usually the most valuable part.

A calculator for your own numbers

You do not need a proprietary tool. Start with the manual work the integration would remove.

monthly manual hours = orders per day x working days x minutes per order / 60

monthly manual cost = monthly manual hours x loaded hourly cost

Use the loaded cost, including salary, benefits and supervision, not the basic wage. Add the cost of corrections: duplicate parcels, wrong addresses, failed deliveries and support calls. Then compare the annual saving with the one-off implementation cost and the monthly run cost.

payback months = one-off cost / (monthly saving - monthly run cost)

cost per order = (one-off cost + 12 x monthly run cost) / annual orders

If the payback depends on removing every manual minute, it is optimistic. Assume adoption below one hundred percent and keep an exception queue in the model.

Why the cheapest connector often costs more

A one-way push that creates a parcel but never reads the status is not an integration. Staff still open the courier panel to check delivery, copy tracking numbers and chase cash. A connector without duplicate protection creates two parcels when the store retries. A connector without a settlement feed turns reconciliation into a monthly argument.

The expensive failures are usually quiet: a status that never maps, a webhook that silently stops, or a COD total that includes cancelled orders. Price the monitoring and the exception handling, because that is where the operational cost lives.

Questions to ask a vendor

  • Does the courier provide an official API, a sandbox and written status definitions?
  • How do you prevent duplicate parcels when a request times out and is retried?
  • Are webhooks signed, and what happens when one is missed or replayed?
  • How are courier statuses mapped to our order states, and who approves the mapping?
  • What format does the COD settlement file use, and how are fees and adjustments handled?
  • Can the design add a second courier without rebuilding the first?
  • Where do failed requests go, who sees them, and how quickly?
  • What is the monthly support scope, and what counts as a change request?
  • Who owns the code, credentials and mapping documentation?

A 90-day rollout

Weeks one and two: map the flow and collect courier documentation. Weeks three and four: build one courier connector and the internal status model. Weeks five and six: test in sandbox and with a small batch of real orders. Weeks seven and eight: pilot one channel with a daily reconciliation check. Weeks nine and ten: add the second courier and the return flow. Weeks eleven and twelve: review exceptions, tune alerts and hand over the runbook.

Going live with one courier first is not a delay. It is how you discover the address and status problems before they are multiplied.

Metrics that show whether it worked

  • Integration success rate and the number of duplicate parcels.
  • Time between a courier event and the order status changing.
  • COD variance and the age of unresolved settlement items.
  • Manual touches per order and exception queue age.
  • Cost per order after run costs are included.

Where this fits in our work

If you need a courier workflow that covers creation, tracking and cash reconciliation, start with Commerce Systems. The pricing page explains how scope is priced. For the wider order process, read ecommerce order management costs.

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