B2B e-commerce platform for SAP Business One

Data silos

Items are maintained in the ERP – and again in the store. Two sets of master data drift apart: descriptions, units of measure, categories. Every correction is double work, every import a source of errors.

Stale prices and stock

Batch sync means the store shows last night’s numbers. A customer orders at a price that no longer applies, or an item that is no longer there – and inside sales gets to make the phone call.

Pricing rules rebuilt by hand

Your sales team negotiates in SAP Business One: price lists, special prices, volume tiers per customer. A generic store cannot express that logic, so it gets rebuilt in the store – and is out of date from day one.

Items

Item master data, units of measure and assortment assignments per storefront – maintained in B1, published by the store.

Inventory

Availability from SAP Business One, so a customer ordering 40 cases sees whether 40 are actually there.

Price lists

B1 price lists and their assignment to business partners – the pricing logic is adopted, not rebuilt.

Special prices

Special prices per business partner that override the list, including volume tiers – the most demanding part of any B1 integration.

Business partners

Customers and their contacts, so every store login maps to the right B1 business partner with the right terms.

Sales orders

Every store order is written back to SAP Business One as a sales order – the only direction in which the store writes.

How do customers see their SAP B1 contract prices?

A customer registers, your team approves the account and links it to the business partner in SAP Business One. From that moment the login carries the B1 price-list assignment and any special prices. A 5-gallon pail of degreaser listed at $64.00 shows the account’s contract price of $51.20 – and no price at all before login.

Nothing is keyed into the store. When sales changes a special price in B1, the customer sees it on the next page load. Details: customer-specific pricing and the dealer portal approval workflow.

Several storefronts from one SAP B1 company – or several

One installation of the CS Order Suite runs multiple storefronts: a brand store for each product line, a store per country, or separate storefronts for dealers and end customers – each with its own assortment, its own look and its own customer group, all fed by the same B1 company.

If your group runs more than one SAP Business One company, storefronts can map to different companies. Either way, prices, stock and orders stay per company in the ERP. See multi-tenant e-commerce.

SAP B1 partners and VARs bring us in when a customer asks for an online store that respects B1 pricing and does not add a second master-data system. You keep the ERP relationship and the B1 configuration; we deliver the store, the adapter connection and the go-live, and coordinate with your consultants on test companies, price lists and business-partner setup. Talk to us about how a joint project runs.

Does it work with our SAP Business One price lists and special prices?

Yes. Customer-specific price lists and special prices come straight from SAP Business One into the store. Every approved business customer sees their negotiated terms after login; pricing is maintained only in the ERP, never in the store.

Do we have to maintain items and inventory twice?

No. SAP Business One remains the system of record. The CS Order Suite adapter synchronizes items, inventory, prices, business partners and orders between the ERP and the store, so there is no second set of master data to keep in step.

What happens to orders placed in the store?

They are created as sales orders in SAP Business One, with the customer’s code, PO reference and lines, and without re-keying. Delivery and invoicing then run in the ERP exactly as they do today. The same applies to scan-to-reorder orders and to punchout orders from a customer’s procurement system.

Does it matter whether SAP Business One runs on premise or is hosted by our partner?

Not for feasibility. It decides the access route: a hosted or cloud-reachable company is the simplest case; for a system inside your own network we agree the connection with your IT or your SAP partner. Testing runs against a B1 test company, never against production.

Can we connect an ERP other than SAP Business One?

Yes, through the adapter architecture. The ready adapter is for SAP Business One; other ERPs such as NetSuite, Dynamics 365 Business Central, Sage, Epicor or QuickBooks Enterprise are connected via a project adapter over REST, OData, SOAP, database views or file exchange.

How does a rollout work?

In clear steps: demo and requirements; concept (storefronts, assortments, pricing logic, account approval); ERP integration with tests against your B1 test company; go-live. SAP Business One stays the leading system throughout, and the timeline depends on the scope of your project.

Want to see your SAP B1 price lists live in a store?

In a live demo we show the integration against your requirements – items, terms, account approval and the order’s path back into SAP Business One. Pricing is something we cover personally.

Your contact

Christian Stockerl

Managing Director
CS Management & IT-Beratung GmbH