GCC and MENA e-commerce sellers running ERPNext hit the same wall every fulfilment day: ERPNext core issues a Delivery Note but has no idea Aramex exists. Warehouse staff re-key each order into the Aramex portal, copy the returned AWB number back into a custom field by hand, print labels from a second browser tab, and chase COD reconciliation in a spreadsheet. Every manual hop is a wrong address, a mismatched weight, or a lost tracking number — and ERPNext's native Shipment DocType only models a generic carrier, with no Aramex Shipping & Rate Calculator API, no COD flag, and no live status feedback.

ECOSIRE builds a proper Frappe app — installed on your own bench, not a hosted middleman — that makes Aramex a first-class carrier inside ERPNext. The app ships as a versioned Frappe module with its own DocTypes (an Aramex Settings single for account number, credentials, and pickup defaults; an Aramex Shipment link that stores the AWB, label PDF, COD amount, and last-known status). A hooks.py doc_events hook on Delivery Note on submit calls a whitelisted server-side method that hits the Aramex CreateShipments endpoint, receives the air waybill, attaches the returned label to the document via the Frappe File API, and writes the AWB back onto the Delivery Note — no copy-paste. Rate and city-service lookups run through the Aramex FetchCities / rate calculator so staff pick a validated destination and see the cost before booking.

Cash-on-delivery is handled as a real shipment attribute: the COD amount and currency flow into the Aramex payload, the returned COD reference is stored for reconciliation, and a client script surfaces a one-click "Book COD" action on the Delivery Note form for users with the right role profile. Pickup creation posts to the Aramex CreatePickup service so the warehouse schedules a collection without leaving ERPNext, and a Frappe scheduler event polls TrackShipments on a configurable cadence, updating each Aramex Shipment's status and stamping the Delivery Note so support and customers see live movement. Everything is exposed over the Frappe REST API and whitelisted methods, so your storefront or a portal page can trigger a booking or read a tracking status programmatically. Credentials live in site config, all API calls are permission-gated by role, and failures are logged to the Frappe Error Log rather than swallowed.

This is a build-to-order engagement, not an instant download. We start with a short scoping call to confirm your Aramex account setup (account number, PIN, entity, source/origin), your Delivery Note workflow, COD reconciliation needs, and whether you're on ERPNext v15 or v16. From confirmed scope, typical delivery is one working week: we build against your requirements, run UAT on a staging bench, then install on production with a rollback plan. You receive the full source as an installable Frappe app plus the git repository, so nothing is locked to us — but we stay on for a post-go-live support window to tune it against real Aramex traffic.