Noon Store Management
The ECOSIRE Noon Store Management module connects your noon seller account to Odoo across the UAE, Saudi Arabia and Egypt from a single instance, and a Namshi Integration Warehouse (FBPI) account as well. It talks to noon's unified Partner API Platform to import orders, sync your catalogue, push stock, and enforce the KSA ZATCA Phase 2 and Egypt ETA tax preflights before an order is processed.
Compatibility: Odoo 17 / 18 / 19 / 20 (Community or Enterprise)
Current maintained build: 17.0 → 17.0.3.10.24, 18.0 → 18.0.3.10.24, 19.0 → 19.0.3.10.24, 20.0 → 20.0.3.10.24
Price: $499 USD (one-time, per Odoo version)
Licence: OPL-1 — no key required; you buy per Odoo major version
Namshi's Partner API publishes orders only for an Integration Warehouse (Fulfilled by Partner Integration, FBPI). It does not publish FBN orders, finance statements, the FBN inventory ledger or a catalogue export, so no connector can import them. On Namshi the connector handles stock, pricing, Integration Warehouse orders and shipments, returns references and event notifications. If you sell on Namshi through FBN only, Namshi orders cannot be imported. noon, including noon FBN, is fully supported. Verified against the live Namshi documentation index on 2026-10-07.
This page is the overview. The step-by-step installation and configuration guide lives at Noon Store Management — installation & configuration.
What this module does
-
Products, contacts and sales orders keep their standard screens (3.10.24, Odoo 17/18/19/20) - the noon Imported Products, Imported Customers and Noon Orders list and search screens open only from the noon menus; product and contact search dialogs and sales order lists elsewhere in Odoo show the standard columns and filters again
-
Pushed prices are in the country's currency (3.10.23, Odoo 17/18/19/20) - the price push converts each product's sales price from your company currency into AED, SAR or EGP at the push date's exchange rate (unchanged when the currencies are the same); a product whose country currency is archived or has no rate is never sent, and the reason is shown on the button or in the Sync Log
-
KSA and Egypt tax checks on every imported order (3.10.22, Odoo 17/18/19/20) - before an order is confirmed, a business buyer missing the KSA VAT registration number, CR number or CR date, or the Egypt 14-digit ETA tax id, keeps the order in draft with the reason in Noon Sync Error and one chatter note; the next sync confirms it once the details are completed. Consumer orders take a simplified invoice and are never held
-
Push prices to noon (3.10.22, Odoo 17/18/19/20) - Push Prices to Noon (Outbound), a Push Prices button and an optional hourly noon: Push Prices schedule send each mapped product's Odoo sales price to noon in the connection's country; both are off by default because the push replaces the offer price buyers see
-
Return credits are never invoiced as sales (3.10.21, Odoo 17/18/19/20) - a small credit noon books for a returned item in "Other Order Fees" stays on the statement marked Return Credit but is never revenue; the Sales order shows Refunded / Returned and the noon Sales report shows the item as Returned. A reversal next to a return credit is credited in full, and with Credit refunded orders automatically switched on, invoices already posted for return credits get a credit note (posted invoices are never rewritten)
-
Orders delivered late no longer stay In Transit (3.10.20, Odoo 17/18/19/20) - each sync re-reads the orders still open, back to the oldest one (up to the 90-day lookback), so a late delivery reaches Completed and is invoiced in its order's month; an item noon reports as undeliverable now maps to Cancelled instead of Delivered
-
noon Sales report (3.10.19) - Finance > noon Sales (and a dashboard Quick Action) counts sales the way noon's Sales Performance Hub does: every ordered unit, in the marketplace currency with VAT, per month and marketplace, with settled value, units awaiting a statement and a clearly labelled provisional value; read-only and limited to your companies
-
Order dates in the marketplace's own calendar (3.10.19) - KSA, UAE and Egypt orders are dated in local marketplace time, so monthly invoice totals line up with noon's; statement values are matched to order lines by noon's item number, and a later settlement correction is no longer taken as a selling price
-
One noon connection per country, without duplicate orders (3.10.8) - the option Only This Country's Orders keeps each connection to its own country (orders by destination, finance rows by currency); an order already held by another connection is not imported again, and catalogue rows are no longer reset to Pending by the order import
-
noon Managers can enter the store key (3.10.12) - the service-account key and OAuth fields are open to the noon Manager role; plain noon users still cannot see them
-
Returns that noon accepts (3.10.11) - the returns lookup asks noon for your connection's own project, and every returned item is saved and linked to its order; every run writes a Sync Log row (3.10.7)
-
Match noon SKU to Internal Reference or Barcode (3.10.10) and VAT that follows each product's own tax (3.10.9)
-
A dashboard that never ends in an error dialog (3.10.6)
-
Refunds, fee types and noon's "-" placeholder (3.10.16) - each noon fee type gets its own total, column and optional account (Noon Fees Account stays the fallback); warehouse, sales team and delivery handling per FBN / FBP; the "-" placeholder noon puts in its reports is never used as a seller SKU, so Internal References are no longer overwritten; FBPO purchase-order events no longer become sales; and, with Auto Credit Notes for noon Reversals switched on (off by default), a full reversal of a settled order posts one reconciled credit note, while a partial reversal is flagged for review
-
Orders use your own product when noon's finance report names its Partner SKU (3.10.15) - noon's order report names only noon's SKU; the import now looks up the Partner SKU noon's finance report states and uses your product matched in the Match noon SKU to field instead of creating a "catalog details unavailable" product, and a product created that way before moves its noon link to yours once the Partner SKU is known (exact match only; open draft quotations move too only with Move Draft Quotations to Matched Products switched on, off by default; confirmed orders and invoices are never changed)
-
Returns found again on FBN projects (3.10.14) - the returns lookup asks noon about the return barcodes the FBN inventory ledger records (return label and return airway bill) before product barcodes, and every unit noon takes back into FBN is recorded as a noon return linked to its order
-
An exact statement of what Namshi offers (3.10.13) - Namshi orders are imported for an Integration Warehouse (FBPI) only; Namshi does not publish FBN orders, finance statements or the FBN ledger through its API
-
Every Partner API operation the connector calls is recorded in ECOSIRE's verified API contract (3.10.5) - the catalogue (SKU generation, mapping, renaming, deletion, barcode import), Content, FBPI invoice upload, FBPO purchase-order, Offer and Cross-Border Pricing operations were already implemented but had not yet been checked into the contract our release gates verify against; each was confirmed on its own page of the noon Partner API reference. No request the connector makes has changed. The release also adds 34 regression tests on all three Odoo series, each proving a failure case a real seller has hit on a marketplace connector (idempotent re-imports, two stores keeping the same order number apart, scheduled sync only where enabled, masked customer data staying masked, an unknown report currency failing closed, and more). It also installs with a clean log on Odoo Online and odoo.sh: the OMS and finance report-quota messages the connector emitted while degrading gracefully were error-level lines, which Odoo's hosting treats as a blocked deployment, and they are warnings now. A run that could not read a report still records error on its sync log with the failed-record count, so nothing is hidden
-
Dashboard and sync endpoints respect company boundaries (3.10.4) - in a multi-company database the dashboard and the sync endpoint now work only with the noon connections of the companies you are working in, and starting a sync is reserved for noon Managers. The noon catalogue list, with its Not Mapped to a Product filter, also has its own Noon → Noon Catalogue menu
-
Installs on Odoo Online (3.10.3) - the module declares its version in the form Odoo Online accepts, so it installs on Odoo's own hosting as well as on your own server. The FBN inbound shipment inspector is also restricted to noon managers, the same access level every other warehouse action in the module already uses
-
Partner API route coverage you can check (3.10) - every operation in noon's unified Partner API is referenced by the module's API client in a form tooling can verify, and a coverage guard ships inside the module that fails loudly if a documented operation ever loses its route. The three operations noon has withdrawn or renamed, and the documented families that sit outside the bounded contract, are recorded with their evidence in a ledger the guard checks in both directions
-
Namshi Integration Warehouse connections (3.9) - Namshi answers on its own gateway and does not host a warehouse listing API at all (warehouses are created in Seller Lab), so Test Connection no longer treats that as a failed connection: type your Warehouse Code and the connection is valid. The Capabilities panel states up front which services Namshi offers and which are noon-only, so you can see what a Namshi connection will and will not do before running a single sync. Namshi AE and Namshi KSA are separate marketplaces and get one connection each
-
VAT that your accountant can file (3.9) - noon reports VAT-inclusive amounts, so the connector used to strip the tax lines and leave invoices with correct totals and no VAT at all. Choose a VAT-included sales tax per connection and the total stays exactly the amount noon reported while the VAT is shown separately
-
A dashboard that says which connection it is showing (3.9) - with noon and Namshi both connected the dashboard used to read one of them silently; it now has a connection selector and names the connection the figures belong to
-
Delivery Handling per connection (3.9) - record the quantities as delivered and cancel the Odoo transfer (right for a pure FBN seller, and still the default), or validate the transfer so the stock move lands in your own inventory
-
Reconciliation that tells you what is wrong, not just that something is (3.8) — a closing balance below zero is impossible in a fulfilment centre, so it is flagged in its own right (Negative stock — missing Noon movement rows) with the cause named: some centres take stock in only through warehouse transfers and return re-inbounds, which noon exports without a matching inbound row. Inventory snapshots are compared against the balance as it stood when noon took the snapshot, so movements posted afterwards are no longer reported as discrepancies between two entirely correct noon reports
-
Refunded orders are called refunded (3.8) — an order carrying noon finance rows with no gross item value but a reversal booked against it is reported as Refunded / Returned with the credited amount, instead of the ambiguous “noon reported no item value”. A cancellation fee is deliberately not counted as a refund
-
Receipt (ASN) tie-out (3.8) — group the movement ledger by Receipt / Document Nr and walk one inbound shipment at a time
-
Orders — FBPI order import (list → per-order detail → idempotent upsert) with honest processed/created/updated/failed counts; Noon OMS and Fulfilled-by-Noon (FBN) orders are also imported through noon's official orders-export report, as draft Sales mirrors that are never auto-confirmed, priced from noon's item-level finance report where the account exposes it
-
Catalogue — product import through noon's official global-catalogue CSV export, with idempotent product shadows mapped to Odoo products
-
Warehouses — discovered automatically through the Warehouse Platform service; single-warehouse accounts configure themselves during Test Connection
-
Tax preflights — for business buyers, KSA (ZATCA Phase 2: VAT registration number, CR number and CR date) and Egypt (14-digit ETA tax id) are required on the customer record before an order for that country is confirmed
-
Multi-country, multi-marketplace — one configuration per country (UAE/KSA/Egypt) and per marketplace (noon, or Namshi for Integration Warehouse orders, stock and pricing)
-
Stock — push to the verified stock-update endpoint for mapped SKUs
-
Finance ledger & statements (3.2) — noon's item-level finance report stored row by row and grouped by statement reference into a receivables view: gross value, fees, payouts and balance transfers
-
FBN inventory ledger, reconciliation & aging (3.2–3.7) — every FBN stock movement from noon's official ledger export, a per-SKU/per-centre/per-month reconciliation with mismatch flags, and age buckets with a staleness threshold; the Seller Lab Inventory Detail close is the authoritative point-in-time control
-
Lost and Found reconciliation (3.7) — signed Lost and Found rows from Inventory v2 appear explicitly as found, lost, net units and source-row count per SKU, fulfilment centre and month; they remain in the movement total and are not disguised as a generic adjustment
-
Automatic historical order valuation (3.7) — scheduled finance runs revisit the oldest delivered and in-transit zero-valued mirrors three months at a time, while explicit amount states distinguish finance still pending from a genuine source-reported zero
-
Current Partner API parity (3.7) — exact helpers and an allowlisted dispatcher cover all 51 operations in noon's current public reference; 65 unique current, legacy and replaced identities are classified, with program-gated operations labelled honestly
-
Content and pricing publication (3.7) — mapped products publish through noon's current Content API and mapped prices use the current country-scoped Pricing API
-
Month-by-month FBN stock statement (3.3) — group the reconciliation by period and one month's closing total is the next month's opening total: SKUs holding stock with no movement that month are listed as Carried Forward so a dormant balance can no longer drop out of the monthly total (filter them out again in one click)
-
Returns (3.2) — returns imported on a schedule, persisted as records and linked back to their orders by item number
-
Content rejections & product analytics (3.2) — why a listing never went live, and per-product/per-country/per-day views, units, revenue and conversion with a "viewed, never sold" flag
-
Capability panel (3.2) — each API family probed and reported as available / not granted / not offered / unknown, so a program restriction never masquerades as an authentication failure
-
Proof of delivery — signature capture from delivery events onto the order
-
Webhooks — Event Notifications with IP-allowlist verification and a fast 200 ACK, with scheduled polling as the fallback so no order depends on the webhook alone
-
Auto-workflow — optional auto-confirm, auto-invoice and auto-deliver per configuration
-
Dashboard — an accessible (WCAG 2.2 AA) OWL dashboard with per-country KPIs in the order's real currency and Chart.js charts
How FBN inventory reconciliation works
The connector deliberately keeps three measures separate:
| Measure | Source | Meaning |
|---|---|---|
| Reported activity | Inventory v2 detailed ledger | The signed movements noon published, including Lost and Found |
| Closing anchor | Seller Lab FBN Inventory Detail close | noon's point-in-time balance for the selected close date |
| Noon Adjustment | Odoo calculation | The quantity the close cannot explain from the published opening plus movements |
Noon Adjustment = Noon Closing Anchor - (Noon Opening Anchor + Net Reported Movements)
Importing the same FBN Inventory Detail close CSV with the same seller, close date, warehouse, and inventory-type filters should reproduce that file's closing quantity exactly. The movement-derived closing is a different measure and can differ when noon's rolling ledger omits history or a movement. Follow the complete FBN reconciliation procedure before comparing totals.
Honest boundaries
- Namshi FBN is not available. Namshi's API publishes orders only for an Integration Warehouse (FBPI). Namshi FBN orders, finance statements, the FBN ledger and the catalogue export are not published to any connector, so they cannot be imported.
- Permissions still apply. Product publication, credential administration, sandbox-order creation, shipment cancellation, invoice upload and other privileged operations work only when noon grants the seller account that capability. Missing product mappings fail before a Content API write and state exactly what is missing.
- No automatic journal posting. Settlement statements can create balanced draft journal entries on configured accounts, but the connector never posts them automatically.
- No buyer name, phone or address on Noon OMS/FBN orders. noon does not expose that data on those orders through any partner endpoint. Real buyer detail is only available for orders placed through the FBPI program; every other order links to one explicit, clearly labelled privacy-protected marketplace buyer instead of a guessed name.
- Historical order values never come from today's offer price. Prices can be pushed through the current Pricing API, but a past order is valued only from noon's item-level finance report for that order and item.
- One report remains manual. The Seller Lab month-end Inventory Detail close is not advertised by the Impex API, so that point-in-time report remains a CSV import. Inventory v2 movements, including Lost and Found, are automatic.
- No bulk coupon/customer export. noon's current public reference does not document one, so the module does not invent it.
Prerequisites
- Odoo 17, 18, or 19 (Community or Enterprise)
- The module, bought on the Odoo Apps Store for your Odoo major version (no key is entered in Odoo)
- A noon (or Namshi) seller account with unified Partner API access: a downloaded service-account credential
.json, or OAuth 2.0 credentials. Namshi orders need an Integration Warehouse (FBPI) - Python packages
requestsandPyJWT[crypto]installed into the interpreter that runs Odoo
Quick start
- Open the Noon Store Management listing on the Odoo Apps Store for your Odoo major version and purchase it there.
- Take the file the store issues for that purchase from your Odoo Apps Store account and extract it into your Odoo addons directory. No ECOSIRE dependency is needed.
- Restart Odoo, then Apps → Update Apps List, search for Noon Store Management and install.
- Create a configuration per country/marketplace, paste your service-account credential (or OAuth token), and click Test Connection.
- Turn on the sync toggles you are ready for — products, orders, customers, inventory — one at a time.
Full detail — including the connection field reference, API coverage boundaries, reconciliation workflow, and troubleshooting — is in the installation & configuration guide.