Skip to content
A map of the United States. A shipment travels west from Newark to Oakland through five hubs. One leg runs off the predicted path. 1 Newark, NJ 14h 45m 2 Greensboro, NC 6h 3 Indianapolis, IN 9h 4 Memphis, TN 1d 2h 45m 5 Phoenix, AZ 10h 6 Oakland, CA 16h
Platform

Every shipment draws two routes.

Shipping Hub maps the path your shipment took against the path we predicted. Each hub carries the time it held the shipment, so a change of plan shows up the moment it happens.

See it with your shipments What runs underneath
  1. 01 Newark, NJ 14h 45m
  2. 02 Greensboro, NC 6h
  3. 03 Indianapolis, IN 9h
  4. 04 Memphis, TN 1d 2h 45m
  5. 05 Phoenix, AZ 10h
  6. 06 Oakland, CA 16h
  • Actual route
  • Off plan
  • Predicted route

Example route. Your own shipments draw the same two lines.

Delivery route

Two lines for every shipment.

The top line is the route your shipment took. The bottom line is the route we predicted. Shipping Hub draws both, hub by hub, and marks the legs that ran off plan.

Actual
14h 45m 6h 9h 1d 2h 45m 10h 16h
Predicted
11h 48m not predicted 7h 12m 21h 24m 13h 12m 12h 48m
  1. Newark, NJ Origin
  2. Greensboro, NC Off plan
  3. Indianapolis, IN
  4. Memphis, TN
  5. Phoenix, AZ
  6. Oakland, CA Destination
Example route. Your own shipments draw the same two lines.
  • Play it back

    Move the scrubber across the timeline at one, two or four times speed and watch the shipment move between hubs.

  • Weather on every scan

    Each carrier scan arrives with the temperature at the place it happened, next to the event on the shipment record.

  • Off plan in its own colour

    A leg we did not predict draws separately from the rest, so the surprise is the first thing you see.

Simulation

Rehearse a change before it reaches anyone.

Your rules live in versions. You edit a draft, then replay it against a scenario you write yourself. The run log shows every action and the words it sends.

  1. 01

    Write the scenario

    A scenario is one shipment life on a clock. You place each event where you want it, then save the list for anyone on the team to reuse.

    Awaiting Parcel 0s · In Transit 2d · Out for Delivery 4d 14h · Delivered 4d 19h
  2. 02

    Replay a draft against it

    Every workflow keeps a live version and a draft. Pick the draft and the scenario, and Shipping Hub runs your events in order against the draft rules.

    Draft 5 · scenario default-next
  3. 03

    Step it forward

    Advance one event at a time, or run straight to the end. Each step names the actions that fired and the time each one took.

    Out for Delivery · 1/1 actions · 5.0 s
  4. 04

    Read the message

    Open an action to see the exact text it sends, with the real names in place. You approve the words before a customer reads them.

    “Hi Joe Schmoe! Your package is out for delivery. You can track it here.”
  5. 05

    Make it live

    The draft goes live when you say so. The version that ran your shipments stays on the record, and you can set any two versions side by side.

    Live 2706d57d · Compare 1d3cfdd6 → b9ed5312

Five rehearsals cost you an afternoon. The confidence they buy lasts as long as the rule does.

Your fields

The keys you already send become fields you can use.

Shipping Hub reads what arrives on your shipments and shows you how often each key appears and when it last came in. Give a key a name and a schema, and it joins search, filters and every message template.

Variables

Named and schema validated, and addressable anywhere a rule or a message runs. A variable reads from the shipment, from your organization or from the whole account.

  • shipment.carrier
  • organization.name
  • global.expected_delivery_duration
Declare once, use everywhere

Metatags

The keys your organization already puts on shipments. They work in templates the moment they arrive. Promote one to give it a short name, a schema and a place in search.

  • shipment.metatags.shipment
Your keys, your names
Control

The account stays in your hands.

Shipping Hub gives you the levers and gets out of the way. Each area below is yours to shape, and every change lands on the record.

  • Members

    The people in your organization, each with the access you give them.

  • Groups

    Sets of people who share a job, and so share the same access.

  • Roles

    Permissions gathered under a name, then attached to a person or a token.

  • Service accounts

    Tokens for your own systems, each with a role and a status you control.

  • Webhooks

    Your endpoints, fed the same events the application reads.

  • Audit

    A record of what changed, who changed it and when.

Put your own shipments on this map.

We connect to the carriers you already use and run a week of your shipments through Shipping Hub. You open the same screens your team would open, with your own data in them.

Talk to us See the products

Your carriers, your data, your screens.