DHL / FedEx / UPS Carrier Connector

This is built to order. After a short scoping call to confirm carriers, services, packaging types and label layouts, a typical build-and-deploy runs about 2 to 4 weeks depending on how many carrier accounts and international paperwork variants you need. ECOSIRE develops the AL extension, validates it against the carriers' sandbox/test endpoints, then installs it as a per-tenant extension on your environment and runs a supervised production cutover. You are not downloading a generic app — you receive a connector wired to your own accounts and workflow.

ECOSIRE supports the connector after delivery. The big-three carriers periodically change their APIs (DHL MyDHL, FedEx RESTful API and UPS OAuth migrations are recurring examples), and we maintain the extension against those changes under a support arrangement agreed at purchase. Because it is a per-tenant AL extension with no base-app modification, it is upgrade-safe across Business Central monthly and major releases; we re-validate after significant BC updates and after any carrier API change you're notified of.

Yes. The connector authenticates with your own DHL Express, FedEx and UPS account credentials, so every rate quote and label uses your contracted pricing and discounts. This is the core reason SMB shippers choose direct account integration over an aggregator that re-rates and marks up your shipments.

No. Everything is delivered through AL table and page extensions, event subscribers, a dedicated permission set and the job queue — standard extensibility patterns. The base app is untouched, credentials live in isolated storage, and the package is upgrade-safe across BC releases.

Yes. The connector can optionally publish shipment and tracking events to Dataverse, which lets you build Power BI dashboards on carrier spend and delivery performance or trigger Power Automate flows (for example, notifying a customer when a tracking status changes). This is scoped as part of the build if you need it.