Aramex Shipping Connector (Middle East)

This is a build-to-order extension, not an instant AppSource install. Typical lead time is 2–4 weeks: we scope your Aramex accounts and document flows, build and unit-test the AL extension, deploy it to your sandbox for UAT, then promote it to production. The exact timeline depends on how many Aramex accounts (UAE/KSA/Kuwait, etc.) and how many shipping workflows are in scope. We confirm a date in writing before starting.

We hand over the source-controlled AL code and documentation, and offer ongoing support to keep the extension healthy through Business Central's monthly and major release cycles and any Aramex API changes. Bug fixes for the delivered scope during the warranty window are covered; new features, additional Aramex accounts or document flows are quoted as a change request. Because it is a per-tenant extension you are never locked to us — your IT team or any AL developer can maintain it.

No. It is a custom per-tenant extension that ECOSIRE builds for your specific environment and installs for you. That is what lets us map it to your number series, locations, permission sets and your live Aramex credentials. There is no public download link — purchase starts the build engagement.

No. The extension calls the Aramex Shipping & Tracking API directly from Business Central using the platform's native HttpClient over HTTPS, and uses a Job Queue entry for scheduled tracking polls. There is no extra server, connector licence or third-party iPaaS to run or pay for.

Yes. COD (cash-on-delivery) amount and currency are pushed into the Aramex booking from your order total, and the generated AWB label is rendered as a Business Central report/PDF so your warehouse can print it directly. Both are validated with you during UAT before go-live.