Skip to Content

Connect Medius and IWD

Connecting Medius and IWD for a company could involve enabling the transfer of relevant financial or operational data between the two systems. This connection could support more efficient workflows by reducing manual data entry, ensuring data consistency, and providing better visibility into processes that span both platforms.

You can build this integration on the System2System platform. We design the connection between Medius and IWD around the way you work — not as an off-the-shelf connector, but to fit your systems.

Contact us

Why connect Medius and IWD?

A company that operates both Medius and IWD could benefit from connecting these systems to enable data exchange between them. The motivation for such a connection often arises from a need to reduce manual work and errors. Without a connection, staff may have to enter the same data into both systems, which can lead to duplicated effort, inconsistent records, and the risk that decisions are made based on outdated information. Over time, this can result in misaligned processes and inefficiencies that impact business performance. The types of data that could be exchanged between Medius and IWD depend on the core functions of each system. For example, Medius is widely recognized as an accounts payable automation platform, while IWD is known for retail execution and merchandising solutions. In this context, a connection could enable the transfer of invoice data, purchase orders, approval statuses, or supplier information from Medius to IWD, or vice versa, to align financial and operational records. It could also support the sharing of store compliance data or merchandising activities, helping to keep both financial and field operations up to date. The specific data that can be exchanged is governed by what each system makes available through its API and must be determined for each situation.

How System2System builds an integration

Connectors

We connect to each system through the interface it offers — an API, a database, a file exchange or a webhook — and handle authentication, rate limits and retries.

Mapping

Fields rarely line up one to one. We map and transform the data so both systems receive it in the shape they expect.

Workflow

We define what triggers an exchange, in which direction data flows and which system takes precedence when the two disagree.

Monitoring

Every exchange is logged. Failures are flagged and can be replayed, so nothing disappears without anyone noticing.

What can actually be exchanged?

That depends on what Medius and IWD make available through their APIs, on the licences and modules in use, and on the version each system runs. Which records are synchronised, in which direction and how often, is something we determine together before any work starts.

We are happy to look at your specific situation and tell you what is feasible — including when the answer is that it is not.

About these systems

Read more about each system and what it can be connected to

Looking to connect these systems?

Talk to us about what your setup needs. No obligation.

Contact us