Automate Aramex shipments, AWB labels, live rates, COD and tracking in Odoo. Built, installed & supported by ECOSIRE for Odoo 17/18/19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
Automate Aramex shipments, AWB labels, live rates, COD and tracking in Odoo. Built, installed & supported by ECOSIRE for Odoo 17/18/19.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Odoo.
You go live in about 2–4 weeks, with a post-launch support window.
The Aramex Shipping Connector is a build-to-order Odoo module that ECOSIRE develops, installs and supports for you — it is not an instant apps.odoo.com download. We wire Odoo's native Inventory delivery flow directly into the Aramex Shipping and Tracking APIs so your team stops re-keying consignments into the Aramex portal and starts booking shipments from the same screen where they pick and pack.
Once installed, a stock.picking delivery order gains a "Book with Aramex" action. The module reads the customer address, package weight and dimensions, resolves the correct Aramex product group and product type (DOM/EXP, PPX/PDX/CDS and so on), calls the Aramex Shipment Creation service, stores the returned AWB number back on the picking, and pulls down the label PDF as an attachment ready to print. Delivery methods are modelled as standard delivery.carrier records so Aramex appears alongside your other couriers in the sale order and eCommerce checkout, with a live Rate Calculator call returning shipping cost before the customer confirms.
Because this is real Odoo engineering, everything lives where an Odoo team expects it. Credentials (account number, PIN, username, password, entity, country code) sit in encrypted Settings fields exposed through res.config.settings, with a clear separation between Aramex test and production endpoints. New fields extend delivery.carrier and stock.picking; computed fields use @api.depends so totals and status stay in sync; access is locked down with ir.model.access.csv and record rules so only shipping and warehouse roles can book or void consignments. Multi-package shipments map each stock.move.line pack into an Aramex ShipmentItem, and cash-on-delivery orders push the collectible amount and currency into the Aramex COD/cash-on-delivery attributes so your last-mile matches your invoice.
The connector supports Odoo 17, 18 and 19 on both Community and Enterprise, and is architected to work with Odoo's out-of-the-box delivery, sales and eCommerce apps rather than replacing them. ECOSIRE hands over the full module source, a tailored configuration mapped to your Aramex account and countries, admin and warehouse-user documentation, a live training session, and a post-go-live support window. Typical delivery is 2 to 4 weeks from requirements sign-off, depending on how many countries, product types and COD flows you need mapped.
An online retailer in the UAE, KSA, Egypt or Jordan shipping daily parcels with Aramex who wants orders, AWB labels and COD collection handled inside Odoo instead of the Aramex web portal, eliminating double data entry and mismatched COD amounts.
The operations lead who processes delivery orders and needs to book Aramex, generate labels, handle multi-package consignments and void wrong bookings quickly — all from the Odoo picking screen with role-based access, not by juggling two systems.
A merchant in Pakistan or the wider region running domestic and international Aramex shipments who needs correct product-group routing, live rates at checkout and tracking visibility across borders, tightly integrated with Odoo invoicing and inventory.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Native Aramex API integration (shipment creation, rates, tracking) | Full — shipment creation, Rate Calculator, tracking and cancellation wired to your account | Possible but you build and maintain every API call yourself | Varies — often partial or generic multi-carrier | |
| Automatic AWB label generation into Odoo | Included | Only if you build the label-fetch and attachment logic | Partial support | |
| COD amount & currency mapping to Aramex | Included | Partial support | Partial support | |
| Multi-package shipments (per-item weight/dimensions) | Included | Partial support | Partial support | |
| Built for your exact Odoo 17 / 18 / 19 version & edition | yes — pinned in __manifest__.py, Community or Enterprise | Included | Depends on the vendor's supported versions | |
| Role-based security (ir.model.access.csv + record rules) | yes — scoped to warehouse/shipping roles | Only if you implement it | Partial support | |
| Installation, configuration & COD/country mapping done for you | yes — ECOSIRE configures against your live account | no — you do it | no — self-serve setup | |
| Post-go-live support & API-change maintenance window | yes — included support window, retainers available | You own all maintenance | Vendor-dependent, often ticket-only | |
| Source code handed over (no lock-in) | yes — full module source | Included | Usually obfuscated or license-gated |
This is a build-to-order module, not an instant download. Typical delivery is 2 to 4 weeks from requirements sign-off, depending on how many countries, Aramex product types and COD flows you need mapped. The process is: discovery call and Aramex account/scope review, then we develop and configure the module against your Aramex sandbox, then a joint end-to-end test (a real AWB and label on your data), then installation on your production Odoo with your team trained and signed off.
Every engagement includes a post-go-live support window covering bug fixes, configuration tweaks and adjustments if Aramex changes its API. You receive the full module source, so you are never locked in. Because we build to your exact Odoo 17, 18 or 19 version, we also handle keeping the connector working when you patch or upgrade Odoo within the support window; longer-term maintenance and version-upgrade retainers are available if you want ongoing coverage.
We build for Odoo 17, 18 and 19, on both Community and Enterprise. The connector is designed to extend Odoo's native delivery, Sales, Inventory and eCommerce apps — Aramex simply appears as another delivery.carrier — so it fits your existing setup rather than replacing standard flows. Tell us your exact version and edition and we pin the __manifest__.py and build accordingly.
Yes. You provide your Aramex account number, PIN, username, password, entity and country codes, which we store in encrypted Odoo Settings (res.config.settings) with separate test and production endpoints. If you don't yet have API access enabled, we'll help you request the Aramex Shipping and Tracking API credentials from your Aramex account manager during the discovery phase.
Yes. For cash-on-delivery, the collectible amount and currency are mapped from the Odoo order/invoice into the Aramex COD attributes so your last-mile collection matches your books. For multi-package consignments, each package or pack line is mapped to an Aramex ShipmentItem with its own weight and dimensions, and a single AWB (or the AWBs Aramex returns) is stored back on the delivery order.
Both. Warehouse staff book shipments from the picking screen with role-based access, but because the logic lives in standard Odoo models it is also reachable through Odoo's XML-RPC / JSON-RPC API. That lets an external OMS, marketplace or storefront trigger an Aramex booking against Odoo programmatically — we can scope that integration as part of the build.
Automate Aramex shipments, AWB labels, live rates, COD and tracking in Odoo. Built, installed & supported by ECOSIRE for Odoo 17/18/19.