Magento is a powerful but complex shop system, and the larger the range, the more important it is that product data, stock and orders are reliably reconciled with ERP and marketplaces. I develop custom integrations that connect Magento 2 with these systems, without anyone retyping data or maintaining it twice.
What I build for Magento
- Connecting the ERP: Items, stock and prices come from the leading system into the shop, and orders go back to the ERP as sales orders, for example to weclapp.
- Keeping product data in sync: New items and changes to items, prices and product data are reconciled between Magento and the connected systems.
- Syncing stock: Available stock is transferred to the shop continuously, so you never sell more than you can deliver.
- Transferring orders: Orders from Magento go automatically to the ERP, supplier or fulfillment partner, and shipping and status come back.
- Tradebyte and marketplaces: With Magento as the shop, product data and stock can be transferred to Tradebyte and marketplaces.
- Reporting: Order, revenue and item data can be prepared for analysis, see Reporting.
Excerpt from my Magento projects
- weclapp and Magento 2: A custom interface that I develop and maintain for a client. weclapp supplies the product data for the Magento 2 store, and orders from the store are transferred back to weclapp.
This is an excerpt from my completed projects, not a complete list of my services. Magento offers REST and GraphQL interfaces, and whatever else you need, I build individually. If your project does not appear here, just get in touch.
Ready-made extension or custom integration?
For many ERP systems and marketplaces there are ready-made Magento extensions. They are a good choice if your process follows the standard. The comparison shows when a custom integration fits better:
| Ready-made extension | Custom integration | |
|---|---|---|
| Fits if | Your process follows the standard | You have special logic or combine several systems |
| Customization | Limited to none | Fully adaptable |
| Counterpart | Only systems supported by the extension | Any system with an API or file interface |
| Load on the shop | Every extension runs inside the shop and needs updates | Runs outside the shop, no additional extension needed |
| Costs | Ongoing license fees | One-time development, running costs usually lower |
Technology: how I work with Magento
I access products, stock, orders and customers via Magento’s REST and GraphQL interfaces. Data is exchanged with the counterpart via REST, GraphQL, JSON, XML, CSV or FTP, depending on the system. We agree together, per data flow, which data leads in Magento and which in the ERP.
Process
- Clarify data flows: Which data goes in which direction, which system leads, which special cases are there?
- Build and test: I build the integration and test it with real data before it goes live.
- Go-live and operation: The integration runs in the background, runs are logged, and I implement process changes afterwards.
Every project is different, so you receive an individual quote after we have agreed the details.
Frequently asked questions
Which Magento version do you support?
My focus is Magento 2. For an older version, we first check whether and how the integration can be implemented sensibly.
Which ERP systems do you connect to Magento?
weclapp, which I have implemented, as well as other systems such as JTL or Xentral.
Can Magento be the leading system?
Yes. Which system acts as the leading system is decided individually per data flow.
Do I need an extension in Magento for the integration?
As a rule, no. The integration uses Magento’s interfaces, so you do not have to install and maintain an additional extension in the shop.
You run a Magento shop (or Magento 2) and need a connection to ERP or marketplaces? Tell me briefly about your project.
Go to contact pageManufacturer: Adobe Inc. — more information: https://business.adobe.com/de/products/magento/magento-commerce.html (opens the manufacturer's website)