SAP Business One + Salesforce integration

Order creation and credit checks are usually event-driven: a Salesforce flow or platform event fires when an opportunity is won or an order reaches an agreed status, and the sales order lands in SAP B1 within seconds to minutes. Items, price lists and stock change in bulk, so they are usually read from the Service Layer on a schedule, often every 5 to 15 minutes. On SAP Business One 10.0 FP 2602 or later, Service Layer webhooks can push Business Partner and document changes instead of polling.

We start with a mapping workbook that pairs every Salesforce field with its SAP B1 counterpart, including user-defined fields and picklist translations for payment terms, sales employees and warehouses. The CardCode is stored in a Salesforce external ID field, so updates match the right Account without a search, and new Business Partners are created only after a duplicate check on tax ID or name and address. Failed transactions go to a retry queue with alerting and a dashboard of records that need attention.

The Service Layer for new integrations. SAP describes it as an OData service built on the same DI core as the DI API, so Business Partners, items and documents have the same properties in both. The DI API is a Microsoft COM library suited to Windows add-ons, and we use it only where the Service Layer lacks a function. Salesforce talks to the integration service, never directly to your SAP server.

Not for the core sync. SAP added Service Layer support for Microsoft SQL Server with SAP Business One 10.0 PL01, so both versions use the same API. Reporting features differ: Semantic Layer views are HANA only, while SQL Server systems can expose their own SQL views through the Service Layer, which is useful for read-only account summaries. Older SQL Server releases without the Service Layer need the DI API or an upgrade.

Yes. Each Service Layer login names one company database, so the integration routes each Account and order to a company by rule, for example by country, business unit or a field on the opportunity. The same customer can exist in several companies with different CardCodes, so we store the company and CardCode pair rather than a single number.

Usually in Salesforce, where reps work, with SAP B1 supplying prices, stock and credit status. Salesforce syncs one quote at a time with its opportunity, so the synced quote is a natural trigger. If your team issues formal quotations from B1, we create a B1 Sales Quotation from the approved Salesforce quote and write the B1 document number back.

Pick one. A won opportunity with products is simplest; a synced, accepted quote suits teams that negotiate line by line; a Salesforce Order suits teams that already manage orders in Salesforce, and its Status field can gate the transfer. Two triggers for the same deal are the most common cause of duplicate SAP orders.

The transfer stops in a queue with the SAP error, for example a missing item, a blocked Business Partner or a credit limit, and the rep sees a failed status on the Salesforce record. Data errors wait for a fix and a replay; technical errors retry automatically. The Salesforce record ID is stored on the SAP order and checked before every create, so a replay cannot produce a duplicate.

API access and daily allocations. Salesforce’s limits reference lists Enterprise Edition, and Professional Edition with API access enabled, at 100,000 API calls per 24 hours plus 1,000 per Salesforce license, for example 115,000 for 15 licenses. A well-designed sync uses a small share of that, but backfills and frequent polling add up, so we batch reads and use change events where they fit.

If your process matches a template, a connector is cheaper to start. APPSeCONNECT lists plans from $99 per month and says its SAP B1 connector handles HANA, SQL Server and multi-company setups; Stacksync lists two-way sync plans from $1,000 per month. Choose custom when approvals, CPQ, multiple companies or custom objects make the template work against your process, or when you want to own the code.

The number of objects and directions, and how much logic sits between them. Quote approvals, CPQ, multiple SAP B1 companies or currencies, custom objects and historical backfills add build and test time. Ongoing cost depends on hosting, monitoring, any iPaaS subscription, Salesforce API capacity and the support you choose.

Yes, read-only. Open A/R invoices, incoming payments and the Business Partner balance sync to the Account on a schedule, and a credit-hold flag can block new orders in Salesforce before they reach SAP. The documents stay in SAP B1 as the record; Salesforce shows what reps need to act.

You choose. We hand over the code, mapping workbook, runbook and alert setup so your team can operate it, or we support it under an agreed plan. Salesforce ships seasonal releases (the current object reference is Winter ’27, API version 68.0) and SAP ships B1 feature packs, so the integration should be retested on a release calendar.

Yes. Alongside or instead of a point-to-point sync, we can build an MCP server that exposes both the SAP B1 Service Layer and the Salesforce API as tools. An agent in Claude, a Slack bot or a custom app can then answer questions like “what is this account’s open balance and last three orders” or draft a sales order from an opportunity, with approval steps where you want a human in the loop.

A standard scope covering accounts, products, prices, stock and order push usually takes a few weeks including mapping workshops and UAT. Adding custom objects, multi-company SAP B1 databases, or complex pricing rules extends that to roughly two to three months. We give a fixed timeline after a short discovery of your SAP B1 configuration and Salesforce customizations.