Multi-Carrier Shipping Hub

Transportation management in Dynamics 365 Finance and Supply Chain Management is genuinely capable, and it rates against tables you maintain. That is the problem. The moment carriers reprice, add a peak surcharge, change a fuel index or renegotiate a zone, the rate tables in F&O become a historical document. Warehouses respond the way warehouses always do: they open the carrier's own web portal on a second screen, key the shipment again, print the label from there, and paste a tracking number back into the ERP later, if there is time. The cost that finally arrives on the carrier invoice bears no traceable relationship to anything the system quoted.

Everything downstream inherits that break. Freight recovery on the sales order is a guess. Carrier invoice audit is impossible at line level, so nobody does it. Customer service cannot answer a where-is-my-order question without a portal login. And the routing decision — which carrier, which service, for this carton, to this postcode, by this date — is made from memory by whoever is packing.

What ECOSIRE builds

A shipping hub that lives inside F&O and rates live against the carrier accounts you already hold. Built to order for your warehouse topology and your carrier mix, delivered as X++ extensions with the source.

Live rate shopping where the decision is made

Rating happens at pack or confirm time, against your negotiated accounts, across parcel, LTL and FTL in the same call. The hub is implemented as a rate engine so it appears alongside native rating rather than beside it, which means the rate route workbench, freight bill types and the transportation configuration your team already understands stay meaningful. Selection is driven by rules you define: cheapest, fastest, cheapest that still meets the requested delivery date, a customer-mandated carrier, a customer collect account, or a routing guide by zone, weight and service level.

Labels at the pack bench

Labels are generated at container or package level and printed through the F&O document routing agent to the network printer at the station, in ZPL for thermal printers or PDF where that is what the site runs. Rating is aware of the packing structure — dimensional weight, container types, multi-piece consignments — so a three-carton shipment is quoted and labelled as a three-carton shipment rather than a rounded guess.

Inside the warehouse mobile app

Where your team works in the warehouse mobile app, the hub is called from the pack, containerize and load steps. The operator scans, closes the container, and receives a rated, labelled carton without leaving the device flow or touching a browser. Nothing about the existing wave, work template and load structure has to change to accommodate it.

Addresses, tracking and the customer

Addresses are validated and classified residential or commercial before a label is bought, with corrections written back to the delivery address and an audit trail of what changed. Tracking numbers are captured against the shipment and packing slip, and status is polled into a tracking workspace on the batch framework. Because tracking is exposed through data entities, your customer portal, service desk or notification flow can read it over OData without anyone re-keying a consignment number.

Freight cost that finance can audit

Quoted freight lands as charges on the sales order or as an estimated freight accrual, depending on how you recover it. When the carrier invoice arrives it is imported and matched line by line against what was quoted and what was actually shipped, producing a variance report. Unused labels are voided and audited so they never become billed freight. Ledger dimensions default onto freight postings so cost lands in the right place in the management pack without a manual journal.

International shipments

Where you ship across borders, commercial invoice data, HS codes from the released product, incoterms and delivery terms feed the carrier call so duty and tax handling is declared correctly at the point the label is bought, rather than corrected by a broker afterwards.

Who it is for

Distributors, manufacturers and multi-site retailers running F&O with a real warehouse operation — typically the Warehouse Management module, multiple ship-from sites, and a mix of small parcel and freight. It suits organisations with negotiated carrier contracts they want to actually exploit, and finance teams who have never been able to audit a freight invoice. It is not for a business shipping a handful of parcels a week from one site, where a carrier portal is honestly sufficient.

How delivery works

1. Scoping call. F&O version and update cadence, legal entities, warehouses and pack stations, whether you run WHS or basic warehousing, your carrier list and which accounts and API credentials exist, printer estate, routing rules, and how freight is recovered from customers today.

2. Fixed quote. A written scope naming every carrier integration, the routing rules, the label formats, the mobile app steps touched, the reports and the acceptance criteria — priced as a fixed figure. We do not start building before you approve it.

3. Build. Development runs against your F&O version, with each carrier integration demonstrated against your own account in a test mode before it is considered done.

4. Install in test, then production. The deployable package goes into your Tier-2 sandbox through your LCS and DevOps pipeline. We configure carrier accounts, routing rules and printers with your team, run live labels at a real pack bench, and then schedule production. Typical end-to-end lead time is one working week depending on how many carriers are in scope.

5. Support. A defined support window follows go-live for defect fixes and carrier API changes within the delivered scope. You already hold the source and the documentation.

What we do not claim

There is no instant download and no free trial, because nothing exists until we build it for your estate. We do not resell a shipping platform and we make no certification or partnership claims. We integrate against the carrier accounts and credentials you hold, using the carriers' own interfaces, and we tell you honestly during scoping which of your carriers expose an API good enough to rate and label against and which do not.