EU distributors and e-commerce SMBs running ERPNext usually manage European parcel shipping in a browser tab that has nothing to do with their ERP. A picker confirms a Delivery Note, then someone re-keys the address, weight, and parcel dimensions into the Packlink PRO or LetMeShip portal, eyeballs a dozen carrier quotes, buys a label, and pastes a tracking number back into ERPNext by hand. ERPNext core ships a Shipment DocType and a couple of carrier integrations, but it has no native concept of a rate-comparison aggregator, no live multi-carrier quote table on the delivery, and no automatic customs-document generation for cross-border EU/UK parcels. That gap is exactly where margin leaks and mis-ships happen.

We build a proper Frappe app (erpnext_packlink_letmeship) with its own module, DocTypes, and hooks.py wiring — not a pile of loose server scripts. On a submitted Delivery Note or Shipment, a whitelisted method (frappe.whitelist()) calls the Packlink PRO and/or LetMeShip REST APIs, normalizes each aggregator's response, and writes the results into a Carrier Quote child table so your team sees ranked, comparable rates — carrier, service level, transit time, drop-off vs pickup, and total price — side by side inside ERPNext. Credentials and per-account defaults live in a single Packlink LetMeShip Settings DocType (API keys stored via Frappe's encrypted Password fieldtype), and every outbound call is logged to a Shipment Sync Log DocType so failed bookings and API errors are auditable, retryable, and never silent.

Once a quote is selected, the app books the shipment through the chosen aggregator, pulls back the shipping label and any required customs documents (CN22/CN23 commercial-invoice data assembled from the ERPNext Sales Invoice/item HS codes), and attaches them to the source document as printable File records. A client script on the Delivery Note form exposes a "Compare Rates" and "Book Shipment" button so the flow stays inside the desk UI your team already uses. Where the destination country supports it, drop-off point selection is surfaced so the customer or picker can choose a parcel-shop instead of a home delivery. A scheduler_event (hourly/daily, tuned to your volume) polls the aggregator tracking endpoints and writes status transitions back onto the shipment, so "in transit / out for delivery / delivered" is visible in ERPNext without anyone logging into a carrier site.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call to confirm which aggregators you use (Packlink PRO, LetMeShip, or both), your carrier mix, origin/destination countries, customs requirements, and your ERPNext/Frappe version (v15 or v16). We then build against a staging bench, run UAT with your real addresses and parcel profiles, and hand over installable source, a git repository, and documentation. Typical delivery is one working week from confirmed scope, followed by a post-go-live support window. You own the code; ECOSIRE installs it, trains your team, and supports it.