TikTok Shop Connector

Selling on TikTok Shop is a volume problem before it is anything else. One livestream or one video that catches can push several hundred orders into the seller centre in an afternoon, each with its own label deadline, and none of them exist in SAP Business One until somebody types them in. Most teams start with a nightly CSV export and a copy-paste routine into Sales Orders. That holds until the first month where returns, affiliate commission and shipping subsidies collide, and the payout lands in the bank as a single lump that reconciles against nothing in the ledger. By then stock in SAP B1 no longer matches what the storefront believes is sellable, oversells turn into cancellations, and cancellations damage the seller score that drives reach. The manual process does not fail loudly. It degrades, and finance absorbs the cost at month end.

This app is built to order. ECOSIRE does not publish a pre-packaged download, there is no trial binary, and the software does not exist until we build it for your tenant. We scope your channel setup, issue a fixed quote, then develop and install against your own company database. Typical lead time is two to four weeks depending on scope.

What ECOSIRE builds

A SAP Business One extension delivered as a companion integration service plus in-client objects. Transactional writes go through the SAP Business One Service Layer (OData/REST) so document creation is validated by the same business logic your users see in the client. Where an operation has no Service Layer equivalent, or where bulk throughput matters, we fall back to the DI API. Configuration, mapping tables and the operations log are implemented as User-Defined Tables and User-Defined Objects so administrators maintain them inside SAP B1 rather than in an external console.

Orders into SAP Business One

Each TikTok Shop order becomes a Sales Order in SAP B1. The platform order identifier is written to a User-Defined Field on the document so every run is idempotent, a replay never duplicates a document, and support can trace a line in the seller centre to a line in ORDR. Order lines carry the channel SKU, the mapped Item Code, quantity, unit price after platform discount, and any seller-funded discount split you nominate. Shipping charged to the buyer posts as a separate freight line or as a service line against a G/L account of your choosing. Orders that fail validation, an unmapped SKU or a Business Partner on credit hold, land in an exception queue with the exact Service Layer error rather than being silently dropped.

Business Partner and address handling

You choose the strategy at scoping time. Either one Business Partner per channel, which keeps OCRD small and treats TikTok Shop as a single marketplace customer, or one Business Partner per buyer, matched on the platform buyer identifier and email so repeat purchasers accumulate history. Ship-to addresses are written as address rows on the Business Partner and referenced from the Sales Order, with masked or tokenised buyer contact data where the platform provides it that way.

Fulfilment, shipping and returns

On pick and pack the connector raises a Delivery from the Sales Order, preserving the base-to-target document trail so nobody loses the audit chain. Tracking number and carrier are written back to TikTok Shop against the order so the fulfilment clock is satisfied. The A/R Invoice is raised from the Delivery on your chosen trigger, either at dispatch or at settlement. Cancellations before dispatch close the Sales Order line. Returns after dispatch raise a Return document and an A/R Credit Memo linked to the invoice, and the stock movement lands in the return warehouse you nominate rather than back into sellable stock by default.

Inventory and price publishing

Available-to-promise is calculated from SAP Business One warehouse stock, In Stock less Committed with an optional Ordered component, per warehouse or per warehouse group. A per-item buffer quantity holds back a floor so a warehouse counting error cannot oversell the channel. Publishing runs on a schedule you set and can additionally be triggered by inventory-affecting documents, so a Goods Receipt PO on a fast mover reaches the storefront in minutes rather than overnight. Price publishing is optional and can be driven from a nominated Price List or from Special Prices.

Settlement, fees and payout reconciliation

This is the part that manual processes never survive. Settlement statements are imported into a User-Defined Table and matched line by line to the corresponding invoices. Commission, affiliate fee, transaction fee, shipping subsidy and platform adjustment are separated and posted as a Journal Entry to the G/L accounts you nominate, so channel cost of sale is visible in your P&L instead of buried in a net figure. The payout itself becomes an Incoming Payment applied against the matched invoices, which means the bank line clears in one reconciliation step instead of a spreadsheet. Statement lines that cannot be matched are held, listed and reportable rather than force-posted.

Who it is for

Companies already running SAP Business One as the system of record that have opened a TikTok Shop and outgrown manual entry. It suits merchants shipping from their own warehouses, brands running affiliate and livestream campaigns whose fee structures need to be visible per order, and finance teams who currently reconcile a monthly payout by hand. It is not aimed at businesses with no ERP, and it is not a storefront builder.

Technical approach and scope boundaries

The connector targets SAP Business One 10.0 on Microsoft SQL Server or SAP HANA, on-premise or hosted, in single or multi-company setups. It requires network access from the integration service to the Service Layer endpoint and to the TikTok Shop API, and a dedicated SAP B1 service user. We do not modify SAP standard tables, we add UDFs, UDTs and UDOs. Approval procedures already configured in your system continue to apply, and we can route credit memos or write-offs above a threshold through them before posting. We do not resell platform API access, we do not act as merchant of record, and we do not make claims about platform certification.

How delivery works

First a scoping call, typically ninety minutes, covering your channel setup, warehouse layout, item master conventions, G/L determination and settlement handling. We follow that with a written scope and a fixed quote, so you approve a price before any build starts. Development happens against a copy of your data structures where you can provide one. Installation goes into your test company database first, where you run acceptance against real order shapes, including a full settlement cycle. Only after sign-off do we install into production, with a documented rollback for every object we add. Cutover is scheduled with you, usually outside trading hours.

After go-live

The engagement includes a support window for defect fixes and configuration help, a written runbook covering reprocessing and error handling, and recorded training for both the operations and finance users. Platform APIs change, and ongoing maintenance beyond the included window is quoted separately as a support agreement rather than assumed.