Amazon MENA Seller Connector

The problem Gulf sellers actually have

Selling on Amazon's UAE, Saudi and Egypt storefronts is not the same business as selling on a single-country marketplace, and the accounting shows it. Each storefront settles in a different currency (AED, SAR, EGP), each one applies a different indirect-tax regime (5% UAE VAT, 15% Saudi VAT, 14% Egyptian VAT), and each one deducts a different mix of referral fees, fulfilment fees, storage charges, removal orders, promotional rebates and reimbursements before a single dirham reaches your bank account. Generic Amazon-to-accounting connectors were designed for a North American or European seller. They assume one tax rate, one currency, Latin-script product titles and a settlement report whose line-item types map cleanly onto a single fee account.

What happens in practice is a slow accumulation of unreconciled noise. Orders land in Zoho Inventory without the tax treatment your accountant needs, so every invoice has to be corrected by hand. Arabic product titles arrive mangled or truncated because the sync path never handled RTL text or the two-language listing structure Amazon MENA uses. Settlement deposits arrive as a single lump figure that nobody can tie back to the orders inside it, so the bank reconciliation in Zoho Books stays open for weeks. Returns and refunds post against the wrong period. And when the FTA or ZATCA asks for the output-tax working behind a return, the answer lives in a spreadsheet someone rebuilt by hand from CSV exports.

What ECOSIRE builds

ECOSIRE builds this connector for your Zoho organisation. It is not an off-the-shelf download — we scope it against your actual storefronts, your Books organizations and your chart of accounts, then build and install it.

Order and listing sync into Zoho Inventory

A scheduled Deluge integration polls the Amazon Selling Partner APIs for orders, order items and shipment events across each marketplace you sell in, and creates the corresponding Sales Order and Package records in Zoho Inventory. SKU matching runs against your existing Item records with a configurable mapping table held in a Zoho Creator app, so an ASIN that maps to a different internal SKU per storefront is handled explicitly rather than by guesswork. Arabic listing fields are stored UTF-8 clean in dedicated custom fields on the Item record, alongside the English title, so your team can search either script inside Zoho.

Per-storefront VAT logic

Each marketplace is bound to its own tax configuration. The build sets up the tax rates, tax authorities and place-of-supply handling inside your Zoho Books organizations so that a UAE order carries 5% output VAT against the correct emirate, a Saudi order carries 15%, and an Egyptian order carries 14%. Where you operate separate Books organizations per country, orders route to the right organization automatically. Where you run a single organization with multi-currency, the connector stamps the exchange rate from the settlement rather than from the order date, so the Books figure matches the money that actually arrived.

Settlement reconciliation

This is the core of the build. The connector ingests each Amazon settlement report, decomposes it line-type by line-type, and posts the components against the accounts you nominate: gross sales, refunds, referral fees, FBA fulfilment fees, storage, advertising cost, reimbursements, adjustments and withheld tax. It then creates a matching bank deposit record in Zoho Books whose total equals the net deposit, with the underlying detail attached. Your reconciliation stops being a lump-sum guess and becomes a line-matched record.

Returns, refunds and reimbursements

Return events create Credit Notes in Books and Sales Return records in Inventory, with the tax reversed at the same rate the original sale carried. Amazon reimbursements post separately, so a lost-inventory reimbursement never gets mistaken for revenue.

Stock and pricing back to Amazon

Available quantity from Zoho Inventory can be pushed back to each marketplace on a schedule, with per-storefront buffer rules so a single warehouse is not oversold across three countries. Price updates can be pushed the same way where you want Zoho to be the master.

Operations surface

A Zoho Creator application gives your team the working screens: a sync dashboard, the ASIN-to-SKU mapping table, a settlement explorer, a failed-record queue with one-click retry, and the marketplace credential configuration. Custom functions and scheduled workflows drive the polling; Zoho Flow is used where a low-code branch is genuinely clearer than script.

Who this is for

Sellers with live Amazon MENA storefronts who already run Zoho Books and Zoho Inventory (or are moving onto them) and whose finance team is currently rebuilding settlement workings by hand. It suits multi-country sellers most — the value compounds the moment more than one tax regime is in play. It is a poor fit if you sell on a single storefront with a handful of orders a month; the manual route is cheaper for you.

How delivery works

1. Scoping call. We go through your storefronts, marketplace IDs, Books organization structure, chart of accounts, SKU model, warehouse setup and how you want settlements posted. We confirm which Amazon API roles your seller account can grant. 2. Fixed quote. You receive a written scope and a fixed price before any build starts. Anything outside it is quoted separately, not billed as a surprise. 3. Build. We develop the Deluge scripts, custom functions, Creator screens, field mappings and scheduled jobs against a sandbox or a duplicated test organization. Typical lead time is two to four weeks depending on how many storefronts and Books organizations are in scope. 4. Install in test. We install into your test environment, run a historical settlement through it, and sit with your finance lead until the posted figures agree with the Amazon report. 5. Production go-live. We install into your live Zoho org, configure credentials, enable schedules and monitor the first full settlement cycle with you. 6. Support window. A defect-fix and configuration-support period follows go-live, with handover documentation and a walkthrough recording for your team.