A build-to-order Dynamics 365 Business Central extension that captures freight, duty, insurance and handling charges and allocates them accurately to inventory cost on receipt — so importers and distributors see true landed product cost. Built, installed as a per-tenant AL extension, and supported by ECOSIRE. Built to order by ECOSIRE for Dynamics 365 BC (build-to-order) — indicative price from $499.00 USD; request a quote for a scoped proposal.
Uygulama manifestosu
İş akışınıza göre tasarlandı
A build-to-order Dynamics 365 Business Central extension that captures freight, duty, insurance and handling charges and allocates them accurately to inventory cost on receipt — so importers and distributors see true landed product cost. Built, installed as a per-tenant AL extension, and supported by ECOSIRE.
Kendiniz kurmanıza gerek yok — ECOSIRE tarafından geliştirilen, kurulan ve desteklenen çalışır bir uygulama.
Tek seferlik geliştirme fiyatıyla başlayın. Kapsamı başlangıçta sizinle birlikte belirleriz.
ECOSIRE, Dynamics 365 Business Central ortamınızda geliştirir, yapılandırır ve kurar.
Yaklaşık 2–4 haftada yayına alırsınız; lansman sonrası bir destek süresi de dahildir.
Business Central's native item charges let you assign a single freight or duty amount to a posted receipt, but they fall short the moment you import in volume: no shipment-level grouping, no estimated-vs-actual reconciliation, weak multi-currency handling, and allocation limited to equal/value/weight/amount on one document at a time. Landed Cost Management closes that gap.
This is a build-to-order extension, not an instant AppSource download. ECOSIRE designs, develops, installs and supports it on your Business Central environment (cloud/SaaS or on-prem) as a per-tenant AL extension, so it fits your chart of accounts, item categories, currencies and posting rules rather than forcing a generic schema on you.
The app introduces a Voyage/Shipment Cost document that groups every cost line for an inbound consignment — ocean/air freight, customs duty, insurance, terminal handling, demurrage — and allocates them across the receipt lines by value, weight, quantity or volume. It captures estimated charges at booking and reconciles them against actual vendor invoices, posting the variance to inventory or a cost-difference account. Multi-currency charges are handled with the document or a charge-specific exchange rate so cost is always recorded in your local currency.
Built with AL using table/page extensions and event subscribers on the warehouse receipt and item-charge posting routines, it stays upgrade-safe across Microsoft's monthly releases. Charge headers and lines are exposed through custom API pages (OData v4) for Power BI, Power Automate and Dataverse, and a job queue entry can pull freight-forwarder rates or flag unreconciled voyages. Dedicated permission sets keep landed-cost posting controlled.
ECOSIRE delivers source, a signed per-tenant build, a sandbox validation pass, and post-go-live support.
Books inbound shipments and needs estimated landed cost at PO time, then a clear variance when the freight and duty invoices actually land — without rekeying figures into spreadsheets.
Owns item cost accuracy. Wants freight, duty and insurance baked into unit cost on receipt so margins, COGS and inventory valuation are true rather than understated.
Needs auditable cost build-up per shipment, reconciled estimates vs. actuals, and Power BI visibility into landed cost trends across voyages and suppliers.
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| Shipment/voyage-level grouping of charges across multiple receipts | Dahil | Kısmi destek | Kısmi destek | |
| Estimated vs. actual landed cost reconciliation with variance posting | Dahil | Kısmi destek | Kısmi destek | |
| Allocation by value, weight, quantity AND volume | Dahil | Kısmi destek | Kısmi destek | |
| Multi-currency charge handling with per-charge exchange rates | Dahil | Kısmi destek | Kısmi destek | |
| Built to your chart of accounts, currencies and posting rules | Dahil | Dahil | Dahil değil | |
| Upgrade-safe per-tenant AL extension (no base-app modification) | Dahil | Kısmi destek | Dahil | |
| OData/REST API pages for Power BI & Dataverse integration | Dahil | Kısmi destek | Kısmi destek | |
| Full source code ownership handed to you | Dahil | Dahil | Dahil değil | |
| Installed, validated and supported on your environment by the vendor | Dahil | Kısmi destek | Dahil değil |
Typical lead time is 2–4 weeks from requirements sign-off, depending on how many charge types, allocation rules and integrations you need. The flow is: discovery and spec, AL development, install on your sandbox for a validation pass with your own data, then a scheduled production deployment. You get a firm timeline in writing before work starts — there is no instant AppSource download; we build, install and validate it on your environment.
Every build includes a post-go-live support window for fixes and questions. Because it ships as a per-tenant extension using table/page extensions and event subscribers (never base-app code edits), it is upgrade-safe across Microsoft's monthly Business Central releases. We re-validate it against major version updates on request, and you hold the full source, so you are never locked in. Ongoing support and enhancement retainers are available.
Yes. It is delivered as a per-tenant AL extension and installs on Business Central online (SaaS) via the admin centre, or on an on-premises / private-cloud deployment. We confirm your version (and any country localisation) during discovery and build the .app to match so it installs cleanly on your sandbox first.
Native item charges let you assign one charge to a posted document and allocate by equal/amount/weight/value on that document alone. There is no shipment/voyage grouping across multiple receipts, no estimated-vs-actual reconciliation, and limited multi-currency control. This extension adds voyage-level grouping, an estimate-then-reconcile workflow with variance posting, volume-based allocation, and duty/customs capture — while still feeding the standard BC cost engine.
Yes. Voyage headers and allocation lines are exposed through custom API pages (OData v4 / REST), so you can pull them into Power BI, trigger Power Automate flows, or sync to Dataverse and the Power Platform. A job queue entry can also flag unreconciled voyages or import forwarder rate sheets on a schedule.
A build-to-order Dynamics 365 Business Central extension that captures freight, duty, insurance and handling charges and allocates them accurately to inventory cost on receipt — so importers and distributors see true landed product cost. Built, installed as a per-tenant AL extension, and supported by ECOSIRE.