Obriym CRMObriym CRMCustomer flow workspace
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Sign inGet started
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Shipping · SAT

A connection with no “get a key” step

SAT's tracking method is open, so connecting is one click rather than an application. The whole journey shows up where the order and the buyer already are.

Try it in a workspaceAll integrations

The whole journey, every step visible in the CRM

SAT is the one connected carrier where the CRM can tell all four states apart — the international services simply do not report at that resolution.

  1. Accepted

    Handed to the carrier

  2. In transit

    In transit

  3. At the pickup branch

    Ready for pickup

  4. Handed to the recipient

    Delivered

Why there is nothing to obtain

This is not us cutting a corner — it is how the carrier's own API works, and we verified it live.

  • Tracking by waybill number is public at SAT: we probed it with the demo key, with a deliberately wrong key and with no key at all — the answer is identical.
  • So the adapter sends no key and never asks you for one: collecting data that changes nothing is worse than not collecting it.
  • SAT's key is for something else — creating waybills and looking them up by internal id. That is a separate capability we do not promise yet.
  • Requests go over HTTPS. SAT's documentation prints the production address as plain http, but the same host answers over HTTPS, and that is what we use.

What it gives you day to day

The manager never opens the carrier's site

Every shipment's status refreshes hourly on its own and sits in the order card beside the products and the payment.

“Ready for pickup” is its own state

A parcel that reached the branch but has not been collected is not counted as delivered — that is exactly the moment to remind the buyer.

An unseen status breaks nothing

SAT publishes no status dictionary, so a wording we have not met leaves the shipment where the manager put it instead of inventing a state.

The handover date is the real one

It comes from the event that recorded the handover — not from the branch arrival, and not from today.

How to connect

  1. 1

    Add the adapter

    Settings → Integrations → Platform adapters → SAT. There is no field for a key, because there is no key.

  2. 2

    Test the connection

    The CRM asks about a deliberately impossible waybill: “not found” proves the request arrived and the answer parses.

  3. 3

    Add a shipment

    On the order card, set SAT as the carrier and enter the waybill number — everything after that happens without you.

Frequently asked

Can the CRM create SAT waybills?
Not yet. Creation uses a key SAT issues on request through the client cabinet — that is a separate piece of work, and we do not promise it in advance.
Do I need a contract with SAT?
Not for tracking. A contract is for shipping goods, not for seeing their status.
How often do statuses refresh?
Hourly, and only for shipments still in flight. Delivered and cancelled ones are no longer polled.
What if a waybill number has a typo?
SAT answers that no such waybill exists and the CRM simply leaves that shipment untouched — one bad number never stops the rest of the run.

Add SAT to the carriers in your CRM

Nova Poshta, Ukrposhta, Delivery, SAT, DHL and UPS — in one order list.

Start free
Obriym CRMObriym CRMCustomer flow workspace

Obriym CRM is a focused workspace for sales teams and e-commerce operations. Leads, deals, orders, and customer retention in one place.

Product by OBRIYM

  • crm@obriym.com
  • OBRIYM
  • Serhii Oberemchuk

Individual Entrepreneur Oberemchuk Serhii Oleksandrovych · State reg. 178752761226

Product

  • AI
  • Features
  • Getting started
  • Pricing
  • Compare
  • Blog
  • Roadmap
  • Integrations
  • API Reference

Company

  • About OBRIYM
  • Founder
  • Contact
  • Roadmap

Developers

  • For developers
  • OpenAPI spec
  • JS Widget
  • Lead intake API
  • Orders API

©2026Obriym CRM by OBRIYM. Built for production sales and e-commerce teams.

Terms of UseTerms of ServicePayment & RefundsPrivacy PolicySubprocessorsData ProcessingLegal detailsData DeletionPricingAPI Docs