Every channel is a separate build
Connecting channels inside SAP means one integration project per channel. Open TikTok Shop after Shopee and you build the same thing again.
BATI CIS collects order, shipment, sales and settlement data from marketplaces such as Amazon, Shopee and TikTok Shop and from your 3PLs, standardizes it, and reconciles each channel's settlements against actual shipments and returns. It then builds journal entries in the format SAP expects and sends only the data SAP needs, so your SAP stays as it is.
Every marketplace has its own order and settlement report formats. Connecting those raw files directly to SAP adds load in development, processing and month-end close.
Connecting channels inside SAP means one integration project per channel. Open TikTok Shop after Shopee and you build the same thing again.
Passing orders, shipments, returns and settlements line by line means SAP processes more records with every new channel and every extra order.
Processing in SAP is expensive per record. Handling unorganized raw data there costs accordingly.
Order data mixes in cancellations, returns and unshipped orders. If settlements are not matched against 3PL shipments and returns first, someone hunts for the differences by hand at every close.
BATI CIS handles channel integration outside SAP, in one middleware layer. A BATI CIS build takes 3 to 6 months and costs under KRW 300 million (standard setup; may vary with integration scope).
SAP handles accounting once an entry exists. Turning scattered channel data into entries is the step before, and that is BATI CIS's job.
Collection is set per channel: automatic, or by receiving files.
Actual shipments and returns
BATI CISCollect · standardize · reconcile · build entries
Journal entries
Orders, shipments, sales and settlements from each channel, plus actual shipment and return data from 3PL and fulfillment partners, come in automatically. For channels that use two-step verification, collection is adjusted: BATI CIS receives files instead of collecting automatically.
Each channel's order and settlement report formats are converted into one schema.
Channel settlements are matched against actual shipments and returns. Orders that have not shipped and items that came back are kept apart, and mismatches surface before the close.
Fees and net sales are organized by channel and product and turned into journal entries in the format SAP expects.
Raw data is processed in BATI CIS, and SAP receives only the consolidated data.
Curious how settlements are matched to orders and actual shipments and returns? More on settlement reconciliation
How each channel's settlement differs: Amazon settlement · Shopee settlement
SAP ECC and SAP S/4HANA run live at customers, and the SAP S/4HANA Cloud Public Edition integration is in development for a 2026 opening (as of November 2026). The method is chosen to fit each customer's SAP environment and IT policy.
| SAP environment | Scope |
|---|---|
| SAP ECC(SAP ERP 6.0) | Sales, return and settlement entries |
| SAP S/4HANA | Sales, return and settlement entries |
| SAP S/4HANA Cloud Public Edition(public cloud) | Sales order → delivery → billing |
Journal entry files in an agreed format go over SFTP. Columns and format are checked first, and a file that does not match is rejected as a whole, so nothing is posted halfway.
Entries go by API. The document type is set automatically, and the same entry is never posted twice.
SAP's published sales order, delivery and billing APIs, in that order.
Only confirmed entries go to SAP.
Rollout steps, system layout and scope are in the SAP integration guide (in Korean). Request the SAP integration guide
Sources (SAP product names) · Checked 2026-11-10
A global K-beauty brand with annual revenue around KRW 500 billion. To connect Amazon, Shopee and TikTok Shop to SAP, SAP is the ERP and BATI CIS is the middleware in between.
Raw data was organized and aggregated in BATI CIS, and only the consolidated data went to SAP, so SAP, where each record is expensive to process, handled fewer records.
* Results vary by setup.
You can also see how the month-end close runs. More on month-end close automation
The sequence is the same without SAP. SAP has a public case, and Douzone, Younglimwon, Ecount and Oracle can also be connected with journal entries in the format each ERP expects. For an in-house ERP we design the integration with you.
Yes. As of November 2026 both SAP ECC and SAP S/4HANA run live at customers. Sales, return and settlement entries are sent by file interface (SFTP) or by Cloud Integration in SAP Integration Suite (often called CPI), whichever fits the customer's environment.
It is in development and opens in 2026. Entries go in through SAP's published sales order, delivery and billing OData APIs, in that order.
Yes. It receives material, customer and price master data and sales results from SAP. What it sends to SAP is sales, return, adjustment, cost and carry-over entries, and only confirmed ones.
BATI CIS does not replace SAP; it works next to it as middleware and sends journal entries in the format SAP expects, so you keep using SAP as you do today. Channels and scope are agreed in the consultation.
Yes. Each channel's settlement reports are collected and reconciled against actual shipments and returns, fees and net sales are organized by channel and product, and the result becomes SAP journal entries. K-Beauty Brand C in our published case also runs BATI CIS between Amazon, Shopee, TikTok Shop and SAP. Channel scope is confirmed in the consultation.
Because SAP processes fewer records. Raw data is organized and aggregated in BATI CIS, and SAP receives only the consolidated data. Processing in SAP is expensive per record, so fewer records mean lower cost.
Yes. Shipment and return data from 3PL and fulfillment partners is matched with channel orders and settlements. Orders that have not shipped and items that came back are kept apart, so SAP receives sales for what actually shipped.
A standard BATI CIS build takes 3 to 6 months and costs under KRW 300 million. It depends on the channels, logistics and ERP you connect, so the exact timeline and cost are given in the consultation.
Yes. K-Beauty Brand C in our published case rolled it out together with a consulting firm. SAP is their ERP, and BATI CIS is the middleware between their global channels (Amazon, Shopee, TikTok Shop) and SAP.
Articles are in Korean.
Enterprise builds start with the inquiry form. We scope the channels, logistics and SAP integration together, and a dedicated manager supports rollout and operations.
Smaller brands running a Cafe24 store can start right away with the Cafe24 app. About the Cafe24 app