Shippo Multi-Carrier Connector for ERPNext

Key Features

Frappe app packaged the standard way, installable via `bench get-app` and `bench install-app` on your own bench

`Shippo Settings` single DocType holding API token, enabled carrier accounts, default parcel presets and fallback service levels

Server-side `@frappe.whitelist()` broker method so the Shippo API token never reaches the browser

Live rate shopping across 85+ Shippo carriers returned as a sortable list on the Delivery Note / Shipment, chosen inline before buy

Discounted label purchase using Shippo's pre-negotiated rates, with the label PDF stored as a File attachment on the source document

Address validation on `validate` / `on_submit` doc events via `hooks.py`, flagging undeliverable or corrected addresses before a label is bought

`Shippo Transaction` DocType recording every label buy, cost, carrier, service level and object id, linked back to the Delivery Note

`Shippo Tracking Event` DocType capturing each status change for an auditable delivery timeline

Signature-verified, whitelisted webhook endpoint that ingests Shippo tracking updates in real time

Hourly `scheduler_events` reconciliation job that back-fills tracking for shipments that missed a webhook

Client script adding `Get Rates` and `Buy Label` buttons to the ERPNext shipping form, no portal-hopping

Permissions and role-profile aware — only users with the shipping role can purchase labels or void transactions

Company and cost-center stamped on every transaction for clean freight-cost reconciliation in accounts

Label void / refund action that calls Shippo and reflects the reversal on the linked `Shippo Transaction`

Built and tested against Frappe/ERPNext v15 and v16, with the target version fixed at scoping

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

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 2-4 weeks from confirmed scope. There is no instant download — ECOSIRE builds it, installs it, hands over the git repository, and supports it afterward.

What you get

Installable source code for your version of the connector as a Frappe app

Installation and configuration on your ERPNext environment (Shippo token, carriers, parcel presets, role permissions)

Technical documentation covering DocTypes, whitelisted methods, hooks, webhook setup and scheduler jobs

End-user guide plus a live training session for your shipping and finance teams

UAT on a staging bench with sign-off before any production change, and a documented rollback plan

Post-go-live support window for defect fixes and configuration adjustments

Handover of the complete git repository so you own and can extend the code

Version-compatibility note and upgrade guidance for Frappe/ERPNext v15 and v16

Who this is for

SMB ERPNext shipping lead

Runs daily outbound fulfillment on ERPNext and wants to compare 85+ carriers and buy discounted Shippo labels directly on the Delivery Note instead of re-keying addresses into a separate carrier portal.

Operations / warehouse manager

Owns delivery accuracy and needs address validation before labels are bought, real-time tracking events on every shipment, and a scheduler-backed reconciliation so nothing falls through the cracks.

Finance / accounts controller

Wants every shipping cost captured as an auditable `Shippo Transaction` stamped with company and cost center, cleanly linked to the source document for freight-cost reconciliation and margin analysis.

ERPNext system administrator

Needs a properly packaged Frappe app with clear DocTypes, hooks and role permissions that installs cleanly on their v15/v16 bench and survives updates, with the git repo handed over for internal maintenance.

How Shippo Multi-Carrier Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Rate shopping across carriers	Live 85+ carrier quotes on the Delivery Note, sortable, picked inline	Possible but you design and maintain the whole rate-shopping flow	Often single-carrier or a fixed subset, limited UI	None — no live rates in ERPNext core
Discounted label purchase	Buy Shippo discounted labels in-document, PDF stored on the record	Build and test the Shippo transaction and label storage yourself	Sometimes, but tied to that vendor's supported carriers	Not available — record a tracking number by hand only
Address validation	On validate/on_submit doc events before a label is bought	You wire the validation calls and error handling	Varies; often absent or add-on	No address validation
Tracking updates	Signature-verified webhook plus hourly scheduler reconciliation	You build the webhook endpoint and reconciliation job	Polling or manual refresh in many apps	Manual entry only
Fit to your ERPNext version and process	Built for your v15/v16 bench, carriers and document types	Fully bespoke but all effort and risk on you	Generic; you adapt your process to the app	Generic core behavior
Security of API token	Server-side whitelisted broker; token never reaches browser	Depends entirely on how your developer implements it	Varies by vendor, not always transparent	N/A — no integration
Support and ownership	Post-go-live support window plus full git repo handover	You own it, but also own every bug and update	Vendor support tiers; source usually closed	Community/support plan only, no shipping feature
Delivery model	Build-to-order, UAT on staging, rollback plan, 2-4 weeks	Timeline and QA depend on your team's capacity	Instant install but limited fit and configurability	Already present but lacks the capability

Frequently Asked Questions about Shippo Multi-Carrier Connector for ERPNext

Is this an instant download from the Frappe Cloud Marketplace?

No. This is a build-to-order connector. ECOSIRE builds it against your ERPNext version and your carrier/parcel configuration, installs it, and supports it. There is no instant-download package — the work starts after we confirm scope on a call.

How long does delivery take?

Typical delivery is 2-4 weeks from confirmed scope. The exact timeline depends on how many carriers, parcel presets, warehouses and document types are in play, and whether you want extras like multi-warehouse rate logic. We fix the timeline in writing after the scoping call.

Which Frappe and ERPNext versions are supported?

The connector is built and tested for Frappe/ERPNext v15 and v16. We fix the exact target version at scoping and build against your environment, so what you receive matches your bench rather than a generic build.

How are updates and support handled after go-live?

Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository, your team can also maintain and extend the code. Longer-term support or enhancements can be arranged separately.

Do I need my own Shippo account and carrier accounts?

Yes. You bring your Shippo account and API token, and connect your own carrier accounts (or use Shippo's pre-negotiated discounted rates) inside Shippo. The connector reads that configuration through `Shippo Settings` — we do not resell shipping or hold your token.

Is my Shippo API token exposed to the browser?

No. All Shippo API calls run server-side through a `@frappe.whitelist()` broker method, and the token lives in the `Shippo Settings` DocType. The browser only ever triggers whitelisted actions; it never sees the token. The inbound tracking webhook is signature-verified as well.

Can it validate addresses and track shipments automatically?

Yes. Address validation runs on the document's `validate`/`on_submit` events so bad addresses are caught before a label is bought, and a signature-verified webhook plus an hourly scheduler job keep `Shippo Tracking Event` records up to date without manual checking.