ERPNext TikTok Shop Connector

Key Features

Inbound TikTok Shop order sync mapped to native ERPNext `Sales Order`, `Customer`, and `Item` records with automatic `Payment Entry` creation

Two-way inventory sync between ERPNext `Bin` quantities and TikTok listings, driven by `scheduler_events` in `hooks.py`

Two-way price sync with per-listing SKU mapping so ERPNext item prices and TikTok prices stay reconciled

FBT (Fulfilled by TikTok) order recognition routed to a dedicated warehouse so TikTok-fulfilled stock never depletes seller-fulfilled inventory

Shipping label and tracking-number writeback to TikTok on `Delivery Note` submit via a `doc_events` hook

Creator and affiliate attribution captured per order and stored on the sales document for commission reporting inside ERPNext

Multi-region support (US / UK / SEA) with per-region credential sets, currency, and tax mapping

`TikTok Shop Settings` single DocType holding encrypted API credentials, poll cadence, and region configuration

Whitelisted (`@frappe.whitelist()`) webhook receiver and manual re-sync endpoints callable from the ERPNext UI

Idempotency guards and de-duplication so retried webhooks and re-polls never double-book orders or stock

`TikTok Shop Sync Log` DocType recording every API call, payload, and error for full auditability and replay

Automatic retry with backoff and a dead-letter queue for failed API calls, surfaced as ERPNext notifications

Permissions and role-profile enforcement so only authorized users can edit credentials or trigger a full re-sync

Configurable order/state mapping (TikTok order statuses to ERPNext document workflow) tuned to your process

Built and tested against ERPNext / Frappe v15 and v16 with a clean, upgrade-safe app structure

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

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

What you get

Installable source code for your version of the connector as a proper Frappe app (DocTypes, hooks, server + client scripts)

Installation and configuration on your bench, including `TikTok Shop Settings`, API credentials, and scheduler wiring

Technical documentation covering architecture, DocTypes, API mappings, and scheduler/webhook flow

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

UAT on a staging environment with a documented rollback plan before any production cutover

Post-go-live support window for bug fixes and configuration adjustments

Git repository handover with full commit history so you own and can extend the code

Sync monitoring and troubleshooting runbook (reading the `TikTok Shop Sync Log`, replaying failed calls)

Who this is for

Social-commerce brand owner scaling on TikTok Shop

Runs a fast-growing TikTok Shop and already uses ERPNext for stock and accounting. Needs orders and inventory to sync automatically so a viral video doesn't cause oversells or hours of manual data entry.

Operations / fulfillment manager

Owns picking, packing, and shipping. Needs FBT and seller-fulfilled orders cleanly separated, and shipping labels plus tracking pushed back to TikTok on `Delivery Note` submit without leaving ERPNext.

Multi-region ecommerce operator

Sells across US, UK, and SEA TikTok Shops. Needs per-region credentials, currency, and tax handling consolidated into one ERPNext backend rather than juggling separate Seller Center logins and spreadsheets.

Finance / affiliate manager

Tracks revenue, reconciliation, and creator commissions. Needs creator/affiliate attribution stored against each sales document so payouts and margin can be reported directly inside ERPNext.

How ERPNext TikTok Shop Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
TikTok Shop order sync	Native mapping to `Sales Order`, `Customer`, `Payment Entry` with idempotency	Possible but you build and maintain the API integration yourself	Often generic; may not map to native ERPNext docs cleanly	No TikTok Shop concept — orders re-keyed by hand
Two-way inventory & price sync	Scheduler-driven `Bin`-to-listing sync both directions with SKU mapping	Requires designing sync cadence and conflict handling from scratch	Frequently one-way or push-only, limited SKU mapping	None — stock managed separately in each system
FBT (Fulfilled by TikTok) support	FBT orders recognized and routed to a dedicated warehouse	Must be specified and coded specifically	Rarely handled; FBT stock often mixed with seller stock	Not supported
Label & tracking writeback	Auto writeback to TikTok on `Delivery Note` submit via `doc_events`	Buildable with effort on the hooks layer	Sometimes manual or unsupported	Manual entry in Seller Center
Multi-region (US/UK/SEA)	Per-region credentials, currency, and tax mapping in one backend	Each region added by more development	Often single-region or single-currency	Separate logins, no consolidation
Creator/affiliate attribution	Stored on sales documents for native commission reporting	Extra data model and reporting to build	Usually not captured	Not available
Fit to your operation	Scoped build-to-order to your SKUs, regions, and fulfillment model	Fully custom but you own all design and delivery risk	Take-it-as-is; adapt your process to the app	Manual workarounds only
Support & ownership	Post-go-live support window plus full git repo handover	Depends entirely on your in-house team	Vendor-dependent; limited access to source	No connector to support

Frequently Asked Questions about ERPNext TikTok Shop Connector

Is this a ready-made app I can download and install today?

No. This is build-to-order. ECOSIRE builds the connector as a Frappe app scoped to your TikTok Shop setup, then installs and configures it on your bench. There is no instant download — the deliverable is a connector tailored to your regions, SKUs, and fulfillment model.

How long does delivery take?

Typically 2 to 4 weeks from confirmed scope. The timeline depends on how many regions you sell in, whether you use FBT, seller-fulfilled, or both, and the complexity of your SKU and tax mapping. We agree the scope and timeline in writing before development starts.

Which ERPNext versions are supported?

We build and test against ERPNext / Frappe v15 and v16. If you are on an older version, we will flag it during the scoping call and recommend an upgrade path, since the connector relies on current scheduler, hooks, and whitelisted-method behavior.

How do you handle updates and support after go-live?

Every engagement includes a post-go-live support window for bug fixes and configuration adjustments. Because you receive the full git repository, your team can extend the code independently, and ECOSIRE offers ongoing support and maintenance if TikTok's API changes or your needs grow.

Does it prevent overselling when a product goes viral?

Yes. Inventory syncs two-way on a scheduler between ERPNext `Bin` quantities and your TikTok listings, and inbound orders use idempotency guards so a retried webhook never double-books stock. FBT stock is routed to a separate warehouse so it doesn't deplete your seller-fulfilled inventory.

How are creator and affiliate sales tracked?

Creator and affiliate attribution from each TikTok order is stored against the corresponding ERPNext sales document. That lets you report commission and channel attribution natively in ERPNext instead of exporting from the Seller Center and reconciling by hand.

Is my data and API access secure?

Credentials live in a `TikTok Shop Settings` DocType with ERPNext-level encryption, and access is gated by role profiles and permissions so only authorized users can edit them or trigger a full re-sync. Webhook and re-sync endpoints are whitelisted methods with validation, and every call is recorded in a sync log for audit.