Belgian ERPNext merchants shipping with bpost usually end up in one of two bad places: staff re-key every order into the bpost Shipping Manager web portal, or they buy a generic multi-carrier plugin that treats bpost as an afterthought and never surfaces parcel-locker choices, Belgian pickup points, or COD reconciliation. ERPNext core gives you a Shipment DocType and a Delivery Note, but it has no bpost Shipping Manager API client, no label PDF retrieval, no barcode/tracking storage, and no way to push a status back to the customer. That gap is exactly where hours leak and where mis-shipments and untracked parcels start costing money.

ECOSIRE builds a proper Frappe app, ecosire_bpost, installed on your own bench alongside ERPNext — not a fragile set of pasted server scripts. It ships a bpost Settings single DocType (API user, passphrase, account ID, default product configuration) with credentials stored encrypted in the site config, plus per-shipment fields extended onto Delivery Note and Shipment for service product, parcel type, weight, insurance, and delivery method. Whitelisted methods exposed over the Frappe REST API — for example ecosire_bpost.api.create_label and ecosire_bpost.api.get_tracking — call the bpost Shipping Manager API, receive the label, and attach the returned PDF/PNG straight to the document via the File DocType so warehouse staff print from inside ERPNext.

Technically the automation is wired through hooks.py doc events and scheduler events rather than manual button-mashing. A Delivery Note on_submit handler can request a label and write back the bpost barcode and tracking URL; a scheduler_events hourly job polls open shipments and updates a Tracking Status field and timeline so customer-service sees live delivery progress without opening the bpost portal. Parcel-locker and pickup-point delivery is handled with a client script that lets the user pick a bpost pickup point (Cyclone/parcel-locker network) on the sales document before the label is generated. COD is supported by mapping the ERPNext outstanding amount into the bpost cash-on-delivery product and reconciling the collected amount back against the invoice. Access is governed by a dedicated Role and Role Profile so only shipping staff can generate labels or edit bpost credentials.

Because this is build-to-order, nothing is a pre-packaged download. We start with a short scoping call to confirm your bpost contract products (national, international, pickup points, COD), your Delivery Note workflow, and your Frappe/ERPNext version — the app targets and is tested on both v15 and v16. You approve a fixed scope, we build against a staging copy of your instance, run UAT there, and only then install on production with a rollback plan. Typical delivery is one working week from confirmed scope, and you receive the full source in a git repository so you are never locked to us.