Shopee and Lazada Marketplace Connector

The problem this solves

Running both Shopee and Lazada alongside SAP Business One usually means one person exporting seller-centre spreadsheets every morning and typing them back into the ERP. Each marketplace has its own order model, its own escrow and settlement timing, and its own fee structure — commission, service fee, transaction fee, free-shipping subsidy, voucher share, seller-borne discount. By the time those lines reach an A/R Invoice in SAP Business One, they have usually been flattened into a single "marketplace sale" figure that nobody can reconcile back to the payout that actually landed in the bank.

Stock is the second failure. A SKU sells on Shopee at 09:14 and on Lazada at 09:15. If the ERP is the source of truth but the channels only learn about it at midnight, you oversell — and oversell penalties on both platforms are a direct hit to seller rating. If the channels are the source of truth, your SAP Business One warehouse quantities drift and your costing and reorder logic drift with them.

The third is volume. A few hundred orders a day is not a data-entry job. It is an integration job.

What ECOSIRE builds

ECOSIRE builds a per-tenant SAP Business One add-on and integration service, written against your marketplace seller accounts and your company database. It is not a shrink-wrapped product you download — it is scoped to your channels, your item master, your warehouse layout and your finance treatment, then built and installed for you.

Order ingestion into real SAP B1 documents

Marketplace orders are pulled on a schedule and posted through the Service Layer (or DI API where a specific document behaviour requires it) as genuine SAP Business One documents. A marketplace order becomes a Sales Order against a dedicated Business Partner per channel — or per buyer, if you want customer-level history — with the marketplace order number, channel, shop ID, buyer nickname and payment method stored in UDFs on the document header. Order lines map to your Item Master through a channel-SKU mapping table held in a UDT, so a seller-centre SKU that differs from your ItemCode still lands on the right item.

Status transitions follow the marketplace lifecycle: ready-to-ship, shipped, delivered, cancelled, returned. Shipment triggers a Delivery document; completion or settlement triggers the A/R Invoice, depending on the revenue-recognition point you choose during scoping.

Fee, escrow and settlement handling

This is where most integrations stop and yours cannot. Each channel's fee breakdown is captured line by line and posted as separate charge lines or a Journal Entry against the G/L accounts your accountant nominates — commission, transaction fee, service fee, shipping subsidy, voucher and campaign share, seller-borne discount, and any adjustment or compensation entry. Escrow amounts are held against a clearing account and cleared when the payout arrives, so the settlement report from the marketplace can be matched against the ERP rather than trusted blindly.

A reconciliation view shows, per payout batch: gross order value, itemised deductions, expected net, and the amount actually received. Variances are listed, not hidden.

Inventory synchronisation

Available quantity is calculated from your chosen warehouses in SAP Business One — including or excluding committed stock, per your rules — and pushed to both channels on an interval you set. You can allocate a fixed pool per channel, share one pool with a safety buffer, or drive a per-SKU rule stored in a UDT. Price pushes are optional and follow a nominated Price List, with a floor guard so a bad price list edit cannot publish a loss-making price.

Returns, cancellations and credit notes

A cancelled order that has not shipped closes the Sales Order. A return after shipment creates a Return document and an A/R Credit Memo, with the marketplace return reason and case ID stored in UDFs so finance can see why the money went back.

Control, visibility and errors

A UDO-based control screen inside the SAP Business One client shows every synchronised order, its channel, its current state and its last sync attempt. Failed syncs are visible with the actual API error, retryable from the same screen. Nothing fails silently into a log file nobody reads. Approval procedures can be attached to the documents the connector creates if your finance team wants a human gate on anything above a threshold.

Crystal Reports layouts can be provided for channel-level sales, fee analysis and settlement reconciliation if reporting is in scope.

Who this is for

Southeast Asian sellers — Malaysia, Singapore, Indonesia, Thailand, the Philippines, Vietnam — running SAP Business One as the back office with meaningful volume on both Shopee and Lazada. It fits multi-shop operators (several storefronts across countries), brands running their own official stores, and distributors whose marketplace channel now rivals their traditional trade.

It is not for a seller doing five orders a week. At that volume, manual entry is cheaper than an integration.

How delivery works

1. Scoping call. We go through your channels and shop IDs, order volume, item and SKU mapping, warehouse setup, the exact fee lines you need broken out, your revenue-recognition point, and your G/L account structure. We also confirm your SAP Business One version, database platform and whether you are on-premise or hosted.

2. Fixed quote. You receive a written scope and a fixed price before any code is written. If your requirements extend beyond the base build — extra channels, custom document flows, additional reports — those are quoted as named line items, not discovered mid-project.

3. Build. ECOSIRE develops the add-on and integration service against the marketplace open-platform APIs and the SAP Business One Service Layer, with UDFs, UDTs and UDOs created by an install routine rather than by hand.

4. Install into test, then production. We install into your test company database first and run your real order data through it. You sign off on document creation, fee posting and stock behaviour there. Only then does it go into the production company database, with a scheduled cutover.

5. Support. A support window is included after go-live for defect fixes and marketplace API changes. Ongoing support beyond that window is available as a separate agreement.

Typical lead time from signed quote to production install is one working week, driven mostly by how many fee lines and document variations your finance team needs and how quickly seller-account API credentials are issued.