ERP Integration: When Does a Custom Connection Beat Standard Software?

Last updated: August 2026

An online shop is running, orders are coming in, and then the manual transfer begins. Copying order numbers from the shop into the ERP, updating stock levels by hand, maintaining customer data twice. Many SMEs know this all too well. The solution sounds simple: a connector. But which one, and is the standard one enough?

This article explains when standard connectors are sufficient and when a custom ERP integration makes the decisive difference, with an example calculation you can apply to your own business.

What standard connectors can do, and what they cannot

Ready-made integrations exist for the most common combinations: WooCommerce ↔ weclapp, Shopify ↔ Lexoffice, JTL ↔ SAP. These connectors cover the standard cases: transferring orders, synchronising stock levels, creating invoices.

The problem lies in the details. Standard connectors work with the fields their developers planned for, not with yours. Typical gaps:

• Custom order fields are missing — project code, cost centre or requested delivery date never reach the ERP
• No transformation — the shop knows "pieces", the ERP knows "unit A/B/C"; without mapping, errors creep in
• Timing problems — many connectors sync every 15 minutes, which is too slow for low-stock items
• Error handling — when a sync fails, often nobody notices until the customer complains
• No reverse direction — changes on the ERP side (price updates, stock leaving through other channels) do not flow back

Three scenarios where custom integration wins

Scenario 1: Complex item structure

An internet service provider sells broadband plans: each package consists of a base fee, a set-up fee and a monthly instalment, linked to a contract term and an address. No standard connector understands this structure.

For an internet provider, we built an invoice generator on top of weclapp that automatically creates invoices from the ERP data as HTML and PDF, logic that no standard connector covers.

Scenario 2: Two-way synchronisation across several channels

If you sell through three channels at once (your own shop, Amazon and a physical store), you have a stock management problem. Standard connectors usually link one channel. A custom system integration brings all channels together into a single source of truth for stock in the ERP and distributes the current stock level in real time.

Scenario 3: Industry-specific business logic

A brewery sells beer in different container sizes (keg, crate, bottle) with a deposit system. For every order, the ERP has to add deposit line items automatically, convert between container sizes and track deposit stock separately. That is not a standard feature.

Technical architecture: how custom integration works

A robust custom ERP integration follows a clear pattern:

• Webhook first — instead of polling, the source actively sends a message with every change. This cuts latency from minutes to seconds.
• Idempotency — each message can arrive more than once (network errors, retries) without creating duplicate bookings.
• Queue-based — a message queue system (Redis, AWS SQS) buffers messages when the ERP is briefly unavailable.
• Error alerting — failed transfers trigger a notification immediately, not when the customer meeting comes round.
• Logging with replay — all transferred data is logged; if something goes wrong, any transfer can be repeated.

Depending on the project requirements, we implement this with Next.js API routes, standalone Node.js services or n8n workflow automation as the orchestration layer.

Break-even calculation: when does custom integration pay off?

The most common question: what does it cost, and when does it pay for itself? An honest calculation:

Assume 3 employees each spend 45 minutes a day manually transferring data between the shop and the ERP. At €25/hour in staff costs, that is €56 a day, €1,120 a month and €13,440 a year. With us, a custom integration that eliminates this work starts from €4,500 (system integration); the exact effort depends on the scope. In this example, the costs would be recovered after roughly four to six months.

On top of this come indirect costs: errors in manual transfer (wrong quantities, missed orders), customer satisfaction and scalability. At 50 orders a day instead of 5, a manual solution does not scale; the integration does.

weclapp-specific considerations

weclapp is widely used among SMEs in Austria and Germany and offers a well-documented programming interface (REST API) through which other systems can read and write data. There are a few specifics to bear in mind during integration:

• Rate limits — weclapp limits API requests depending on the plan. Bulk operations have to be batched.
• Webhook configuration — weclapp supports webhooks for order changes; configuring them requires HTTPS and correct event filters.
• Custom fields — your own fields in weclapp can be read and written via the API, but require specific field names.
• Multi-tenancy — with several weclapp tenants, the integration must keep each tenant's data cleanly separated.

What does a custom ERP integration cost?

The range is wide because it depends on the scope. A simple one-way sync (shop → ERP, standard fields) can be implemented in 3–5 days. A complex two-way integration with several channels, error handling, monitoring and documentation takes 2–4 weeks.

We always recommend starting with an MVP: automate the most important use case first, measure, then expand. Get in touch with us about custom development based on your specific system landscape.

Further reading

Related: When does a custom weclapp integration pay off instead of standard software?