Tracking

by goshippocf8e96532f24No licenseListed Oct 8, 2026Updated Oct 8, 2026

Track packages across carriers, view tracking history, and set up tracking webhooks via the Shippo API

Instructions onlyProductivity & Workflow
AI-generated overview

Track packages across carriers via the Shippo API, including tracking history and webhooks.

What it does
This skill guides an agent through using the Shippo API to track shipments. It covers calling GetTrack with a carrier token and tracking number, interpreting status values, substatus details, and ETA fields, and presenting current status plus chronological event history. It also describes finding trackable packages from successful transactions and registering a track_updated webhook.
When to use it
Use it when a user wants to check where a package is, review a shipment's tracking history, look up tracking for past successful transactions, or set up push notifications for shipment updates.
Requirements
Requires access to the Shippo API and its tracking endpoints, carrier tokens and tracking numbers, and an HTTPS webhook URL for webhook registration. It ships no scripts; it is instructions only.
<!-- ⚠️ DO NOT EDIT. Auto-generated from skills/tracking/SKILL.md by scripts/sync.js Edits here will be overwritten on the next sync. To change this content, edit the canonical source and re-run the sync script. -->

Package Tracking

Track by Number

  1. Determine carrier and tracking number. Carrier must be a lowercase Shippo token (e.g., usps, ups, fedex, dhl_express). See shippo/references/carrier-guide.md for tracking number format hints per carrier. If uncertain, ask the user.
  2. Call GetTrack with carrier and tracking_number.
  3. Key response fields: tracking_status (status, status_details, status_date, location), tracking_history, eta.
  4. Each tracking event includes a substatus object with code, text, and action_required (boolean). Include substatus details when presenting tracking history -- these provide more specific information about what happened at each step.
  5. Present: current status, location, ETA, substatus details, and chronological event history (most recent first).

Status Values

See shippo/references/carrier-guide.md for carrier-specific status nuances. Standard values:

StatusMeaning
PRE_TRANSITLabel created, carrier has not received the package
TRANSITPackage is in transit
DELIVEREDDelivered
RETURNEDBeing returned or returned to sender
FAILUREDelivery failed
UNKNOWNNo tracking information from carrier

The eta field is provided by most major carriers (USPS, UPS, FedEx, DHL Express) but availability is carrier-dependent, it may be null for regional carriers or for shipments before the carrier has finalized routing. Treat absence as informational, not as an error condition.


Find Trackable Packages

Call ListTransactions. Filter for object_status: SUCCESS. Each successful transaction has tracking_number and carrier info. Then call GetTrack for selected items.


Register a Tracking Webhook

  1. Get the user's HTTPS webhook URL.
  2. Call createWebhook with url and event: track_updated.
  3. Optionally call CreateTrack with carrier and tracking number to register a specific shipment for push updates.

Quick Reference

Track a package: GetTrack with carrier + tracking number

Find past shipment tracking: ListTransactions -> filter SUCCESS -> GetTrack

Source and attribution

Source:goshippo/aiinproviders/claude/plugin/skills/trackingat commitcf8e965

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from goshippo/ai

Upgrade Shippo

goshippo

Guides Shippo API version awareness, webhook payload versioning, and troubleshooting of the hosted Shippo MCP server.

Software DevelopmentOct 8, 2026

Shippo Support Ticket

goshippo

Generate a complete, auto-classified, ready-to-paste Shippo support ticket for a single shipment or label. Use when a support agent or customer needs to escalate a shipping issue (lost/delayed package, unused-label refund, billing/rate adjustment, address exception, customs hold, carrier-account, or tracking-webhook problem). Given a tracking number + carrier, a transaction (label) ID, or a shipment ID, it classifies the issue, runs the right read-only Shippo MCP lookups, computes the triage timeline, and emits both a copy-paste support message and a routing-tagged JSON block so the ticket lands in the right pipeline first time.

Awaiting classificationOct 8, 2026

Shippo Best Practices

goshippo

Guides Shippo integration decisions, choosing between Rates at Checkout vs. full Shipments+Transactions vs. Batch processing, address validation strategy (v1 vs v2 fields), domestic vs international workflows (customs declarations, incoterms), label format selection, and webhook setup. Use when planning, building, or reviewing any Shippo integration, including building checkout flows, bulk fulfillment pipelines, address validation, label generation, package tracking, customs handling, or webhook subscriptions.

Awaiting classificationOct 8, 2026

Shipping Analysis

goshippo

Analyzes shipping costs, compares carriers, optimizes package dimensions, and reviews historical shipping spend via the Shippo API.

Business & FinanceOct 8, 2026

Rate Shopping

goshippo

Compares multi-carrier shipping rates via the Shippo API and recommends cheapest, fastest, or best-value options.

Business & FinanceOct 8, 2026

Label Purchase

goshippo

Guides purchasing domestic, international and return shipping labels through the Shippo API, including customs and refunds.

Business & FinanceOct 8, 2026