Sendcloud Multi-Carrier Connector for ERPNext

Key Features

Single Sendcloud API integration (public/secret key pair) that unlocks DHL, DPD, UPS, GLS, PostNL and 80+ European carriers without per-carrier API work

Frappe app with its own module, `Sendcloud Settings` single DocType for credentials, sender addresses and default shipping methods

`hooks.py` doc_events on Delivery Note (and optional Sales Order) to create parcels, fetch live rates and buy labels in place

Custom fields plus a `Sendcloud Parcel` child DocType storing carrier, tracking number, label PDF, service level and shipping cost — fully queryable in ERPNext reports

Service-point and parcel-locker selection via a client script and the Sendcloud points API, saved onto the order for checkout and portal

Bulk label and manifest generation as a background job across selected Delivery Notes for peak-hour throughput

Whitelisted server methods (`@frappe.whitelist()`) backing checkout, portal and service-point calls with input validation

Scheduler event that polls Sendcloud or consumes its webhooks to keep tracking statuses in sync and trigger ERPNext notifications

Branded tracking pages and a customer return portal wired to Sendcloud return rules

Automatic carrier/service selection driven by ERPNext Shipping Rule logic, weight, destination country and your business rules

Role-profile permissions so warehouse staff print labels without exposure to API credentials

Label PDF stored as a File attachment and printable directly from the Delivery Note print flow

Sandbox vs production credential switching for safe testing before go-live

Customizations shipped as Frappe fixtures for clean, repeatable install across staging and production, built for ERPNext v15 and v16

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

European e-commerce merchants running ERPNext hit the same wall: the Shipping Rule and Shipment DocTypes in ERPNext core can compute a flat or weight-based charge, but they do not talk to real carriers. To actually create a parcel, buy a label, offer a customer a DPD parcel-shop or a PostNL service point, and push a tracking number back to the order, teams fall back to copying addresses into the Sendcloud web panel by hand. That double entry is slow, error-prone at peak, and leaves ERPNext with no record of which carrier shipped what, at what cost, or where the parcel is now.

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.

What you get

Installable, versioned Frappe app source code targeting your ERPNext v15 or v16 site

Installation and configuration on your staging environment (bench get-app / install-app, Sendcloud credentials, sender addresses, carrier defaults)

Technical documentation: DocType/field reference, hooks, whitelisted methods, scheduler events and configuration guide

User guide plus a live training session for warehouse and customer-service staff

UAT on a staging site with a documented test plan and an agreed rollback plan before production go-live

Full git repository handover so you own and can extend the app

A post-go-live support window for bug fixes and defect resolution

ERPNext role/permission setup and Sendcloud webhook or scheduler configuration

Who this is for

European ERPNext e-commerce operations lead

Runs multi-carrier fulfilment across DHL, DPD, UPS, GLS and PostNL and needs labels, service points and tracking booked from the Delivery Note instead of retyping every order into the Sendcloud panel.

Warehouse and fulfilment manager

Wants bulk label and manifest generation for peak-hour batches, printable labels from ERPNext, and staff who can ship without ever seeing API keys.

Cross-border D2C merchant

Ships across the EU and needs carrier choice by destination and weight, parcel-locker options at checkout, and branded tracking plus a self-service return portal to cut support tickets.

ERPNext system owner / IT lead

Needs a clean Frappe app on v15/v16 delivered as fixtures with source and git handover, proven on staging with a rollback plan, so nothing is a fragile one-off site hack.

How Sendcloud Multi-Carrier Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Carrier coverage	DHL, DPD, UPS, GLS, PostNL and 80+ EU carriers via one Sendcloud integration	Only the carriers your team codes and maintains	Whatever the app author chose to support	None — Shipping Rule computes a charge but books no carrier
Label and manifest creation	Buy labels from the Delivery Note plus bulk manifest jobs for peak	Built from scratch and must be re-tested per carrier	Usually single-label; bulk often a paid add-on	No live label purchase at all
Service points / parcel lockers	Client-script picker saved on the order via Sendcloud points API	Rarely built due to effort	Inconsistent or missing	Not available
Tracking and returns	Scheduler/webhook sync, branded tracking pages, self-service return portal	You build and host tracking and returns yourself	Basic status writeback at best	Manual status entry only
ERPNext v15/v16 fit	Built and tested on both, shipped as fixtures	Depends entirely on your developer's rigor	May lag ERPNext releases	Core, but no carrier layer
Ownership and extensibility	Full source plus git repo handover — yours to extend	You own it but carry all build cost and risk	Closed or licence-locked; limited extension	Core code, no shipping feature to own
Support and updates	Post-go-live window plus optional retainer for API/version changes	Your team owns every future fix	Generic vendor support, variable SLAs	Community/subscription support, no connector
Time to live	2–4 weeks from confirmed scope, UAT on staging first	Often months of in-house build and testing	Fast to install but needs your integration work anyway	Immediate, but the shipping gap stays unsolved

Frequently Asked Questions about Sendcloud Multi-Carrier Connector for ERPNext

How long does delivery take?

This is a build-to-order product, so there is no instant download. After a scoping call to confirm your carriers, Sendcloud plan, portal and return needs, and target ERPNext version, typical delivery is 2 to 4 weeks from confirmed scope, including UAT on staging before go-live.

Which ERPNext versions do you support?

We build and test against Frappe/ERPNext v15 and v16. The app installs as a standard Frappe app via bench and ships its customizations as fixtures, so it applies cleanly across your staging and production sites.

Do I need a Sendcloud account and which carriers are covered?

Yes, you supply an active Sendcloud account and API key pair. Because Sendcloud aggregates carriers, the single integration reaches DHL, DPD, UPS, GLS, PostNL and 80+ European carriers — you enable the carriers your Sendcloud plan includes.

How does it fit into our existing ERPNext workflow?

It hangs off the documents you already use. Doc events on Delivery Note (and optionally Sales Order) let staff create the parcel, fetch rates and buy a label in place; tracking number, carrier, cost and label PDF are written back to the order and a Sendcloud Parcel DocType for reporting.

What about support and updates after go-live?

Every build includes a post-go-live support window for bug fixes and defect resolution. Because you receive the full source and git repository, you own the app outright; we also offer ongoing support and enhancement retainers, including updates for future Sendcloud API or ERPNext version changes.

Can customers pick a service point or parcel locker, and return items themselves?

Yes. A client script plus the Sendcloud points API lets customers select a service point or parcel locker that is saved on the order, and we wire branded tracking pages and a self-service return portal using your Sendcloud return rules.

Will warehouse staff need access to the API credentials?

No. Credentials live in a secured Sendcloud Settings DocType, and permissions are wired to role profiles so warehouse and customer-service staff can print labels and manage shipments without ever seeing the API keys.