Soneta Integrator is today a key element of integrating XWMS with enova365. For manufacturing companies, it means a faster project start, lower implementation risk and integration based on the ERP vendor’s official standard. For enova365 Partners, the Integrator is a real alternative to writing their own costly, hard-to-maintain interfaces.
In this article we show what Soneta Integrator is in practice, what role it plays in connecting with XWMS, and why it is increasingly the foundation of warehouse implementations based on enova365.
Soneta Integrator as the foundation for integrating external systems
The Integrator is developed and maintained by Soneta, the vendor of the enova365 ERP system. It is a middleware module that enables standardised data exchange between enova365 and external systems, including WMS systems. Technically, the Integrator exposes the enova365 API via Soneta Web API. It allows data to be read from the ERP system and added or updated by external systems, regardless of the hardware platform. Communication with enova365 takes place via Soneta Web API using SOAP or REST. Whatever the communication model, data processing is based on the same proven mechanisms known from Soneta.EDI.
“Our cooperation with EX7 has lasted many years and has played an important role in shaping the approach to integrating WMS with enova365. Together we saw the need to organise and standardise the integration of warehouse systems with ERP, developing the concept of WMS integration based on the Integrator module. The experience gained from this cooperation became the basis for further development of integration solutions at Soneta, including the concept of the Soneta WMS add-on, which remains the foundation of warehouse integrations based on enova365 to this day. It’s an example of cooperation in which the practical experience of a WMS vendor has genuinely influenced the direction of an ERP system’s development” – says Wojciech Chrobak, enova365 Trade Project Manager, Soneta sp. z o.o.
The Integrator is not an add-on created for a single project, nor a one-off integration layer built for a specific client. It’s a Soneta standard that organises integration and gives the ERP and external systems such as XWMS a common language. As a result, integration is no longer a separate technical entity, but becomes part of the enova365 system architecture that can be developed and scaled as the company grows. It’s precisely this approach, based on many years of cooperation between the ERP vendor and the WMS vendor, that makes the Integrator not a theoretical solution, but a tool developed in real implementation projects.
A natural direction for companies using enova365
For companies already working with enova365, implementing XWMS based on the Integrator is today the most natural scenario. The ERP remains the master system, while the WMS takes responsibility for operational warehouse handling, relying on a standard integration mechanism supported by the vendor. The same model also works for companies that are only now choosing their ERP and WMS. Combining enova365 with XWMS via the Integrator makes it possible to design a consistent, scalable environment from the outset, without building custom interfaces.
“For companies that think of enova365 and a WMS as one coherent ecosystem, XWMS with the Integrator is the logical choice. It’s an approach in which the warehouse isn’t an add-on to the ERP, but its natural extension, based on Soneta’s official integration standard. As a result, there’s no need to reinvent the integration from scratch every time or build your own communication mechanisms. From day one, the company works on a solution that is predictable, scalable and in line with the direction of enova365’s development.” – says Jakub Wajda, board member of EX7, the vendor of XWMS.
The role of schemas and business logic in the Integrator
Schemas are a key element of the Integrator, each responsible for a specific area of data exchange, such as documents, products, stock levels or business partners. The schemas define the business logic that determines what happens to the data in enova365. Among other things, they decide where individual pieces of information are stored, how business partners are looked up, when a document is created and how its fulfilment is reported. As a result, integration isn’t just simple data transfer – it reflects real business processes.
The Integrator and the WMS add-on as a complete warehouse solution
For XWMS, the Soneta WMS add-on is of key importance. Only the combination of the Integrator with this add-on provides a complete, ready-to-implement warehouse integration. The add-on handles the event mechanism, the configuration of documents and warehouses covered by the integration, and the logic typical of warehouse processes. As a result, the warehouse system becomes the active party and retrieves only those documents that actually need to be fulfilled.
“The event-based mechanism is a huge step forward in WMS–ERP integrations. Instead of periodically scanning the entire enova365 database, the WMS reacts only to specific new events, such as a new order being released for fulfilment. This makes the integration lighter, more predictable and does not burden the ERP system, which is crucial with large numbers of documents” – says Jakub Wajda.
Lower risk, more predictable projects
One of the common reasons ERP Partners choose to build their own API is the desire for full control and clear responsibility. In practice, however, this also means designing, testing and maintaining unique solutions in every new implementation. The Integrator changes this model. Responsibility for the standard lies with Soneta, while WMS vendors and ERP Partners focus on configuring the solution and tailoring it to the client’s real needs. Warehouse processes such as receiving, issuing, orders for fulfilment and shortage handling are already described and have been tested many times.
Why the Integrator simplifies XWMS implementations
From a project perspective, the Integrator brings concrete benefits:
- it eliminates the need to write a dedicated API,
- it shortens implementation time and reduces costs,
- it limits the risk of design errors,
- it improves performance at large scale,
- it ensures compliance with the direction of enova365’s development,
- it allows older integrations to be modernised in stages.
XWMS and enova365 as one coherent ecosystem
The ERP and WMS market is clearly moving towards standardised, flexible integrations. Soneta Integrator fits this trend perfectly, and XWMS naturally complements enova365 in the area of advanced warehouse logistics.
For companies using enova365, XWMS isn’t an add-on “next to the system”. It is a logical extension of the ERP, based on an official integration standard that simplifies implementations today and provides a solid foundation for future growth.
