What Cargovate connects to — and what it will not touch.

Handheld scanners and your own hardware

A scanner or a warehouse device authenticates with a key issued for that facility, which you can revoke at any time without touching anything else. Devices post what they see — a scan, a position, a reading — and nothing about the integration requires the device to be one we sell.

You need

Anything that can make an HTTPS request. A phone browser is enough to start.

The fleet system you already run

If your vehicles report to a telematics platform, those positions can flow into Cargovate so a shipment's location comes from the same feed your drivers already generate — rather than from a second tracker stuck to the same pallet.

Today

Motive, by webhook.

Air cargo

Waybill and flight tracking is built in; the feed from your cargo data provider is connected during onboarding.

Pattern

Others follow the same shape and are added per customer.

Don't see the system you use?

Tell us which tracking, telematics or cargo data provider you rely on. Connectors are built in the order customers ask for them, and we will let you know when yours is ready.

Two X12 transaction sets, and no more

Suppliers' advance ship notices come in as X12 856 and become expected receipts that your warehouse receives against. Stock availability for a facility goes out as an X12 846 inventory advice. The separators are read from each document's own envelope rather than assumed, and a resent notice updates the delivery instead of duplicating it.

Today

X12 856 in, X12 846 out, both for the warehouse module.

Not yet

Other X12 sets (warehouse orders, transfers, purchase orders) and EDIFACT.

Your system of record stays your system of record

Orders, parties and stock come in from the export your ERP already produces. What we deliberately do not do is write back into it.

That is a limit we choose. Writing into a customer's ERP makes us a participant in their change control, their audit scope and their outages, and the failure mode is a corrupted production system at a site we cannot log into. If data needs to flow back, we produce an export your integration team consumes on their own terms — the same asymmetry, pointed the other way, with responsibility sitting where the system does.

Programmatic access

A documented HTTP API covers what an integration most often needs: creating shipments and moving them on under your own references, proposing custody transfers, reading the audit trail and reporting figures, and sending readings from devices you build. Each key carries only the scopes your administrator chose, and the reference lists exactly what a key can call.

API reference for integrations

Access

Issued to your organisation; scoped and revocable.

Named honestly

Direct ERP connectors, EDI beyond the two X12 sets above, and label or automation hardware are all things we know how to build and have not shipped as products. If one of them is a condition of your operation working, say so early and it becomes defined work with a date — rather than a logo on a slide that turns into a discovery call six weeks in.