Check pin code serviceability, book Stallion Express shipments, print labels and share tracking with your customers, without maintaining a second carrier workflow.
Stallion Express is often chosen for how well it handles particular territories, which makes serviceability the number one question to answer before anything else. The rate request settles it. If the destination pin code is reachable, the booking is created; if it is not, the order can still be changed or routed to another carrier. Once the shipment is accepted, labels, tracking and cancellations all follow the same path, and your team is not switching between a portal and your system to keep up.
Rates, bookings, labels, cancellations, tracking and pickups, each tied to the order the parcel was packed for.
A booking is created from the order, using the address and the weight measured at the packing station. Stallion Express returns the consignment reference and the label, both attached to the order, so the parcel on the belt and the record on the screen cannot disagree.
Cancellations are handled from the same order while the consignment is still open, whether the customer has changed their mind or the shipment was created against the wrong details. The cancellation reference stays on the record for later reference.
Tracking events are stored against the order so customers can follow the shipment from your own site. Your support team sees the same history, which matters most in territories where customers tend to query a shipment while it is still moving.
Where Stallion Express does not push updates, status is requested again at an interval you choose. We set that per carrier rather than as one global default, because the right interval depends on your order volume, not on the carrier.
Rate cards and account credentials are configured per Stallion Express account, so each contract is applied only to the shipments it was negotiated for. It also keeps a rate meant for one territory from being applied to another by accident.
Pickup requests and manifests are generated from the orders they cover, and a booking can still be placed by hand for anything unusual. Pin code serviceability is confirmed before the label is produced, which is what prevents an avoidable failed delivery.
The fetch rate is how often your system calls the Stallion Express API. Five minutes suits a busy dispatch queue; an hour suits an operation that ships in waves. Rates can also be pulled on a trigger such as a new order or a status change instead of running on a timer.
Pickup requests are sent through the API, so parcels ready at a given address can be flagged for collection from your system rather than by telephone. The request remains attached to the consignments it covers, which is what settles any question about what was included.
The estimated delivery date comes from Stallion Express after pickup rather than at booking. Distance, the service selected and the time the order took to process all contribute, so the figure your customer sees becomes more dependable once the parcel has moved.
Pin code serviceability arrives with the rate, and for a carrier with a network that is not uniform across the country it is the question worth answering first. Knowing early means an order can be rerouted before a label is printed, not after a delivery attempt fails.
Stallion Express charges in accounts payable are compared with the carrier's statements, transaction by transaction. Drawing the data in through the API is what makes weight discrepancies and surcharge lines visible while they can still be queried with the carrier.
Several Stallion Express accounts can be active at once, selected by rule rather than by hand. Consignments can be split by weight slab, one account for parcels under 5 kg and another for heavier ones, or assigned by region with a default account for every location that matches no specific rule.
