# B2B ecommerce SAP integration: what flows which way

> B2B ecommerce SAP integration keeps a parts store and SAP agreeing on materials, prices, stock, customers, quotes and orders. Ownership, timing and failures.

B2B commerce · The Intellsys team · 18 November 2026 · 6 min read

B2B ecommerce SAP integration is the connection that keeps a business-to-business parts store and SAP agreeing about six things: materials, prices, stock, customers, quotations and orders. The design question is not which connector to use. It is which system owns each kind of record, which way it flows, how fresh it must be, how records are matched, and who fixes it when a message fails. Settle those on paper before anyone writes code.

## The short answer

- Name one owner system for each kind of record. Two owners means two truths.
- Most data flows out of SAP into the store; customers and orders also flow back.
- Stock and buyer-specific prices must be fresh. Descriptions can wait for a nightly run.
- Matching keys, units and codes decide whether an integration works. Agree them first.
- Every failed message needs a log, an owner and a daily reconciliation.

## Which system owns each record

In most parts businesses that run SAP, the ERP is where money, stock and customers are accounted for. The store is where buyers search, compare and ask. That suggests a default split, which each business should confirm against how it actually works.

| Record | Usually owned by | Flows | How fresh it must be | Matched on |
| --- | --- | --- | --- | --- |
| Materials | ERP, with descriptions and images enriched in the store | ERP to store | Daily is often enough | Material number |
| Prices, including buyer-specific prices | ERP | ERP to store | Within the hour, or checked when a quote is made | Material, buyer and validity dates |
| Stock | ERP | ERP to store | As near live as the business needs | Material, plant and storage location |
| Customers | ERP for approved accounts; store for new sign-ups | Both ways | New sign-ups within the day | Customer number, tax registration |
| Quotations | Store, or ERP if quotes are made there | Agreed per business | When sent and when won | Quotation number and version |
| Orders | ERP | Store to ERP; status back | Within minutes of being placed | Order number, buyer reference |

The rows that cause the most argument are customers and quotations. Write down the answer, and who signed it off, before the build starts.

## What has to flow, and which way

- **ERP** Materials, prices, stock by plant and storage location, approved customers.
- **Parts store catalogue** Takes materials and enriches them with fitment, images and collections.
- **Buyer and sales team** Search, check stock, request and receive quotations.
- **Quotation won** The agreed version, with buyer, lines, prices and terms.
- **Order to ERP** Created in the ERP with the buyer's reference, for delivery and invoice.
- **Status back** Order, delivery and invoice status return to the buyer's view.

*The round trip between a parts store and SAP. Master data flows out of the ERP; customers, quotes and orders flow back in.*

The store adds what the ERP rarely holds well: fitment to machines, buyer-friendly descriptions, images and collections. Those are owned in the store and need not go back. Our guide to [spare parts catalogue management](https://intellsys.cloud/blog/spare-parts-catalogue-management) covers that side.

## What must be live and what can wait

Not every flow needs to be instant, and making everything instant makes the whole thing fragile. Sort each flow by what goes wrong if it is late.

| Needs to be fresh | Can run on a schedule |
| --- | --- |
| Stock at the plant a buyer is supplied from | New materials and description changes |
| A buyer's own price when a quotation is made | Images and catalogue enrichment |
| A new order reaching the ERP | Price-list changes announced in advance |
| Credit status before a large quote is sent | Closed or blocked customer accounts |
| Order and delivery status a buyer is waiting on | Historic orders for the buyer's account view |

*Sort every flow by the harm of lateness. Fresh where a buyer acts on the number; scheduled where nobody does.*

A stock figure that is a day old is worse than none: a buyer orders on it and a sales executive spends the afternoon apologising. If live stock is not possible, show "available to confirm" and check it when the quotation is made.

## Keys, units and codes: the dull part that decides everything

Integrations rarely fail on the big flows. They fail on small mismatches nobody wrote down.

- **Material numbers** One number per material, with its exact format agreed, zeros in front included.
- **Units of measure** Each, box or metre, and the conversion between selling and stock units.
- **Plant and storage location codes** The same codes on both sides, with a list of which plants serve which buyers.
- **Customer numbers** How a store sign-up becomes an approved account, and who approves it.
- **Tax codes and registration** So a quote and an invoice calculate tax the same way.
- **Price validity dates** Which price applies on the day a quote is made, and on the day it is accepted.

*Six small things to agree before an integration is built. Each one, left unsettled, turns into a daily manual fix.*

## When a message fails

Every integration drops messages: a network blip, a blocked customer, a material that does not exist on one side. What matters is that a failure is seen and owned.

1. **Log every message** The integration keeps what it sent, what came back and when.
2. **Retry what can be retried** Temporary failures are retried a set number of times.
3. **Alert a named role** Anything that still fails goes to the integration owner's queue.
4. **Fix the cause, not the record** Correct the mapping or the master data, then resend.
5. **Reconcile every day** Compare order and stock totals on both sides; investigate any gap.

*Failure handling for a parts store and ERP integration. Each step has an owner, so no failed order sits unseen.*

The integration owner should be a role on the business side, not only the developer who built it. Our comparison of [a business operating system, a CRM and an ERP](https://intellsys.cloud/blog/business-os-vs-crm-vs-erp) explains why the ERP stays the record for money and stock.

## How Intellsys OS fits beside SAP

In venture partner deployments Intellsys OS runs beside SAP. It holds a catalogue with variants, collections, machine fitment and parts, with bulk import, and stock by plant and storage location. It makes [business-to-business quotations](https://intellsys.cloud/blog/quotation-management-system) with versions, a PDF and sharing by WhatsApp or email, handles requests for quotation, and sends payment links.

> **How Intellsys OS handles it.** Tuffex runs a business-to-business parts store connected to SAP.

Dealer ordering and checkout sit on the same record. Order Management carries each order through dispatch, invoice and payment, in step with the ERP, which stays the record for money and stock. Requests usually arrive first as an RFQ, covered in our guide to the [RFQ process](https://intellsys.cloud/blog/rfq-process). See [the commerce part of the platform](https://intellsys.cloud/platform/commerce).

## Questions people ask

### What is B2B ecommerce SAP integration?

It is the connection that keeps a business-to-business store and SAP agreeing on materials, prices, stock, customers, quotations and orders, with one owner system for each record, an agreed direction and timing for each flow, and a way to catch failures.

### What data should flow from SAP to a B2B store?

Usually materials, prices including buyer-specific ones, stock by plant and storage location, and approved customer accounts. Descriptions, images and fitment are often enriched in the store and do not need to go back.

### What should flow back from the store to SAP?

New customer sign-ups for approval, won quotations where the business needs them in the ERP, and orders with the buyer's reference. Order, delivery and invoice status then return to the store for the buyer to see.

### Does stock have to be real time?

It has to be as fresh as the decisions made on it. Where buyers order on the figure, it should be near live. If that is not possible, show stock as available to confirm and check it when the quotation is made.

### What usually breaks a store and ERP integration?

Small mismatches: material number formats, units of measure, plant codes, customer numbers, tax codes and price validity dates. Agree each in writing before the build, and reconcile totals on both sides every day.

---

[Request a demo](https://intellsys.cloud/demo) · [Blog](https://intellsys.cloud/blog)

This is the Markdown version of https://intellsys.cloud/blog/b2b-ecommerce-sap-integration. Intellsys is built by GrowthJockey, a full stack venture architect.
