Have questions? Leave your message here or Schedule a quick call with our manager now

SAP Business ByDesign Integration is coming soon — Get notified when it's ready

SAP Business ByDesign Integration — Coming Soon

API2Cart is evaluating a planned SAP Business ByDesign integration for software providers that need unified access to eCommerce data. Share your ERP workflow to help define the roadmap.

Your APP or Software

APP Icon - Unified Shopping Cart Integration API

Unified API

API2Cart - Unified Shopping Cart Integration API

Your APP or Software

APP Icon - Unified Shopping Cart Integration API

API2Cart - Unified Shopping Cart Integration API

What API2Cart Is Evaluating for SAP Business ByDesign Integration

01

Candidate workflow

Connect commerce orders with accounts, materials, sales documents, fulfillment, and finance. Final entity and method coverage will follow verified vendor interfaces and customer requirements.

02

Operational outcome

The intended result is to retain company, sales-unit, site, currency, tax, and document-flow relationships. Identity rules and idempotency would be defined before transactional writes are enabled.

03

ERP safeguards

The design must respect approval and release states across integrated business processes. Customers, products, sales orders, fulfillments, invoices, and production records would keep their distinct lifecycle roles.

Develop Integrations Faster and Save Up to 9x on Costs

Speed up your integration rollout
Speed up your integration rollout
Connect your software to multiple shopping platforms and marketplaces using one reliable and unified API, shortening your time to market.
Save development time
Save development time
Let your developers focus on other high-value tasks. We take care of the integration with eCommerce platforms.
Expand your reach and boost revenue
Expand your reach and boost revenue
Integration with 70+ shopping platforms equals 1+ million of e-stores as your potential customers.
Save costs on integrations
Save costs on integrations
With API2Cart, integration costs can be lowered by as much as 9x.

Trusted by

What We Know About SAP Business ByDesign So Far

Based on SAP Business ByDesign’s own documentation and API2Cart’s discovery process — not a promise of a release date.

API & Integration. SAP Business ByDesign exposes business objects primarily through OData v2 services (plus older SOAP web services), with key users controlling which objects, nodes, and elements are exposed via the "Application and User Management – OData Services" work center. Authentication supports either Basic auth (username/password) or OAuth 2.0 SAML Bearer for user-context, principal-propagated access. SAP provides an API sandbox with test data for trying out GET calls before building against a live tenant, and native webhook support is limited — inbound event notifications typically require custom work in SAP Cloud Application Studio to call an external webhook URL rather than a built-in subscription mechanism.

SAP Business ByDesign integration is not live yet. Authentication, modules, entities, fields, writes, events, limits, editions, and release timing remain subject to technical discovery and demand.

Background. SAP records that it unveiled Business ByDesign in 2007 as its first on-demand solution for small and midsize enterprises. The product was designed as an integrated cloud suite rather than a hosted copy of SAP’s largest-enterprise ERP.

Where it specializes. Business ByDesign brings finance, sales, purchasing, supply chain, project management, and product management into one tenant. It is most relevant to growing midsize organizations, subsidiaries, product businesses, and service companies that need cross-functional processes without a large on-premises SAP landscape.

Integration challenge. SAP provides standard web services and configurable OData services. In the OData Service Explorer, an administrator selects business objects, fields, associations, and operations and assigns work-center access. API2Cart discovery must therefore inspect the customer’s actual service definitions, communication arrangements, user authorizations, tenant URL, and supported create, read, update, and delete operations. CSRF handling, pagination, code-list values, and business-object lifecycle rules must be tested before synchronizing products, stock, customers, or orders.

Technical validation. Engineering must verify OData and SOAP services, communication arrangements, scopes, and change notifications. Unsupported modules and operations would remain outside the public scope.

Verified vendor documentation. SAP documents OData service modeling, CRUD capabilities, access rights, authentication, and CSRF handling. Communication arrangements and supported business objects must be validated for each customer. Read the official SAP Business ByDesign OData Services documentation.

Roadmap evaluation considers API maturity, sandbox access, operational correctness, commerce relevance, scale, customer demand, maintenance cost, deployment variants, and overlap with existing connectors. This page records a candidate, not a promised release date.

Primary sources: SAP history: Business ByDesign unveiled in 2007 · SAP Business ByDesign product overview · SAP Business ByDesign OData documentation

Related planned integrations: Oracle JD Edwards EnterpriseOne integration · Oracle E-Business Suite integration · Oracle PeopleSoft integration · Deltek Costpoint integration

Interested in SAP Business ByDesign Integration?

Let us know you’re interested, and we’ll notify you as soon as SAP Business ByDesign support becomes available.