South Asia Marketplace Connector (Daraz)

The problem

A seller running at scale on a South Asian marketplace ends up with two systems of record and no reliable bridge between them. The marketplace seller centre knows the orders, the stock and the fees. NetSuite knows the general ledger, the purchase orders and the real cost of goods. Between them sits a person with a CSV export and a deadline.

The symptoms are consistent. Orders are keyed in a day late, so revenue reporting lags. Stock in the seller centre is updated from a stale report, so fast-moving lines oversell and get cancelled — which then costs you seller metrics as well as the sale. Marketplace commission, payment fees, shipping fees and promotional contributions are deducted before payout, so the amount in the bank never equals the value of orders shipped, and nobody can explain the difference without an afternoon of work.

Sellers operating across more than one South Asian market carry that entire problem several times over, in several currencies, often under different legal entities. Channel-level profitability stops being measurable, which is exactly when a business most needs to measure it.

What ECOSIRE builds

ECOSIRE builds a connector that runs inside your NetSuite account as an SDF project, delivered as an unmanaged bundle you own outright. It authenticates with your own marketplace seller credentials and moves data directly between your seller account and NetSuite.

Order import

A Scheduled Script polls the seller order endpoint per seller account and per market on an interval you set, handling paging, rate limits and backoff. Every order is written first to a staging custom record (customrecord_eco_dz_order_stage) with the raw payload, the marketplace order number, market, seller account and processing status. A Map/Reduce script then drains that queue into Sales Orders with governance-safe yielding, so a campaign-day spike does not exhaust script limits mid-batch.

The marketplace order number lives on a custom body field, and the order item identifiers live on the lines. Both are checked with a saved search before creation, so repeated polling and replayed events cannot create duplicate transactions or double-fulfil a line.

Market and entity structure

A configuration custom record maps each seller account to a subsidiary, currency, location, department, class and customer form. In OneWorld accounts, orders from each market post into the correct legal entity with the correct currency, rather than being consolidated and unpicked later. A custom segment tagging marketplace and market is applied at line level so channel and market reporting comes from standard saved searches and the standard income statement, not from a separate spreadsheet.

Order status and fulfilment

Marketplace orders move through pending, ready to ship, shipped, delivered, cancelled, returned and failed-delivery states, and each has a different accounting consequence. A Scheduled Script pulls status changes and applies them: creating Item Fulfilments with the marketplace-issued tracking number and carrier, closing cancelled lines, raising Return Authorisations and, on receipt, Item Receipts and Credit Memos. Failed deliveries and returned-to-seller items are handled explicitly, because in this market they are a meaningful share of volume and quietly ignoring them corrupts both stock and revenue.

Where a shipping label or tracking number is issued by the marketplace, it is written back to the Item Fulfilment so warehouse staff work from NetSuite rather than the seller portal.

Stock and price push

A Scheduled Script pushes sellable quantity per market from an Inventory Item saved search, netting out committed quantity and excluding the locations you nominate. Sellers sharing one warehouse across several markets can set a reserve or a percentage allocation per market instead of publishing the same pool everywhere. Prices are pushed from a nominated price level, with currency-specific price levels per market and optional guard rails so a mis-keyed price cannot be published.

Fees, promotions and settlement

Commission, payment fees, shipping fees and seller-funded promotional contributions are imported against the orders they relate to and posted to expense accounts you nominate. The Sales Order therefore carries gross revenue and the deductions appear as costs — which is what makes marketplace gross margin computable at all. Payout and settlement statements are imported into a custom record and matched against the underlying orders and fee lines, producing a saved search that shows which transactions constitute each bank deposit. Anything unmatched is flagged for review rather than plugged.

Errors and monitoring

Every API call and every order attempt is logged to a custom record with the payload, outcome and resulting internal ID. Failures — unmapped SKUs, missing tax codes, expired tokens, rate-limit exhaustion — appear in a single saved search and dashboard portlet, and a SuiteFlow workflow escalates by email when an order or a token problem sits unresolved past your threshold.

Who this is for

Established sellers, brand owners and distributors operating across Pakistan, Bangladesh or Sri Lanka who already run NetSuite and have material marketplace volume. It suits businesses that need channel-level margin, clean payout reconciliation and stock accuracy across markets, and that prefer to own the integration code rather than depend on an external service.

How delivery works

Scoping call. We review your seller accounts and markets, your API access and entitlements, your fulfilment arrangements, your NetSuite subsidiary and currency setup, and exactly how you want fees, promotions and settlements to post.

Fixed quote. You receive a written scope covering mappings, scripts, markets and acceptance tests, at a fixed price. Additions after that are quoted separately.

Build. ECOSIRE develops the connector as an SDF project under version control. Typical lead time is two to four weeks from a signed scope, extending where several markets, entities or fulfilment models are involved.

Install in sandbox. We deploy to your sandbox first, run your real historical orders and a real payout statement through it, and review the results with your finance and operations teams before anything reaches production.

Install in production. After sign-off the same bundle goes to production, configuration is completed, deployments and schedules are enabled, and we watch the first live polling cycles with you.

Support. A defect-fix support window runs from go-live against the agreed scope, with extended support and enhancements quoted separately.

What you should know before you buy

This is a build-to-order engagement. Nothing is pre-built, there is no instant download and there is no trial version, because the software does not exist until it is built for your account. The integration also operates strictly within your own marketplace seller API entitlements — the endpoints, fields and rate limits available to your account define what can be automated. We confirm those during scoping and design to them, instead of quoting for behaviour the marketplace does not expose.