API & ERP Integrations
Reliable connections between nopCommerce and your ERP, CRM, payment gateways, PIM and logistics providers.
Services
nopCommerce SAP Business One Integration Services
We connect nopCommerce to SAP Business One so items, prices, stock, business partners and orders move between the store and the ERP without re-keying. We use the SAP Business One Service Layer on SAP HANA or Microsoft SQL Server, queue every order so none is lost, and log every sync so your team can see what happened.
Where this helps
Situations that typically lead businesses to this kind of work.
- Web orders are re-entered in SAP Business One as sales orders, by hand.
- Stock in the store does not match the SAP Business One warehouses.
- Business partners have price lists and special prices that only exist in SAP.
- SAP Business One runs on-premise and the store cannot reach it safely.
Capabilities
What we deliver
Items and variants
SAP Business One items mapped to nopCommerce products and attribute combinations by item code, with units of measure and item groups.
Price lists and special prices
Price lists, special prices for business partners, and period and volume discounts shown to the right customers.
Stock by warehouse
Available quantities from the SAP Business One warehouses you choose, per warehouse in nopCommerce.
Business partners
Customers, contact persons and bill-to and ship-to addresses kept in step with SAP Business One business partners.
Orders, quotations and deliveries
Web orders sent as sales orders or sales quotations, with deliveries, tracking numbers and A/R invoice status sent back to the store.
Monitoring and retries
A queue with retries, so each order reaches SAP once, and an admin log with the Service Layer error text.
The same principles of record ownership, background exports and safe retries apply to any ERP. See them worked through in our nopCommerce NetSuite integration guide.
Selling to trade customers on top of SAP pricing? See B2B eCommerce on nopCommerce: company accounts, approvals and quick order.
Options
Is there a SAP Business One connector for nopCommerce?
Not a packaged one. The nopCommerce marketplace lists SAP as an integration that is not developed yet and refers store owners to solution partners, and the integration platforms that sell SAP Business One connectors for other shopping carts do not cover nopCommerce.
We build the integration as nopCommerce plugins that talk to the SAP Business One Service Layer. It runs inside your store, uses nopCommerce’s own services so stock history, emails and caches behave normally, and you own the source code.
- SAP Business One 10.0, version for SAP HANA or for Microsoft SQL Server
- nopCommerce 4.50 to 5.00 on SQL Server, MySQL or PostgreSQL
- User-defined fields (UDFs) mapped to nopCommerce fields or attributes
- One or several SAP companies, tied to nopCommerce stores
Data
What a nopCommerce SAP Business One integration synchronises
The catalog usually flows from SAP Business One to the store, and orders flow back. SAP owns item codes, prices, stock and business partner terms. The store owns web content such as descriptions, pictures and SEO fields. We agree this field by field before building.
Each order becomes the SAP document your team already works with: a sales order for most stores, a sales quotation when orders need review, and optionally an A/R invoice and incoming payment for prepaid web orders.
- SAP to nopCommerce: items, item groups, units of measure, price lists, special prices, period and volume discounts, stock per warehouse
- nopCommerce to SAP: business partners, contact persons and addresses, sales orders or sales quotations, payment details
- SAP to nopCommerce: deliveries with tracking numbers, order status, A/R invoice status
- Optional: batch and serial numbers on deliveries, credit limits and payment terms for B2B accounts
How it connects
Service Layer, DI API and on-premise SAP Business One
The Service Layer is SAP Business One’s REST/OData web API. It is available for the SAP HANA version and, from SAP Business One 10.0, for Microsoft SQL Server too, and it is what we use for new integrations. Older installations without the Service Layer can be connected through the DI API, case by case.
Many SAP Business One systems run on a server in the office or a private cloud. The Service Layer does not have to be opened to the internet: it can be reached over a VPN or an IP-restricted reverse proxy, or a small connector service inside your network can push changes to the store and pull orders from it, using outbound connections only.
- Service Layer (REST/OData) on SAP HANA or SQL Server, with batch requests for bulk updates
- A dedicated SAP user with only the permissions the integration needs
- Access over VPN, an IP-restricted reverse proxy, or an outbound-only connector service
- DI API for older systems without the Service Layer, assessed per project
B2B pricing
Showing SAP Business One prices to business customers
SAP Business One prices can come from several places: the business partner’s price list, special prices for that partner, period and volume discounts, and discount groups. nopCommerce has tier prices and customer roles, which cover the simple cases. For the rest, we add a price service that applies the same rules SAP does, from synchronised data or a live check for logged-in customers.
- Price list per business partner or customer group
- Special prices for a business partner, including date ranges
- Quantity breaks from period and volume discounts
- The price shown in the cart matches the price on the SAP sales order
Effort
What determines the effort and cost
Every SAP Business One company is configured differently, often with add-ons and user-defined fields from the reseller who set it up. After a short review of your system and store, we give a fixed scope and quote for a first phase, usually catalog, stock and order export, and plan the rest as later phases.
- SAP Business One version, database (HANA or SQL Server) and whether the Service Layer is installed
- How pricing is set up: price lists, special prices, discount groups
- Number of warehouses, companies and currencies
- User-defined fields, user-defined tables and add-ons the integration must respect
- How the store will reach SAP: VPN, reverse proxy or an on-site connector
Approach
How we approach it
- 01
Review your SAP setup
We check your version, database, Service Layer access, user-defined fields and add-ons, and how pricing is set up.
- 02
Agree the mapping
Which side owns each field, how items and business partners are matched, and which SAP documents an order creates.
- 03
Test on a copy, then go live
We test against a copy of your company database, then switch on catalog sync first and orders second.
Platform
nopCommerce versions we support
We build for and support nopCommerce 4.50 to 5.00. Each release runs on a specific .NET version, which sets the hosting a store needs and how much work an upgrade involves.
Stores on 4.40 or later upgrade the database automatically when the new release first starts. Plugins and the theme still need builds for the target version.
Planning a move between versions? Read our nopCommerce upgrade guide.
| nopCommerce | .NET runtime | Notes |
|---|---|---|
| 4.50 | .NET 6 | |
| 4.60 | .NET 7 | |
| 4.70 | .NET 8 | |
| 4.80 | .NET 9 | |
| 4.90 | .NET 9 | Previous release line, latest patch 4.90.8 |
| 5.00 | .NET 10 | Current release, 27 October 2026 |
Checked against the nopCommerce source code and release notes on 27 October 2026. Sources: nopCommerce releases on GitHub, Official upgrade documentation.
Questions
SAP Business One Integration FAQ
Something else on your mind? Ask us directly.
Is there a SAP Business One connector for nopCommerce?
Not a packaged one. The nopCommerce marketplace lists SAP as not developed yet. We build the integration as nopCommerce plugins that connect to the SAP Business One Service Layer, and you own the source code.
Do you support SAP Business One on SQL Server as well as SAP HANA?
Yes. The Service Layer is available for both from SAP Business One 10.0. For older versions on SQL Server without the Service Layer, we can connect through the DI API after checking your setup.
Our SAP Business One server is on-premise. Can the store reach it?
Yes, without opening it to the internet. We can connect over a VPN or an IP-restricted reverse proxy, or install a small connector service in your network that only makes outbound connections to the store.
Which SAP document does a web order create?
Usually a sales order. If orders need review before they are accepted, a sales quotation instead. For prepaid orders we can also create the A/R invoice and the incoming payment, so finance does not have to.
Can you work with our user-defined fields and add-ons?
Yes. User-defined fields can be read and written through the Service Layer and mapped to nopCommerce fields or product attributes. We review add-ons from your SAP reseller first, so the integration does not conflict with them.
Will the store keep taking orders if SAP Business One is down?
Yes. Orders are queued in nopCommerce and sent when SAP is back, exactly once. Stock and prices keep their last synced values in the meantime.
Which nopCommerce versions do you support?
nopCommerce 4.50 to 5.00. If the store is older, we will tell you whether upgrading first is the better investment.
Related
Often combined with
B2B eCommerce Solutions
Customer-specific pricing, company accounts, approval flows and quick ordering for trade customers.
Enterprise Commerce Integrations
Commerce architecture that connects nopCommerce to ERP, PIM, WMS, CRM and identity systems.
Ready to plan your nopCommerce project?
Tell us about your storefront, ordering workflows or integrations by email, phone or WhatsApp. An outline is enough to start.