shipment-tracking

Normalize carrier webhook events into a unified shipment status vocabulary.

14|3|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/tomtoto757/ecomm-ai-skills-hub --skill shipment-tracking-tomtoto757
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shipment-tracking
Source: https://github.com/tomtoto757/ecomm-ai-skills-hub/tree/main/skills/orders-shipping-returns/finsilabs/fulfillment-shipping/shipment-tracking
Command: npx skills add https://github.com/tomtoto757/ecomm-ai-skills-hub --skill shipment-tracking-tomtoto757

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Customers and ops teams suffer from fragmented, delayed, or unclear shipment status because carriers use different status codes, many platforms only link to carrier pages, and exceptions (lost or failed deliveries) are often detected too late. This Skill centralizes carrier events, normalizes status updates, and enables branded tracking and proactive notifications so merchants can reduce "where is my order" tickets and resolve delivery problems faster.

Core Features & Use Cases

  • Aggregated carrier webhooks: Receive and normalize tracking events from EasyPost, Shippo, or direct carrier webhooks to a unified status vocabulary.
  • Proactive customer notifications: Send emails/SMS at key milestones (in_transit, out_for_delivery, delivered) and trigger internal alerts on exceptions.
  • Branded tracking pages: Host or embed a store-branded tracking experience instead of sending customers to carrier sites.
  • Exception handling & ops workflows: Detect failure/return events, file carrier claims, and create service tasks in support tools (Zendesk/Gorgias) via integrations.
  • Headless & platform integrations: Applies to Shopify, WooCommerce, BigCommerce, and custom/headless setups using webhook-driven or aggregator-based flows.

Quick Start

Track order 12345 by registering its carrier tracking number with EasyPost or Shippo, normalize incoming webhook events, persist idempotent tracking events, and notify the customer when the status changes to out for delivery or delivered.

Frequently Asked Questions about shipment-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I normalize multi-carrier tracking webhooks into a unified status vocabulary?

Yes, you can use EasyPost and Shippo to aggregate carrier tracking webhooks for Shopify, WooCommerce, BigCommerce, and headless setups. These aggregator APIs deliver centralized status events to normalize and process your customer shipments.

How do I prevent duplicate customer notifications when receiving duplicate shipment tracking webhooks?

Shipment tracking detects delivery exceptions and lost package events by normalizing carrier status codes. It triggers internal alerts for operations teams and can create service tasks in support tools like Zendesk or Gorgias to resolve failed deliveries.

Does this shipment tracking approach work with headless e-commerce platforms?

Yes, this shipment tracking approach works with headless e-commerce platforms using webhook-driven or aggregator-based flows. It applies the same carrier event normalization and idempotent persistence for custom setups as it does for Shopify or WooCommerce.

How do I automatically update order status to delivered upon receiving carrier webhooks?

To automatically update order status to delivered, you verify the webhook signature and normalize the incoming carrier event. When the unified status maps to delivered, the system updates the e-commerce order accordingly.