Agree where each piece of data comes from
A good data flow starts by assigning ownership of the information. M3 can own item numbers and trading terms, for example, while a PIM system maintains copy and images.
It has to be clear which system is allowed to change what. Otherwise you risk an update from one system overwriting a change made in another.
Include the difficult workflows from the start
What happens when an item is out of stock? When the customer has a special price? Or when an order has been created in M3, but the webshop never received the confirmation?
Those are exactly the situations the integration needs clear rules for. That is why we include the critical workflows in the scoping and talk about how errors should be spotted, who handles them, and how a transfer can be resumed.
For you, that means the project gets a concrete scope that both the business and IT can work with.
Your M3 environment determines the connection
M3 Cloud Edition and older or on-premise M3 environments can place different demands on the integration. Version, access, available APIs and existing customisations therefore need to be known before the technical solution is chosen.
We go through the connection options together with you and your M3 partner. If you already have an integration, we also look at which data and workflows need to be carried over.
More integrations for Infor M3
The webshop is rarely the only system that needs to be connected to M3.
- PIM: Centralise product data and streamline distribution to your sales channels – for example Plytix or Struct PIM.
- POS: Synchronise sales, stock and customer information in real time between store and ERP.
- Payment solutions: Automate transactions and reconciliation – for example Billwerk+, Clearhaus, QuickPay or PensoPay.
- Marketplaces: Automate order processes and stock synchronisation on Amazon, for example.
Get a clear basis for project and price
An integration scoping should make it easier to decide what to get started on. We take your webshop, M3 environment and most important workflows as the starting point and review what needs a closer technical assessment.
After that we can talk specifics about the scope of the project, who is responsible for what, and the price. Implementation, support, API maintenance and later changes should all be set out in the agreement you choose.