Can you trust the numbers in EasyPost?

EasyPost is a shipping API that lets businesses build shipping and package tracking into their own software. Its own help pages give 3 reasons its numbers can look different from what you expect. The first to rule out: As EasyPost's developer docs explain, the detail you see for a package can differ from one carrier to another, so two shipments may not look equally complete.

Wins · Are they booking and buying?

Is it broken, or just counted differently?

A number can look wrong because the business changed, or because of how EasyPost counts it. Below is what EasyPost keeps, where its help pages say the numbers can differ, and how to check them yourself.

What does EasyPost keep track of?

  • EasyPost keeps a record for each package that shows where it is now and where it has been.

    In EasyPost's own words: Each Tracker includes both current and historical tracking data. Tracker, read 2026-11-12.

  • Every tracked package comes with a page you can send to the customer showing its progress.

    In EasyPost's own words: Each tracker includes a public_url field, which links to a public tracking page that can be shared with recipients. Understanding Trackers, read 2026-11-12.

What can make EasyPost's numbers look wrong?

  1. As EasyPost's developer docs explain, the detail you see for a package can differ from one carrier to another, so two shipments may not look equally complete.

    In EasyPost's own words: Data availability varies by carrier. Tracker, read 2026-11-12.

  2. As EasyPost's developer docs explain, when location details are incomplete, some scan times are shown in UTC rather than local time.

    In EasyPost's own words: When location information is incomplete, timestamps default to UTC. Tracker, read 2026-11-12.

  3. As EasyPost's help pages say, how often a package's status updates can differ from one carrier to another.

    In EasyPost's own words: Update frequency may vary by carrier. Understanding Trackers, read 2026-11-12.

How do I check EasyPost's numbers myself?

  1. EasyPost's docs point to the tracker's main status field as the most reliable signal to act on, rather than other details.

    In EasyPost's own words: The top-level status field on the Tracker object is the most reliable indicator for business logic. EasyPost Tracking Guide, read 2026-11-12.

  2. To check why a package shows a given status, you can read the full list of scan events EasyPost stored for it.

    In EasyPost's own words: The tracking_details array contains all current and historical status information returned by the carrier. EasyPost Tracking Guide, read 2026-11-12.

How does EasyPost work with Feder?

Connect EasyPost to Feder and it joins your Wins apps. Feder only reads. It never changes anything in EasyPost.

When you connect EasyPost, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Other apps that feed Wins

Questions owners ask about EasyPost

See every connection.

Where do these answers come from?

Everything this page says about EasyPost comes from EasyPost's own pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.