System and API integration: Stop retyping orders between systems.

Integration work is rarely difficult and frequently nasty. The interface is documented incorrectly, the errors arrive with a success status code, field names are misspelled in the response, and the rate limit uses a status nobody expects.

We deal with that by putting the third-party client in its own layer with no dependency on the surrounding application, then testing it against recorded responses from the real service. Every behaviour we have been bitten by becomes a test, so it can only bite once.

The result is that a courier, a payment provider or a supplier feed can be exercised in milliseconds on a laptop, and an upgrade to the surrounding system cannot quietly break the connection to it.

01Who it is for

A business where someone retypes the same order, address or invoice from one system into another, or where a connection to a courier or a supplier breaks without anyone noticing until a customer does.

If this is the wrong service for you, we will say so and point you to the right one.

02What you get

1. A connection to each service in its own layer, independent of the rest of the system
2. A test suite recorded against the real service, covering every failure we have seen from it
3. Scheduled synchronisation that retries and backs off instead of giving up quietly
4. Payment checkouts and webhooks, courier vouchers and tracking, supplier and price feeds

You can read one of these in full: our ACS Courier plugin for WooCommerce is open source, and its test suite is part of the repository.

03What we need from you

Your own account with each service, with API access switched on; whatever documentation the provider gives you; and a few examples of what goes wrong today, since those become the first tests.