If you sell on Noon across the UAE and KSA, your operations team lives in two places at once. Orders land in Noon Seller Lab while your books, stock, and fulfillment live in ERPNext — so someone re-keys orders, someone else guesses which SKUs Noon thinks are in stock, and settlement reports get reconciled by hand in a spreadsheet weeks after the money moved. ERPNext ships no native Noon integration; its stock, pricing, and Sales Order engine is excellent, but there is no connector, no marketplace DocType, and no scheduler job that knows Noon's Partner API exists. That gap is exactly where double-entry, oversells, and unreconciled fees come from.

ECOSIRE builds a proper Frappe application — not a script bolted onto your bench — that turns Noon into a first-class channel inside ERPNext. The app installs its own module with dedicated DocTypes such as Noon Settings (single, encrypted API credentials), Noon Marketplace Account, Noon Order and Noon Fulfilment Log, plus an item-mapping DocType that ties each Noon SKU/partner-SKU to your ERPNext Item and Warehouse. Order ingestion runs on scheduler_events (a cron-style hook in hooks.py) that pulls new Noon orders through the Noon Partner REST API, deduplicates on the Noon order reference, and creates ERPNext Sales Order documents with the correct customer, taxes, and channel. FBN (Fulfilled by Noon) and FBP (Fulfilled by Partner) inventory are handled distinctly: FBP stock is pushed from your ERPNext Bin quantities so you never oversell, and FBN quantities are pulled back so your ERPNext view reflects what Noon actually holds in its fulfilment centres.

Technically it is built the way ERPNext itself is built. Price and listing pushes are driven by doc_events hooks on Item Price and Item so a change in ERPNext propagates to Noon on save, with a queued background job for the API call. Shipping and tracking writeback fires when a Delivery Note is submitted, pushing carrier and tracking data back to Noon. Settlement and fee reconciliation imports Noon's payout files into a Noon Settlement DocType and matches commission, fulfilment, and refund lines against the originating Sales Invoice, so finance sees real net revenue. Every external call is a whitelisted method behind Frappe's permission model, all writes respect role profiles you approve (for example a Noon Manager role), failures are logged to a retriable error DocType rather than lost, and rate limits and idempotency are enforced so a webhook or scheduler retry never duplicates an order. Client scripts add the Noon status, sync buttons, and mapping helpers directly onto the ERPNext forms your team already uses.

Because every Noon account differs — your SKU count, FBN vs FBP mix, tax setup, multi-company or multi-warehouse structure, and which flows you actually need on day one — this is a build-to-order engagement, not a shelf download. We start with a short scoping call, confirm the exact scope and your Frappe/ERPNext version (v15 or v16), and build against a staging copy of your instance. Typical delivery is one working week from confirmed scope. You receive the installable app source for your version, a documented install, UAT on staging with a rollback plan, a training session, and a post-go-live support window — plus the git repository so the code is yours to keep and extend.