Generate Xpressbees shipping labels from confirmed orders, schedule pickups and pass tracking to your customers, without a dispatcher copying data between systems all day.
Xpressbees is used by marketplaces and sellers who are printing labels all day, which is a different problem from sending the occasional parcel. At that volume, the failures that matter are the quiet ones: a weight entered twice, a pickup that arrived half a day early, an invoice that nobody reconciled until quarter end. The Xpressbees API Integration takes those tasks off the dispatch queue and keeps the consignment tied to the order it came from.
Booking, labels, tracking, pickups and the monthly carrier bill, all handled from Softpal so dispatch does not depend on a carrier portal being open.
The booking is built from data already in the order, including the weight that determines both the rate and the serviceability of the destination pin code. The AWB comes back against the order and automated Xpressbees shipping labels print locally, which means a label generated by the system always matches the parcel it is stuck to.
Cancellations are part of daily work rather than an exception. An order changed after labelling, a customer who no longer wants the item, a duplicate booking created in error: each can be cancelled from the same record while the consignment is still open, with the reference recorded against the order.
Xpressbees tracking events are pulled into Softpal so customers can follow a parcel from your own site, and your support team sees the same history. When a seller is dispatching hundreds of shipments a day, the tracking question is the one that fills the inbox, and answering it from one record is what makes the difference.
Where the carrier does not push updates, status is fetched on an interval. This is worth configuring deliberately at high volume, because polling every open consignment every few minutes is a lot of requests for very little new information, and the interval that suits a hundred orders a day is not the one that suits ten thousand.
Accounts, rate cards and pickup locations are configured per Xpressbees account, so a seller with its own contract and a seller on a shared contract can both ship without seeing each other's pricing. Pickup scheduling is part of the same configuration, which matters when collections are happening daily.
Multi-piece shipments, manifests and pickups stay attached to the orders they cover, so nothing gets separated later. Where a consignment needs manual handling, it can still be booked by hand, and pin code serviceability is confirmed before the label is generated rather than after a failed delivery.
The fetch rate is how often your system calls the Xpressbees API. Five minutes is reasonable for a busy dispatch queue; hourly suits an operation that ships in fixed batches. Fetching can also be triggered by an event, such as a new order or a status change, rather than repeating on a clock.
Pickup requests are sent through the API, so parcels ready at a warehouse can be flagged for collection without a call. The request stays linked to the consignments it covers, which is what settles a dispute about whether a particular order was in the batch.
Xpressbees returns an estimated delivery date after pickup rather than at booking. Distance, the service selected and the time the order took to process all feed the estimate, so it becomes more dependable once the parcel is actually in the network.
Whether a shipment can be booked is decided by the destination pin code, and the rate request confirms it in the same call. Checking serviceability before the label prints means an undeliverable address is caught while the order can still be changed, which is far cheaper than a failed delivery and a re-ship.
Xpressbees charges in accounts payable are matched against the carrier's statements, transaction by transaction. At dispatch volume that comparison is not optional, and bringing the data in through the API is what makes weight discrepancies and surcharge lines visible while they can still be queried.
Several Xpressbees accounts can be active at once, and the account is chosen by rule rather than by hand. Weight slabs are the usual split, consignments under 5 kg on one account and anything heavier on another, and accounts can also be assigned by region with a default account covering every location that matches no rule.
