Smart Business Automator add-on

Package tracking can become a real SaaS module.

The practical build is not a scraper. It is a tracking service inside the SBA backend: carrier detection, provider lookup, event normalization, approval gates, alerts, and outcome tracking.

USPS UPS FedEx DHL Amazon Logistics OnTrac

TRACK-9941

Auto-detected: UPS · confidence 99%

In transit
ETA: tomorrow Approval: hold if delayed Outcome: delivered on time

SBA value

Tracking is useful. Tracking plus rules, AI, approval gates, and outcome analytics is a business automation feature.

Executive answer

Yes, this can be added to the actual SaaS.

1

Build as a backend service

Do not bury it in the marketing site. Add it to the SaaS backend as a reusable tracking service with a stable API.

2

Use providers for live status

Open source can detect carrier patterns, but live tracking at scale needs Shippo, EasyPost, AfterShip, or direct carrier accounts.

3

Wrap it with SBA workflow logic

The differentiator is not showing “in transit.” It is triggering the right action when a delivery threatens a job, service call, or cash event.

Open source reality

Open source exists, but mostly for carrier detection.

Ruby

jkeen/tracking_number

Detects common carriers from tracking-number formats and uses shared pattern data. Its own README says it does not perform live tracking.

Data

tracking_number_data

Shared carrier pattern definitions for libraries. Useful as a reference set for auto-detection logic, tests, and confidence scoring.

Node/Python

Detection ports

There are Node and Python ports/packages around tracking-number validation. They help identify likely carriers, but do not replace carrier APIs.

Bottom line

There is no dependable open-source-only way to track all major U.S. couriers live without carrier/API relationships. Scraping carrier pages is brittle and creates terms, reliability, and scaling risk.

Recommended architecture

Put a tracking service between the SaaS product and the carrier ecosystem.

SBA SaaS app

Orders, projects, field jobs, approvals, customer notifications, dashboards.

Tracking service

Detect carrier, call provider, normalize events, cache status, run rules, write outcomes.

Providers + carriers

Shippo, EasyPost, AfterShip first. Direct USPS/UPS/FedEx/DHL later where volume justifies it.

Detect

Normalize number, identify carrier candidates, require confirmation for ambiguous formats.

Track

Fetch status by provider API or receive webhook updates for active shipments.

Decide

Rules and AI evaluate ETA risk, missing scans, job impact, and approval requirements.

Learn

Store delivery outcomes, exception reasons, supplier performance, and automation ROI.

Provider strategy

Use an aggregator first. Add direct carrier APIs only when there is a business reason.

Shippo / EasyPost / AfterShip Fastest path to a broad carrier list, normalized tracking statuses, webhooks, and fewer carrier-by-carrier auth headaches.
Direct carrier APIs Best when volume, cost, data depth, or enterprise requirements justify maintaining USPS, UPS, FedEx, DHL, and regional integrations separately.
Open-source detection Good for instant carrier suggestions and fallback tracking links. It should not be presented as live tracking by itself.
SBA workflow layer The actual SaaS moat: alerts, approval gates, escalation rules, job/project linkage, customer messaging, and outcome analytics.
SaaS data model

The module needs tracking records, events, rules, approvals, and outcomes.

Core tables
  • shipments
  • tracking_events
  • carrier_candidates
  • tracking_provider_requests
Automation tables
  • tracking_rules
  • approval_gates
  • notifications
  • automation_runs
Learning tables
  • delivery_outcomes
  • supplier_scorecards
  • carrier_performance
  • exception_reasons

Tenant-safe SaaS requirement

Every record needs tenant/account ownership, audit logging, role checks, retention policy, and rate limiting. Tracking data often contains customer addresses and delivery history, so treat it as operationally sensitive.

API contract

A clean SaaS API can stay stable even if providers change later.

POST /api/v1/tracking/shipments
{
  "tracking_number": "1Z879E930346834440",
  "carrier": "auto",
  "project_id": "job_123",
  "supplier_id": "vendor_42",
  "rules": ["jobsite_delay_risk"]
}
{
  "shipment_id": "shp_789",
  "carrier": "ups",
  "confidence": 0.99,
  "status": "in_transit",
  "eta": "2026-07-09",
  "risk": "low",
  "next_action": "watch"
}

GET status

`GET /tracking/shipments/:id` returns normalized status and event history.

Provider webhook

`POST /tracking/provider-webhooks/:provider` updates shipments asynchronously.

Outcome closeout

`POST /tracking/shipments/:id/outcome` stores whether the automation protected the business result.

Approval gates

This becomes valuable when package status drives approved business actions.

1

Watch shipment

  • Supplier order linked to project
  • ETA tracked against schedule
  • Missing scans flagged
2

Detect risk

  • Late delivery threatens crew
  • Material is critical path
  • AI drafts mitigation
3

Ask approval

  • Expedite alternate source
  • Notify customer
  • Reschedule crew
4

Track outcome

  • Delay avoided or not
  • Cost impact captured
  • Supplier score updated
MVP scope

Build the first version in four practical phases.

1

Detection + links

  • Carrier pattern library
  • Manual override
  • Carrier tracking URL
  • Unit tests with sample formats
2

Live lookup

  • Shippo or EasyPost
  • Normalized status model
  • Retry/rate-limit handling
  • Provider request logs
3

Workflow layer

  • Rules per customer
  • Approval gates
  • Email/SMS/Slack alerts
  • Project/job linkage
4

Outcome tracking

  • Delivered vs delayed
  • Cost avoided
  • Supplier scorecards
  • AI recommendations improve over time
Decision

Recommendation: ship a provider-backed MVP, not an open-source-only tracker.

Use now

  • Open-source carrier detection for instant UX and fallback links.
  • Shippo or EasyPost for live tracking in the first SaaS version.
  • SBA rules, AI, approval gates, and outcome tracking as the product layer.

Avoid initially

  • Scraping carrier websites.
  • Maintaining every direct carrier integration on day one.
  • Calling this “AI” without approved actions and measurable outcomes.

This can be sold as a logistics intelligence and action module inside SBA: “Know where critical materials are, know what delays matter, approve the fix, and measure whether the outcome improved.”

Sources and implementation references

Where to start.

Open source: jkeen/tracking_number

Carrier detection library and README note that it does not do live tracking.

 Open source: tracking_number_data

Shared tracking-number pattern data used by detection libraries.

 Provider: Shippo Tracking API

Get tracking status by carrier and tracking number.

 Provider: EasyPost Trackers

Create trackers and receive normalized shipment status/events.

 Provider: AfterShip Tracking API

Tracking and courier-detection focused API option.

 Deployment: Cloudflare Pages

Standalone static presentation hosted on a Pages URL without attaching a custom domain.
1 / 11