Book Xpression shipments, print labels and share tracking with your customers, with rates and serviceability checked before the order reaches your packing station.
Connecting Xpression is less about adding a courier than removing a workaround. Teams usually pick up a new carrier because a particular region is served better, or because a second contract gives them room to negotiate, and then carry the extra weight of a separate portal. With Xpression connected through the API, the warehouse keeps the same routine whichever carrier ends up on the consignment, and the Xpression tracking your customers see comes from your own pages.
What changes once Xpression is connected: rate checks, bookings, labels, tracking and pickups happen from your warehouse or order system.
The booking is generated from the order and the packing station's own data, which is why the weight on the label is the weight that was measured. Xpression returns the AWB and the label, and both are attached to the order so the packing list, the label and the carrier record agree with each other.
Bookings can be cancelled from the same record while they are still open, whether the order changed after labelling or the shipment was created against the wrong address. The cancellation reference is kept with the order, and so is the reason it happened.
Xpression tracking information is stored against the order in Softpal. Your customer sees a status from your own site rather than a carrier redirect, and the person answering the call has the same scan history on screen, which shortens the conversation considerably.
Where the carrier does not push updates, the status is fetched at a configured interval. This is the least visible part of any integration and one of the easiest to leave on a default that costs more than it returns, particularly across many open consignments.
Rate cards, service codes and credentials are configured for the Xpression accounts you hold, so each contract applies to the shipments it was negotiated for. That separation also means a regional contract cannot quietly apply to a nationwide volume.
Pickups and manifests are produced from the same view as the orders they cover, and a booking can still be placed by hand where a consignment needs something unusual. Serviceability is checked while the order is being processed, so an address Xpression cannot serve is caught before the label reaches the packing table.
The fetch rate is the interval between calls to the Xpression API. Every five minutes suits a busy dispatch floor; an hour suits a business that ships in waves. Rates can also be pulled on a trigger, such as a new order or a status change, rather than on a fixed schedule.
Pickup requests go through the API, so a batch of ready parcels can be flagged for collection from your system. The request remains linked to the consignments it covers, which is what settles a question later about what was in the collection.
Xpression returns an estimated delivery date after pickup rather than at booking. Distance, the service selected and the time taken to process the order all contribute, so the estimate your customer sees firms up once the parcel is moving.
Pin code serviceability arrives with the rate, before an order is confirmed. For a seller deciding between carriers, that answer is often the deciding one, and having it returned early is what makes the choice possible at all.
Xpression charges recorded in accounts payable are compared against the carrier's statements, transaction by transaction. Bringing the data in through the API is what surfaces weight discrepancies and surcharge lines while they can still be queried with the carrier.
Several Xpression 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 above, or assigned by region with a default account covering everything that matches no specific rule.
