SAP Integration
For businesses running SAP and selling on marketplaces across several seller accounts, warehouses or countries. At this scale the expectation is not speed but consistency: every order written complete, every record that could not be written visible with its reason, and settlements that agree at month end. Rollout opens by reading, writing nothing.
Included from the Starter planPlans and pricing ›
What is the SAP integration?
The SAP integration is the layer that ties order, stock and price movement on the marketplace side to its counterpart in SAP. An order from a channel is written into SAP against the counterparts agreed in the field mapping, and the stock and prices held in SAP go out to every connected account and channel. The processes you have built in SAP are left untouched.
In businesses running SAP, order volume and channel count long ago outgrew manual tracking. What matters here is not that a record passes quickly but that no record disappears quietly. An order that cannot be written sits in a list with its reason and raises an alert while the list is not empty, so a failed transfer shows up without waiting for month end.
In enterprise setups field mapping varies by project, and we plan that together before onboarding. In shadow mode the system writes nothing into SAP and only reads, showing the numbers on both sides side by side. Write access opens channel by channel only after you approve it, and every step is reversible.
Which plan includes it?
Every marketplace and platform integration is included from the Starter plan; the number of channels depends on the plan.
What you can do with the SAP integration
Orders written into SAP
Every marketplace order is written into SAP with its customer, line items, carrier, payment details and tracking number. Because field mapping varies by project in enterprise setups, we agree the scope together before onboarding.
Visibility of records that fail to write
If an order cannot be written into SAP, it sits in a list with its reason and raises an alert while the list is not empty. No order fails silently; once the cause is fixed the record is processed from that same list.
Many accounts, warehouses and countries
Several seller accounts, warehouses and countries are managed from one panel, each with its own stock and price rules. You decide during setup which warehouse is exposed to which channel.
Stock from SAP across every channel
SAP is the source of the stock figure; whichever channel the sale happens on, the unit comes off every connected channel at the same time. Adding a channel or a seller account never means splitting stock, because the new account joins the same pool.
Price management
Prices start from the list price in SAP; selling and floor prices are defined separately per marketplace and per country, and a campaign price never drops below the floor.
Settlement reconciliation and roles
Settlement reports arrive in the panel on their own and each line is tied to its order, with returns whose commission is not refunded and orders that go negative flagged separately. Who can reach these screens is limited through roles.
How the SAP integration is set up
Plan
Before onboarding we agree together which fields map where, and which seller accounts and warehouses are in scope. You prepare the access details required with your SAP partner.
Match
Products and variants in SAP match marketplace listings through SKU and barcode. Anything that does not match is listed and broken down by channel.
Watch
Shadow mode keeps writing switched off entirely: the system reads both sides and leaves no record in SAP. Order counts, stock quantities and the list of records that would fail to write are visible against real data in advance.
Hand over
Write access opens channel by channel and account by account: orders first, then stock, then prices. Every step is reversible and the scope can start as narrow as you like.
Technical summary
| Data carried | Orders, stock, prices, products and variants, returns, settlements |
|---|---|
| Direction | Orders from the marketplace into SAP; stock and prices from SAP out to the marketplaces |
| Matching key | SKU and barcode; variants match at barcode level |
| Fields carried on an order | Customer, line items, carrier, payment details, tracking number |
| Field mapping | Varies by project in enterprise setups; the scope is planned together before onboarding |
| Records that fail to write | Sit in a list with their reason and raise an alert; no order fails silently |
| Update timing | The moment a sale is made on a channel, with no waiting and no fixed polling hour |
| Needed on the SAP side | Access details are prepared with your SAP partner |
| Invoicing and shipping | Stay inside your existing SAP processes; the integration never enters the invoicing or dispatch step |
| Onboarding method | Starts in shadow mode; the system reads only and lists in advance the records that would fail to write, and write access opens step by step per channel and per account |
| Accounts and countries | Several seller accounts, warehouses and countries from one panel, each with its own stock and price rules |
What it works with
Free calculators
Test pricing and shipping decisions without leaving the page. Runs in your browser and sends no data.
Frequently asked questions about the SAP integration
How does the SAP marketplace integration work?
Bulutegra gathers every connected seller account in one place and runs the flow between those accounts and SAP. It takes the order from the channel and writes it into SAP with customer and line items, and it sends the stock and prices held in SAP out to the channels. Invoicing and dispatch continue inside your own SAP processes.
Is development needed on the SAP side?
The required access details are prepared with your SAP partner. Because field mapping varies by project in enterprise setups, we plan the scope together before onboarding.
What happens to an order that cannot be written?
The record sits in a list with its reason and raises an alert while the list is not empty. No order fails silently; once the cause is fixed the record is processed from that same list.
Can several seller accounts, warehouses and countries be managed?
Yes. They are all managed from one panel, each with its own stock and price rules, and you decide which warehouse is exposed to which channel.
How narrow can the initial scope be?
As narrow as you like: you can enter shadow mode with a single seller account and a single channel, then widen the scope account by account once the numbers agree.
Can the integration corrupt data in SAP?
In shadow mode the system writes nothing into SAP and only reads. At that stage you see not just whether the numbers agree but also the list of records that would fail to write, against real data and in advance. Write access opens only after you approve it, per channel and per account.
How do settlements reconcile against the records in SAP?
Report lines are matched to their orders, so you can see order by order where a gap comes from. Returns whose commission is not refunded, orders that go negative, and cases where the same product is charged different commission are grouped under separate headings.
Can I restrict which screens my team can reach?
Yes. Roles are defined; team members working with the Accounting role, for example, reach only the settlement and reconciliation screens.
What size of business is a SAP integration suited to?
Businesses running several seller accounts, warehouses and countries, where order volume has outgrown manual tracking. Onboarding still starts in shadow mode and is handed over channel by channel.