One integration. Many possibilities.

The problem behind the request

ERP integrations often accumulate as separate pieces of custom code. Each new connection brings another host, another payload, and another implementation to maintain.

The opportunity was to turn those repeated decisions into configuration while keeping the integration close to the business events that trigger it.

Make variation configurable

I built an ERP integration system with an administration interface for the ERP host, target entity, and payload. That allowed the pieces that change between integrations to be managed as configuration.

Connecting the system to Shopware’s Flow Builder made it possible to trigger integration workflows through the platform’s existing event-driven tools.

Keep the abstraction useful

The important design decision was deciding what belongs in configuration and what should remain in code. The goal was to replace repeated custom integrations with one maintainable approach, without hiding the business logic behind unnecessary complexity.