If you ship with FedEx, ERPNext gives you a Delivery Note and a Shipment DocType, but no live connection to a carrier. Warehouse teams end up copying weights and addresses into fedex.com, keying tracking numbers back into ERPNext by hand, and guessing at freight cost until the invoice lands. There is no rate at the point of sale, no label from inside the Delivery Note, no customs commercial invoice for international parcels, and no delivery status flowing back to the customer. ERPNext core runs out of road exactly where cross-border and multi-warehouse FedEx shipping gets complicated.

ECOSIRE builds a proper Frappe app — its own module, not a pile of loose customizations — that talks directly to the FedEx REST API. We add a FedEx Settings DocType that stores OAuth client credentials per warehouse or company, so each origin authenticates with its own FedEx account and negotiated rates. From a Delivery Note or the standard Shipment DocType, a whitelisted server method calls FedEx Rate to return live service options (Ground, Express, International Priority) with landed cost, and the user selects a service before confirming. On submit, hooks.py doc events call the Ship endpoint to generate the label (PDF or ZPL for thermal printers) plus, for international movements, the commercial invoice and required customs documentation from your item HS codes and declared values. Addresses are validated against FedEx before a label is ever purchased, so you catch bad shipping addresses at data-entry time rather than paying for a correction.

Under the hood the app follows Frappe conventions end to end: DocTypes for settings, shipment records, and rate logs; server scripts and hooks.py handlers for the rate/label/void lifecycle; client scripts that add the rate-shopping and print-label buttons to the Delivery Note form; role profiles and permissions so only shipping roles can spend money on labels; and a scheduler event that polls FedEx Track on a fixed interval to sync in-transit and delivered statuses back onto the shipment, updating the linked Delivery Note and optionally notifying the customer. Every carrier call is available as a whitelisted method over the Frappe REST API, so your POS, e-commerce front end, or a partner system can request rates and buy labels programmatically. Credentials stay in the Frappe site config, OAuth tokens are cached and refreshed automatically, and every request/response is logged for dispute resolution.

Because this is build-to-order, you are not downloading a generic marketplace app and hoping it fits. After a short scoping call we confirm your FedEx account structure, the services and packaging you actually use, your international paperwork requirements, and your ERPNext version (we support Frappe/ERPNext v15 and v16). We build against that scope, ship you the installable source, deploy it to a staging bench for UAT, and cut over to production with a rollback plan. Typical delivery is one working week from confirmed scope, and you get a support window plus the full git repository so your team owns the code.