Noon Marketplace Seller Connector

The pain

Selling on Noon across the UAE and Saudi Arabia means running two tax regimes, at least two fulfilment models, and a settlement cycle that arrives as a net figure with commission, fulfilment fees and returns already netted out. Sellers who keep their books in Zoho Books usually bridge the gap by hand: export orders, re-key or bulk-import invoices, guess at the VAT treatment on cross-border lines, and then spend the end of every settlement cycle trying to explain why the bank credit does not equal the sales they recorded.

The fulfilment split makes it worse. Stock held in Noon's fulfilment centres is invisible to Zoho Inventory unless something reconciles it, so available-to-promise numbers are wrong for every other channel you sell on. Seller-fulfilled orders need pick, pack and AWB handling that the seller panel and Zoho do not share. Returns land back in a fulfilment centre with no corresponding movement in your own stock ledger.

And VAT is not optional detail. UAE and KSA each have their own registration, rate treatment and reporting requirements, and marketplace commission invoices from a regional entity need the correct input treatment. Getting this wrong is a filing problem, not a bookkeeping preference.

What ECOSIRE builds

ECOSIRE builds a connector that runs inside your own Zoho organisation — Deluge custom functions, scheduled jobs, Zoho REST API calls and, where the flow calls for it, Zoho Flow orchestration and a Zoho Creator control app. Nothing is hosted by us and nothing charges per order.

Order ingestion into Zoho Inventory

Scheduled functions pull Noon orders and create Sales Orders in Zoho Inventory. Every order stores the Noon order number, item-level reference, fulfilment type, ship-from country and current marketplace status in custom fields, so downstream logic never has to parse a text reference. Ingestion is idempotent on the item-level identifier, so a re-run or an overlapping polling window cannot duplicate an order.

Two fulfilment models, handled separately

Fulfilled-by-Noon and seller-fulfilled orders are not the same accounting or inventory event, and the connector treats them differently. For fulfilment-centre stock we maintain a dedicated Zoho Inventory warehouse representing inventory held at Noon, reconcile it against the marketplace's inventory position on a schedule, and raise a discrepancy record when the two disagree. For seller-fulfilled orders we generate Packages and Shipments in Zoho Inventory, write the AWB back, and drive the dispatch-by deadline into your picking workflow.

Multi-entity and multi-currency structure

Where you sell into both the UAE and Saudi Arabia, we configure the posting structure your accountant requires — separate Zoho Books organisations per entity, or a single organisation with branch and tax-treatment segregation. Base currency, AED and SAR handling, and exchange differences on settlement are configured explicitly rather than left to defaults.

VAT configuration

We configure tax rates, place of supply logic driven by the ship-to country, zero-rated and out-of-scope treatments where they apply, and the input VAT treatment on marketplace commission and fulfilment invoices. The output is a Zoho Books VAT return report that reflects marketplace activity correctly, rather than a set of summary journals your accountant has to unpick.

Returns and cancellations

Cancellations before dispatch release the stock reservation. Customer returns create Credit Notes in Zoho Books linked to the original Sales Order and post the physical movement to the correct warehouse — a returns bin for seller-fulfilled goods, or the fulfilment-centre warehouse for stock that stays with Noon. Where a return is written off rather than restocked, the write-off posts to the account you nominate.

Settlement reconciliation in Zoho Books

Settlement statements are parsed at line level. Each payout produces the customer receipt plus separate Bills or Expense entries for commission, fulfilment and storage fees, shipping charges, promotional or marketing deductions and penalties, each mapped to an account you choose. The payout is then matched to the bank transaction in Zoho Books, and the marketplace clearing account is expected to reconcile to zero. Anything that does not match appears as an open item rather than being force-balanced.

Exception handling

Unmapped SKUs, API errors, settlement lines with no matching order, quantity mismatches and inventory discrepancies all raise records in an exception queue with the raw payload retained. Alerts go to Zoho Cliq or email. Runs log every call so a disputed figure can be traced back to what the marketplace actually returned.

Reporting

We deliver Zoho Analytics or Zoho Books reports covering net realisation per SKU after commission and fees, fulfilment-centre stock position against Zoho Inventory, return rate by SKU and country, and settlement ageing showing what is owed but unpaid.

Who this is for

UAE and Saudi sellers already running Zoho Books with VAT localisation, regional brands operating Noon alongside their own store or other channels, distributors who need marketplace stock reflected in a single inventory picture, and finance teams who have to file VAT from data they can defend.

How delivery works

1. Scoping call. We review your Noon seller account structure, which countries and fulfilment models you use, your Zoho Books organisation or organisations, VAT registrations, warehouse layout and how your accountant wants marketplace fees posted. You provide sample order and settlement exports. 2. Fixed quote and specification. A written scope listing every object, custom field, function, mapping and report, with assumptions stated and a fixed price. Work starts only after you approve. 3. Build. Usually one working week. Development happens in our environment and against a sandbox or trial Zoho organisation, never against your live books. 4. Install in test. We install into a test organisation, run your real historic orders and a real settlement file through it, and reconcile the results with you and your accountant. 5. Production go-live. On sign-off we install into production, configure credentials and schedules, and run the first live settlement cycle alongside your team. 6. Support. A defined post-go-live support window covers defects, marketplace changes and configuration adjustments, with ongoing support available separately.

What this is not

There is no instant download and no free trial, because the software does not exist until we build it for your organisation. Data access depends on the API credentials or report exports your own Noon seller account is entitled to; we confirm exactly what is available to your account during scoping and build to that, not to an assumed access level.