This is a build-to-order module, not an instant download. Typical delivery is one working week 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.