European e-commerce sellers running on ERPNext hit a wall the moment fulfilment gets serious. ERPNext core knows how to raise a Delivery Note and mark a Sales Order as shipped, but it has no concept of a carrier label, a rate shop across DPD/PostNL/DHL/GLS/UPS, a branded returns portal, or a CN22/CN23 customs declaration. Warehouse staff end up re-keying every order into the Sendcloud web panel, copying tracking numbers back by hand, and reconciling two systems that never agree. That double entry is where mis-ships, wrong carriers, and angry "where is my parcel?" tickets are born.

We build a proper Frappe app — installable with bench get-app and bench install-app on Frappe/ERPNext v15 and v16 — that makes Sendcloud a native part of your fulfilment flow. The app ships its own DocTypes (a Sendcloud Settings single for API credentials and defaults, a Sendcloud Parcel log linked back to the Delivery Note, and a carrier/method mapping table), plus a Sendcloud Connect API client that authenticates with your Public/Secret key pair. hooks.py document events on Delivery Note submit call Sendcloud's Parcels API to create the parcel, pull the label PDF into the Frappe File store, and stamp the tracking number and carrier back onto the Delivery Note. Whitelisted server methods expose rate-shopping and label actions to a client script button on the Delivery Note form, so a warehouse user picks the cheapest eligible service and prints without leaving ERPNext.

Beyond outbound labels, we wire the parts ERPNext has no answer for. A scheduler event (Frappe's scheduler_events hook) polls Sendcloud for tracking status transitions and posts them onto the linked delivery, optionally creating Comments or triggering notification emails. The branded tracking and returns portal is exposed through Sendcloud's return API and a Frappe web page / portal route, so customers self-serve returns that land back in ERPNext as draft return material authorisations. For cross-border shipments the app assembles the customs line data (HS codes, item values, weights from the Item master) and passes it to Sendcloud so CN22/CN23 and commercial-invoice generation happen automatically. Pickup and dispatch requests are scheduled through the API rather than booked manually. Everything is permission-gated: we ship a dedicated role and role-profile so only fulfilment staff can generate labels or trigger pickups, and every API call is logged for audit.

Because this is build-to-order, nothing is a black box. We start from a scoping call to confirm which carriers, contracts, and warehouses you use, then build against a copy of your data on a staging bench. You get the full source as a versioned Frappe app in a git repo you own, installed on your own instance, validated in UAT before go-live, with a rollback plan and a post-launch support window. Typical delivery is one working week from confirmed scope, depending on how many carriers and edge cases (multi-warehouse, split shipments, dropship) are in play.