Integrations
Connect ecommerce to the rest of your business
We build integrations between your ecommerce platform and the ERP, CRM, PIM, warehouse, accounting, payment, shipping and supplier systems the business runs on – and connectors for systems that don’t have one.
Sound familiar?
What people ask us to connect
“Orders need to reach our ERP automatically.”
Each order goes to the ERP as it’s placed, in the structure the ERP expects, and what the ERP knows comes back: dispatch status, tracking numbers, invoice references.
“Stock must stay synchronised across multiple systems.”
We agree which system owns stock for each location and channel, move changes as they happen, and run a scheduled reconciliation to catch anything that was missed.
“Customer information needs to update our CRM.”
Accounts, orders and marketing consent reach the CRM against the right contact, without creating a duplicate every time someone checks out as a guest.
“Our supplier only provides a CSV, XML or API feed.”
We import it on a schedule, validate it, map it to your catalogue and hold back the rows that don’t make sense instead of publishing them.
“Our internal system has no existing ecommerce connector.”
If an off-the-shelf connector doesn’t exist, we can build one – against an API, a database, file drops or, where there is nothing else, the application’s own exports.
Systems
What we connect ecommerce to
ERP, CRM, PIM, warehouse systems, fulfilment, accounting, stock systems, payment providers, shipping, marketplaces, suppliers, internal databases, APIs and legacy applications.
ERP
- Shopify and Sage 200orders, stock and customer accounts
- Magento and SAPprice lists, orders and dispatch status
CRM
- WooCommerce and HubSpotcustomers, orders and consent
- Shopify Plus and Salesforcecompany accounts and order history
Product data and suppliers
- A PIM and the storefrontattributes, images and translations
- Supplier CSV, XML and API feeds and the catalogueproducts, prices and availability
Warehouse and shipping
- An online store and MetaPackshipments and delivery options
- Orders and a WMSpicks, dispatch confirmations and tracking
Accounting and payments
- WooCommerce and Xeroinvoices, payments and refunds
- Checkout and Checkout.compayments, captures and refunds – eplatforms is an official Checkout.com partner
- Refund records and gateway transactionsreconciliation across platform APIs
Channels and internal systems
- An online store and Amazon UKstock and orders across sales channels
- A legacy database and a new APIcontrolled access for a modern storefront
These illustrate the kinds of connection we build; the systems named are examples, not a client list.
How we build them
Integrations that keep working after launch
- One owner for each piece of data. Before any code, we agree which system is the source of truth for products, prices, stock, orders and customers. Most integration problems start with two systems both believing they are in charge.
- Designed for failure. APIs go down and records arrive malformed. Changes are queued until the other side is back, retries never create a second order, and anything that needs a person reaches a named person.
- Visible. A log you can read and a reconciliation you can run, so “is the ERP up to date?” has an answer that isn’t a guess.
- Within the limits. Platform API rate limits, webhook delivery rules and API version retirements are designed around from the start, not discovered in peak trading.
- Yours. The code lives in your repository, with documentation another developer could pick up.
In practice
What this work typically involves
An integration usually starts with a map of every system that touches an order, product, price or customer, and an agreement on which one owns each piece of data. The connectors are then built against APIs, webhooks, file drops or databases, with queues, retries and a reconciliation that can be run at any time, and tested against real data before they go live.
Typical pieces of work are orders sent to an ERP with dispatch status and tracking coming back, one view of stock, orders and fulfilment across a website and a marketplace, payments and refunds reconciled with the payment provider, and shipping and courier options chosen by destination, weight and dimensions.
eplatforms also builds and runs its own product, Order Exceptions, which connects to the BigCommerce, WooCommerce and Shopware APIs and checks each refund against the payment transaction behind it.
Platforms
Integration on the platform you already run
Shopify and Shopify Plus
Custom apps on the Admin API and webhooks, with Shopify Functions where the logic must run inside checkout.
WooCommerce
Custom plugins and the REST API, with scheduled work run by a real server scheduler rather than page visits.
Magento and Adobe Commerce
Modules, the REST and GraphQL APIs and message queues for high-volume imports and exports.
Custom platforms
Direct database, file or API integration, including building an API where a legacy system has none.
Next step
Two systems that should exchange data but don’t?
Tell us which systems, which data and how often it needs to move.