Most ERPNext merchants hit the same wall the moment they start shipping at volume: ERPNext core has no native carrier integration. You can print a Shipping Rule and a packing slip, but there is no way to compare live rates across FedEx, UPS, USPS, DHL, and regional couriers, no one-click label purchase, no address validation, and no automatic tracking. Warehouse staff end up copy-pasting order data into a carrier portal, buying labels off-system, and manually pasting tracking numbers back into the Delivery Note — a slow, error-prone process that leaves your Sales and Support teams blind to where a shipment actually is.

The EasyPost Multi-Carrier Connector closes that gap by building EasyPost directly into your ERPNext instance as a proper Frappe app. We add a EasyPost Settings single DocType to hold your API key (production and test), default parcel presets, and carrier-account selection, plus a Shipment and Shipment Rate DocType structure that binds each shipment back to its source Delivery Note or Sales Order. From the Delivery Note itself, a client script exposes a "Get Rates" action that calls a whitelisted server method; that method builds the EasyPost shipment payload from the document's addresses and items, requests live rates across every carrier account you've connected, and writes them back as child rows you can sort by price and transit time. Cheapest-rate and rule-based selection (for example "cheapest ground under 3 days", or "force UPS for insured orders over a threshold") are enforced in Python so buying the wrong service is impossible.

Technically, the connector is real Frappe engineering, not a screen-scrape. Label purchase, address verification, and rate requests run through whitelisted methods and are wired into the document lifecycle via hooks.py doc events (for example on_submit of a Delivery Note can auto-buy the selected label and attach the PDF/PNG to the document). EasyPost webhook events for tracking updates hit a dedicated whitelisted endpoint that verifies the payload and updates a Shipment Tracking log plus the parent document's status, so your team sees "In Transit" or "Delivered" without touching a carrier site. A Frappe scheduler event provides a reconciliation sweep for any tracker that missed its webhook. Address verification uses EasyPost's verify API before a label is ever purchased, catching undeliverable addresses at data-entry time. Everything respects ERPNext permissions — we ship a role profile so warehouse operators can buy labels while rate configuration stays locked to managers — and every API call is logged for audit and debugging.

Because this is build-to-order, you are not downloading a generic marketplace plugin and hoping it fits. ECOSIRE scopes your exact carriers, document flow, warehouse layout, and edge cases on a short call, then builds the app against your Frappe/ERPNext v15 or v16 instance. We install it on a staging site first, run UAT with your real orders, and only then cut over to production with a documented rollback path. Typical delivery is one working week from confirmed scope, depending on how many carriers and custom rules you need. You receive the full source code, a git repository handover, technical and user documentation, a training session, and a post-go-live support window — so the integration is yours to keep and extend, not a black box you rent.