Technical architecture
Platform architecture
BEWISE is not a simple connector but a full middleware layer. Below the technical setup for IT architects and developers.
BEWISE is not a simple connector but a full middleware layer. Below the technical setup for IT architects and developers.
Every order, stock mutation or customer change goes through a standardised pipeline — regardless of platform or ERP.
Webhook ingest & polling adapters capture events from external systems.
Universal data model that normalises platform-specific payloads.
IntegrationRouteResolver determines the correct flow per tenant and source.
Destination adapters translate canonical DTOs into ERP API calls.
5 attempts, exponential backoff (60→300→900→1800s). Specific error codes like SKU_NOT_FOUND fail immediately.
Full tenant isolation at database level via tenant_key. Platform admins see all tenants; users only their own scope.
Field mappings, pricing mode (destination/payload) and status filters configurable per integration flow via Filament UI.
Two panels: Admin panel for platform admins and power users; Portal for end-customers with simplified view.
Webhooks for direct events (WooCommerce, Shopify); cursor-based polling for Shopware, Bol.com and SW-Retail.
API credentials stored as encrypted JSON per connection. Never in plain text in the database.
BEWISE uses a strict three-tier model for settings: global, per connection and per flow. Every setting has exactly one place.