The pain
Amazon is often the largest revenue line in a Zoho Inventory account and the least understood one. The order data that reaches the ERP is thin, the fee data usually never arrives at all, and the money in the bank is a fortnightly net figure that resembles nothing in the ledger.
Sellers describe the same three problems.
FBA is invisible. Fulfilment by Amazon moves your stock between fulfilment centres, holds it as reserved during picking, marks units unfulfillable, loses some and reimburses you for others. If the ERP only knows about orders, none of that reaches your books. Your Zoho Inventory quantity is a number you stopped trusting months ago, and your stock valuation is wrong in a way nobody can quantify.
Fees are a black hole. Referral fees, FBA fulfilment fees, monthly storage, long-term storage, removal orders, advertising, refund administration fees and reimbursements are all deducted before you see a penny. Booking the deposit as one lump of revenue overstates sales and hides the fact that a particular ASIN loses money on every unit.
Regions and marketplaces do not line up. A seller listing in the UAE, Saudi Arabia, the UK and India is dealing with different marketplace IDs, currencies, tax treatments and settlement cycles. Native coverage does not extend everywhere, and where it does, it treats each marketplace as an island rather than reconciling them into one Zoho organisation.
What ECOSIRE builds
We build an Amazon Selling Partner API connector that treats Amazon as a full financial channel inside Zoho, not just an order feed.
Orders across FBA and FBM
We poll the SP-API Orders resource on a schedule you choose and create the corresponding Zoho Inventory Sales Order or Zoho Books Invoice, complete with line items matched by SKU or ASIN, buyer information within Amazon's data-protection limits, ship-from and ship-to addresses, and marketplace identification. FBM orders route into your normal Zoho picking and shipping flow with tracking pushed back to Amazon through the Merchant Fulfilment or Feeds path. FBA orders are recorded as fulfilled by Amazon and decrement the FBA warehouse rather than your own.
FBA inventory as a real warehouse
We map each Amazon fulfilment network to a dedicated Zoho Inventory warehouse and sync the FBA inventory summaries into it: fulfillable, reserved, inbound working, inbound shipped, inbound receiving and unfulfillable quantities, each held as a distinct figure rather than one blended number. Inbound shipment plans created in Seller Central are reflected as transfer orders so stock in transit is visible and valued. Removals and disposals are recorded against the warehouse instead of quietly disappearing.
Fee and settlement reconciliation
This is the core of the build. We pull settlement reports and finances data and construct the matching entries in Zoho Books: gross product sales, promotional rebates, referral fees, FBA fulfilment fees, storage and long-term storage fees, refunds, refund administration fees, reimbursements, advertising charges and any marketplace-specific levies. Each is posted to its own configured account so the settlement deposit in your bank feed reconciles against a single grouped set of lines, and your P&L shows what Amazon actually cost you.
Where you want per-SKU profitability, we attach fee data at line level so a Zoho Analytics report can show contribution after Amazon fees by ASIN.
Multi-marketplace, multi-currency
Each marketplace you sell in gets its own configuration: marketplace ID, currency, settlement cycle, tax treatment and target warehouse. Orders carry their marketplace currency and the applied rate into Zoho Books. For Indian sellers we map GST treatment with place of supply from the ship-to state; for Gulf sellers we map the applicable VAT treatment to your configured Books tax rates. One Zoho organisation can hold several marketplaces without their numbers being pooled into a meaningless total.
Listings and stock push
Available quantity from your own Zoho Inventory warehouses is pushed to your merchant-fulfilled listings through the SP-API Listings and Feeds paths, on a schedule and with a configurable buffer so a single warehouse does not oversell across channels. Price updates can be pushed the same way where you want Zoho to be the master. Suppressed and inactive listings are reported so a stocked item that is not actually buyable does not silently sit there.
Returns, reimbursements and claims
Return reports create credit notes or return receipts in Zoho against the original order. Reimbursements are posted separately from sales so they never inflate your revenue figures. Lost and damaged units are surfaced in a report you can use to raise claims, rather than being absorbed into an unexplained stock variance.
Rate limits, retries and visibility
SP-API enforces per-operation rate limits and report generation is asynchronous. The connector implements the documented token-bucket backoff, queues report requests, polls for completion and handles the throttling responses properly. Every operation writes to a Sync Log module with its request, response and status, retries failures with backoff, and permits manual replay. A daily reconciliation job compares Amazon order counts and FBA quantities against Zoho and emails the differences.
Who this is for
Amazon sellers running Zoho Inventory or Zoho Books who need their marketplace numbers to be as trustworthy as their direct sales: FBA sellers who cannot see stock movement inside the fulfilment network, multi-marketplace sellers operating across the Gulf, India, the UK or Europe, and finance teams that currently treat the settlement deposit as a single revenue line because breaking it down by hand is not feasible.
It suits sellers with a Professional selling account and access to their own SP-API application or developer credentials.
How delivery works
Scoping call. We list your marketplaces, your fulfilment mix, your settlement cycle and the accounts you want each fee type posted to. We look at a real settlement report with you and agree line by line where each transaction type lands in Zoho Books. We confirm your Zoho plans and your Amazon selling account type and API access.
Fixed quote. You receive a written specification covering the marketplaces in scope, the order and inventory flows, the settlement mapping table and the reports, plus a fixed price and delivery window. Nothing begins until you approve.
Build. Typical lead time is two to four weeks and extends with the number of marketplaces and the depth of settlement mapping. We develop against Amazon's sandbox endpoints where they exist and against a Zoho trial or sandbox organisation.
Install in test, then production. We install into your test organisation and run a live matrix: an FBM order through to shipment confirmation, an FBA order, a refund, a return, an FBA inventory sync including reserved and inbound quantities, a stock push to a merchant listing and a full settlement period reconciled against the actual deposit. You confirm the settlement reconciles before we go near production. Go-live uses an agreed cut-over date so historic orders are not double-imported.
Support. Thirty days of post-go-live support cover fee mapping corrections, marketplace additions, throttling issues and user questions. Extended support and additional marketplaces are quoted separately.
The connector runs inside your own Zoho organisation using your own Amazon developer credentials, and the source is handed to you.