Systems we connect
Most logistics operations run on a mix of off-the-shelf platforms and older in-house software. We work with both. Platforms we've integrated include:
- Carrier and shipping platforms: Metapack, Scurri
- ERP and finance: SAP, Microsoft Dynamics, Sage, Xero
- Warehouse and fulfilment: Mintsoft, cross-dock and bespoke WMS
- Marketplaces and CRM: Amazon, Salesforce
- Reporting: QlikView
- Vehicle routing and planning software
If your platform isn't listed, ask. If it has an API, we can work with it. If it doesn't, we can usually still get the data in and out through files, a database or a custom connector.
What we build
API integrations. Direct connections between your systems and third-party platforms. For example, orders from an e-commerce store flowing straight into the warehouse management system, or shipment events coming back from a carrier platform into your tracking.
Middleware. When several systems need to share the same data, a single integration layer is easier to run than a web of point-to-point links. It gives you one source of truth, one place to monitor and one place to change when a supplier changes their API.
Public APIs for your customers. Endpoints that let your clients send you orders and pull back status and tracking automatically, instead of emailing spreadsheets. We've built APIs handling many thousands of orders a day.
Customer account integrations. Connecting into your customers' own systems so their orders, bookings and updates arrive without manual handling.
Custom modules for existing software. Add-ons and plugins for platforms like SAP, Sage and Xero when the standard product doesn't quite fit your process.
Management dashboards. Once the data is connected, we pull it into one view of performance, operating statistics and service levels.
Working with legacy systems
Many integration projects start with a system that runs the business and that nobody wants to touch. We don't assume it needs replacing. Often the lower-risk route is to wrap it with an API, connect it to newer platforms and move functions across in stages. We'll tell you honestly which approach suits your situation.
Proof
- A two-man home delivery network connected its operations to a track and trace platform that gives the major retailers it delivers for live status on every order. Read the case study
- A chilled distribution business replaced paper with a connected driver app and management system covering routes, proof of delivery and temperature logs. Read the case study
How an integration project runs
- Map the data. We document what moves between which systems, how often, and what happens when something fails.
- Build and test against real data. Integrations are tested with simulated and real traffic before go-live.
3. Release in stages. One flow at a time, with the old process available as a fallback. - Monitor and support. We watch for failed messages and supplier API changes, and fix them before your team notices.
We work to ISO 27001 and ISO 9001 and hold Cyber Essentials, which matters when an integration carries customer and order data between companies.
Frequently asked questions
It depends on the systems and the quality of their APIs. A single connection to a well-documented platform can take a few weeks, while a middleware layer across several systems is usually a phased project over a few months.