Integrations That Fit The Stack You Already Run
Connect the systems you sell and account on, so orders, stock and tracking move by themselves — no exports, no re-keying, no reconciliation by spreadsheet.
The integration is the operation
A fulfilment partner is only as good as the data it receives. If orders arrive by email and stock is reconciled by spreadsheet, mistakes are not a risk — they are a certainty, and they scale with your volume.
We connect at the source. Orders arrive complete with the service level, the address and any gift or note fields. Stock levels flow back as picks happen. Tracking is written to the order and the customer notification goes out without anyone touching it.
Where a native connection exists, we use it. Where it does not, we build against our API or accept a scheduled file. Either way the connection is set up, tested against real orders and monitored — not handed over as a set of credentials and a wish of good luck.
Everything covered by partners & integrations
Channel connection
Sales channels connected and tested with live orders before go-live, including the awkward edge cases.
Inventory synchronisation
One stock pool pushed to every connected channel, so a unit sold on one storefront disappears from the others.
Tracking write-back
Carrier and tracking number written back to the order so your platform sends its own shipping notification.
Courier rate shopping
Our carrier accounts compared per parcel, or your own accounts used if you have negotiated better rates.
API and webhooks
A documented REST API and webhook events for teams that want to build against the operation directly.
EDI and file transfer
Scheduled CSV, XML or EDI exchange over SFTP for wholesale customers and legacy back-office systems.
The partners & integrations process
The same sequence runs every time, which is what makes the result predictable.
- 01
Map the systems
We list what you sell on, what you account on, and where data currently gets re-keyed by hand.
- 02
Connect and configure
Channels are connected, SKUs matched, and routing rules configured for splits, holds and service levels.
- 03
Test with real orders
A small batch of live orders is run end to end, including a return and a partial, before we switch fully over.
- 04
Monitor and maintain
Connections are monitored for failures, and platform API changes are handled by us rather than discovered by you.
Connection methods
We will recommend the simplest method that does the job. Complexity is only worth it when the volume or the system demands it.
| Method | Typical setup time | Best suited to |
|---|---|---|
| Native channel connection | 1 – 3 working days | Mainstream carts and marketplaces |
| Multichannel manager | 3 – 5 working days | Sellers already running several channels |
| REST API and webhooks | 1 – 2 weeks | Custom platforms and in-house systems |
| Scheduled file transfer | 3 – 5 working days | Wholesale feeds and legacy back-office tools |
| EDI | Quoted per project | Retail trading partners with EDI requirements |
What we connect to
If it is on this list, connection is routine. If it is not, it is almost certainly still possible — the API and file routes cover most systems.
Shopping carts
Shopify and Shopify Plus, WooCommerce, Magento, BigCommerce, Squarespace and Wix.
Marketplaces
Amazon, eBay, Etsy, TikTok Shop and other channels via a connected multichannel manager.
Couriers and carriers
Royal Mail, DPD, DHL, FedEx, UPS, Evri and pallet networks, on our accounts or yours.
Back office and ERP
Accounting and inventory systems fed by scheduled export, API or EDI depending on what they support.
Subscription platforms
Recurring billing platforms connected so renewal orders drop into the same pick run as one-off sales.
Custom and headless
In-house and headless builds integrated against our REST API with webhook events for status changes.
What changes once this is running
No manual re-keying
Orders arrive complete. The most common source of address and quantity errors disappears entirely.
Add channels without adding admin
A new marketplace becomes another connection into the same pool, not another spreadsheet to maintain.
Fewer oversells
Stock decrements across every channel as picks happen, instead of at the end of the day.
Faster dispatch
Orders that arrive clean are orders that can be batched immediately rather than queued for review.
Partners & Integrations FAQs
Looking for something more general? Read the full FAQ page.
Standard channel connections are set up as part of onboarding at no additional cost. Custom API work and EDI projects are quoted separately, and we will tell you which category you fall into before any work starts.
Yes. If you have negotiated rates worth keeping, we will ship on your accounts. Most brands compare both and keep whichever is better per service, which is exactly what rate shopping is for.
We monitor the connections and handle version changes on the platforms we support, so it does not become your problem. If a change requires a decision from you, we will explain what it affects and what the options are.
A bundle can be held as its own SKU with its own stock, or as a virtual kit that decrements component stock when it sells. Which is better depends on whether the components also sell individually, and we will work through that with you at onboarding.
Yes, they can be run as separate stock pools under one relationship, with separate reporting and invoicing. It is a common arrangement for groups running several brands from the same inventory base.
Services brands usually pair with this one
Tell us what you sell on
List your channels and back-office systems and we will confirm exactly how each one connects, and how long it takes.