Noon Marketplace Connector

The problem

Selling on Noon while running SAP Business One usually means somebody exports a CSV from Noon Seller Lab every morning, re-keys orders into Sales Orders, and manually adjusts stock so the marketplace does not oversell a SKU that a retail branch already shipped. Settlement reports arrive later, in a different shape, with commission, fulfilment fees and returns netted off — and nobody can reconcile the bank deposit to the A/R Invoices it was supposed to pay.

The damage is not theoretical. Overselling on a Gulf marketplace costs seller-score points and eventually suppresses your listings. Late order acknowledgement burns the dispatch SLA. And because Noon deposits net of fees, the finance team either posts the gross and leaves an unexplained variance in the bank reconciliation, or posts the net and loses all visibility of what commission actually cost.

SAP Business One has no native concept of a marketplace channel. There is no standard object for a marketplace order, no place to keep a channel SKU alongside your ItemCode, and no mechanism to push available-to-promise quantities outward on a schedule. Everything below is what ECOSIRE builds to close that gap.

What ECOSIRE builds

We build a dedicated SAP Business One add-on and integration service for your tenant. It is written against the Service Layer (REST/OData) for transactional posting and querying, with the DI API used where an operation has no Service Layer equivalent. Master-data extensions are delivered as UDFs and UDTs, and channel entities that need their own forms, authorisations and approval behaviour are delivered as UDOs so they behave like first-class B1 objects rather than loose tables.

Order ingestion

The connector polls your Noon seller API credentials on a configurable interval and creates a marketplace order record in a UDO, then a Sales Order in SAP Business One against a dedicated marketplace Business Partner. Line matching is done through a channel-SKU mapping table (UDT) that resolves the Noon SKU or partner SKU to your ItemCode, including bundle and multi-pack decomposition where one channel SKU maps to several B1 items. Shipping fees, promotional discounts and cash-on-delivery charges land on their own service lines so the document total reconciles to the marketplace order value exactly.

Order state changes — confirmed, packed, shipped, delivered, cancelled, returned — are written back to the marketplace order UDO and drive downstream document creation: Delivery on dispatch, A/R Invoice on the trigger you choose, Return and A/R Credit Memo on a marketplace-approved return.

Inventory and pricing sync

Available quantity is calculated from the warehouses you nominate — typically your fulfilment warehouse, optionally netted for open Sales Orders and reserved stock — and pushed to Noon on a schedule with a configurable buffer so a shared-stock SKU cannot be sold twice. Price pushes read from a nominated Price List, with optional per-channel uplift rules so marketplace pricing can carry commission without a manual second price file.

Settlement reconciliation

This is the part most CSV workflows never solve. The connector ingests the Noon settlement statement, matches each line back to the originating B1 invoice, and creates the Journal Entry that separates gross revenue, commission, fulfilment fee, shipping recovery and return reversals into the G/L accounts you nominate. Incoming Payments are proposed against the matched invoices so the bank deposit clears cleanly. Unmatched lines are held in an exception queue rather than being force-posted.

Fulfilment models

We handle both the seller-fulfilled and marketplace-fulfilled patterns. For marketplace-fulfilled stock we model the fulfilment centre as a separate B1 Warehouse and generate Inventory Transfer documents on inbound consignment, so your stock ledger reflects where the goods physically are instead of showing them as sold the moment they leave your door.

Operational controls

Every API call and every document created is logged to a UDT with the marketplace reference, request/response payload and outcome, exposed through a monitor screen in the B1 client. Failed calls retry with backoff; permanently failed items land in an exception queue an operator can inspect and reprocess. Where your process requires sign-off — a price push above a threshold, a credit memo above a value — we wire the relevant document into B1 approval procedures rather than inventing a parallel approval mechanism.

Who this is for

Gulf sellers and distributors already live on SAP Business One who have taken a Noon storefront seriously enough that manual order entry has become a headcount problem. It suits businesses selling the same stock through multiple channels — retail, wholesale, own webstore, marketplace — where overselling is the daily pain, and businesses whose finance team currently cannot explain the gap between marketplace sales and marketplace deposits.

It is not for a business testing its first ten marketplace orders. At that volume, manual entry is cheaper than an integration.

How delivery works

1. Scoping call. We walk through your Noon account structure, fulfilment model, warehouse layout, SKU mapping reality, tax treatment and the exact G/L accounts settlement should hit. We look at your live company database structure, not a generic template.

2. Fixed quote. You receive a written scope and a fixed price before any code is written. If your requirements exceed the standard build — unusual bundle logic, a second marketplace, a custom settlement treatment — that is priced explicitly rather than discovered halfway through.

3. Build. ECOSIRE develops the add-on against your SAP Business One version and database platform. Nothing is pre-built and waiting; typical lead time is one working week from a signed scope.

4. Install into test. We install into your test company database first, load real order data from your Noon account, and run the full cycle — order in, document chain, stock push, settlement post — with your team watching. Corrections happen here.

5. Install into production. After your sign-off on the test company, we install into production, configure credentials and schedules, and run the first live cycle alongside your team.

6. Support. A defined support window follows go-live for defect correction and configuration adjustment, with the terms stated in your quote.