Social commerce moves fast, and TikTok Shop is where a lot of that demand now lands — often across US, UK, and Southeast Asian storefronts at once. ERPNext gives you a solid backend for inventory, accounting, and fulfillment, but it has no native concept of a TikTok Shop order, a Fulfilled-by-TikTok (FBT) warehouse, or a creator/affiliate attribution. Teams end up re-keying orders from the TikTok Seller Center into Sales Order, missing stock-out risks because inventory lives in two places, and losing the thread on which creator drove which sale. That manual gap gets expensive precisely when a video takes off.

ECOSIRE builds the ERPNext TikTok Shop Connector as a proper Frappe app installed on your bench — not a spreadsheet import or a brittle no-code zap. The app ships its own DocTypes (for example a TikTok Shop Settings single DocType for credentials and region config, TikTok Shop Order staging records, and a TikTok Shop Sync Log for auditability), registers scheduler_events in hooks.py to poll the TikTok Shop Partner API on a cadence you choose, and uses doc_events hooks so that when a Delivery Note is submitted the shipping label and tracking number are written back to TikTok automatically. Whitelisted methods (@frappe.whitelist()) expose secure endpoints for TikTok's webhooks and for manual re-sync from the ERPNext UI, and inbound orders are mapped to native Sales Order, Customer, Item, and Payment Entry records so your accounting and stock ledgers stay correct.

Technically, the connector handles the parts that make TikTok Shop different from a standard store. Inventory and price sync run two-way: your ERPNext Bin quantities push out to TikTok listings on a scheduler, and TikTok inventory adjustments flow back, with SKU mapping and idempotency guards so a retried webhook never double-books stock. FBT (Fulfilled by TikTok) orders are recognized and routed to a dedicated warehouse so TikTok-fulfilled units don't deplete your seller-fulfilled stock. For seller-fulfilled orders, submitting the Delivery Note triggers a label/tracking writeback. Creator and affiliate data captured on each order is stored against the sales document so you can report commission and attribution inside ERPNext. Multi-region shops are handled with per-region credential sets and currency/tax mapping, and everything respects ERPNext role profiles and permissions so only the right users can touch credentials or trigger a full re-sync. Built and tested against ERPNext v15 and v16.

Because this is build-to-order, we start from your actual TikTok Shop setup — which regions, which SKUs, FBT or seller-fulfilled or both, and how you want creators attributed — and scope the app to fit. Typical delivery is one working week from confirmed scope. You get the installable source code for your version, a UAT pass on staging with a rollback plan before anything touches production, a training session, and a post-go-live support window. There is no instant download here: the value is a connector that matches your operation instead of forcing your operation to match a generic template.