Sendcloud Multi-Carrier Connector for ERPNext

This connector closes that gap with one integration instead of a dozen. ECOSIRE builds a proper Frappe app (its own module, DocTypes, and hooks.py) that authenticates to the Sendcloud API with your public/secret key pair and manages your Sendcloud sender addresses and shipping-method defaults from a Sendcloud Settings single DocType. Because Sendcloud already aggregates DHL, DPD, UPS, GLS, PostNL and 80+ carriers, that single credential set unlocks all of them — you pick the carrier and service level per shipment or by rule, and never integrate another carrier API again.

Technically, the app hangs off the documents your team already uses. A doc_events hook on Delivery Note (and optionally Sales Order) exposes actions to create a Sendcloud parcel, fetch live rates, and buy a label; the returned tracking number, carrier, label PDF and cost are written to custom fields and a child Sendcloud Parcel DocType so everything is queryable in ERPNext reports. Whitelisted server methods (@frappe.whitelist()) back the checkout and portal calls — service-point and parcel-locker selection is driven by a client script and the Sendcloud points API so the customer picks a pickup location that is saved on the order. Bulk label and manifest generation runs as a background job over selected Delivery Notes, and a scheduler event polls Sendcloud (or consumes its webhooks) to keep tracking statuses current, trigger branded tracking-page and return-portal links, and fire ERPNext notifications on delivery or exception. Permissions are wired to role profiles so warehouse staff can print labels without touching API credentials.

Everything is designed for and tested against Frappe/ERPNext v15 and v16 and is delivered as a versioned app you install with bench get-app and bench install-app, with all customizations shipped as fixtures rather than manual site tweaks.

Because this is build-to-order, there is no instant download. We start with a short scoping call to confirm your carriers, Sendcloud plan, portal/return requirements and target ERPNext version, then build against your exact needs, prove it on a staging site through UAT, and go live. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the full source and git repository so the app is yours to own and extend.