Social Commerce Connector

Key Features

Per-channel `Social Channel` setup table holding credentials, market, currency, posting group defaults and a per-channel stock buffer

Channel SKU to `Item No.` / `Variant Code` mapping with barcode and unit-of-measure translation, including bundle and kit expansion into component lines

Order capture creating real Sales Orders or Sales Invoices — never a parallel shadow table — with `Channel Order No.` and `Channel Order Line Id` on a sales header/line table extension

Custom API pages on the Business Central REST API v2.0 / OData v4 surface, secured with Microsoft Entra ID service-to-service authentication for middleware or Power Automate posting

Idempotent order ingestion keyed on channel order id, so a webhook replay or polling overlap cannot create duplicate sales documents

Availability calculated as on hand less reservations less channel buffer, pushed as delta updates on a job queue schedule with an accelerated live-session cadence

Optional reservation entry creation against the sales line at order capture, so a live drop cannot commit the same stock across two channels

Event subscribers on sales posting, warehouse shipment and item ledger movement that trigger targeted stock re-push instead of full catalog resends

Fulfilment push writing carrier, tracking number and shipped quantity back to the channel from posted sales shipments, handling partial and multi-package shipments line by line

Returns and cancellation handling that creates Sales Return Orders or credit memos linked to the original channel order reference

`Channel Settlement` worksheet importing the channel payout statement and matching lines to orders, splitting commission, shipping subsidy, refunds and adjustment fees to nominated G/L accounts and dimensions

Reconciliation exception list for unmatched settlement lines, with drill-down to the order and no silent posting of differences

Dedicated permission sets, one job queue entry per background task, and Application Insights telemetry with retry and dead-letter handling for channel API failures

Optional Dataverse / Power Platform surfacing for live-session dashboards, approvals or channel-team screens outside Business Central

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 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 2-4 weeks 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.

What you get

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

Installation, deployment and configuration on your sandbox and production environments, including permission sets and job queue entries

Technical documentation: object ranges, table and page extension model, integration and authentication design, API contracts, error and retry behaviour

End-user guide plus a live training session for order desk, warehouse and finance users

UAT run on a sandbox copy of your environment against real order and settlement shapes, with a documented rollback plan

Post-go-live support window for defect fixes and configuration adjustments on the delivered scope

Git repository handover with full commit history and build pipeline notes, so you or another partner can maintain it

Channel onboarding checklist covering API access, credentials, webhook endpoints and settlement statement formats

Who this is for

E-commerce / Channel Manager

Runs the social storefronts and live sessions, and finds out first when an oversell turns into a refund and a channel penalty. Needs channel stock to reflect the real warehouse position within minutes, and orders in Business Central without anyone re-keying them.

Finance Manager or Controller

Receives a single net payout that already had commission, shipping subsidy and refunds deducted, and has to explain it against posted revenue. Needs settlement lines matched to orders, fees posted to the right accounts and dimensions, and a visible exceptions list rather than a plug entry.

Operations / Warehouse Lead

Ships what the channel sold, under channel SLA clocks. Needs orders to arrive as normal sales documents flowing through existing warehouse shipment processes, and tracking numbers to go back to the channel automatically when the shipment posts.

IT Manager or Business Central Partner

Owns the environment and the upgrade path. Needs an extension with clean object ranges, no base-app modification, documented API surface and permission sets, telemetry they can monitor, and source code they can maintain after handover.

How Social Commerce Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	Dynamics 365 Business Central Native
Fit to your channels and posting rules	Built against your channels, item structure, dimensions and posting policy after scoping	Fully bespoke, but you carry the design decisions and the discovery time	Fixed feature set; your process bends to the app's assumptions	No concept of a social channel as an order source
Order capture into Business Central	Real Sales Orders/Invoices with channel order id on a table extension, idempotent ingestion	Achievable, but duplicate handling is the step most in-house builds skip	Usually solid for standard orders; bundles and live-session refs often unsupported	Manual entry or a CSV import with no channel reference
Stock reservation during live drops	On hand less reservations less per-channel buffer, delta push with live-session cadence, optional reservation entries	Possible, but reservation logic against sales lines is genuinely hard to get right	Typically a scheduled full-quantity push; buffers and reservations rare	Inventory is accurate internally but never reaches the channel
Fulfilment and tracking push	Carrier, tracking and quantity pushed from posted shipments; partial and multi-package handled	Straightforward for the simple case; partial shipments add real effort	Common for whole-order shipments; partials often push incorrectly	Tracking is re-keyed into the channel seller centre by hand
Payout and settlement reconciliation	Settlement worksheet matching lines to orders, fees split to your G/L accounts and dimensions, exceptions listed	Rarely built — the piece most in-house projects run out of budget before reaching	Often a summary import; fee breakdown and dimensions usually generic	Net deposit posted manually with a balancing entry nobody can explain
Upgrade and release-wave safety	Extension-only, reserved object range, documented subscribers, compatibility check each wave	Depends entirely on the discipline of whoever wrote it	Vendor-maintained, but you wait on their timeline for a fix	Nothing to break, because nothing is integrated
Source code and ownership	Full AL source plus git repository handed over at delivery	You own it, and you own every future fix as well	Compiled app; source is not yours and behaviour cannot be changed	Not applicable
Ongoing channel API changes	Handled under an optional ongoing arrangement, quoted separately and stated up front	Falls to your internal team each time a platform deprecates a version	Vendor absorbs it, bundled into the subscription	No exposure, and no integration either

Frequently Asked Questions about Social Commerce Connector

How long does delivery take?

This is a build-to-order extension, so nothing is downloaded and installed on day one. After a scoping call we confirm channels, mappings and settlement rules and issue a fixed scope and quote. Typical delivery is 2-4 weeks from confirmed scope, including sandbox build and UAT. More channels, unusual settlement statements or heavy bundle/kit logic move it toward the upper end, and we tell you which before you commit.

What support and updates do I get after go-live?

Delivery includes a post-go-live support window for defect fixes and configuration adjustments within the agreed scope. Because you receive the full AL source and the git repository, you or your existing partner can maintain it afterwards. We also offer an ongoing arrangement covering Business Central release-wave compatibility checks and channel API changes — social platforms deprecate API versions on their own schedule, and that work is quoted separately rather than assumed.

Which Business Central versions and deployments does it support?

We build against your version. The extension targets current Business Central release waves on SaaS (online) and supports on-premises where your environment allows outbound calls, either directly or through a middleware layer. We confirm your exact version, localisation and existing extensions during scoping, so object ranges and event subscribers do not collide with what you already run.

Which social channels can you connect?

Any social storefront or live commerce platform that exposes a documented order, inventory and fulfilment API and grants your account access to it. Channel API access is issued by the platform, not by us, so during scoping we confirm your eligibility and programme tier before quoting. Where a channel has no usable API, we can build a supervised file or middleware-based lane instead — and we will say so up front rather than promising a live sync we cannot deliver.

Will it stop overselling during a live session?

It reduces oversell risk substantially but cannot eliminate it, and we would rather be straight about why. Stock is pushed as deltas on a schedule you control, with a faster cadence during a live-session window, and incoming orders can create reservation entries so the same stock is not committed twice inside Business Central. The residual risk is the seconds between a channel checkout and its webhook arriving — no integration removes that. We handle it with per-channel buffers and a clear exceptions path for the orders that land short.

Does it modify the base application or interfere with upgrades?

No. It is an AL extension using table and page extensions, codeunits and event subscribers within a reserved object range, with no base-app modification — that is what keeps it upgrade-safe across Business Central release waves. We still recommend a compatibility check each major wave, and the documentation lists every event subscriber and API dependency so that check is quick.

Can we get it as an AppSource app instead of a per-tenant extension?

Yes. Most customers take it as a per-tenant extension because it is tailored to their mappings and posting rules. If you need it packaged for the AppSource track — for example to deploy across multiple tenants in a group — we build to those technical requirements instead. That choice affects design and timeline, so we settle it during scoping.