B2B commerce

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.

A fine-line chart of Saturn's rings seen nearly edge on, ruled like a scale, two moons on the line.

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.

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.

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.

RecordUsually owned byFlowsHow fresh it must beMatched on
MaterialsERP, with descriptions and images enriched in the storeERP to storeDaily is often enoughMaterial number
Prices, including buyer-specific pricesERPERP to storeWithin the hour, or checked when a quote is madeMaterial, buyer and validity dates
StockERPERP to storeAs near live as the business needsMaterial, plant and storage location
CustomersERP for approved accounts; store for new sign-upsBoth waysNew sign-ups within the dayCustomer number, tax registration
QuotationsStore, or ERP if quotes are made thereAgreed per businessWhen sent and when wonQuotation number and version
OrdersERPStore to ERP; status backWithin minutes of being placedOrder 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

  1. ERPMaterials, prices, stock by plant and storage location, approved customers.
  2. Parts store catalogueTakes materials and enriches them with fitment, images and collections.
  3. Buyer and sales teamSearch, check stock, request and receive quotations.
  4. Quotation wonThe agreed version, with buyer, lines, prices and terms.
  5. Order to ERPCreated in the ERP with the buyer's reference, for delivery and invoice.
  6. Status backOrder, 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 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

  • Stock at the plant a buyer is supplied from
  • A buyer's own price when a quotation is made
  • A new order reaching the ERP
  • Credit status before a large quote is sent
  • Order and delivery status a buyer is waiting on

Can run on a schedule

  • New materials and description changes
  • Images and catalogue enrichment
  • Price-list changes announced in advance
  • Closed or blocked customer accounts
  • 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 numbersOne number per material, with its exact format agreed, zeros in front included.
  • Units of measureEach, box or metre, and the conversion between selling and stock units.
  • Plant and storage location codesThe same codes on both sides, with a list of which plants serve which buyers.
  • Customer numbersHow a store sign-up becomes an approved account, and who approves it.
  • Tax codes and registrationSo a quote and an invoice calculate tax the same way.
  • Price validity datesWhich 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 messageThe integration keeps what it sent, what came back and when.
  2. Retry what can be retriedTemporary failures are retried a set number of times.
  3. Alert a named roleAnything that still fails goes to the integration owner's queue.
  4. Fix the cause, not the recordCorrect the mapping or the master data, then resend.
  5. Reconcile every dayCompare 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 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 with versions, a PDF and sharing by WhatsApp or email, handles requests for quotation, and sends payment links.

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. See the commerce part of the platform.

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.

Read next

See it on a live workspace.

A demo shows the parts of Intellsys OS that are in use today, with the people who run it.

Request a demo
Request a demo