E-Commerce Integration Development
Connect Your Shop, ERP and PIM Reliably
Data goes missing between shop, ERP and warehouse every day, and usually the customer notices first. I build e-commerce integrations that move product data, stock, prices, customers and orders reliably between your systems.
You work directly with me, André Flitsch. I establish which system owns which data first. What follows is an interface that works outside the happy path too.
When Systems Only Appear to Understand Each Other
Plenty of interfaces work until somebody looks closely. Stock is mostly right, orders arrive eventually, and a nightly import gets repaired by hand each morning. That is not a stable integration, it is a process with hidden supervision.
Nobody knows the source of truth
Price, stock or product copy is maintained in several systems. Changes overwrite each other and nobody is certain which value should win.
Failures stay invisible
An import completes green while records are missing. An API stops responding and nobody is told. The problem surfaces when a customer calls.
People are the interface
CSV files get emailed, orders get re-entered, discrepancies get resolved by phone. The process works only because somebody is always watching it.
Every change threatens operations
A new field, an update or another sales channel breaks assumptions that were never written down. Small changes become slow and risky.
What I Connect
Shop and ERP or inventory management. Transfer orders, synchronise stock, exchange prices and customer data, and write status changes back reliably.
PIM and sales channels. Distribute product data, categories, media and translations from one source to shop, marketplaces and other channels. I work with Akeneo regularly, for example at Kaufhaus der Berge, where PIM and a Magento multi-store work together. The principle holds regardless of product: one system owns the product data, everything else receives it.
CRM, marketing and marketplaces. Move customers, consents, campaign data and order information only where they are needed, with clear ownership of every field.
APIs, import, export and data pipelines. REST, GraphQL, files, queues, or older systems with no modern API. The technical shape follows the system landscape, not the other way round. Event-driven synchronisation between ERP, PIM and storefront belongs here too.
An Interface Is Only Finished When Failures Are Visible
Reliability does not come from a successful test run. A production integration needs clear data ownership, traceable transformations, controlled retries, and a way back when something goes wrong.
-
Establish data and ownership
Where does each piece of data originate? Which system may change it? What ordering and what delay are acceptable?
-
Define the interface contract
Fields, formats, statuses, required values and failure cases get described before they disappear into code.
-
Build it repeatable and observable
Processing has to survive being run twice. Failures are logged, reported, and can be retried deliberately without creating duplicate orders or wrong stock levels.
-
Roll out under control
Test with realistic data, enable in stages, compare results, keep a way back. Afterwards I document operation, error handling and responsibilities.
From Live Integration Projects
-
Built the integration layer for a multi-brand platform: one connection instead of one per brand, with clear ownership of which system holds product data, prices and stock.
-
Automated fulfilment across several warehouses: orders reach the right process without manual routing, even when more than one location could serve the same order.
-
Akeneo PIM integration for a Magento 2 multi-store in DE, EN and IT, keeping product data consistent across languages and channels. Ongoing development partnership.
Most of my work is white-label development for agencies and ships under their name. What is listed here is the part I am allowed to name.
Magento Is Often Involved, but Not the Boundary
Magento is a central component in many of my integration projects. The actual work usually starts outside the shop: data models, inventory management, product maintenance, fulfillment, and the question of which system makes which decision. For dedicated backend work on Magento itself there is the Magento development page.
If you want to build, modernise or extend a shop into a B2B portal, the online shops page describes the broader offer.
If the problem is mainly recurring manual work, quotes, documents or reports that cost time every week, the automation page goes further.
Common Questions
Can you connect our online shop to our ERP?
Yes. First I establish data ownership, the interfaces available, volumes, freshness requirements and failure cases. That decides whether a direct API, middleware, files or a combination makes sense.
What if a system has no modern API?
Older systems can usually still be connected reliably, through files, database exports or defined import processes. What matters is making the constraints visible and not pushing error handling onto people.
Does everything have to sync in real time?
No. Stock or order status can be time-critical while other data is fine every few hours. Real time is only better when the business benefit justifies the extra work.
Can you take over an existing, unstable interface?
Yes. I reconstruct the data flow, the responsibilities and the failure patterns, keep operations safe, and improve the integration step by step. A full rebuild is not automatically the first move.
Will you work with our existing ERP vendor?
Yes, that is the norm rather than the exception. I agree fields, formats and failure cases with them and own the side that belongs to the shop. What matters is that responsibilities are named before data starts moving.
Do you only work with Magento?
No. Magento is significant experience, but integration work also covers ERP, inventory management, PIM, CRM, marketplaces, files, APIs and bespoke systems.
Where Is Your Data Going Missing?
Tell me briefly which systems are involved, what data should flow, and where manual work or errors happen today. I will tell you how I would scope the job.