If you run a Saudi or GCC operation on ERPNext and fulfil through Naqel Express, the day-to-day reality is a broken loop: warehouse staff finalise a Delivery Note in ERPNext, then re-key the consignee, weight, piece count and COD amount into the Naqel portal, print the AWB there, and later paste tracking numbers back into ERPNext by hand. ERPNext ships with a generic Shipment DocType and a couple of parcel-service integrations, but there is no native Naqel connector, no Naqel rate card, and nothing that understands GCC cross-border customs fields or Naqel's COD remittance model. That gap is where mispicks, wrong COD totals and untracked parcels creep in.

This connector is a proper Frappe app — its own module, DocTypes and permissions — installed into your bench alongside ERPNext, not a fragile spreadsheet macro. We add a Naqel Settings single DocType to hold your API credentials, account number, default origin address and environment (staging vs production), with the API key stored as a Password field so it never renders in plain text. A hooks.py doc_events handler on Delivery Note and Shipment lets your team generate a Naqel AWB with one click: the app calls Naqel's shipment-creation API server-side through a whitelisted method, stores the returned waybill number, label PDF and tracking URL on a linked Naqel Shipment DocType, and attaches the label to the source document so it prints straight from ERPNext. COD orders carry the collected amount through to Naqel and are matched back on remittance, so finance reconciles against real numbers instead of guesses.

Under the hood everything runs on native Frappe primitives so your team can read, audit and extend it. Serviceability and rate lookups are exposed as whitelisted REST methods you can call from a client script on the Sales Order or from your own storefront over the Frappe REST API. Pickup scheduling is handled through a Naqel Pickup Request DocType plus a scheduler event (a scheduler_events cron/hourly hook) that can batch same-day pickups. Status polling runs on a Frappe background job that updates each Naqel Shipment and writes tracking events back to the linked Delivery Note timeline. Errors from Naqel are captured in the Error Log with the request payload, and access is scoped by a dedicated role profile so only shipping and dispatch roles can generate or void labels. GCC cross-border shipments get the extra customs and consignee fields Naqel requires, validated before the API call so a submission never fails silently.

Because this is build-to-order, you get software written against your exact Naqel account, your ERPNext version and your fulfilment rules — not a one-size-fits-all listing. After a short scoping call we confirm the Naqel services you use (domestic, cross-border, COD), the documents you generate labels from, and your v15 or v16 target, then build against a staging copy of your site. Typical delivery is one working week from confirmed scope. You receive the full app source in a Git repository, UAT on staging with a rollback plan, installation on your production bench, and a post-go-live support window. Nothing is downloaded and left to you to figure out — ECOSIRE builds it, installs it, and stands behind it.