NL EN

Magento connected to the rest of your business.

Orders, stock and prices that find their own way. With it written down up front which data goes where, and what happens when something goes wrong.

Discuss your integration Integrations between sites
Drawing of Magento in the middle, with lines to an ERP, the accounting software, the stock system, a carrier, a marketplace and a second shop. A small packet of data travels along each line.ERPAccountingStockShippingMarketplaceSecond shop

Retyping is an integration, just with people.

Entering orders into the ERP by hand, updating stock in two shops, copying tracking codes into an email. It works, until someone is ill, it gets busy or a number comes across wrong.

A good integration does the same work without mistakes and without anyone having to think about it. A bad integration also runs without anyone thinking about it, and that is exactly the problem. So we write down up front what it does, and measure afterwards whether it keeps doing it.

What we connect.

Any system with an API. These are the integrations a Magento shop needs most often, with what usually travels back and forth.

System For example What goes back and forth Direction
ERP AFAS, Exact, SAP Business One, Microsoft Dynamics Orders, customers, prices, stock, product data Both ways
Accounting Exact Online, Moneybird, Snelstart, Twinfield Invoices, credit notes, payments Magento to accounting
Stock and warehouse A WMS, or the stock in your ERP Stock per location, shipping status, returns Both ways
Shipping PostNL, DHL, DPD, Sendcloud Labels, tracking, pickup points Both ways
Product information (PIM) Akeneo, Pimcore, or a supplier feed Product copy, images, specifications, translations PIM to Magento
Marketplaces bol.com, Amazon Listings, prices, stock, orders Both ways
Customer contact and email A CRM or email marketing package Customers, orders, newsletter consent Magento to CRM

The packages are examples of software with an API. Whether an integration with your package is possible, and how, we find out for you before you are committed to anything.

Integrations between sites.

Not every integration goes to an ERP. Often two shops, or a shop and a website, need to talk to each other. That works, as long as it is settled up front which site is the source for what.

Several shops, one stock
Two or more shops, in Magento or elsewhere, selling the same stock. What sells in one shop is immediately no longer for sale in the other.
A business and a consumer shop
One product catalogue, two shops with their own prices, terms and look. You maintain the products in one place.
Magento and WooCommerce
A smaller shop or a brand store in WooCommerce that exchanges products, stock or orders with the Magento shop.
A website that reads from the shop
A WordPress site or another website that shows Magento products or prices, without anyone entering them twice.
Suppliers and dropshipping
A supplier’s stock and prices in your shop automatically, and orders that go to that supplier automatically.

How an order flows.

An example of a shop with an ERP, a warehouse, a carrier and accounting software. Nobody retypes anything.

  1. Order

    A customer checks out in Magento. The order goes into the queue.

  2. ERP

    The integration puts the order into the ERP, with customer, lines, VAT and shipping method.

  3. Warehouse

    The warehouse packs the order. Stock goes down, in the ERP and in the shop.

  4. Shipping

    The label is created and the tracking code goes back to Magento and the customer.

  5. Accounting

    The invoice and the payment land in the accounts, on the right ledger account.

What a good integration does

One source per piece of data

For each kind of data we agree which system is in charge. For example: stock and prices come from the ERP, product copy from Magento. That way two systems never overwrite each other.

Straight away or on a schedule

An order has to go through at once. Stock can often run on a fixed schedule. We choose per piece of data what is needed, so the integration puts no needless load on your shop or your ERP.

Through a queue

Messages go through a queue. If the ERP is down for a moment, the orders wait and go through as soon as they can.

Never twice

A message that arrives twice must not become two orders. So an integration we build recognises what has already come in.

A log

Every exchange can be traced: what went, when, and with what result. If someone asks where order 1234 went, the answer is there.

An alert when it keeps failing

If something still fails after a few attempts, we get an alert, and so do you if you want. Not only when a customer calls because their parcel has not arrived.

The integration plan

Before we build, it is written down:

  • Which data goes, field by field, and which system is the source for each
  • In which direction, and straight away or on a fixed schedule
  • What happens on an error: how often we retry, and who gets an alert
  • How we test: which orders, returns and edge cases we check before it goes live
  • Who manages what after go-live, and what that costs per month

The plan is yours. Even if you end up having someone else build the integration.

Questions

Which systems can you connect Magento to?

Almost any system with an API, which covers most ERP, accounting, stock and shipping packages. Sometimes a good ready-made module already exists; then we recommend it and set it up. If there is no module, or the existing one does not do what you need, we build the integration ourselves.

What happens to orders when the ERP cannot be reached?

They wait in the queue. The integration tries again, and as soon as the ERP is back, the orders go through in the right order. They are kept until they are processed, and an order that has already arrived is not created a second time. If it keeps failing, we get an alert and find out what is going on.

How quickly does an order reach our ERP?

We agree that per integration, and it depends on what your ERP can handle. We usually send orders on straight after checkout. Stock and prices often run on a fixed schedule, because pushing every change at once puts needless load on your shop and your ERP. The integration plan says how often, for each piece of data.

Can two online shops share the same stock?

Yes. We agree which system keeps the stock, usually the ERP or the main shop, and have the other shops read from it and report their sales back to it. That works between two Magento shops, and also between Magento and WooCommerce or another shop with an API.

Our existing integration keeps failing. Can you take it over?

Yes. We start with the logs and the code, if there are any, and find out where it goes wrong. Often an integration can be repaired. Sometimes rebuilding is cheaper than repairing it again and again, and then we say so, with the reason and a fixed price for both routes.

What does a Magento integration cost?

That depends on the systems and on what has to go back and forth, so you get a proposal up front: a fixed price for building it, or an hourly basis if the scope cannot be pinned down in advance, and a fixed monthly price for managing it. It starts with the integration plan, which says exactly what the integration does, so the price means something.

More about Magento

Tell us what you run.

An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.

Get in touch

or email [email protected]