“Record created. / Shipment information received (Aramex)”Normalized: label_created (Label created)Aramex (أرامكس) (aramex)

What Aramex 'Record created.' means (and why it hasn't moved yet)

The merchant or Shop & Ship warehouse has generated an electronic Aramex waybill (`Record created.`), but Aramex has not physically scanned the parcel at an origin facility yet.

Try a live tracking number:

What is happening in the supply chain

This is Aramex's pre-shipment manifest event (`Record created.` / `Electronic shipping information received`). The 10-to-11-digit Aramex AWB exists in Aramex's database, and the shipping label has been printed in the seller's warehouse, but the physical parcel is still waiting to be picked up by an Aramex driver or inducted at the origin sorting hub.

92… USPS Awaiting Item Checker →
Verbatim carrier scan
“Record created. / Shipment information received (Aramex)”
Normalized API status
label_created
Typical time to delivery
Pending shipper handoff (typically 1–3 business days until first origin hub scan)
Recommended recipient action
Wait 24–72 business hours for the seller to hand the parcel to Aramex; once scanned at the origin hub, Aramex will display an estimated delivery date.
Developer / WISMO action
Normalize to `label_created` (pre-shipment). Do not trigger transit delay alerts until the first physical `Collected by Aramex` or `Received at Origin Facility` scan appears.

How lastscanned normalizes this scan

Instead of maintaining brittle regexes for every carrier's raw scan phrasing across 273 carriers, query GET /v1/track/{number} or connect https://mcp.lastscanned.com.

Get an API keyAramex (أرامكس) API docs

Synchronous GET request

curl "https://api.lastscanned.com/v1/track/34829104921" \
  -H "Authorization: Bearer lsk_live_YOUR_API_KEY"

Normalized JSON response

{
  "carrier": "aramex",
  "trackingNumber": "34829104921",
  "status": "label_created",
  "statusDescription": "Record created. / Shipment information received (Aramex)",
  "message": "Record created.",
  "events": [
    {
      "timestamp": "2026-10-26T14:22:00Z",
      "localTime": "2026-10-26T10:22:00",
      "status": "label_created",
      "description": "Record created. / Shipment information received (Aramex)",
      "location": "DUBAI, AE"
    }
  ]
}

Frequently asked questions

Why has my Aramex tracking been stuck on 'Record created.' for 3 days?
Because `Record created.` only means the seller generated the shipping label online. Aramex does not have the physical box until you see `Shipment collected` or `Received at Origin Facility`.
What is the next scan after 'Record created.' on Aramex?
Once Aramex picks up the parcel, the status updates to `Shipment collected` or `Received at Origin Facility` (for example in Dubai, London, Istanbul, Hong Kong, or Riyadh).
Why does my cross-border ASOS, Next, or iHerb order show 'Record created.' in my home country?
For consolidated cross-border linehaul, the merchant prints the final-mile Aramex waybill before the bulk air cargo lands at Dubai (`DXB`), Riyadh (`RUH`), or Johannesburg (`JNB`), so Aramex shows `Record created.` until the consolidated pallet clears customs.

Related cross-border e-commerce scans

View all 210 scan statuses →

All 273 supported carriers

Major carriers

Regional and last mile

International posts and couriers

Cross-border