A build-to-order SAP Business One add-on that syncs your Noon seller catalogue, orders, stock and settlements both ways. Scoped, quoted and built for your company database — not an off-the-shelf download. Built to order by ECOSIRE for SAP Business One (build-to-order) — indicative price from $799.00 USD; request a quote for a scoped proposal.
A build-to-order SAP Business One add-on that syncs your Noon seller catalogue, orders, stock and settlements both ways. Scoped, quoted and built for your company database — not an off-the-shelf download.
Sob encomenda
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.
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.
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.
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.
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.
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.
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.
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.
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 two to four weeks 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.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Spends the first hour of every day re-keying marketplace orders and the last hour reconciling stock so the channel does not oversell. This removes the re-keying entirely and pushes accurate available quantities on a schedule, so the seller score stops taking hits from cancellations.
Cannot tie the Noon bank deposit to any set of invoices because commission and fulfilment fees are netted off before payout. Settlement ingestion posts the fee split to real G/L accounts and proposes matched Incoming Payments, so the deposit clears and commission becomes a reportable cost line.
Is asked to make the marketplace work but does not want an unsupported script writing directly to B1 tables. Everything posts through the Service Layer and DI API with UDO-based objects, logging and approval-procedure integration, so the install stays supportable and upgradeable.
| Critério | ECOSIRE | Construção personalizada | Concorrente |
|---|---|---|---|
| Automated Noon order to Sales Order creation | Incluído | Incluído | Suporte parcial |
| Channel SKU mapping with bundle decomposition | Incluído |
A partir de $799.00
Ponto de partida — orçamentado de acordo com o seu âmbito
| Suporte parcial |
| Scheduled available-to-promise stock push with safety buffer | Incluído | Suporte parcial | Suporte parcial |
|---|
| Settlement statement posting with commission and fee G/L split | Incluído | Suporte parcial | Não incluído |
|---|
| Marketplace-fulfilled consignment stock as a separate B1 Warehouse | Incluído | Suporte parcial | Não incluído |
|---|
| Built on Service Layer and DI API rather than direct table writes | Incluído | Suporte parcial | Suporte parcial |
|---|
| Operator exception queue with retry and reprocessing | Incluído | Não incluído | Suporte parcial |
|---|
| Fixed price agreed before development starts | Incluído | Não incluído | Suporte parcial |
|---|
A build-to-order SAP Business One integration with your 3PL: order release, shipment and tracking confirmation, receipts and stock adjustments posted automatically, built to your provider's spec.
A SAP Business One add-on that syncs Amazon Seller Central orders, FBA inventory, settlements and returns into Sales Orders and A/R Invoices. Built to order for your company database after a scoping call.
A build-to-order B2B portal on top of SAP Business One letting wholesale customers reorder at their own contract pricing, check availability, track Deliveries and download A/R Invoices. Built for your catalogue and pricing after a scoped quotation.
One-click forward and backward genealogy across batches and serials in SAP Business One, with FEFO allocation, expiry control and recall reporting. Built to order for your company database after a scoping call and fixed quote.