How the service works.

Create an account and sign in to use an account-scoped shipment workspace. Shipment records are shown and changed for the account that owns them. Paid shipment actions are checked on the server against the signed-in account and its billing status.

The product can store a carrier, tracking identifier, shipment expectations, and descriptions of intended tracking-feed or shipment-email sources. A saved description is not a connection or authorization. No compatible source connector is currently installed or authorized, so those descriptions are not monitored and incoming updates are rejected without changing shipment data.

Exception reporting depends on source updates and the shipment expectations available to Haulwhistle. A confirmed exception is needed before an eligible status request can be sent. The status request asks for information; it does not book, arrange, or change freight.

The current offer is a recurring subscription at USD $99 per account per month, plus applicable taxes. It includes supported, authorized source monitoring for up to 100 active shipments, supported exception reporting with shipment context, follow-up requests when outbound email delivery is configured, and an owner-scoped workspace with server-verified billing access.

Source monitoring requires a compatible connector and authorization. Those connectors are not currently available in this app. The included feature description does not mean a source is connected or that updates are being received today. The pricing page shows the current offer.

A signed-in user starts checkout through the hosted payment page. Haulwhistle chooses the monthly price on the server. A return or success redirect by itself does not unlock paid actions: the app checks payment evidence and the subscription associated with the signed-in email, including the $99 monthly amount and an eligible subscription status.

The account page links to the hosted billing portal for billing management. The checkout and portal depend on the company payment integration being configured and available.

Haulwhistle sends a status request only after a user asks it to send one, outbound email delivery is configured, a recipient and matching exception trigger are saved, and the shipment has a confirmed matching exception. The email contains shipment and exception context. If these conditions are not met, the app does not send the request.