Skip to content

Carrier connection

Aramex.
Connected to dispatch.

Scope Aramex service selection, labels and dispatch handoff against your carrier account.

Responsibilities

Agree where each record belongs.

Conceptual illustration: A packing station, label printer and outgoing parcel joined by one violet reference.

A supported dispatch workflow does not establish a pre-built carrier connector. Agree the connection method and limitations during scoping.

What flows where

Scope the records in each direction.

These are proposed flows for scoping, not a promise that every object or event is already supported.

Conceptual illustration: An active record tray, storage cartridge and archive drawer with a shared record marker.
Aramex: records, direction and setup requirements
RecordFrom → toTriggerScope note
Service and shipment detailsOpsUI → AramexAt dispatch preparationConfirm rating and service-selection scope.
Label and tracking referenceAramex → OpsUIAfter shipment acceptanceConnection and account support to confirm.
Manifest / dispatch handoffOpsUI → AramexAgreed dispatch cut-offConfirm direct API, aggregator or file requirements.
Tracking updatesAramex → OpsUIWhen supported events arriveEvent coverage and timing require verification.

Set up the connection around your operation.

Conceptual illustration: A disconnected storage module, a second available module and records waiting for review.
  1. Confirm access

    Bring your Aramex account type, service mix and shipping locations.

  2. Agree the mapping

    Confirm rate, label, tracking and manifest access, including printer formats.

  3. Test the handoff

    Test representative parcels, rejected addresses, label retries and end-of-day handoff.

Questions about Aramex.

Is this the old Fastway Couriers integration?

Yes. Aramex Australia is the rebrand of Fastway Couriers (the change completed in 2021). If your team still calls it Fastway, this is the same franchise courier network. OpsUI connects to it under the Aramex name and account.

Do I use my own Aramex account or one supplied by OpsUI?

Your own. You keep your Aramex account, your franchise courier contract and your negotiated rates. OpsUI dispatches against them. We never resell freight or sit between you and the carrier on pricing.

Is the Aramex connector live in production today?

It is configurable, not a pre-built live link. OpsUI owns the dispatch workflow, rate, label, track and manifest, in the Shipping/Outbound module regardless of carrier, and the exact Aramex connection (direct API, aggregator such as Shippit, or file-based) is confirmed during scoping. NZ Couriers is currently our one live carrier API.

Can I run Aramex alongside other carriers in OpsUI?

Yes. OpsUI is carrier-agnostic, so you can dispatch Aramex next to Australia Post, StarTrack, Sendle, Toll, CouriersPlease and others, and use business rules to pick the right carrier per order, zone or service level.

Your next step

Bring your system. Map the connection.

Share the account or version you use, the records that matter and the exceptions your team needs to handle.

Back to all integrations