Shopify
Authenticates withX-Shopify-Access-Token header; the old key-and-password-in-the-URL form no longer works. The dated API version is a setting, because it retires after about a year.
Cursor paging out of the Link header. A limit=250 call with no cursor reads the first 250 orders and silently ignores the rest, and nobody notices until a shopper telephones. Stock is set by inventory item and location, never by SKU, and a despatch is a fulfillment against a fulfillment order — which is what emails the shopper their tracking.
WooCommerce
Authenticates withConsumer key and secret, which travel in the request — so the store must be https, and nothing writes an unredacted URL to a log.
Its own status vocabulary (pending, processing, on-hold, completed), so which status to read and which to write are settings. There is no fulfillment object: despatch is the order moving to completed plus the tracking number written into the meta keys the common tracking plugins read.
Any other storefront
Authenticates withWhatever that platform uses, held as JSON on the channel record.
A bespoke Laravel or Odoo shop, CS-Cart, or a marketplace with an ordinary REST API runs on the generic adapter, with paths and field names configured. A new storefront is a form to fill in, not a release.
REST carriers
Authenticates withA token, a JSON POST to book and a GET to track, with paths and field names on the carrier record.
Covers the majority of modern carrier APIs. Each carrier’s own status words map to yours with a house default and a per-carrier override — an unmapped word leaves your status alone rather than guessing, because a wrong guess marks a parcel delivered and stops anybody chasing it.
First Flight
Authenticates withAccount credentials on the carrier record.
Returns failures inside an HTTP 200. Reading the status line as success puts unbooked parcels on a van, so the body decides. Its tracking splits date and time into two fields that have to be rejoined.
DPost
Authenticates withCredentials in the query string.
Every value is percent-encoded — a password containing # truncated the request in the older code — and every stored form is redacted.
Manual carriers
Authenticates withNone, deliberately.
A regional carrier whose driver arrives with a book of pre-printed waybills is most of the world. The clerk types the number and the shipment records honestly that no API was involved, rather than the system inventing one.
EDI
Authenticates withPer trading-partner configuration.
850, 856, 945 and 846 in and out, in both X12 and EDIFACT, with the message store and downloads for anything a partner queries.
Outbound webhooks
Authenticates withSigned events your client’s own system verifies.
Queued and then sent, so a client learns about a receipt or a despatch without polling you, and a slow endpoint on their side does not hold up your floor.
Orders arrive three ways and all land in the same table: a webhook posted as the order is placed, a scheduled pull against the store’s API, or a JSON payload pasted in for a marketplace not yet connected. An unknown SKU is matched and the mapping remembered. The same payload twice does not create the order twice. A push with no credentials saved is recorded as a dry run rather than reported as a success.