Selling through Meta storefronts creates a control problem that Dynamics 365 Business Central was never shipped to solve. Your product data lives in Item, Item Variant, Item Attribute Value and your item pictures, but Meta wants a feed with its own retailer IDs, availability states, condition codes and image URLs. Checkout orders land in Commerce Manager, not in your Sales Header. Inventory is committed in Business Central through item ledger entries and reservation entries, while Meta only knows the last quantity you told it. The result is the familiar pattern: someone exports a spreadsheet every morning, someone else retypes orders, and the first oversell happens on the first campaign that actually works. Business Central has no native Facebook or Instagram Shops integration, no Commerce Platform (Graph API) client, and nowhere to store a Meta catalog ID against an item — so the road ends before the first sync.

We build a Business Central AL extension that closes that gap inside the system where your stock and financials already live. Item and variant records gain table and page extensions carrying the Meta retailer ID, catalog assignment, product set membership and last-sync state, so the mapping is a first-class field on the card rather than a spreadsheet column. A catalog codeunit projects your items into Meta's product schema — title, description, price, sale price, currency, availability, condition, brand, GTIN, image URLs — and pushes them through the Graph API in batches, honouring Meta's batch limits and rate-limit headers with retry and backoff. Orders flow the other way: a poller, or a webhook receiver exposed through a Business Central API page, pulls checkout orders, resolves the buyer to a Customer under your chosen strategy, maps line items back to items and variants by retailer ID, and creates a Sales Order carrying the Meta order ID, buyer note, shipping option and tax breakdown. Because the order is a real Business Central document, your existing posting setup, dimensions, VAT posting groups, item tracking and warehouse flow all apply unchanged.

Stock accuracy is handled as a continuous concern rather than a nightly overwrite. The extension subscribes to standard Business Central events on item ledger and reservation activity, computes available-to-promise from your chosen source — plain inventory, ATP, or a buffered quantity per location — and pushes deltas to Meta, so a campaign spike does not sell inventory you have already committed to a wholesale order. Optional soft reservation holds quantity against imported Meta orders until they ship. Fulfilment runs the same way in reverse: when a warehouse shipment or sales shipment is posted, a codeunit pushes the fulfilment with carrier, tracking number and tracking URL back to Meta, so the buyer sees a real shipping notification and the order closes on Meta's side. Payout reconciliation imports Meta's payout and settlement records and stages them against your bank account with line-level fees and refunds, so the deposit that hits the bank ties out to orders instead of being posted as a lump journal line.

Everything runs on Business Central's own scheduling and security model. Sync operations are Job Queue Entry records with independent cadence per operation, full run logging, per-record error capture and safe re-run, so one bad image URL does not stop the catalog push. Credentials are held in isolated storage, never in a plain setup field. A dedicated permission set separates who may configure the connection from who may view sync logs or force a resync. On Business Central SaaS the extension is delivered as a per-tenant extension, or prepared for AppSource submission under your own publisher account if you prefer; on-premises deployments are supported on current release waves from the same codebase, with an upgrade codeunit for schema changes. Where you already use Power Platform, the sync-state and error tables are exposed through API pages (REST API v2.0 / OData v4) so Power BI, Power Automate and Dataverse read the same state your users see.

This is a build-to-order product, not a Microsoft AppSource download you install today. We start with a short scoping call, confirm your Business Central version and deployment type, your Meta catalog and Commerce Manager setup, your variant and pricing model, and the fulfilment and payout flow you actually run. From confirmed scope, typical delivery is two to four weeks. You get the installable source code for your version, installation and configuration on your environment, technical and user documentation, a training session, UAT on a sandbox with a documented rollback plan, and a post-go-live support window. Anything outside the confirmed scope is quoted before it is built — no surprise scope, and no half-finished integration left running in production.