BigCommerce Store Connector

A BigCommerce store rarely stays simple. It starts as a B2C storefront with a handful of SKUs, then a customer group appears with negotiated pricing, then a second warehouse, then a wholesale channel that expects net terms and a credit limit. At that point the storefront and SAP Business One are two systems each convinced they hold the real customer, the real price and the real stock figure. Somebody exports orders once a day and keys them in. Somebody else maintains the same price twice, once in a Price List in SAP B1 and once in a BigCommerce price list, and the two drift within a quarter. Credit-held customers keep checking out. Stock published to the store is yesterday's number. None of this is dramatic on any given day, and all of it is expensive over a year.

This app is built to order. ECOSIRE does not publish a ready-made download and there is no trial installer, because the value is in mapping your catalogue, your customer groups and your pricing rules correctly. We scope, quote a fixed price, then build and install against your company database. Typical lead time is two to four weeks.

What ECOSIRE builds

An integration service plus in-client SAP Business One objects. Documents are created through the SAP Business One Service Layer (OData/REST) so standard validation, numbering series and approval procedures apply exactly as they do for a user working in the client. The DI API is used where the Service Layer has no equivalent or where a bulk operation needs it. Mapping tables, run configuration and the operations log live in User-Defined Tables surfaced through User-Defined Objects, so your administrator maintains them inside SAP B1 rather than in a separate web console.

Orders and documents

Each BigCommerce order becomes a Sales Order in SAP Business One, with the store order ID written to a User-Defined Field so reruns are idempotent and support can trace a storefront order to a document number. Line items carry the mapped Item Code, quantity, the price actually charged, and any coupon or order-level discount allocated according to the rule you choose at scoping. Shipping and handling post as freight lines or as service lines against nominated G/L accounts. Tax is applied using the tax codes and determination already configured in your company, not recalculated by the connector. Depending on your process the connector then raises the Delivery and A/R Invoice, or hands the Sales Order to your warehouse team and picks up the documents they create.

Customers, customer groups and credit

Storefront shoppers map to Business Partners in OCRD. For pure B2C traffic a single channel Business Partner keeps the master data clean. For B2B you almost always want one Business Partner per trading customer, matched on email or on an account code the customer enters at registration. Where a BigCommerce customer group corresponds to a trading agreement, the connector aligns it to the SAP B1 Business Partner group, Price List and payment terms. Credit limit and account status held in SAP B1 can be surfaced back to the store so a customer already over limit is handled by your rules rather than discovered a week later.

B2B price lists and special prices

This is the piece most integrations do badly. Pricing stays authoritative in SAP Business One. The connector publishes from a nominated Price List, and where a Business Partner has Special Prices or a volume discount structure, those are published to the corresponding BigCommerce customer group price list so the buyer sees their contracted price at the point of purchase instead of a generic list price. Currency, unit of measure and price-per-unit conversions are handled explicitly and confirmed with you during acceptance rather than assumed.

Catalogue and inventory

Item attributes you choose from the Item Master, description, weight, dimensions, barcode and selected UDFs, can be pushed to the store so a new product does not need double entry. Stock is calculated from SAP Business One warehouse quantities, In Stock less Committed with an optional Ordered component, per warehouse or per warehouse group, with a per-item buffer so a counting error cannot cause an oversell. Publishing runs on a schedule and can also be triggered by inventory-affecting documents, so a Goods Receipt PO on a fast mover updates the storefront in minutes.

Returns and credits

A storefront return or a refund raises a Return document and an A/R Credit Memo linked to the original invoice, keeping the base-to-target trail intact. Refund handling can be posted or held for approval depending on value, using the approval procedures you already run.

Who it is for

Mid-market companies running SAP Business One as the system of record with a BigCommerce storefront, particularly those running B2B alongside B2C, multiple warehouses, or negotiated customer pricing. It suits distributors and manufacturers who sell to trade accounts online and need the ERP to remain authoritative for price, credit and stock. It is not a storefront design service and it is not aimed at businesses without an ERP.

Technical approach and scope boundaries

The connector targets SAP Business One 10.0 on Microsoft SQL Server or SAP HANA, on-premise or cloud-hosted. It needs outbound access to the BigCommerce API and network access to your Service Layer endpoint, plus a dedicated service user. No SAP standard tables are modified; we add UDFs, UDTs and UDOs only. We do not act as a payment processor, we do not build storefront themes, and we make no certification or partnership claims about any platform vendor.

How delivery works

We begin with a scoping call, usually ninety minutes, covering catalogue structure, customer groups, pricing rules, warehouse layout, tax setup and where you want the document boundary between the store and the warehouse. You then receive a written scope and a fixed quote, and no build starts until you approve it. Development runs against your data structures where you can supply them. Installation goes into your test company database first, where you run acceptance with real orders, real trade accounts and a real price list, and only after sign-off do we install into production. Every object we add has a documented rollback, and cutover is scheduled with you.

After go-live

You get a support window for defect fixes and configuration help, a runbook covering reprocessing and error handling, and recorded training for the operations and finance users. Storefront APIs evolve, so continuing maintenance after the included window is offered as a separate support agreement quoted up front rather than left open.