MENA and cross-border sellers running ERPNext hit a wall the moment fulfilment scales past a handful of daily orders. ERPNext core gives you a generic Shipment DocType and an address book, but it has no native Aramex integration — no live rate lookup, no AWB creation, no label PDF, and no tracking status flowing back onto the order. Teams end up re-keying every consignment into the Aramex portal, copying tracking numbers by hand, and reconciling COD cash collection in spreadsheets. That double entry is exactly where wrong weights, mismatched addresses, and lost parcels creep in.

ECOSIRE builds a proper Frappe app — installed on your own bench as an aramex_connector module, not a fragile pile of pasted server scripts — that talks directly to the Aramex Shipping, Rate Calculator, and Tracking APIs. A dedicated Aramex Settings single DocType holds your account number, credentials, pickup addresses, and a sandbox/production toggle, with secrets kept in Frappe's encrypted Password fields rather than plain custom fields. Custom fields on Delivery Note and the standard Shipment DocType carry the AWB number, service/product group, COD amount, and live status, so shipping data lives on the same documents your team already works in.

Technically, the flow is deliberate. Whitelisted methods (@frappe.whitelist()) wrap each Aramex call — calculate_rate, create_shipment, print_label, track_shipment — and are the only entry points the UI and REST API touch. A hooks.py doc_events handler on Delivery Note on_submit can create the shipment and reserve the AWB automatically, or your team triggers it from a client-script button; which of the two we wire is decided during scoping. Labels and dispatch documents are pulled as the carrier PDF (or rendered through a Frappe Print Format) and attached to the document. A scheduler event registered in scheduler_events polls open AWBs on an interval and writes each milestone back to the Shipment status and timeline, so nobody refreshes the Aramex site. Role profiles and DocType permissions gate who can rate-shop, dispatch, and reconcile COD. Everything targets Frappe/ERPNext v15 and is forward-checked against v16.

Because this is build-to-order, there is no instant download. We start with a short scoping call, confirm your Aramex account type (domestic, international, COD, cash-on-delivery reconciliation), your ERPNext version and warehouse/pickup topology, then build against your sandbox. You review on a staging bench during UAT, we cut over with a rollback plan, and you receive the versioned source and Git repo. Typical delivery is one working week from confirmed scope, depending on how many Aramex service products and COD workflows are in play.