Skip to Content

Connect BigCommerce and Medius

Connecting BigCommerce and Medius for a company that uses both could enable the transfer of order, invoice, and payment data between the e-commerce and financial systems. This could support more accurate financial reconciliation and help automate the flow of transactional data, reducing manual entry and supporting consistent reporting across departments.

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

Contact us

Why connect BigCommerce and Medius?

A company operating both BigCommerce and Medius could benefit from connecting these systems to enable more accurate and timely information flow between online sales and financial or procurement processes. Without a connection, staff may need to manually re-enter orders, invoices, or payment data from one system to the other, which could result in errors, duplicated effort, and delays. Over time, this manual handling can cause records to diverge, with inconsistencies between sales reported in BigCommerce and those processed or paid in Medius. Such discrepancies could lead to decisions being made on outdated or incomplete information, affecting financial oversight and customer service. If these two systems were connected, the kinds of data that could be exchanged include sales orders, invoices, payment statuses, and supplier or customer records. This could help ensure that transactions initiated in BigCommerce are promptly reflected in Medius, reducing the risk of missed or mismatched entries. The specific information that can be exchanged depends on what each system makes available through its API and is determined for each individual case.

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 BigCommerce and Medius 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