A carrier milestone tracking and customer notification layer for Dynamics 365 Finance & Operations shipments. Built to order by ECOSIRE against your carriers and workflows — not an off-the-shelf download. Built to order by ECOSIRE for Dynamics 365 F&O (build-to-order) — indicative price from $799.00 USD; request a quote for a scoped proposal.
A carrier milestone tracking and customer notification layer for Dynamics 365 Finance & Operations shipments. Built to order by ECOSIRE against your carriers and workflows — not an off-the-shelf download.
按单定制
Once a shipment is confirmed and packed in Dynamics 365 Finance & Operations, the tracking story stops. The load is released, the packing slip is posted, a tracking number lands somewhere in the shipment record, and from that moment the customer service desk works blind. Agents keep a browser window open per carrier, paste tracking numbers into portals one at a time, and only discover an exception — a failed delivery attempt, a customs hold, a weather delay — when the customer phones to complain. Nobody inside F&O knows a delivery is late until the sales order goes past its confirmed ship date and somebody happens to run a report.
The consequences are boring and expensive. Service agents spend their day doing lookups a machine should do. Delivery promises to customers are made from stale data. Exceptions are discovered by the customer, not by you. And because the tracking status lives on a carrier portal rather than in the ERP, none of it can drive a workflow, a credit hold decision, or a customer notification.
ECOSIRE builds a shipment tracking and notification hub as an X++ extension model for Dynamics 365 Finance and Supply Chain Management. No overlayering — everything is chain-of-command, extension classes, table extensions and event handlers over the standard WHSShipmentTable, WHSLoadTable, SalesTable and CustPackingSlipJour objects, so your environment stays upgradeable through Microsoft's service update cadence.
A new tracking header table hangs off the load and shipment, keyed by carrier code and tracking number, with a child milestone table holding the raw and normalised event stream. Normalisation matters: each carrier speaks its own vocabulary, so the extension maps carrier-specific status codes to a single internal milestone enum — created, picked up, in transit, out for delivery, delivered, exception, returned — that the rest of F&O and your reporting can rely on. Carrier codes come from the standard shipping carrier setup so the mapping stays configuration, not code.
A batch job class extending RunBaseBatch (or a SysOperation service, depending on your preference) polls each configured carrier endpoint on a schedule you control from the batch framework. Polling is incremental and windowed: only shipments in an open tracking state are queried, with exponential backoff on transient carrier failures and a dead-letter table for tracking numbers the carrier does not recognise. Where a carrier offers webhooks instead of polling, ECOSIRE exposes a custom service endpoint so the carrier can push events straight into the milestone table. Every carrier integration is built against the credentials and account numbers you supply during scoping — ECOSIRE writes the connector for the carriers you actually use.
A second batch job evaluates open shipments against rules you configure per legal entity: no scan within N hours of despatch, delivery date slipping past the confirmed ship date on the sales line, an exception milestone received, or a shipment sitting in customs beyond a threshold. Breaches raise records in an exception workbench form and can trigger the standard workflow framework so a customer service supervisor gets a real approval-style task rather than an email that gets ignored. Alerts can also be pushed to a Teams channel or a Power Automate flow through Dual-write or a custom service, where your operating model expects that.
Branded notification templates are held as configurable records with token substitution for order number, item lines, carrier, tracking number, estimated delivery and a tracking link. Notifications are queued in a dedicated outbound table and sent by batch, so a mail server outage never blocks the shipment posting. Sending respects per-customer opt-out flags on an extended CustTable field, and every send is logged against the shipment for audit. The notification event points at a branded tracking page rather than the carrier's own portal, so the customer stays in your brand.
Users get a tracking workspace with tiles for shipments in transit, exceptions open, deliveries due today and notifications failed, plus list pages filtered by legal entity and warehouse. The shipment and sales order forms gain a tracking FactBox showing the milestone timeline inline, so an agent answering a call never leaves the order. All tracking and milestone tables are exposed as data entities through the Data Management Framework, with OData endpoints enabled, so Power BI, a customer portal or a downstream system can read the same normalised event stream. Ledger dimension defaults on any carrier surcharge postings follow your existing financial dimension setup.
Distributors and manufacturers running outbound shipping from F&O with more than one carrier, where the customer service team currently checks carrier portals by hand. It suits organisations with multiple legal entities and warehouses that need consistent milestone semantics across carriers, and businesses whose delivery promise is part of the product.
This app is built to order. Nothing is downloaded and nothing is pre-built.
1. Scoping call. ECOSIRE walks your carriers, warehouses, legal entities, notification requirements and F&O version with your team, and confirms what integration credentials exist. 2. Fixed quote. You receive a written scope and a fixed price before any development starts. No hourly drift. 3. Build. ECOSIRE develops the extension model against a matching F&O version, typically over two to four weeks depending on carrier count. 4. Install in test. The deployable package is delivered to your LCS project (or your ADO pipeline) and applied to your sandbox first. Your team validates against real shipments and real carrier accounts. 5. Production. After your sign-off, the same package moves to production through your normal release process. ECOSIRE supports the cutover but does not deploy to your production environment without written approval. 6. Support. A defect-fix window follows go-live, covering issues in the delivered code against the agreed scope.
Source code for the model is handed over. You are not locked into ECOSIRE to keep the app running.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
We install on your instance, hand over the source, and support it for twelve months.
Their team spends hours a day pasting tracking numbers into carrier portals and still learns about failed deliveries from angry customers. This puts every milestone inside F&O next to the order, and pushes exceptions to a supervisor before the customer notices.
They run several carriers whose status vocabularies do not agree, so there is no single view of what is late. Normalised milestones and configurable exception rules give one consistent picture across carriers, warehouses and legal entities.
They have to keep the environment upgradeable through Microsoft's service updates and refuse anything that overlayers. This is delivered as a clean extension model with source handover, data entities and standard batch and workflow integration.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 |
|---|---|---|---|
| Carrier milestones stored inside F&O against load and shipment | 包含 | 包含 | 部分支持 |
| Status codes normalised to one milestone vocabulary across carriers | 包含 | 部分支持 | 部分支持 |
| Configurable exception rules with workflow task assignment | 包含 | 部分支持 | 部分支持 |
| Branded customer delivery notifications with opt-out and audit log | 包含 | 部分支持 | 部分支持 |
| Extension-only, no overlayering, upgrade-safe | 包含 | 部分支持 | 部分支持 |
| Data entities and OData exposure for Power BI and portals | 包含 | 部分支持 | 部分支持 |
| Fixed price agreed before development starts | 包含 | 不包括在内 | 部分支持 |
| Full X++ source handed over to your repository | 包含 | 包含 | 不包括在内 |
A build-to-order integration between Dynamics 365 F&O and your third-party logistics providers or external WMS, covering ASNs, receipts, shipments, adjustments and returns with a full audit trail.
A build-to-order Amazon Selling Partner API integration for Dynamics 365 Finance and Supply Chain Management. Nothing is pre-built: ECOSIRE scopes, quotes and develops it for your environment.
A built-to-order X++ integration linking your BigCommerce storefront to Dynamics 365 Finance & Operations. We scope, quote and build it for you — nothing is downloaded ready-made.
A build-to-order X++ extension for Dynamics 365 Finance & Operations that tracks supplier-owned and customer-site stock, captures consumption and triggers invoicing. We build it for you after a fixed quote.
从$799.00起
起步价——最终按您的需求范围报价