Lazada and Shopee Seller Connector

The problem

Selling on Lazada and Shopee means living in two seller centres that know nothing about your accounting system. Orders arrive in a marketplace dashboard, stock moves in a marketplace warehouse view, and commissions, shipping fees and campaign charges are netted off inside a settlement statement that lands days or weeks after the sale. Zoho Inventory has no built-in Lazada or Shopee sales channel, so the usual answer is a person exporting CSVs each morning, re-keying orders into Zoho Books, and then trying to reconcile a lump-sum payout against dozens of individual invoices at month end.

The cost is not just the data entry. Stock in Zoho Inventory drifts away from what each seller centre advertises, so you oversell on one channel and hold dead inventory on another. Revenue in Zoho Books is recorded gross while the bank receives net, so the marketplace receivable never clears cleanly. Multi-country sellers running Malaysia, Singapore, Thailand and the Philippines from one group face the same problem several times over, each with its own currency and tax treatment.

What ECOSIRE builds

This is a build-to-order integration. Nothing here is a shrink-wrapped download — after a scoping call we build the connector against your Zoho org, your marketplace shops and your chart of accounts, then install it and support the go-live.

Order ingestion into Zoho Inventory

We build scheduled and event-driven pulls from the Lazada and Shopee seller APIs into Zoho Inventory Sales Orders. Each pull is implemented as a custom function in Deluge, invoked on a schedule and callable on demand, with cursor-based pagination and a stored watermark so a restart never re-imports the same order. Marketplace order identifiers are written to a dedicated custom field on the Sales Order so every record traces back to a seller-centre order, and a lookup on that field makes the import idempotent.

Buyer records are matched or created as Zoho Inventory Contacts using the marketplace buyer identifier, with masked-contact handling for the fields marketplaces redact. Shipping addresses, courier selection, tracking numbers and marketplace order status transitions map onto Packages and Shipments so your fulfilment team works inside Zoho rather than switching tabs.

Catalogue and stock mapping

We build a mapping layer between marketplace SKUs and Zoho Inventory Items, held in a Zoho Creator app so your team can maintain it without a developer. The mapping covers item variants, bundle or combo listings that decompose into component items, and per-shop overrides where the same product is listed differently by country.

Available stock is pushed back to both seller centres from the Zoho Inventory item stock endpoints, with a configurable buffer per warehouse and per channel so you do not publish your last unit to three places at once. Where you operate multiple warehouses, stock is calculated per selected location rather than as one global figure.

Zoho Books, settlements and tax

Invoices are created in Zoho Books against the correct Books organization for each country, using your existing item and account mappings. When a marketplace settlement lands, we import the statement lines and build the payout as a set of Zoho Books records: customer payments applied to the invoices in the batch, plus Expense or Bill records for commission, transaction fees, shipping subsidies and campaign charges, all posted to the accounts you nominate. The result is a marketplace clearing account that actually reconciles to the deposit on your bank feed.

Tax treatment is configured, not assumed. We set the tax rates, tax authorities and exemption handling in each Books organization to the treatment your accountant specifies for that market, including SST or VAT registration where applicable, and mark marketplace-collected tax separately where the marketplace acts as collector.

Returns, cancellations and adjustments

Cancellations and buyer returns pull through to Credit Notes in Zoho Books and stock adjustments in Zoho Inventory, so refunded units come back into available stock and the ledger reflects the reversal rather than leaving a stale open invoice.

Operations, alerts and visibility

Every sync run writes a log record. Failures raise notifications through Zoho Flow to email or a Cliq channel, and we build a Zoho Creator dashboard showing last successful run per shop, unmapped SKUs, orders held for review, and settlement batches not yet reconciled. Token refresh for the marketplace APIs is handled automatically with alerting before an authorisation expires.

Who this is for

Sellers running Lazada or Shopee shops in one or more Southeast Asian markets who already use Zoho Books or Zoho Inventory as their system of record. It suits businesses past the spreadsheet stage — several hundred orders a month or more, multiple SKUs with variants, and an accountant who needs marketplace payouts to reconcile without manual journals. It is equally relevant to a group running separate Books organizations per country that wants one operating model across all of them.

It is not the right fit if you sell a handful of orders a month, or if you have no Zoho tenancy yet — in that case the first engagement is a Zoho implementation, and the connector follows.

How delivery works

1. Scoping call. We walk through your shops, countries, Books organizations, warehouses, SKU structure, tax treatment and settlement cadence. We look at your existing item and account setup rather than assuming a greenfield org.

2. Fixed quote. You receive a written scope and a fixed price covering exactly the flows agreed, plus anything explicitly out of scope. No work starts until you approve it.

3. Build. We develop the connector — Deluge custom functions, Zoho Flow orchestration, the Creator mapping and dashboard app, custom fields and the API integrations — against a sandbox or a test Books organization, using your real catalogue structure and non-production marketplace credentials where available.

4. Install in test, then production. We deploy into your test environment first and run real orders through end to end with your team: an order lands, stock moves, an invoice posts, a settlement reconciles. Once you sign off, we install into production, migrate the mappings, and run the first live cycle alongside you.

5. Support. You get a support window after go-live for defects, marketplace API changes and configuration adjustments, along with the source and documentation so you are never locked out of your own integration.

Typical lead time from approved quote to production go-live is two to four weeks, driven mainly by how many shops and countries are in scope and how clean the existing SKU mapping is.