All terms

Glossary

ERP integration

Connecting a system to inventory management, so that stock, prices, orders and documents are not maintained twice.

The integration decides which system holds the truth. Without that decision two stock levels emerge, they drift, and nobody knows which is right.

Technically the range spans from a modern interface to a nightly file exchange, depending on the age of the system.

How you notice it

  • Orders are transferred into the ERP by hand.
  • Stock levels differ between shop and ERP.
  • The ERP vendor only knows nightly file exchanges.

Frequently asked

What is the most common source of failure?

The assumption that the ERP is always reachable. It is not: maintenance windows, locks, year end closing. Everything going into the ERP belongs on a queue with retries, otherwise orders are lost exactly when it is expensive.

Read moreOnline shop with in-store integration

Where this comes up in my work

Building online shops

Online shops for retailers whose standard shop fails at the integration: inventory management, point of sale and store stock in real time, in-store pickup, search and product recommendations.

To the service

Process automation

Replacing manual workflows with real systems: wired into the software you already run, with permissions and an audit log instead of a chain of tools.

To the service

Backend development

Backends for SaaS and platforms that hold under real load: Go and PHP 8, event-driven, with tenant isolation and recovery designed in.

To the service

Automating invoice processing

From the incoming document to the posted entry without retyping: read XRechnung and ZUGFeRD, match against the purchase order, route the approval, hand over to your ERP, with a full trail.

To the service

Related terms

CachingMessage queue