Real-time
Two-way sync
Changes in Bill or Shopware instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ E-commerce
Bill to Shopware integration — real-time, two-way sync
Keep Bill and Shopware in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
Adopted by fast-scaling companies moving mission-critical data in real time
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Bill and Shopware
Turn every Shopware order into clean revenue: Bill and Shopware keep customers, orders, and payment status aligned in real time, in both directions.
Shopware runs the storefront — the catalog, the orders, and the buyers placing them. Bill records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.
Stacksync syncs Bank Accounts, Vendor Credits and Credit Memos, Bills, Vendors in Bill with Media, Products, Categories, Customers in Shopware field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Shopware, its paid-or-overdue state from Bill — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.
The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.
Common use cases
- 01 Read Payments and payment status into a reconciliation database once bills are marked paid in BILL.
- 02 Read approved Bills and their line items into a Postgres warehouse for spend, accrual, and cash-flow reporting without CSV exports.
- 03 Stream new `order` records with their `order_line_item`, `order_delivery`, and `order_transaction` rows into a warehouse or accounting system for revenue and fulfillment reporting.
- 04 Sync `customer` records two-way with a CRM so support and marketing see order history while reps write updates back onto the account.
Common sync patterns
One customer master
Where both systems keep customer or buyer records, an edit in either propagates to the other, ending duplicate accounts and mismatched contact details.
Catalog and pricing stay aligned
Products, SKUs, and prices maintained on one side propagate to the other, so what the store sells and what the ledger books stay in step.
Refunds and credits reconcile
Refunds, cancellations, and credit notes raised in either system update the corresponding record in the other, keeping balances honest on both sides.
What you can sync between Bill and Shopware
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Bill objects | Shopware objects | How this pairing syncs | |
|---|---|---|---|
| Customers AR customer master records; mapped to customer/account records in a CRM or ERP so finance and sales share one view. | Customers Storefront customer accounts (`customer`) with addresses and group; synced two-way with a CRM or support tool. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Vendor Credits and Credit Memos AP and AR adjustments applied against bills and invoices; synced so balances stay accurate on both sides. | Orders Order headers (`order`) with totals, state, and sales-channel reference; read out to accounting and written back for status updates. | Vendor Credits and Credit Memos is specific to Bill and Orders to Shopware — each maps to any object or custom field on the other side. | |
| Bills Accounts-payable amounts owed to vendors, with bill line items; read and created via /v3/bills and pulled incrementally by filtering on createdTime/updatedTime. | Order Line Items Per-order product rows (`order_line_item`); read alongside the order for revenue and fulfillment reporting. | Bills is specific to Bill and Order Line Items to Shopware — each maps to any object or custom field on the other side. | |
| Vendors Payee master records; synced two-way with vendor/supplier tables in an ERP or accounting system so new payees don't have to be re-keyed. | Order Deliveries Shipping records (`order_delivery`) carrying delivery state and tracking codes; written back from a 3PL or WMS. | Vendors is specific to Bill and Order Deliveries to Shopware — each maps to any object or custom field on the other side. | |
| Invoices Accounts-receivable invoices sent to customers; created and read via /v3/invoices to keep billing status aligned with the ERP or CRM. | Order Transactions Payment records (`order_transaction`) holding payment method and state; read to reconcile against a billing or finance system. | Invoices is specific to Bill and Order Transactions to Shopware — each maps to any object or custom field on the other side. | |
| Payments Outgoing vendor payments and received customer payments; read for reconciliation and created to schedule bill pay. | Sales Channels Per-storefront configuration (`sales_channel`); used to scope and consolidate orders and customers across multiple storefronts. | Payments is specific to Bill and Sales Channels to Shopware — each maps to any object or custom field on the other side. |
How changes propagate between Bill and Shopware
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Bill Shopware Sub-second propagation
DetectionBill notifies Stacksync of record changes through webhook events. Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on.
DeliveryEach detected change is written to Shopware through its API, with automatic retries and rate-limit backoff.
Shopware Bill Sub-second propagation
DetectionShopware notifies Stacksync of record changes through webhook events. App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field.
DeliveryEach detected change is written to Bill through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Bill: 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
- Shopware: No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores.
What ships with Bill ⇄ Shopware
Connect Bill and Shopware for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Bill–Shopware connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Bill or Shopware data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Bill or Shopware record.
Observability
Monitoring
Track your Bill ⇄ Shopware sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Bill and Shopware.
How the Bill and Shopware connectors work
Bill
- Integration surface
- REST/JSON (BILL v3 Connect API)
- Authentication
- Session-based: POST /v3/login with username, password, organizationId, and a developer key (devKey) returns a sessionId that is passed with the devKey as headers on every subsequent call; OAuth is available for partner/embedded apps
- Change detection
- Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback
- Capabilities
- read · write · webhooks
- Rate limits
- 20,000 requests per developer key per hour; login (POST /v3/login) capped at 200/hour; maximum 3 concurrent requests per developer key per organization. Spend & Expense API is a separate token at 60 calls/token/minute.
Shopware
- Integration surface
- Admin API (REST / JSON:API) with a bulk POST /api/_action/sync endpoint
- Authentication
- OAuth 2.0 — client-credentials grant using an Integration's Access Key ID + Secret Access Key, or resource-owner password grant for a user; access tokens expire after 10 minutes
- Change detection
- App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields
- Capabilities
- read · write · webhooks
- Rate limits
- No general throttle on Admin API entity endpoints; Shopware's RateLimiter guards only specific routes (login, oauth, password reset, guest order/contact) and is configurable on self-hosted stores
How it works
How to connect Bill to Shopware — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Bill and Shopware with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Bill
connected
Shopware
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Bill and Shopware objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Bill ⇄ ShopwareCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Bill ShopwareCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Bill and Shopware integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Bill and Shopware: authenticate both systems, choose the objects to sync (such as Bill's Customers and Vendor Credits and Credit Memos), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Bill: List endpoints support filtering and sorting on createdTime and updatedTime with ISO 8601 date-time ranges, which sync engines use to pull only incremental changes. Shopware: Prices are stored per currency as a nested price array with net and gross values, and products model variants as parent/child rows, so field mappings must handle nested structures. Stacksync's field mapping accounts for these differences between Bill and Shopware without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Bill and Shopware records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Bill and Shopware connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Bill–Shopware integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Bill and Shopware. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Bill: Webhook event subscriptions (POST /v3/subscriptions) for bills, vendors, payments, invoices, and bank accounts, with polling on createdTime/updatedTime list filters as the fallback. On Shopware: App-system webhooks on entity events (product.written, order.written, customer.written) deliver the changed record's primaryKey and updated field names; otherwise poll on the updatedAt / createdAt fields. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
SECURITY
Security teams trust Stacksync
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Related integrations
Every pair below is a real-time, two-way sync. Search all 458 integrations available for Bill and Shopware.
Popular · 8 of 458
-
Bill ⇄ Nuorder -
Bill ⇄ Shipwire -
Bill ⇄ Akeneo -
Bill ⇄ Bigcommerce -
Shopware ⇄ Stripe -
Shopware ⇄ Coupa -
Shopware ⇄ Zuora -
Shopware ⇄ Adyen
No integrations match .
