Selling DIY, garden and home-improvement goods on ManoMano means running a second order book. Orders arrive in the ManoMano seller back office, stock is decremented in a spreadsheet or by hand, and someone re-keys each line into Dynamics 365 Business Central so that inventory, VAT and the general ledger eventually agree. Business Central is excellent at what happens after an order exists — reservations, warehouse shipments, posted sales invoices, item ledger entries — but it has no native concept of a marketplace offer, a marketplace order status, or a marketplace commission deducted before payout. Out of the box there is no ManoMano authentication, no offer feed, no shipment push-back, and no way to reconcile a settlement statement against posted documents. Oversell, late dispatch confirmations and unexplained payout gaps follow.

ECOSIRE builds a dedicated AL extension for your Business Central tenant that closes that gap. The extension ships as a per-tenant extension for SaaS (or a compiled .app deployed to your on-premises service tier) and follows standard Business Central patterns: a ManoMano Setup page holding endpoint, seller account and credential references, setup credentials stored in Isolated Storage rather than plain table fields, table extensions on Sales Header, Sales Line and Item for marketplace identifiers, new tables for offers, mapping and a transaction log, and codeunits invoked by Job Queue Entries so no operator has to remember to press a button. Outbound calls use HttpClient with retry and throttling handling; every request and response is written to a log table you can filter, so a support question is answered from data rather than guesswork.

Functionally, order import polls ManoMano on the schedule you choose, creates Sales Orders (or Sales Invoices, if that suits your flow) against a marketplace customer template, and maps marketplace order states onto a status field you can filter and act on — waiting for acceptance, accepted, shipped, cancelled, refunded. Stock and price synchronisation runs the other way: an event subscriber on item ledger and reservation changes marks affected items dirty, and a queued codeunit pushes available quantity and price for the offers you have flagged, so availability reflects Business Central reality instead of a nightly guess. Product listing export maps Business Central items — with item category, item attributes and unit of measure — onto ManoMano's category and attribute expectations through a mapping table you maintain in the client, not in code. When a Warehouse Shipment or Sales Shipment is posted, the carrier and tracking number are pushed back to ManoMano automatically. Settlement files are imported into a reconciliation worksheet that matches gross sales, commission and other fees to the posted documents and produces balanced General Journal lines for the fee and payout accounts your accountant nominates.

Everything is exposed the way the rest of your platform expects. Dedicated permission sets separate operators from administrators; API pages (REST API v2.0 / OData v4) surface marketplace orders and offer status so Power BI, Power Automate or a Dataverse-connected app can read them without direct SQL; and telemetry events are emitted to your Application Insights resource so failures are visible in the same place as the rest of your Business Central signals. The extension targets current Business Central release waves and is built and tested against the platform and application version your tenant is actually on, with AL test codeunits covering the mapping and reconciliation logic.

This is a build-to-order product, not an AppSource download. We start with a scoping call — your ManoMano seller account setup, catalogue size, which of your Business Central companies are in play, how you want marketplace orders to hit the ledger, and which fee accounts settlements should post to. We come back with a fixed scope, then build against your Business Central version, deliver into a sandbox for UAT, and go live only once you have signed off. Typical delivery is two to four weeks from confirmed scope, depending on catalogue complexity and how much of the settlement reconciliation you want automated. You receive the full AL source for your version, a git repository handover, install and configuration documentation, a user guide, a training session, and a post-go-live support window.