Reverb Marketplace Connector

Key Features

Order import from the Reverb REST API into Business Central sales orders or invoices, with the Reverb order number written to `External Document No.` for one-touch lookup

`Reverb Order` staging table with marketplace status mapping (paid, shipped, refunded, cancelled, disputed) so a malformed payload never posts a half-built document

Buyer-to-customer mapping configurable at scoping: a customer per buyer, or one marketplace customer with per-order ship-to addresses

Outbound stock queue driven by event subscribers on `Item` and `Item Ledger Entry`, drained by a job queue entry on the interval you choose

Location- and variant-aware available quantity calculation, so warehouse-only, reserved or blocked stock is never published to Reverb

Price synchronisation from a nominated Business Central price list or sales price, with an optional marketplace uplift percentage per category

Listing export with Reverb category mapping plus make, model, finish, year and condition attribute mapping held in a dedicated mapping table

Shipment confirmation and tracking push-back via an event subscriber on the posted-shipment codeunit, closing the order on Reverb automatically

Settlement and fee reconciliation: payout, selling fee, payment processing fee, shipping label and refund posted to the G/L accounts you nominate

`Reverb API Log` table recording every request and response with correlation ids, so a failed sync is replayable rather than reconstructed from memory

Rate-limit and retry handling in the `HttpClient` codeunit layer, with exponential backoff and a poison-message threshold that raises a Business Central notification

Dedicated permission sets separating warehouse, accounting and administrator access to setup, credentials and settlement posting

API pages (REST API v2.0 / OData v4) exposing connector order, listing and settlement data for Power BI, Power Automate and Dataverse-connected apps

Multi-company aware setup, so a group running several Reverb seller accounts can map each account to its own Business Central company

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 two to four weeks: 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.

What you get

Installable AL source code built and tested against your Business Central version and release wave (SaaS or on-premises)

Installation and configuration on your sandbox and production environments, including Reverb API credentials, job queue entries and permission set assignment

Technical documentation: object ranges, table and page extensions, codeunit responsibilities, event subscribers and the API contract used

End-user guide covering order import, listing export, stock sync monitoring and settlement reconciliation, plus a live training session for your team

UAT on a staging environment using Reverb sandbox or low-volume live orders, with a documented test script and sign-off checklist

Documented rollback plan and a pre-install environment backup, so an install can be reversed without a support ticket

Post-go-live support window for defect fixes and configuration adjustments after the first live sync cycles

Handover of the private git repository with full source history, so the extension is yours to maintain or extend

Who this is for

Owner-operator of a multi-channel gear shop

Sells vintage and used instruments through Reverb, a physical shop and sometimes other channels, and is currently the person keying Reverb orders into Business Central at night. Needs orders to land as real Business Central documents and stock to stop overselling across channels, without hiring a second admin.

Operations or warehouse manager

Owns pick, pack and dispatch. Needs Reverb orders visible in the normal sales order list with the correct ship-to address, and needs tracking numbers to reach the buyer the moment a shipment is posted rather than after someone re-enters them in the Reverb dashboard.

Finance lead or controller

Closes the month and has to explain why the Reverb payout does not equal the sum of the invoices. Needs selling fees, payment processing fees, shipping labels and refunds posted as identifiable entries against nominated G/L accounts so the bank line reconciles cleanly.

Business Central partner or internal IT lead

Responsible for the tenant, its extensions and the next release wave. Needs a properly built AL extension with permission sets, source code, an object range that will not collide, and a supplier who keeps it compatible when the wave lands.

How Reverb Marketplace Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	Dynamics 365 Business Central Native
Fit to your Reverb selling model	Built to your scoped rules: buyer mapping, publishing locations, fee accounts	Same fit possible, but you specify, build and test everything yourself	Generic mapping; you bend your process to the app's assumptions	No Reverb concept exists in Business Central
Order import	Reverb orders become sales orders with status mapping and a replayable staging table	Achievable, though staging and replay are usually skipped under deadline	Import exists; status coverage and error handling vary by vendor	Manual re-keying from the Reverb seller dashboard
Stock accuracy across channels	Event-driven queue, location and variant aware, job queue interval you set	Depends whether the developer used event subscribers or a nightly batch	Often a fixed scheduled batch on total on-hand, not filtered stock	No outbound sync; overselling is discovered after the fact
Settlement and fee reconciliation	Fee-type-level entries to nominated G/L accounts, reconciling to the payout	Frequently the first scope item dropped when the budget tightens	Usually a summary import; fee splits often stay in a spreadsheet	Spreadsheet reconciliation of the lump-sum payout each period
Delivery time and effort on you	Two to four weeks from confirmed scope; we build, install and train	Hiring or freeing an AL developer, then months of build and rework	Installs in minutes, then weeks of configuration compromise	Live today, at the cost of permanent manual work
Source code and lock-in	Full AL source plus the git repository handed over to you	You own it outright, and you own every future fix	Closed source on a recurring licence; leaving means starting over	Nothing to own
Release-wave compatibility	Built to your current wave, maintained forward under a support agreement	Your team owns regression testing for every wave	Vendor updates on their roadmap, not on your upgrade calendar	Microsoft maintains Business Central, but no Reverb integration exists
Security and access control	Dedicated permission sets separating warehouse, accounting and admin access	Permission sets are often an afterthought in one-off builds	Typically one broad permission set covering the whole app	Standard permission sets only; no marketplace surface to secure

Frequently Asked Questions about Reverb Marketplace Connector

How long does delivery take?

This is a build-to-order extension, so nothing is downloaded and installed the same day. After you request a quotation we run a scoping call — typically 30 minutes — to fix the requirements, then typical delivery is two to four weeks from confirmed scope. That covers development in a sandbox, UAT on your staging environment and the production install. Unusually large attribute mapping sets, multi-company rollouts or heavy customisation of the settlement posting rules can extend that, and we tell you before you commit rather than afterwards.

What happens after go-live, and what about Business Central updates?

A post-go-live support window is included, covering defect fixes and configuration adjustments once real Reverb traffic is flowing. Beyond that we offer an ongoing support and maintenance agreement that keeps the extension compatible with new Business Central release waves and with changes Reverb makes to its API. Because you receive the AL source and the git repository, you are never locked in — your own partner or internal team can maintain it if you prefer.

Is this an AppSource app I can install myself?

No. It is built for your tenant and delivered as a per-tenant extension, or packaged for AppSource where you specifically want that route. That is deliberate: Reverb selling models differ enough — how buyers map to customers, which locations publish stock, which G/L accounts absorb which fee — that a one-size install would force configuration compromises. We build to your setup and hand over the source.

Does it work on Business Central on-premises as well as SaaS?

Yes. The extension is AL and targets current Business Central release waves on both SaaS and on-premises. On SaaS it runs as a per-tenant extension with job queue entries handling the scheduled sync; on-premises it installs the same way against your service tier. We build and test against the exact version you are running, and we confirm that version at scoping.

How does it avoid overselling stock that is already committed elsewhere?

Published quantity is calculated from the locations and item variants you nominate, not from total on-hand. You decide at scoping whether reserved quantities, warehouse-only stock, blocked items or a safety-stock buffer are excluded. Changes are picked up by event subscribers on `Item` and `Item Ledger Entry` and pushed on the job queue interval you choose, so the gap between a shop sale and the Reverb listing update is measured in minutes rather than overnight.

What exactly does the settlement reconciliation post?

The connector imports Reverb payout and fee data and generates entries against the G/L accounts you nominate for each fee type — selling fee, payment processing fee, shipping label, refund — so the lump-sum payout on your bank statement reconciles against a matching set of entries. The account mapping is yours to define at scoping, and we walk your finance lead through a full month-end reconciliation during training.

Can we extend it later, or connect it to Power BI and Power Automate?

Yes to both. The connector exposes its order, listing and settlement data through API pages (REST API v2.0 / OData v4), so Power BI, Power Automate and Dataverse-connected apps can read it without direct table access. And because you hold the AL source and the git repository, adding a channel, a new attribute mapping or a custom posting rule later is a normal development task — by us, your partner, or your own team.