Sürat Kargo Integration

Leave the service address empty and you land in the test environment

There is a default worth watching in the Sürat Kargo connection: if the service address field is left empty, the test (prova) environment is used rather than production. In many other integrations leaving a field empty means "default to live", so this reversed behaviour surprises people. The consequence: shipments appear to be created without error, but no real carrier record comes into existence.

Going live is straightforward: write the production service address Sürat gave you into this field. When you do want to work against the test environment there is a separate test switch, and ticking it is enough.

The account code and the tracking key

The identity consists of two values: your account code and your integration web password. Alongside them sits an optional tracking key. Fill it in and delivery status is queried in a structured form; leave it empty and status is derived from movement records. Both work; the first is cleaner.

The raw tracking response is stored — why?

On the Sürat Kargo connection you can create shipments, cancel them and query tracking. Translating the delivery status in the tracking response into an order status is not done yet: without the carrier's official code list a correct mapping cannot be written.

So the raw response is stored as it comes. The reason is not only honesty but a practical route: as real shipments move, the actual codes will be read from the stored responses and the mapping written against them. The gap will close with measurement, not guesswork.

Until then you advance the order status by hand; creating shipments and the barcode side work normally.