Aramex API integration connects your order system to Aramex for booking, label generation, tracking, pickup requests and cancellation, so international consignments travel through the same workflow as everything else you ship.
Aramex moves export and import consignments, and its customs brokerage support covers the paperwork international shipping requires. The integration puts the Aramex Shipping API behind your order system, so bookings, labels, tracking and cancellations happen where the order was entered. Bookings can run on a schedule or fire the moment an order is confirmed, and the Aramex accounts, service codes and pickup locations you already hold stay under your control.
Each card below maps to a step in the Aramex shipping workflow, from pulling rates through to reconciling the carrier invoice.
A confirmed order becomes an Aramex booking with the air waybill, service code and shipper details carried across as one record. Nothing is typed a second time, and the booking reference comes back against the order so the warehouse can print straight away.
Customers change their minds and orders turn out to be incomplete. Either way, the booking can be cancelled from the same screen and the cancellation reference recorded against the order, which keeps the audit trail intact once an air waybill has already been generated.
Scan history for each consignment is pulled into Softpal, so customers can see the current status and your support team can answer a tracking question without logging into the Aramex portal. Aramex tracking data covers the movement from pickup through customs clearance to delivery.
Where Aramex sends updates, the integration uses them. Where it doesn't, Softpal polls the API on a schedule you set. Polling is simple to configure, but the interval matters: a five-minute gap across a large order book adds up, so it's worth matching the frequency to how quickly your team actually needs status changes.
Rate cards, service codes, pickup locations and credentials are configured per Aramex account, so one seller on a contract never sees another seller's pricing. We build the integration around the accounts you already hold rather than a default setup, and adjust it as those contracts change.
Bookings, cancellations and pickup requests sit together with the rest of the shipment record instead of in a separate carrier portal. When a consignment has to be booked by hand, an odd weight or a special service for example, manual entry is still there, and service availability can be checked before you commit to a carrier.
The fetch rate is the gap between API calls to Aramex. Every five minutes suits a busy order book; hourly is enough for a catalogue that ships in batches. Rates can also be fetched on a trigger, such as a new order or a shipment status change, rather than on a clock.
Aramex exposes an API for pickup requests, which means goods ready at a given location can be flagged for collection from your system rather than by phone call. Once the pickup is accepted, the consignment moves and the delivery estimate can be calculated.
The estimated delivery date comes back from the Aramex API after pickup, not at booking. Distance, shipping method, the carrier network and the time the order took to process all feed into it, which is why the estimate settles once the shipment has actually been collected.
Aramex handles export and import consignments alongside express parcel, with freight forwarding available in the same account. Customs brokerage support covers the documentation and clearance requirements that apply to each destination country, and tracking continues through clearance rather than stopping at the border.
Reconciliation compares the shipping bills sitting in accounts payable against Aramex's statements, line by line. Pulling those expenses in through the API instead of retyping them from a PDF means weight disputes and surcharges show up while there's still time to query them.
Several Aramex accounts can run at once, each assigned by rules you define. Accounts can be tied to weight slabs, so consignments under 5 kg book on one account and anything heavier on another, or split by geography, with a default account for everything that matches no rule. For an Indian operation that often means separate accounts for Hyderabad in Telangana and Bangalore in Karnataka, with a fallback account for the rest of the country.
