Social Commerce Connector

Key Features

Dedicated Frappe app with its own module, fixtures and versioned releases — installed via `bench get-app` / `bench install-app`, not Server Scripts pasted into a live site

`Social Channel` DocType holding per-storefront credentials, API base URL, region, default Company, Warehouse, Price List and Sales Taxes and Charges Template

`Social Channel Item` mapping platform SKU and variant id to an ERPNext Item Code with UOM conversion, so platform bundles resolve to your stock UOM

Dual ingestion: a whitelisted `allow_guest` webhook endpoint with signature verification, plus a `scheduler_events` polling job on a configurable cron as a safety net

Idempotent order capture keyed on the platform order id — a replayed webhook updates the existing `Social Order` instead of creating a duplicate Sales Order

Automatic Sales Order creation with channel customer resolution, shipping charge line, tax template application and the platform order reference retained for audit

Stock reservation at capture time against the channel warehouse, so a live session cannot oversell physical stock before pickers ever see it

Availability push back to the social catalog from ERPNext `Bin` actual and reserved quantity on a scheduled job, closing listings without manual edits

`doc_events` hook on Delivery Note `on_submit` enqueuing a background job that pushes carrier, tracking number and shipped status to the seller API

Return and cancellation handling that pulls platform-side cancellations into draft Sales Returns or Credit Notes for accounts review rather than posting silently

`Social Payout` reconciliation exploding a netted settlement into gross sales, commission, transaction fees, shipping subsidy and campaign deductions, matched to Sales Invoices

Automatic Journal Entry or Payment Entry generation for settled payouts, each fee type posted to a nominated expense account, unmatched lines routed to an exceptions report

Role Profiles and permission rules so channel operators manage orders and sync state without access to the General Ledger or Item valuation fields

Client Script on Sales Order surfacing platform order id, channel and sync status with a manual re-sync action; failures logged to Error Log and retried through the Frappe background queue

Whitelisted REST methods documented for your own downstream integrations, built and tested against Frappe/ERPNext v15 and v16

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 ERPNext.

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 commerce creates orders faster than a spreadsheet can absorb them. A live session sells 300 units in twenty minutes, the seller centre shows them as paid, and your warehouse team is copying names into a picking list while ERPNext still believes the stock is available. Oversells get discovered at packing, refunds get processed by hand, and the payout that lands two weeks later bundles gross sales, platform commission, shipping subsidies, and campaign fees into one number nobody can tie back to a Sales Invoice. ERPNext core has excellent order-to-cash and stock ledgers, but it ships no connector for social selling channels: there is no DocType that knows what a social shop item is, no scheduler job polling a seller API, and no reconciliation model for a netted marketplace payout. Teams end up running the real business in the seller centre and using ERPNext as an after-the-fact bookkeeping copy.

ECOSIRE builds a proper Frappe app for this — a versioned application installed on your bench with its own module, not a pile of Server Scripts glued onto standard DocTypes. The app introduces channel DocTypes: Social Channel holding credentials and endpoint configuration, Social Channel Item mapping a platform SKU and variant to an ERPNext Item and UOM, Social Order as the immutable inbound record, and Social Payout for settlement lines. Ingestion runs two ways: a whitelisted REST endpoint receives platform webhooks where the channel supports them, and scheduler_events in hooks.py run a polling job on a configurable cron so nothing is lost when a webhook is dropped. Every inbound order is written idempotently against the platform order id, so a replayed webhook updates rather than duplicates.

On ingestion the app maps the payload to a real ERPNext Sales Order against the channel's customer or a per-buyer Customer, applying the mapped Item, UOM conversion, channel-specific Price List, taxes template, and shipping charge line. Stock is protected at capture time rather than at delivery: the app raises a reservation against the channel warehouse and, on the reverse leg, pushes available quantity from Bin back to the platform catalog so listings go out of stock before you oversell. Fulfilment is bidirectional — a doc_events hook on Delivery Note on_submit queues a background job that pushes carrier and tracking number back to the seller API and advances the platform order status, with the raw response and any error stored on the Social Order for audit. Cancellations and returns pull the other way, creating draft Sales Returns or Credit Notes for your accounts team to review.

Payout reconciliation is the part most integrations skip. The app pulls settlement statements, explodes each netted transfer into its component lines (gross order value, platform commission, transaction fee, shipping subsidy, campaign or affiliate deduction, adjustments), matches them to the originating Sales Invoices, and produces a Journal Entry or Payment Entry with each fee type posted to the expense account you nominate. Anything that does not match lands on an exceptions report instead of silently balancing. Around all of this we ship Role Profiles and permission rules so a channel operator can work orders without touching your GL, client scripts that surface the platform order and its sync state directly on the Sales Order form, and a retry-and-alert path for API failures using Frappe's background queue and Error Log.

This is a build-to-order engagement, not an instant download. We start with a scoping call to confirm which channels and regions you sell in, your ERPNext version (v15 or v16), your warehouse and accounting structure, and exactly which platform APIs and credentials you hold. You get a fixed written scope before any code is written. Typical delivery is 2-4 weeks from confirmed scope, depending on channel count and reconciliation complexity. We build against your version, deploy to a staging site for UAT with your own catalog and a real test order, then go live with a documented rollback plan. Source code is handed over in your own git repository, so you are never locked to us.

What you get

Installable Frappe app source built for your exact ERPNext version (v15 or v16), delivered as a bench-installable app

Installation and configuration on your site: channel credentials, item mapping, warehouse wiring and accounting setup

Technical documentation covering DocTypes, hooks and scheduler events, whitelisted API methods and field mappings

User guide plus a live training session for your channel operations and accounts teams

UAT on a staging site with your own catalog and real test orders, plus a written go-live and rollback plan

Post-go-live support window for defect fixes and configuration adjustments after cutover

Handover of the full git repository so you own and can extend the code independently

Item and channel mapping workbook prepared with your team so day-one sync runs against real SKUs

Who this is for

Social commerce / channel manager

Runs the live sessions and social storefronts and is judged on oversell rate and on-time dispatch. Needs orders to appear in ERPNext within seconds of purchase, stock reserved at capture, and listings to close automatically instead of after an angry customer message.

Operations and warehouse lead

Picks, packs and ships whatever the channel sells. Needs one queue inside ERPNext instead of exporting CSVs from a seller centre, and needs the tracking number to reach the platform automatically when the Delivery Note is submitted.

Finance manager or controller

Has to explain why the bank received a netted payout that matches no invoice. Needs each settlement exploded into commission, transaction fees and subsidies, posted to the right expense accounts, with unmatched lines visible on an exceptions report rather than plugged.

IT lead or ERPNext system owner

Owns the bench and the upgrade path. Needs a properly versioned Frappe app with documented hooks and DocTypes, source in their own git repository, and no undocumented Server Scripts sitting in production.

How Social Commerce Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Fit to your channels and accounting	Built to your confirmed scope — your channels, warehouses, tax templates and expense accounts	Fully bespoke, but you write the spec and absorb the discovery cost	Fits whatever the vendor's average customer needed	No social channel concept exists in ERPNext core
Order capture	Webhook plus scheduled polling, idempotent on platform order id, into a real Sales Order	Depends entirely on the developer you hire	Usually polling only; duplicate handling varies	Manual entry or CSV import after the fact
Stock protection during live sales	Reservation at capture, and availability pushed back to the catalog from Bin	Achievable, but this is the part DIY builds usually postpone	Often one-way stock sync on a fixed interval	Stock moves on Delivery Note — too late for a live session
Fulfilment and tracking	Delivery Note on_submit hook queues a tracking push, with the API response retained for audit	Possible, but usually built without retry or audit trail	Tracking push common; error visibility often poor	Tracking re-keyed into the seller centre by hand
Payout reconciliation	Settlements exploded into fee lines, matched to invoices, posted to the GL, exceptions reported	Frequently descoped as too complex once the budget is set	Typically a payout report only, with no GL posting	Finance reconciles the netted transfer manually in a spreadsheet
Code ownership	Git repository handed to you; extend it with any Frappe developer	You own it, and you also own every future fix	Vendor-controlled release cycle and roadmap	Nothing to own — the capability is not there
Upgrade path to v15 / v16	Built and tested on your version, with upgrade support available	Upgrade regressions are your team's problem	Depends on whether the vendor still maintains the app	Core upgrades cleanly, but the gap remains after every upgrade
Time and effort to live	2-4 weeks from confirmed scope, including staging UAT and a rollback plan	Months of discovery, build and rework in most cases	Installs in a day, then weeks of workarounds for what it does not do	Live immediately, with the manual process unchanged

Frequently Asked Questions about Social Commerce Connector

How long does delivery take?

This is a build-to-order app, not an existing marketplace download, so nothing ships instantly. Typical delivery is 2-4 weeks from confirmed scope. The clock starts when the written scope is agreed, not at first enquiry — channel count, how many platform APIs are involved, and how complex your payout reconciliation is are what move the number within that range. We confirm a date for your specific build on the scoping call.

What happens after go-live — support and updates?

Every engagement includes a post-go-live support window for defect fixes and configuration adjustments on the scope we delivered. Beyond that, ongoing support and version maintenance are available as a separate agreement covering platform API changes, ERPNext version upgrades and additional channels. Because you receive the git repository, you can also maintain it in-house or with any Frappe developer — there is no licence lock.

Which ERPNext versions do you support?

We build against Frappe and ERPNext v15 and v16, targeting the exact version and patch line running on your site, confirmed during scoping. If you are mid-upgrade we can build against your target version and stage the deployment to follow your upgrade window.

Do you need API credentials for my social storefront?

Yes — the connector talks to the platform's official seller API, so it needs credentials or an app registration on your account. We use staging or sandbox credentials for development wherever the platform offers them, and production credentials are entered by your team into the `Social Channel` DocType on your own site. We do not need to retain them.

How is this different from exporting orders and importing them into ERPNext?

An import is a snapshot after the fact. The connector reserves stock at the moment of capture so a live session cannot oversell, pushes availability back so listings close themselves, pushes tracking numbers out automatically on Delivery Note submission, and reconciles a netted payout down to individual invoices. None of that is reachable through a periodic CSV import.

Can it handle multiple storefronts, regions or companies?

Yes. Each storefront is its own `Social Channel` record with its own credentials, Company, warehouse, Price List and tax template, so multi-region and multi-entity setups map cleanly onto ERPNext's existing multi-company structures. The number of channels in day-one scope is agreed on the scoping call because it affects the delivery estimate.

What if the platform changes its API after we go live?

Platform APIs do change. The connector isolates each channel behind an adapter layer so a breaking change is contained rather than requiring a rewrite, and API failures are logged to Error Log with retries through the Frappe background queue instead of silently dropping orders. Keeping adapters current against platform releases is what an ongoing support agreement covers.