SMSA Express Shipping Connector for ERPNext

Key Features

Dedicated Frappe app with `SMSA Settings` single DocType holding API base URL, account number, and passkey stored via encrypted `Password` fieldtype

`SMSA Shipment` DocType that persists each air waybill, parcel details, COD amount, and full status history per Delivery Note

SMSA Express API authentication with retry/backoff and structured error surfacing into a `Carrier Error Log`

One-click AWB creation from the `Delivery Note` via a `@frappe.whitelist()` server method and a client-script action button

Dual-language (Arabic + English) SMSA label PDF returned and auto-attached to the document through the Frappe File API

Cash-on-delivery support: COD amount and currency passed to SMSA and stored for reconciliation against Payment Entries

Pickup booking request that schedules SMSA collection and records the pickup reference on the shipment

`scheduler_events` hourly job that polls SMSA tracking for in-transit shipments and writes checkpoints to the timeline

City coverage and serviceability lookup exposed as whitelisted methods and surfaced in the UI before booking

`hooks.py` doc events (`on_submit`/`on_cancel`) to auto-create or void the AWB in step with the Delivery Note lifecycle

Shipment cancellation/void flow that calls SMSA and keeps ERPNext and the carrier in sync

Role profile and permission rules so only authorized roles can book, cancel, or edit SMSA credentials

Full request/response audit logging for every carrier call, with sensitive fields masked

Configurable weight, dimensions, and package-count mapping from ERPNext item/packing data to the SMSA payload

Built and tested against Frappe/ERPNext v15 and v16, delivered as versioned source in a git repository

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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 2 to 4 weeks 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.

What you get

Installable source code for the SMSA connector app, built for your ERPNext version (v15 or v16)

Installation and configuration on your instance, including `SMSA Settings`, role profile, and doc-event hooks

Technical documentation: DocTypes, whitelisted methods, hooks, scheduler jobs, and config reference

User guide plus a live training session for your fulfillment and support team

Post-go-live support window for defect fixes and configuration adjustments

UAT on a staging/test bench with sandbox SMSA credentials before any production change

Documented rollback plan and a clean production install with backup taken first

Handover of the full git repository so you own and can extend the code

Who this is for

KSA e-commerce operations manager

Runs daily fulfillment on ERPNext and needs SMSA AWBs, COD handling, and pickups to happen inside the Delivery Note instead of a separate carrier portal, so the team stops double-keying every order.

Finance / COD reconciliation lead

Owns cash-on-delivery collections and needs each SMSA COD amount and reference tied back to ERPNext so remittances reconcile cleanly against Payment Entries instead of by spreadsheet.

Customer support lead

Fields 'where is my order?' tickets and needs live SMSA tracking checkpoints written back into ERPNext so agents answer from the shipment timeline, not a stale carrier lookup.

ERPNext administrator / IT owner

Maintains the Frappe bench and wants a clean, permissioned, well-documented app on v15/v16 with the source in git — no black-box marketplace binary they cannot audit or extend.

How SMSA Express Shipping Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Fit to your ERPNext instance	Built to your Delivery Note, print, and COD process on v15/v16	Fully bespoke but you specify and maintain everything	Generic flow you must bend your process around	No SMSA concept at all
SMSA AWB label generation	Arabic + English SMSA PDF auto-attached to the document	Possible, but you build the API and label logic	Varies; often English-only or a fixed layout	Not supported
Cash-on-delivery handling	COD amount + reference stored for Payment Entry reconciliation	Only if you design and build it	Sometimes; reconciliation rarely tied to ERPNext	Manual, off-system
Live tracking back into ERPNext	Scheduler job writes SMSA checkpoints to the shipment timeline	You build the poller and scheduler job	May offer a portal link, not in-record status	None
Delivery model	Build-to-order, 2-4 weeks from confirmed scope, UAT + rollback	Longer; depends on your team's capacity	Instant install but generic and unsupported for your case	Immediate, but no functionality
Source code ownership	Full git repository handed over — no lock-in	You own it because you wrote it	Often a closed binary you cannot audit	N/A
Support and updates	Post-go-live support window + retainer option for API changes	Your team maintains it indefinitely	Vendor-dependent; may lag SMSA API changes	N/A
Permissions and audit	Role profile + full masked carrier-call logging	Only if explicitly built	Usually minimal, app-defined defaults	N/A

Frequently Asked Questions about SMSA Express Shipping Connector for ERPNext

How long does delivery take?

This is a build-to-order app, not an instant download. After a short scoping call we confirm a fixed scope, and typical delivery is 2 to 4 weeks from that confirmed scope. Timing depends on your SMSA account setup, label and COD requirements, and how much custom warehouse mapping is involved.

Which ERPNext versions do you support, and how do updates work?

We build and test against Frappe/ERPNext v15 and v16. You receive a post-go-live support window for defect fixes and configuration adjustments, and because you own the git repository your team or ours can extend it later. Ongoing SMSA API changes or feature additions can be handled under a support retainer or a follow-on scope.

Is this an official SMSA product or a Frappe Marketplace app I can just install?

No. ECOSIRE is an independent integrator. This is a custom Frappe app we build against the SMSA Express API for your instance — it is not an official SMSA product and not a one-click marketplace download. You will need your own active SMSA Express account and API credentials.

Do you handle cash-on-delivery (COD) shipments?

Yes. The connector passes the COD amount and currency to SMSA when the waybill is created and stores the SMSA reference on the `SMSA Shipment` record, so your finance team can reconcile carrier COD remittances against ERPNext Payment Entries instead of tracking them manually.

How does live tracking reach my customers and agents?

A Frappe `scheduler_events` job polls SMSA tracking for all in-transit shipments on a schedule and writes each checkpoint back onto the shipment timeline in ERPNext. Your support team reads status directly from ERPNext, and the same data can feed customer-facing notifications if that is in scope.

Will it work with our existing Delivery Note and warehouse process?

That is exactly why we scope first. The app hooks into your `Delivery Note` lifecycle via `hooks.py` doc events and maps your weight, dimensions, and packing fields into the SMSA payload. We tailor the buttons, print format, and permissions to how your team already works rather than forcing a generic flow.

How do you protect our production system during install?

We build and test on a staging/UAT bench with sandbox SMSA credentials first, run acceptance testing with your team, take a backup, and only then install to production with a documented rollback plan. Credentials are stored encrypted using Frappe's `Password` fieldtype and never committed to code.