Skip to main content

Noon Store Management

The ECOSIRE Noon Store Management module connects your noon (or Namshi) seller account to Odoo across the UAE, Saudi Arabia and Egypt from a single instance. It talks to noon's unified Partner API Platform — the same gateway noon and Namshi share — 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 (Community or Enterprise) Current shipped version: 17.0 → 17.0.3.2.1, 18.0 → 18.0.3.2.1, 19.0 → 19.0.3.2.1 Price: $499 USD (one-time, per Odoo version) License: One ECOSIRE licence per Odoo major version — a licence issued for Odoo 17 will not activate on 18 or 19

Installing for the first time?

This page is the overview. The step-by-step download, licence-activation and configuration guide lives at Noon Store Management — installation & configuration.

What this module does​

  • 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 — KSA (ZATCA Phase 2: VAT registration number + CR number) and Egypt (14-digit ETA tax id) are required on the customer record before an order for that country is processed
  • Multi-country, multi-marketplace — one configuration per country (UAE/KSA/Egypt) and per marketplace (noon or Namshi, both on the same Partner API gateway)
  • 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) — 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 CSV import remains the snapshot fallback
  • 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

What this module does not do​

  • No catalogue product create/update push. That capability is access-gated by noon behind Tech-Team approval; the module raises a clear error instead of calling a route it does not have access to.
  • No automated journal entries. The 3.2 finance ledger stores noon's own reported rows as a receivables view — it does not post accounting entries, and the settlement ledger remains a manually-fillable draft with a journal-entry link.
  • 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.
  • No price synchronization yet and no bulk coupon/customer export — no verified endpoint exists for either today.

Prerequisites​

  • Odoo 17, 18, or 19 (Community or Enterprise)
  • An active ECOSIRE licence for this module and your Odoo major version
  • A noon (or Namshi) seller account with unified Partner API access: a downloaded service-account credential .json, or OAuth 2.0 credentials
  • Python packages requests and PyJWT[crypto] installed into the interpreter that runs Odoo

Quick start​

  1. Download the ZIP for your Odoo version from your ECOSIRE dashboard.
  2. Extract it into your Odoo addons directory, along with the free ecosire_license_client dependency, and restart Odoo.
  3. Apps → Update Apps List, search for Noon Store Management, install.
  4. Activate your ECOSIRE licence at Settings → ECOSIRE.COM.
  5. Create a configuration per country/marketplace, paste your service-account credential (or OAuth token), and click Test Connection.
  6. Turn on the sync toggles you are ready for — products, orders, customers, inventory — one at a time.

Full detail — including how to obtain a licence, the connection field reference, and troubleshooting — is in the installation & configuration guide.

Support​

Last updated on