Another year, another project for Merida Sp z o.o. This time, a need for a new EDI system arose.
Merida Sp. z o.o.
B2B & ERP integration
PHP, Symfony, Postgres, REST API, Vue.js
Year of implementation
What is EDI?
If you work in the commercial industry, you probably already know that EDI stands for Electronic Data Interchange. Generally, it is about the exchange of commercial and accounting documents in electronic form. This type of software works well when you have a certain pool of business partners from whom you accept orders and provide them with invoices and goods issue documents (generally speaking an accounting document). The functionality is similar to the system of a typical e-commerce system, but in the case of EDI, the scope of the mechanism in which order data is received can be significantly extended and support, for example, mass import / export of data in various formats. This type of approach is to allow the handling of large orders or group orders carried out for branches of large companies.
The role of the EDI2 project is to receive the order data from contractors in the simplest possible way (also in a mass manner) and make accounting data available to contractors. In the case of EDI2, a dedicated cart system based on lists was prepared, the idea was that no matter where you are, if you see a product on the list and it is available for you as a contractor (for sale), you can select it and the product immediately goes to your shopping cart. This mechanism is to allow easy duplication or selection of products from previous orders, invoices or goods issue documents. In addition, we have made available the so-called order templates. The template can be prepared by a sales supervisor or by the contractor himself to facilitate the submission of further orders. In addition, the ordering person can download technical documentation, certificates and other attachments if they are made available for a given product. This is a significant convenience for sales departments and frees salespeople from having to spend time receiving e-mails with orders from their customers.
Also noteworthy is the payer's context mechanism, which allows one EDI user to fulfill orders for different payers. When is this the case? For example, a cleaning company serves several business entities, orders disinfection products for them in appropriate quantities, with the invoice and payment being made directly by the operated business entities.
All orders from the EDI system are automatically transferred to the ERP system where they are further processed.
Context of the payer, a complex system of differentiating access rights and product lists mechanism, application speed.
Backend Restful API build with PHP, base on Symfony Framework. Frontend JS application build with Vue.js