Selling musical gear on Reverb while running Dynamics 365 Business Central usually means two systems of record and a person in the middle. Orders arrive in the Reverb seller dashboard and get keyed into Business Central as sales orders, sometimes hours later. Stock levels drift because the last unit of a vintage pedal sold in the shop but is still listed on Reverb, so you oversell and eat a cancellation against your seller metrics. Reverb payouts land as one lump sum that does not tie to any single sales order, so someone reconciles selling fees, payment processing fees, shipping labels and refunds by hand in a spreadsheet before the bank account can be closed off. Business Central out of the box has no concept of Reverb: no marketplace order source, no listing record, no fee model, and nothing that speaks Reverb's REST API. The Shopify connector Microsoft ships covers Shopify only, and generic e-commerce apps assume a webstore you control, not a marketplace with its own order states, shipping providers and fee schedule.

ECOSIRE builds a Reverb Marketplace Connector as a proper AL extension for your tenant — delivered as a per-tenant extension or, where you want it, packaged for AppSource — not a middleware subscription sitting between you and your data. The extension adds its own setup table and page (Reverb Connector Setup) holding credentials, the base API endpoint, default posting groups, item and shipping mappings, and per-company defaults for a multi-company install. Codeunits handle the HTTP layer against Reverb's REST API using HttpClient with retry and throttling awareness, and every request and response is written to a Reverb API Log table so a failed order import can be replayed rather than guessed at. Order import creates real Business Central sales orders or invoices with the Reverb order number in External Document No., maps the Reverb buyer to a customer (either a per-buyer customer or a single marketplace customer with a ship-to address, your choice at scoping), and maps Reverb order states — paid, shipped, refunded, cancelled — to a status field on a Reverb Order staging table so a bad payload never posts a half-built document.

Stock and price synchronisation runs the other way. Event subscribers on Item Ledger Entry and Item insert and modify events flag changed items into an outbound queue, and a job queue entry drains that queue on the interval you set — near real time where volume allows, batched where Reverb rate limits make that smarter. Available quantity is calculated from the locations and item variants you nominate, so warehouse-only stock or reserved units never get published. Listing export maps Business Central items to Reverb listings with category, make, model, finish, year and condition attribute mapping held in a dedicated mapping table, so your item attributes drive the listing rather than being retyped. When a shipment is posted in Business Central, an event subscriber on the posting codeunit pushes the shipment confirmation and tracking number back to Reverb, which closes the order on the marketplace and starts the buyer's tracking notification without anyone opening a browser tab. Settlement import reads Reverb payout and fee data and generates general journal entries against the accounts you nominate — selling fee, payment processing fee, shipping label, refund — so the payout on your bank statement reconciles to a balancing entry set rather than a spreadsheet.

Everything ships with permission sets so warehouse staff can see marketplace orders without touching setup or credentials, and API pages (REST API v2.0 / OData v4) expose the connector's order, listing and settlement data if you want Power BI, Power Automate or a Dataverse-connected app reading it. The extension is built and tested against your Business Central release wave, on SaaS or on-premises, and we keep the code compatible when you take the next wave.

This is build-to-order, not an AppSource download. You request a quotation, we run a short scoping call, and we write down exactly which Reverb order states you sell under, which locations and variants publish stock, how buyers should map to customers, and which G/L accounts absorb which fee type. From confirmed scope, typical delivery is one working week: we build in a sandbox against a copy of your data, you run UAT on staging with Reverb sandbox or low-volume live orders, and we install into production with a documented rollback plan. You receive the AL source, the git repository, technical documentation, a user guide, a training session and a post-go-live support window.