Connect SAP Business ByDesign (SAP ByD) and Shopify so paid web orders become ByDesign sales orders with their payment attached, and stock, prices and deliveries flow back to the store. AIONDATA builds on ByDesign’s web services and OData, tests in your test tenant, and adds monitoring and reconciliation.
California-based leadership · Serving US and international teams
SAP ByDesign Shopify integration connects a cloud ERP that runs your finance and logistics to a store that takes payment before anything ships. Shopify sends paid orders, customers, cancellations and returns; ByDesign sends materials, price lists, stock and delivery status. Payment is the detail that shapes the design: SAP’s own samples create sales orders with external payment through the Manage Sales Orders web service, because OData cannot carry it. We build on the same services, keep the Shopify reference on every ByDesign document, and prove the full sell-from-stock flow in your test tenant first.
These decisions shape the scope, cost and acceptance tests. The flows below describe possible implementation behavior, not a preinstalled connector or a guarantee for every product edition.
Confirm the ByDesign test and production tenants, the scoped sales and outbound logistics processes, and who can create communication systems, scenarios and arrangements. Decide whether the integration runs outside the tenant or needs a Studio add-on.
Agree how a paid Shopify order appears in ByDesign: sales order with external payment, delivery proposal, goods issue and customer invoice. Map each Shopify payment method to its payment reference, and decide how refunds reach finance.
Pick the stock figure Shopify should show, per site or logistics area, and the price lists or discount lists that apply to each Shopify market or B2B catalog.
SAP upgrades the test tenant before production. Schedule go-live and any Studio deployment outside that window, and agree who reviews Shopify API version changes each quarter.
Field mapping
The records, match keys and triggers most implementations start from. Your scope confirms each row against your editions, custom fields and business rules.
| Source | Target | Match key | Direction | Trigger | Notes |
|---|---|---|---|---|---|
| ByDesign material (custom OData service or Query Materials) | Shopify product and variant | Material ID = Shopify variant SKU | SAP ByD → Shopify | Scheduled delta on last change date and time | Only materials with sales data for the web channel; quantity conversions applied when the selling unit differs. |
| Stock overview (analytics OData, by site or logistics area) | Shopify inventory level per location | Site or logistics area = Shopify location; material ID = SKU | SAP ByD → Shopify | Every few minutes for fast movers; nightly full comparison | Sellable quantity = on-hand stock minus an agreed buffer; Product Availability Check can confirm a single item without reserving it. |
| Sales price lists and discount lists (Manage Sales Price Lists) | Shopify variant price or B2B price list | Price list ID + material ID | SAP ByD → Shopify | Scheduled read of changed price list items | Base list for retail prices; customer-group or customer-specific lists for B2B catalogs. |
| Shopify paid order (orders/paid webhook) | ByDesign sales order with external payment (Manage Sales Orders) | Shopify order ID as the external reference; existing-order check before create | Shopify → SAP ByD | orders/paid webhook, plus a scheduled sweep | Payment method and reference mapped to the agreed external payment data; shipping and discounts sent as price components. |
| Shopify customer or guest checkout | ByDesign account (Manage Accounts, Query Accounts) | Email or stored Shopify customer ID | Shopify → SAP ByD | Before the first order posts | Or post guest orders to one generic web account, as agreed with finance. |
| Released outbound delivery (Query Outbound Deliveries) | Shopify fulfillment (fulfillmentCreate) | Sales order reference = Shopify order ID; delivery items = fulfillment order lines | SAP ByD → Shopify | Scheduled query of newly released deliveries | Carrier and tracking number from the delivery; partial deliveries create partial fulfillments. |
| Customer invoice (Query Customer Invoices) | Shopify order metafield | Sales order reference = Shopify order ID | SAP ByD → Shopify | Scheduled | Invoice number and status for service teams; the document stays in ByDesign. |
| Shopify return or refund (refunds/create webhook) | ByDesign customer return and credit memo | Shopify refund ID + original order reference | Shopify → SAP ByD | refunds/create webhook | Goods returns follow the return-to-stock steps; refund-only adjustments go to finance for review. |
| Shopify payments and payouts | ByDesign payment clearing (clearing house or bank statements) | Shopify order ID in the payment reference | Shopify → SAP ByD | Daily | Agree with finance how card settlements are cleared against customer invoices. |
| ByDesign account (B2B customer) | Shopify company and company location | ByDesign account ID stored on the Shopify company | SAP ByD ↔ Shopify | On account creation or change | Decide which system creates B2B companies; Shopify catalogs attach to company locations. |
Download this mapping as a CSV worksheet · no email required
Options, cost and timeline
A prebuilt connector is sometimes enough. This comparison shows when each route fits, what it typically costs and how long it takes.
| Approach | Typical cost | Typical time | Fits when | Watch for |
|---|---|---|---|---|
| iPaaS connector | From about $99/month (vendor list price, checked Sep 2026) for APPSeCONNECT plans; ProcessFlow packs cost extra | Days to weeks for standard flows, depending on mapping and testing | Mainly B2C selling where the vendor’s customer, item, price and order flows match your process | Check external payment, returns, stock by site and B2B price lists; APPSeCONNECT treats changes beyond its standard flows as paid change requests |
| Custom integration outside the tenant (AIONDATA) | Quoted after a short discovery; hosting and support priced separately | Usually a few weeks including testing for a standard sync; typically two to three months with multiple stores, B2B price lists or bundles | External payment, returns, several stores or B2B pricing, and teams that want to own the code | Needs an owner for monitoring and for ByDesign and Shopify release checks, or a support agreement |
| SAP Cloud Applications Studio add-on | Quoted as ByDesign development work | Add time for deployment to each tenant and for upgrade windows | Logic that must run inside ByDesign, such as a custom web service or an outbound REST call from a business object | Uploaded per tenant, not copied to a new production tenant automatically, and timed around SAP upgrades |
| SAP Integration Suite with the Shopify adapter | Requires an SAP Integration Suite subscription; confirm licensing with SAP | Weeks to months, because the flows are built rather than installed | Companies that already run Integration Suite for other SAP interfaces | SAP’s Shopify adapter supports Shopify’s REST and GraphQL Admin APIs, but the Hub lists no ByDesign Shopify package, so every flow is built |
Vendor prices are list prices from their public pages on the date shown; confirm current pricing with each vendor.
ByDesign manages sales prices in price lists and discount lists at several levels, including base, customer-group and customer-specific lists, which the Manage Sales Price Lists web service reads and maintains. They map well to Shopify B2B, where price lists with fixed or percentage prices are attached to catalogs, and catalogs are assigned to company locations.
Shopify’s pricing page lists Shopify B2B on Basic, Grow and Advanced with up to three catalogs, and unlimited catalogs on Plus. If you have more customer price groups than your plan allows, decide which lists reach Shopify and which buyers keep ordering through a sales rep.
With several Shopify stores, each store needs rules for which ByDesign company, sales organization, site and currency its orders use. Plus lists up to nine free expansion stores; the integration treats each one as a separate channel with its own credentials, mapping and monitoring.
We run these in the ByDesign test tenant against a Shopify development store, then repeat the order and fulfillment tests in production with an internal order.
Technical details last reviewed September 26, 2026. Product capabilities and prices change; confirm them for your edition.
Sources: SAP-samples: SAP Business ByDesign API samples (web services and OData) · SAP Business Accelerator Hub: SAP Business ByDesign APIs · SAP Knowledge Base Article 2694770: ByDesign tenant lifecycle FAQ · SAP Knowledge Base Article 2136036: requesting a new ByDesign tenant · SAP Cloud Applications Studio: Web Services Quick Guide · SAP Business Accelerator Hub: SAP Business ByDesign Master Data to SAP S/4HANA Cloud Public Edition · SAP Business Accelerator Hub: Shopify Adapter for SAP Integration Suite · Shopify: REST Admin API (legacy notice) · Shopify: About webhooks (ordering, duplicates and reconciliation) · Shopify: webhook topics reference · Shopify: fulfillmentCreate mutation · Shopify: PriceList object · Shopify: B2B on Shopify for developers · Shopify: plan pricing and features (B2B catalogs, expansion stores) · Shopify: API versioning and release schedule · APPSeCONNECT: SAP Business ByDesign and Shopify integration · APPSeCONNECT: pricing
Outcomes
A mix, chosen per flow. The Manage Sales Orders web service creates orders with external payment. Custom OData services read materials, deliveries, invoices and returns, and accept batch requests. The analytics OData APIs read the stock overview. SAP lists the web services on the SAP Business Accelerator Hub, and your tenant’s Service Explorer provides WSDLs that include your extension fields.
You can for some cases, but not with external payment. SAP’s ByDesign API samples note that external payment information cannot be created using OData, so their web shop scenario creates the sales order through the Manage Sales Orders web service and uses OData for the steps that follow. Shopify orders are paid at checkout, so we follow that pattern.
Some iPaaS vendors publish one. APPSeCONNECT, for example, lists customer, item, price and sales order flows for ByDesign and Shopify. When we checked in September 2026, the SAP Business Accelerator Hub listed Shopify packages for S/4HANA but none for ByDesign. A connector is enough when its flows match your process; check how it handles external payment, returns, stock by site and B2B prices before you commit.
Usually not. An external integration calling web services and OData covers the standard order, stock, price and delivery flows. The Studio fits when something has to happen inside ByDesign, for example calling Shopify from a ByDesign action or exposing a custom web service on your own business object. Studio solutions are uploaded to each tenant and need their own testing around upgrades.
We build and test in your ByDesign test tenant and a Shopify development store. SAP’s standard package includes one test tenant and one production tenant, and SAP can provide a test tenant as a full copy of an existing tenant when you need realistic data. Communication arrangements are set up per tenant, so go-live includes repeating and checking that configuration in production.
Orders post within minutes of payment. Stock is read on a schedule, usually every few minutes for fast movers, from the stock overview that ByDesign already aggregates by site and logistics area. For a single item, the Product Availability Check web service checks availability without reserving quantity. A nightly job compares every SKU and corrects drift.
It waits in a queue with the ByDesign message, for example an unknown material, a missing price or a blocked account. A person fixes the data and replays it. Before creating anything, the integration checks for an existing ByDesign sales order with the same Shopify reference, so a replay or a duplicate webhook cannot create a second order.
Choose deliberately. Creating an account per shopper gives full history in ByDesign but grows master data quickly. Posting guest orders to one generic web account keeps master data small, with the delivery address carried on each order. We agree the rule with finance and your privacy owner before build.
Yes. Shopify companies and locations map to ByDesign accounts and ship-to parties, and customer-group or customer-specific price lists feed Shopify price lists attached to catalogs. Shopify’s pricing page lists up to three B2B catalogs on Basic, Grow and Advanced, and unlimited catalogs on Plus. Plus also lists up to nine free expansion stores, and each one needs its own order routing rules.
It changes how we package the work, not whether to start. SAP publishes migration content on the Business Accelerator Hub for moving ByDesign master data, transactional data and accounting data to S/4HANA Cloud Public Edition. We keep the Shopify side and the mapping rules separate from the ByDesign connector, so a later move swaps the ERP adapter instead of rebuilding the store integration.
You decide. We hand over the code, mapping workbook, runbook and alert setup so your team can run it, or we support it under an agreed plan. Two calendars matter: ByDesign tenant upgrades, and Shopify’s quarterly API versions, each of which Shopify supports for at least 12 months.
A standard products, stock, orders, customers and fulfillment sync usually takes a few weeks including testing. Multiple stores, B2B price lists or complex bundles typically take two to three months. Communication arrangements, business configuration changes and your tenant upgrade dates are planned in from the start.
Other pairs involving SAP ByD or Shopify.
Share your objects, volumes, and timing needs — we'll come back with a written scope.
Please share the systems and workflow—not credentials or customer records. We’ll confirm API access, scope and next steps.
Part of NVIDIA’s program for startups building with AI and accelerated computing.
About the program
Pravin’s experience includes Google and SmartBear. Sravan previously held leadership roles at JPMorgan Chase and First Republic Bank.
Meet the founders9110 Alcosta Blvd Ste H345, San Ramon, CA 94583
US-led delivery, with engineering in India. Supporting US and international organizations.