Selling through social storefronts and live shopping breaks the moment volume arrives. A live session sells 400 units in nine minutes, the channel seller centre says one thing, the warehouse says another, and someone is pasting order lines into Business Central by hand at midnight. Oversells become refunds, refunds become channel penalties, and finance ends the month with a payout deposit that matches no invoice in the ledger. Business Central out of the box has no concept of a social shop: there is no channel order source, no reservation against a live drop, nowhere to hold a channel order id, and no reconciliation for a net payout that already had commission, shipping subsidy and returns deducted before the money landed.

We build a per-tenant AL extension (or an AppSource-track app where you want it packaged that way) that makes each social channel a first-class order source inside Business Central. A Social Channel setup table holds credentials, market, currency and posting defaults per shop; item and variant mapping tables bind channel SKUs to your Item No. and Variant Code, with barcode and unit-of-measure translation. Codeunits poll or receive channel order webhooks, and each order is created as a real Sales Order or Sales Invoice with a table extension carrying Channel Order No., Channel Order Line Id, buyer handle, live-session reference and the payment status the channel reported. Inbound calls arrive through custom API pages built on the Business Central REST API v2.0 surface (OData v4), authenticated with Microsoft Entra ID service-to-service tokens, so a middleware layer, Power Automate flow or Logic App can post orders without a user session.

Stock is the part most integrations get wrong, so we treat it as the core. Available quantity is calculated from your real inventory position — on hand less reservations, less an optional buffer per channel — and pushed back to the shop on a job queue cadence you control, with a faster push during a live-session window. Incoming orders can create reservation entries against the sales line so a drop cannot oversell the same lot to two channels, and event subscribers on posting and warehouse activity trigger a delta push rather than a full catalog resend. Fulfilment goes the other way: when a warehouse shipment or posted sales shipment is created, a codeunit pushes carrier, tracking number and shipped quantity back to the channel, marking partial shipments line by line.

Payouts land in a Channel Settlement worksheet that imports the channel statement, matches each settlement line to its order, splits gross revenue, commission, shipping subsidy, refunds and adjustment fees into the G/L accounts and dimensions you nominate, and produces a posting that reconciles to the bank deposit — with an exceptions list for anything that does not match, rather than a silent write-off. Everything runs under dedicated permission sets, with a job queue entry per task, telemetry to Application Insights, and retry plus dead-letter handling for channel API failures. Dataverse and Power Platform connectivity is available where you want dashboards or approvals outside Business Central.

This is build-to-order, not a shelf download. Nothing is installed until you request a quotation and we agree scope, so what you receive is written against your Business Central version and release wave, your channels, your item and dimension structure and your posting policy — not a lowest-common-denominator app that assumes everyone sells the same way. We start with a short scoping call, confirm which channels and which of their API programmes you have access to (channel API access is granted by the platform, not by us — we confirm eligibility before quoting), then produce a fixed scope and quote. Typical delivery is one working week from confirmed scope, depending on channel count and settlement complexity. We build on a sandbox copy of your environment, run UAT with your team against real order shapes, and go live with a rollback plan. You receive the full AL source, a git repository, technical and user documentation, a training session and a post-go-live support window.