Introduction
Integration of your ERP data with Luminovo is simple, but includes a few steps, which may differ depending on your IT infrastructure and the cleanliness of your ERP data.
1. Understand Your Data
Before you start, it is important to understand which data is available in your ERP system and can be extracted. Already looking into the Point 2, check, what can be done?
2. Decide on the integration type
There are two ways in which you can integrate with Luminovo. They are different in complexity and their power.
Integration type | Time estimates | Developer Time | What speaks for it |
Upload .csv files | 2-3 days | 2+ hours | - Easy and quick to implement |
Luminovo Rest API (recommended) | 5-7 days | 6+ hours | - Build powerful integrations |
💡 The time estimates for the implementation heavily depend on the initial quality of the data. If your data is not clean, both .csv and API integration will take longer! Read more on cleanliness of your data here: ERP/PLM Data Cleanliness
The decision on which integration type to choose is not easy. The .csv integration seems like the more attractive solution, offering a quick way to kick-start your usage of Luminovo. Indeed, many start with .csv to get the first data in Luminovo.
However, the .csv integration is only suitable for the most basic integrations.
💡 To build advanced End-to-End integrations, automating even more and saving even more time in your internal processes, an API integration is a must.
Available integration endpoints
3. Decide on integration use-cases
In the above table, you can see all available integrations with Luminovo. Depending on what integration type you are going for, decide which integration use-cases are the most important for you. Note, most of the below integrations are only available via the REST API.
Luminovo’s recommendation
💡 From our experience, there are a couple of integration use-cases that show to bring the most value to our customers. Those are the integration of components, inventory, and offers
Start with synchronising your component library and stock data. Those are must-have integrations!
Import Components (supported in .csv upload)
Import Inventory (supported in .csv upload)
Next, import the offers from your suppliers
Import Offers (only supported with the Rest API)
Import Customers
Import Assemblies
Data back to your ERP: get the costed BOM
Export Costed BOM
Export Manufacturing Costs (for
Product Costingusers)Export Assembly Costs (for
Product Costingusers)
Explore further integration possibilities with our API documentation.
Build powerful automations
💡 Using Luminovo webhooks to e.g. monitor the status of RfQs opens a broad range of automation capabilities
💡 If you have a particular automation in mind that you want to build with Luminovo but don’t know yet how to do it, shoot us a message on integrations@luminovo.com!
Our customer builds many different E2E integrations with Luminovo. Just to name a few examples:
Create and send purchase orders
Create sales offers
Automatically create IPNs in the ERP system
4. Map the data
After you decide which integrations you are going to build, you need to understand which data is needed to feed the endpoints. This information can be found in the API documentation or, if you are only going for the simplest integration use cases (components + inventory), in the documentation for the .csv upload.
Example 1: integrate components and inventory upload via the API
If you decide to integrate the components and inventory upload endpoints via the API, here is an example of how you can do the mapping of your data to Luminovo’s API.
Get an overview of all available data fields (refer to the documentation)
Understand which data points are available in your ERP system or data warehouse
Map the data
You can use this example excel table for data mapping
Discuss the mapping with your procurement expert to ensure that all data fields are mapped correctly
Example 2: integrate components and inventory upload via the .csv upload
In this case, you simply need to provide the data in a format described in the documentation for the .csv upload
5. Upload the data to Luminovo
💡 You can get your API key in Luminovo’s support chat.
💡 You can start testing your data uploads on the live system, if there’s no production data on it which is being actively used by your procurement team.
💡 If your tenant already has some production data, it’s better to do tests in a separate tenant. Contact integrations@luminovo.com if you need one!
During this step, you need to test sending the data to Luminovo. This step depends on the upload method you are using (CSV vs API) and is described in the corresponding documentation.
6. Set up a scheduled upload
💡 After you have tested and verified the data you upload to Luminovo, set up a scheduled data exchange.
This step will also vary depending on the type of integration you are seeking. For the .csv upload, the upload once/day is enough.
For the REST API connection:
Components Import: This endpoint is not synchronous, and the data sent to it gets processed only once/day at midnight
All other endpoints: those endpoints are live, and you can send or receive the data on demand.
7. Monitor the data quality
💡 After you’ve set up the uploads, monitor the quality of the data linking in your components library. Make adjustments when needed.