If you ship through more than one courier, the daily reality is a tab-and-portal marathon: staff copy addresses from ERPNext into Packlink, LetMeShip or SendCloud, eyeball rates by hand, paste tracking numbers back into a note field, and re-key customs data for every export parcel. ERPNext core ships a Shipment DocType with a basic Frappe/ERPNext connector for a couple of carriers, but it stops well short of true multi-carrier rate shopping, label printing directly off a Delivery Note, automated tracking status sync, or pickup scheduling. As order volume grows, the manual handoff becomes the bottleneck — mispriced shipments, transposed tracking numbers, and no single place to see where a parcel actually is.

ECOSIRE builds a dedicated Frappe app that turns ERPNext into your shipping control tower. We add a Carrier Account DocType to hold per-carrier API credentials and service mappings, a Shipping Rate Request that fans out to Packlink, LetMeShip and SendCloud in parallel and returns a ranked, comparable rate table, and we extend the standard Shipment/Delivery Note flow so a dispatcher picks a service and gets a printable label in one action. Under the hood we wire carrier calls through hooks.py doc events (for example an on_submit handler on Delivery Note and a validate guard on Shipment), expose @frappe.whitelist() methods that your fulfilment screen and any external WMS can call over the Frappe REST API, and add client scripts on the form for the rate-picker and one-click label button. Generated labels and the commercial/customs invoice PDF are stored as File attachments against the shipment so they are auditable and reprintable.

Tracking stays current without anyone watching it. We register scheduler_events (a cron-style hook) that polls each carrier for in-transit parcels, writes normalized status back onto the shipment, and can fire ERPNext Notifications or webhooks when a parcel is delivered or exception-flagged. Pickup scheduling is a whitelisted method that books a collection window with the carrier and records the confirmation on the record. Access is governed by proper ERPNext permissions and role profiles — for instance a Shipping User who can rate-shop and print labels versus a Shipping Manager who can edit carrier credentials — and every carrier API call is logged for troubleshooting. The app targets ERPNext v15 and is built forward-compatible for v16.

Because this is build-to-order, you are not downloading a generic plugin and hoping it fits. We start with a short scoping call to confirm which carriers, services, warehouses and label formats you actually use, then build your version, run it through UAT on a staging bench, and install it on your site with a documented rollback. Typical delivery is one working week from confirmed scope. You receive the installable source, technical and user documentation, a training session, a post-go-live support window, and the git repository so the code is yours to keep and extend.