Selling through Facebook and Instagram Shops means running a second inventory in Meta Commerce Manager. Your team maintains a product feed in one place and stock levels in ERPNext, and the two drift within days — a variant sells out on the shop floor while Instagram keeps taking checkout orders, or a price change in the Item Price list never reaches the catalog. Orders arrive as CSV exports or manual copy-paste into a Sales Order, so nobody can answer basic questions: which Sales Invoices came from Meta, what did Meta actually pay out last week after commissions and refunds, and does that number tie to the bank statement. ERPNext core has no Meta Graph API integration at all — there is no Commerce Manager catalog sync, no checkout order import, and no payout reconciliation. The e-commerce settings that ship in core are built for a Frappe-hosted webshop, not for a third-party marketplace with its own order lifecycle and settlement schedule.

We build a proper Frappe app — its own module, DocTypes, hooks and scheduler events — installed on your bench alongside erpnext, never as a pile of loose Server Scripts. A Meta Shop Settings single DocType holds the Business Manager ID, Catalog ID, Page/Instagram account mapping, System User access token (stored as a Password field, never in plain text) and the pinned Graph API version. A Meta Catalog Mapping structure links each ERPNext Item and Item Variant to its Meta retailer_id and content ID, so the same item can be published to more than one catalog with different price lists. Catalog pushes run through the Graph API /batch endpoint with idempotent request keys, and every call is written to a Meta Sync Log DocType with the request payload, response, HTTP status and retry count — when Meta rejects an item for a missing GTIN or an image below its minimum resolution, the reason is on the record, not lost in a console.

Sync is event-driven where it should be and scheduled where it must be. hooks.py doc events on Item, Item Price and Website Item enqueue a background job on on_update so a price or content change reaches the catalog in seconds rather than waiting for a nightly run. Stock is the harder half: we subscribe to Stock Ledger Entry and Bin changes and compute available quantity as actual qty less reserved qty for the warehouses you nominate, then debounce and batch so a 400-line Stock Entry produces one availability push rather than 400. Optional soft reservation creates a Meta Stock Reservation record when a checkout order lands, so the same unit is not sold twice across Meta and your other channels. Inbound, we consume Meta's order webhooks through a whitelisted endpoint (@frappe.whitelist(allow_guest=True)) that verifies the X-Hub-Signature-256 HMAC before doing anything, writes a raw Meta Order Event for replay, and then creates the Customer, Sales Order and — on your rules — Sales Invoice and Delivery Note. A reconciling scheduler event re-polls the Orders API on a cron interval to backfill any webhook that never arrived. Fulfilment runs the other way: when a Delivery Note is submitted with a tracking number, a job pushes carrier and tracking back to Meta, with cancellations and refunds mapped to Credit Notes and stock returns. Payout reconciliation pulls Meta's settlement reports into a Meta Payout DocType with line-level commission, tax withheld and refund adjustments, and produces a Journal Entry against your clearing account so the Meta receivable actually clears against the bank.

Everything respects Frappe permissions rather than bypassing them. We ship a Meta Commerce Manager role and role profile, set permlevel on the credential fields so only a System Manager sees tokens, and expose read-only List Views plus a Query Report for order-to-payout tracing that finance can use without touching integration settings. Long-running work goes to the long queue via enqueue, failures raise a proper frappe.log_error plus a notification to a nominated owner, and a scheduled check warns before a System User token expires instead of letting the connector go silently dark. Client Scripts add the practical desk touches — a Publish to Meta button on Item, a Meta order badge on Sales Order, and a mapping-health indicator so you can see at a glance which items Meta has rejected. The app targets Frappe/ERPNext v15 and v16, pins the Graph API version explicitly, and is written to survive a bench update without patching core.

This is build-to-order, not a marketplace download. You request a quotation, we run a short scoping call to confirm your catalog structure, warehouse and price list rules, order-to-invoice policy and payout treatment, and then we quote fixed scope. Typical delivery is one working week from confirmed scope, depending on how many catalogs, currencies and warehouses are in play. We build against your ERPNext version, deploy to a staging bench for UAT against your Meta sandbox or a low-volume live catalog, and only then go to production behind a documented rollback. You receive the full source in a git repository you own, installation and configuration on your bench, technical and user documentation, a training session, and a post-go-live support window for defects.