If you run a KSA e-commerce operation on ERPNext, the last mile is where the native workflow runs out of road. ERPNext gives you a solid Delivery Note and Shipment foundation, but it has no concept of SMSA Express: no air waybill numbers, no SMSA-formatted Arabic/English labels, no cash-on-delivery amount handoff, no pickup booking, and no live tracking status flowing back to the customer. Teams end up re-keying every order into the SMSA portal, printing labels in a separate browser tab, reconciling COD collections by hand, and answering "where is my order?" tickets with a stale spreadsheet. That double-entry is slow, error-prone, and does not scale past a few dozen shipments a day.

ECOSIRE builds a dedicated Frappe app — a proper installable module with its own SMSA Settings single DocType for API credentials and defaults, an SMSA Shipment DocType to persist each AWB and its lifecycle, and a child-table mapping so one Delivery Note can dispatch multiple parcels. Credentials and the passkey are stored encrypted via Frappe's Password fieldtype, never in plain text. The integration authenticates against the SMSA Express API and exposes clean, @frappe.whitelist()-decorated server methods so your users create a waybill straight from the Delivery Note without leaving ERPNext.

Technically, the connector hangs off hooks.py document events: a Delivery Note on_submit handler can auto-request an AWB, while a client script adds a "Create SMSA Shipment" button and a status indicator to the form. Label generation returns the SMSA PDF (Arabic and English) and attaches it to the document via the File API so it is one click to print. COD shipments pass the collection amount and currency to SMSA and store the reference for later reconciliation against Payment Entries. A scheduler_events hook (a cron/hourly job) polls SMSA tracking for all in-transit shipments and writes each checkpoint back to the SMSA Shipment timeline, so agents and customers see live status without anyone touching the carrier portal. Serviceability and city-coverage lookups are exposed as whitelisted methods and surfaced in the UI so staff can validate a destination before committing a shipment. Everything respects ERPNext permissions — we ship a role profile so only authorized roles can book or cancel shipments, and all carrier calls are logged for audit.

The app targets Frappe/ERPNext v15 and v16, is built to your instance's fields and print requirements, and ships as clean source code in a git repository you own — no black-box lock-in. Because SMSA's own API contract and your warehouse process are specific, we treat every engagement as build-to-order rather than a one-click marketplace install.

Delivery is build-to-order: we start with a short scoping call to confirm your SMSA account type, COD terms, label layout, and warehouse flow, then produce a fixed scope. Typical delivery is one working week from confirmed scope. We stage the app on your test/UAT bench first, run acceptance testing with your team against real (sandbox) SMSA credentials, and only then install to production with a rollback plan. You receive the source, documentation, a training session, and a post-go-live support window.