Selling on Target Plus while running Dynamics 365 Business Central usually means two systems that never agree. Orders are keyed by hand or pasted from a CSV export, so Business Central sees them hours late and the reservation engine allocates stock the marketplace has already promised. Available inventory drifts between the Target Plus listing and the item ledger, which produces the two outcomes every seller wants to avoid: overselling and a cancellation defect rate, or a padded safety buffer that hides sellable stock. At month end, finance receives a settlement statement full of commissions, referral fees, returns and adjustments, reconciled against a bank deposit that matches no single sales order. Business Central out of the box has no notion of a marketplace channel at all — no order source, no marketplace fee handling, no listing state, and nowhere to store a Target Plus order ID against a sales header.

We build a dedicated AL extension for Business Central that owns this integration end to end. A Target Plus Setup page holds credentials, environment (sandbox or production), API base URL, retry and page-size settings, and the number series, locations, customer template and posting groups the connector uses. Order polling runs from a job queue entry on your chosen cadence; each marketplace order is staged in a connector table first, then converted to a Sales Order by a codeunit, so a downstream failure never leaves a half-written document. Marketplace order states map to Business Central document states through a configurable mapping table rather than hard-coded case statements, so a new Target Plus status is a data change, not a code change. Table extensions add Target Plus order ID, listing ID, marketplace status, fee amounts and settlement reference to the sales header, sales line, item and posted sales documents; page extensions surface them where your team already works — the Sales Order card, the Item card and the Posted Sales Invoice.

Inventory and price synchronisation runs the other way. Event subscribers on item ledger and reservation entry changes mark affected items dirty, and a batched, rate-limit-aware job queue codeunit pushes availability and price to Target Plus. You publish a calculated figure — inventory at nominated locations, minus open reservations, minus a configurable safety buffer — rather than a raw quantity on hand. Listing export maps Business Central items, variants, item attributes and item categories onto Target Plus categories and attribute schemas through a mapping table you maintain, with validation before submission so rejected listings are caught inside Business Central. Warehouse shipment and posted sales shipment triggers push carrier, tracking number and package detail back to the marketplace. Settlement files are parsed into commission, referral fee, refund and adjustment lines that post to the general journal against the accounts and dimensions you nominate, so a marketplace deposit reconciles to a bank ledger entry with a documented trail.

Everything is built to current Business Central practice: API pages exposing connector entities over REST API v2.0 and OData v4 for Power BI, Power Automate and Dataverse-connected flows; dedicated permission sets so warehouse, customer service and finance see only what they should; telemetry emitted to Application Insights via Session.LogMessage on every outbound call and failure; and a retry, backoff and dead-letter table so a Target Plus outage never silently drops an order. We deliver as a per-tenant extension for Business Central online, or as a deployed package for on-premises and hosted container environments, targeting your current release wave with an upgrade codeunit path so the extension survives Microsoft's twice-yearly updates.

This is build-to-order, not an AppSource download. After you request a quotation we run a scoping call to confirm your Target Plus seller account setup, Business Central version and localisation, locations, posting groups and the settlement treatment your accountant wants. We then write the extension, test it against your sandbox, and hand over the source, the app package and the documentation. Typical delivery is two to four weeks from confirmed scope — longer only where you need unusual settlement handling, multi-entity consolidation or a complex kit and bundle model, and we tell you that before you commit. You receive UAT on a staging environment, a signed-off test script, a rollback plan and a post-go-live support window before anything touches your production tenant.