Integration with ERP systems.
The problemThe same order is entered twice, and the stock on the website lags behind the warehouse.
Products, stock and prices come from the ERP, and orders from the website go back into it as documents.
It fits when
- Products and stock are kept in the ERP and entered into the store by hand.
- Orders from the website are retyped into the accounting or warehouse system.
- Prices differ between the ERP and the website, and that leads to errors.
We don’t promise a ready-made connector for every ERP: the scope depends on the interfaces and documentation of the specific system.
How the work changes
- TodayStock is entered into the store by hand AfterStock comes from the ERP on a schedule or on change
- TodayOrders from the website are retyped AfterThe order enters the ERP as a document
- TodayPrices differ between the systems AfterPrices are kept in one place
What we build
What the solution includes.
-
01
Products
Codes, names, attributes and categories from the ERP to the website.
-
02
Stock
Per warehouse, updated on a schedule or on change, depending on what the system supports.
-
03
Prices
Price lists and discounts from the ERP instead of keeping them in two places.
-
04
Orders and documents
Orders from the website go into the ERP; statuses and documents go back to the customer.
-
05
Exchange log
What went through, when and with what result; a retry and a notification on error.
What the integration brings
Advantages
- No double entry of products and orders
- Fewer errors in stock and prices
- A log: you see what was exchanged and when
What to plan for
- Dependence on the ERP’s API and documentation
- The quality of the data in the ERP determines the result
- Changes by the ERP vendor may require adjustments
Process
How we work.
-
01
Analysis of the systems
What interfaces and documentation the ERP has, what data and in which direction.
Result: exchange table
-
02
Mapping
Codes, fields, units of measure and rules for conflicts.
Result: mapping approved
-
03
Development and testing
An integration with a log, tested on a copy of the data.
Result: exchange verified
-
04
Launch and monitoring
Launch, error notifications, support.
Result: data exchanged
What we need from you: Documentation for the ERP’s interfaces, test access, a contact at the system vendor.
What we clarify before we quote
The answers determine the scope, timeline and price. You don’t need to know them all — we clarify them in the first call.
- 01Which ERP system do you use, and what interfaces does it provide: an API, scheduled files?
- 02Which data, in which direction and how often?
- 03How are codes, units of measure and customers matched?
- 04Who is the contact at the system vendor?
Technologies
Python, Java or PHP for the data exchange services — depending on the systems on both sides. The method — an API, scheduled files or another supported interface — depends on their documentation.
- Python
- Java
- PHP
Questions
Questions about ERP integration.
General questions about price, timeline, handover and support are in Contact.
Do you work with our ERP system?
We’ll give a specific answer after reviewing the documentation.
What matters is the interfaces the system provides: an API, file exchange or database access. After the review we tell you what is possible and with what scope.
How often is the stock updated?
Depending on what the ERP supports.
On a schedule (for example every 15 minutes) or on change, if the system sends notifications. We set the frequency together, based on the load and the need.
Tell us which ERP you use and what is entered by hand today.
The form has a service selected; you can change it.