Why Bangladesh Businesses Need ERP-eCommerce Integration
The typical Bangladesh online seller manages their business across four or five disconnected systems. Daraz Seller Center shows orders. A WooCommerce dashboard shows website orders. WhatsApp shows inquiries that become informal sales. A spreadsheet tracks dispatch. Tally or separate accounting software handles invoices. Odoo handles (theoretically) inventory.
The result is predictable: inventory overselling, delayed order confirmation, wrong stock counts, missed VAT on digital channels, and customer support chaos when orders placed on one channel cannot be tracked in another. I have seen this pattern in Dhaka electronics retailers, Chittagong export traders, and Dhaka fashion brands simultaneously.
Integration solves this by making Odoo the single source of truth for products, pricing, stock, and orders — with each sales channel as a synchronized outpost that pushes and pulls from that central system.
The goal of eCommerce integration is not to have a fancy tech stack. It is to sell from one inventory, fulfill from one queue, and report from one place.
Option 1: Odoo's Native eCommerce Module
Odoo eCommerce — Built on Top of Odoo Website
Odoo's eCommerce module is a full online store built directly into your Odoo instance. Products, prices, stock levels, and orders live natively in Odoo — there is no "sync" because the website and the ERP are the same database. This eliminates the integration problem entirely for the website channel.
What it includes:
- Product pages with variants (color, size, etc.) pulled from Odoo product catalog
- Real-time stock display (shows "Only 3 left" based on actual Odoo inventory)
- Cart, checkout, payment, and order confirmation — all native
- Automatic sale order creation in Odoo on each purchase
- Shipping calculation using Odoo's delivery methods
- Customer portal for order tracking
- Multi-currency support for international buyers
Bangladesh-specific consideration: Odoo Website/eCommerce gives you a new domain-hosted website on your Odoo server. If you already have an established WooCommerce site with SEO history, customer accounts, and customized design, switching to Odoo native eCommerce means rebuilding all of that. For a new online store starting fresh, Odoo native eCommerce is the simplest path. For an existing store with SEO equity, WooCommerce integration is better than migration.
Payment in Bangladesh: Install the SSLCommerz payment provider module from the Odoo App Store to accept bKash, Nagad, Rocket, and card payments through SSLCommerz's aggregator. This is the standard path for Bangladesh-facing Odoo eCommerce stores.
Option 2: WooCommerce + Odoo Integration
WooCommerce Connector for Odoo
If your Bangladesh business already has a WooCommerce website with SEO rankings, customer base, and customized theme, migrating to Odoo native eCommerce may cost more than the integration it avoids. The better path is a WooCommerce-Odoo connector that syncs both systems bidirectionally.
How the sync works:
- Products: Products created in Odoo (with variants, pricing, and images) are exported to WooCommerce. Changes in Odoo (price update, new variant) sync to WooCommerce automatically.
- Inventory: When stock moves in Odoo (sale confirmed, purchase received), WooCommerce stock quantities are updated. This prevents overselling — a critical issue for Bangladesh sellers on multiple channels.
- Orders: When a WooCommerce order is placed, a sale order is created in Odoo automatically. The connector maps WooCommerce customer data to Odoo customer records (creating new records or matching existing ones by email).
- Order status: When the Odoo sale order is confirmed and delivery is validated (shipped), the WooCommerce order status updates to "Processing" or "Completed."
Connector options for Bangladesh: Several connector modules are available on the Odoo App Store. OdooTec's WooCommerce connector and Cybrosys's integration are widely used. Pricing: one-time $200–400 or annual subscription. Installation requires: WooCommerce REST API credentials (Consumer Key and Secret from WooCommerce → Settings → Advanced → REST API) and Odoo admin access.
Do not manage products or pricing directly in WooCommerce once you enable the connector. All product data should flow from Odoo → WooCommerce. If you update prices in both systems independently, the sync will overwrite one with the other, causing pricing inconsistencies. Establish Odoo as the single master for product data from day one of the integration.
Option 3: Shopify + Odoo for Bangladesh Export Sellers
Shopify-Odoo Connector — International Buyer Channel
Many Bangladesh exporters — particularly in RMG samples, handicrafts, and cycle accessories — use Shopify because of its international reach, Shopify Payments' global payment acceptance, and its export-friendly features. Shopify is not available as a payment processor in Bangladesh (you cannot receive Shopify Payments to a Bangladesh bank account), but you can use Stripe, PayPal, or 2Checkout to accept international payments through Shopify.
The integration use case: A Bangladesh RMG exporter takes sample orders from international buyers on a Shopify store. These orders need to flow into Odoo manufacturing as production orders (or sale orders linked to available stock), generate export documentation (commercial invoice, packing list), and update Odoo's export accounts receivable in USD or EUR.
Connector setup: Shopify connectors for Odoo are available from OdooTec, Syncoria, and several other vendors on apps.odoo.com. The integration uses Shopify's Admin API (REST). Key configuration: (1) map Shopify product SKUs to Odoo internal references; (2) set the receiving warehouse for Shopify orders; (3) configure currency handling (Shopify multi-currency vs. Odoo pricelist).
What to sync: Orders (Shopify → Odoo) and inventory availability (Odoo → Shopify). Do not sync customers back to Shopify from Odoo — let Shopify maintain its own customer records and pull customer data into Odoo on order creation.
Option 4: Daraz Marketplace Integration
Daraz Open Platform + Odoo API
Daraz is the dominant eCommerce marketplace in Bangladesh, Pakistan, and Sri Lanka. For Bangladesh businesses selling on Daraz, order volumes can be significant — 50–500+ orders per day for established sellers. Managing these manually alongside Odoo is unsustainable at any meaningful scale.
Integration options in order of reliability:
- Custom Odoo module using Daraz Open Platform API: Daraz provides a Seller API (Open Platform) that allows registered sellers to retrieve orders, update stock quantities, and confirm shipments programmatically. A Bangladesh Odoo developer can build a custom connector module that calls this API on a schedule (every 5–15 minutes). One-time development cost: BDT 80,000–150,000 depending on complexity. This is the most reliable and maintainable long-term solution.
- Third-party Odoo-Daraz connector on apps.odoo.com: Search for "Daraz" on apps.odoo.com — available options vary. Verify the module was updated for your Odoo version and check reviews before purchasing.
- Middleware (Make / Zapier): If Daraz and Odoo both have supported connectors in Make or Zapier, you can build an order sync workflow without coding. Reliability is lower for high-volume sellers; Make handles up to 10,000 operations/month on mid-tier plans.
What must sync from Daraz to Odoo: Order details (product, quantity, buyer, delivery address), payment status (prepaid vs. COD), and tracking number once shipped. The inventory sync (Odoo stock → Daraz available quantity) is equally important — without it, you will oversell on Daraz when stock is depleted by other channels.
The Unified Order Flow
The key design principle: every order from every channel creates a sale order in Odoo. Inventory deduction, delivery, invoicing, and accounting all happen in Odoo regardless of order source. Channel-specific systems (Daraz Seller Center, WooCommerce admin, Shopify admin) become order intake points only — not systems of record.
Inventory Sync & Overselling Prevention
Overselling — accepting an order for a product you do not have in stock — is the most damaging consequence of disconnected sales channels. In Bangladesh, where customer trust is harder to build and easier to lose (Daraz ratings, Facebook reviews), an overselling incident with a 7-day "sorry we're out" delay damages your seller score significantly.
The correct architecture:
- One inventory location in Odoo — do not create separate virtual locations for "Daraz stock" and "website stock" unless you physically separate the goods. One location, one truth.
- Odoo pushes stock updates to all channels — every time stock moves in Odoo (any reason), all connected channels receive an updated quantity within the sync interval.
- Safety stock buffer — configure a virtual safety quantity buffer in your connector. If Odoo shows 10 units, push 8 to Daraz. This absorbs the sync delay between channels (orders placed in the 5-minute window between syncs).
- Reserve stock for priority channels — if your direct website is higher-margin than Daraz, set Daraz available quantity to Odoo quantity minus a reserved buffer for direct orders.
Bangladesh Payment Gateways in the Integration Context
| Gateway | Odoo Integration Method | Accepted Methods | Transaction Fee |
|---|---|---|---|
| SSLCommerz | Odoo App Store module (SSLCommerz Payment Provider) | bKash, Nagad, Rocket, Visa, Mastercard, DBBL Nexus | 1.5–2.5% depending on method |
| bKash Direct | Custom Odoo payment provider module (developer required) | bKash wallet only | 1.5–1.85% + BDT 2 per transaction |
| Nagad Direct | Custom Odoo payment provider module (developer required) | Nagad wallet only | 1% (promotional), typically 1.5–2% |
| SSLC / WooCommerce | WooCommerce SSLCommerz plugin; orders flow to Odoo via connector | All SSLCommerz methods above | Same as SSLCommerz above |
| Stripe (Shopify) | Shopify-side; Odoo receives confirmed sale order | Visa, Mastercard, international cards | 1.5% + $0.30 international |
Under Bangladesh VAT law, sales made through your own website or Odoo eCommerce are subject to standard VAT (15% for taxable goods). Odoo's tax framework handles this automatically if your tax configuration is correct (see the NBR VAT compliance setup). Daraz and Shopify do not auto-generate NBR-compliant VAT invoices — you must generate these from Odoo using the sale order created by the connector. Do not treat marketplace orders as "off the books" — NBR is actively monitoring large sellers on Daraz.
Shipping API Integration
Bangladesh's courier ecosystem has matured significantly. Pathao Courier, Steadfast Courier, Redx, and Paperfly all offer REST APIs for parcel booking, tracking, and status updates. Connecting these to Odoo enables automatic shipment booking when a delivery order is validated.
How it works: When you validate a delivery order in Odoo (pick, pack, ship confirmed), the shipping API integration sends the parcel booking request to your courier API (parcel weight, delivery address, COD amount if applicable). The courier returns a tracking number, which is saved on the Odoo delivery order. This tracking number is then synced back to the sales channel (WooCommerce order status updated, Daraz tracking number submitted).
Available integrations: Check apps.odoo.com for "Pathao", "Steadfast", or "Redx" — community developers have built connectors for each. Alternatively, for the API integration guide covering Odoo's connection to Bangladesh's broader ecosystem, the Odoo API Integration guide for Bangladesh covers the technical setup in detail.
Common Integration Pitfalls (Bangladesh-Specific)
1. SKU mismatch between systems. The most common cause of failed product sync is inconsistent internal references. Odoo uses "Internal Reference" as the product identifier. WooCommerce uses SKU. Shopify uses SKU. Daraz uses Seller SKU. These must all match exactly for the connector to map products correctly. Audit and standardize your SKU system before enabling any integration.
2. Currency confusion for export channels. If you sell in USD on Shopify and BDT domestically, configure Odoo's multi-currency and pricelist correctly before enabling the Shopify connector. Orders imported in USD must use the correct pricelist — otherwise Odoo will apply the BDT price to a USD order and create a financial reporting error.
3. Duplicate customer records. If the same customer places an order on your WooCommerce site and later on Daraz, the connectors will create two separate Odoo customer records (different contact details, no email to match on). After 12 months, many Bangladesh businesses have hundreds of duplicate customer records that inflate customer counts and distort CRM reporting. Build a deduplication step into your integration from the start — use email as the matching key and merge duplicates quarterly.
4. Tax mapping for marketplace orders. Daraz collects payment on behalf of sellers and remits it. The tax treatment of marketplace commissions versus sale revenue is a specific Bangladesh accounting consideration. Your Odoo chart of accounts and journal configuration must handle: (a) sale revenue recorded at full order value; (b) Daraz commission recorded as a sales expense; (c) net remittance from Daraz recorded as payment. This requires careful Odoo accounting configuration, not just a connector.
For the CRM and sales pipeline foundation that supports eCommerce order tracking, the Odoo Sales & CRM for Bangladesh Exporters guide covers the upstream configuration.
If you are a Bangladesh business considering multi-channel eCommerce integration with Odoo, I can help scope the connector requirements, identify the right modules, and plan the implementation in a way that avoids the pitfalls above. Contact me for a scoping call →
Frequently asked questions
Can Odoo integrate with Daraz (Bangladesh marketplace)?
Yes, but not natively. Integration requires either a third-party connector from the Odoo App Store, a custom module built using Daraz's Open Platform Seller API, or a middleware tool like Make. For sellers with 50+ daily orders, a custom connector built by a Bangladesh developer (BDT 80,000–150,000) delivers better reliability than third-party options. Daraz's API supports order retrieval, stock updates, and shipment tracking confirmation.
How does Odoo sync inventory with WooCommerce?
Using a WooCommerce connector module, Odoo pushes stock updates to WooCommerce via the WooCommerce REST API whenever inventory changes in Odoo. WooCommerce orders are pulled into Odoo as sale orders. Sync frequency is typically 5–30 minutes. All product management should be done in Odoo and pushed to WooCommerce — not managed directly in WooCommerce once the connector is active.
What payment gateways work with Odoo eCommerce in Bangladesh?
For Odoo native eCommerce: install the SSLCommerz payment provider module from the Odoo App Store — this enables bKash, Nagad, Rocket, and card payments through SSLCommerz's aggregator. For WooCommerce integrated with Odoo: set up payment plugins on the WooCommerce side (SSLCommerz, bKash, Nagad) — payment confirmation flows into Odoo through the connector. For international Shopify sales: Stripe and PayPal are the most reliable options for Bangladesh-based exporters receiving USD payments.
Do I need a developer to integrate Odoo with Shopify?
Not for a standard integration. A pre-built Shopify connector from the Odoo App Store (OdooTec, Cybrosys, Syncoria — $200–500) can be configured by a knowledgeable Odoo user using Shopify Admin API credentials. A developer is needed for complex product variant mapping, custom fulfillment logic, or syncing non-standard data between systems. Start with the connector module and only commission custom development for specific gaps the module cannot handle.