If you ship physical goods out of ERPNext, the shipping step is where the system runs out of road. ERPNext core gives you a Shipment DocType and a place to record a tracking number, but it has no live rate shopping, no label purchasing, no address validation, and no carrier webhooks. In practice that means someone copies the delivery address into a carrier portal or Shippo's own dashboard, eyeballs the cheapest service, buys the label there, and pastes the tracking number back onto the Delivery Note by hand. Rates are not compared consistently, tracking numbers go missing, and finance has no clean link between what you paid to ship and the sales order it belongs to.

This connector makes Shippo a first-class part of the ERPNext document flow. We deliver it as a proper Frappe app installable with bench get-app and bench install-app, not a pile of loose customizations. It ships a Shippo Settings single DocType to hold your API token, default parcel presets, enabled carrier accounts and fallback service levels; a rate-shopping action on Delivery Note and Shipment that calls Shippo server-side and returns a sortable list of live quotes from 85+ carriers so a rep picks a service inline; and Shippo Transaction plus Shippo Tracking Event DocTypes so every label purchase and status update is an auditable record tied back to its source document.

Technically, the integration lives in server-side Python. A whitelisted method (@frappe.whitelist()) brokers every call to the Shippo REST API so your token is never exposed to the browser, and a client script adds the "Get Rates" and "Buy Label" buttons to the Delivery Note form. hooks.py doc events (on_submit, validate) trigger address validation and can auto-request rates on submit; the purchased label PDF and commercial invoice are stored as File attachments against the document. Inbound Shippo tracking webhooks are received on a whitelisted, signature-verified endpoint and fan out to Shippo Tracking Event records, while a scheduler_events hourly job reconciles any deliveries that missed a webhook. Access is governed by ERPNext's standard permissions and role profiles, so only users with the shipping role can buy labels, and every transaction is written under the correct company and cost center for clean reconciliation. Built and tested for Frappe/ERPNext v15 and v16.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm which carriers, parcel presets, warehouses and document types you actually use, then build against your ERPNext version on a staging bench. You get the installable source, install and configuration on your environment, UAT sign-off before anything touches production, and a rollback plan. Typical delivery is one working week from confirmed scope. There is no instant download — ECOSIRE builds it, installs it, hands over the git repository, and supports it afterward.