Cold Chain Logistics for Business Central

Características clave

Temperature-zone model on `Location` and `Bin` via table and page extensions — setpoint, tolerance band, permitted item temperature classes and maximum ambient dwell minutes

Put-away and movement validation in a codeunit subscribing to warehouse activity events, blocking a frozen item into a chilled or ambient bin before the line posts

FEFO picking engine that ranks by expiration date and enforces a per-customer minimum remaining shelf life, so short-dated lots are never allocated against a contract that forbids them

`Temperature Excursion` document (header/line) capturing source, start/end, min/max reading, duration above tolerance, affected bins and the lot numbers resident at the time

Automatic lot quarantine on excursion, with a dispositioning workflow — release, downgrade, or scrap — recorded with user, timestamp and reason code against the lot

Reefer trip planning with vehicle and compartment master data, multi-temperature compartment assignment, and load sequencing that respects both drop order and thermal compatibility

API pages on Business Central's REST API v2.0 / OData v4 surface for logger and telematics ingestion, so readings post against a trip, a compartment and the lots on board

Job queue entries for scheduled telemetry polling, dwell-time monitoring and expiry-horizon alerting, with failure handling and Application Insights telemetry

Dock-to-stock timers that start on receipt registration and flag any receipt left outside its permitted ambient window before put-away completes

Delivery temperature certificates, lot genealogy reports for recall tracing, and excursion registers as report objects driven from posted data — HACCP and GDP audit shaped

Dedicated permission sets separating driver, warehouse operator, QA releaser and administrator surfaces, so an excursion release cannot be self-approved by the operator who logged it

Dataverse and Power Platform connectivity for handheld dock-reading Power Apps and Power BI models over excursion and dwell history

Upgrade codeunits and versioned data migration so zone configuration, excursion history and trip data survive Business Central release-wave upgrades

Built for current Business Central release waves on SaaS (online) and on-premises, shipped as a per-tenant extension or an AppSource-shaped app

Hecho a medida, listo para ti

Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.

Haces el pedido

Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.

Creamos e instalamos

ECOSIRE la crea, la configura y la instala en tu Dynamics 365 Business Central.

En marcha + soporte

Sales en vivo en unas 2–4 semanas, con un periodo de soporte posterior al lanzamiento.

Sobre este producto

Cold-chain operators live and die on two facts Business Central does not natively record: what temperature a lot was held at, and what temperature it was moved at. Standard Business Central gives you bins, item tracking with lot and expiration dates, and warehouse shipments — but a bin has no setpoint, a lot has no thermal history, Pick According to FEFO only sorts within what item tracking already knows, and there is nowhere to log a chiller alarm at 03:40 against the lots that were sitting in it. Warehouse workers end up keeping the real cold-chain record in a paper logbook or a separate monitoring portal, and when an auditor or a rejecting customer asks for proof, someone spends a day reconciling three systems by hand.

We build an AL extension that puts that record inside Business Central where the inventory already lives. Bins and locations gain a temperature zone with a setpoint, tolerance band and dwell rules via table and page extensions on Location, Bin and Item, so a frozen item can never be put away into an ambient bin — enforced in a codeunit subscribing to the warehouse put-away and movement events rather than by user discipline. Picking is driven by a FEFO engine that honours both expiry and a per-customer minimum remaining shelf life, so a lot with nine days left is never picked for a retailer whose contract demands fourteen. Excursions are first-class documents: a new Temperature Excursion table with header/line structure records the reading source, duration, min/max, affected lots and bins, and pushes the affected lot into a quarantine status until a quality user dispositions it — with the whole path recorded so a release is always attributable to a named user.

On the transport side we add reefer trip planning over your shipments: trips carry a setpoint, a vehicle with a compartment layout, multi-temperature compartment assignment, and a load sequence that respects both drop order and thermal compatibility. Telemetry from your loggers or a telematics provider lands through API pages exposed on Business Central's REST API v2.0 / OData v4 surface, or is polled on a schedule by a job queue entry, so readings attach to the trip and to the lots on board rather than sitting in a separate portal. Compliance documents — delivery temperature certificates, lot genealogy for a recall, and excursion registers for an HACCP or GDP audit — are generated as report objects from that same data, so the paperwork is a projection of the transactions, not a parallel record someone maintains.

Everything ships as a properly built extension: dedicated permission sets so a driver, a warehouse operator and a QA releaser see different surfaces; upgrade codeunits so your data survives release-wave updates; telemetry to Application Insights for the background jobs; and Dataverse/Power Platform connectivity where you want a Power App on a handheld for dock readings or a Power BI model over excursion history. It targets current Business Central release waves and runs on SaaS (online) or on-premises, and we build it as a per-tenant extension by default or as an AppSource-shaped app if you plan to distribute it.

This is build-to-order, not a download. You request a quotation, we run a scoping call, and we write a specification against your actual products, temperature classes, customer shelf-life contracts and logger hardware. Once you confirm scope and the commercial terms, typical delivery is two to four weeks — longer only if we are integrating an unfamiliar telemetry vendor or you need a regulator-specific document format. We install into a sandbox first, run UAT with your team, then deploy to production with a rollback plan, hand over the git repository and the source, and stay with you through an agreed post-go-live support window.

lo que obtienes

Installable AL extension source code, compiled and targeted at your specific Business Central version and release wave

Installation and configuration on your sandbox and production environments, including temperature zones, permission sets, job queue entries and API endpoints

Technical documentation — object ranges, table and page extension map, event subscribers, API contracts and integration points

End-user guide plus a live training session for warehouse, transport and QA roles

UAT on a sandbox environment against your own data, with a written test script and a documented rollback plan

Post-go-live support window with defect fixes for the agreed period

Full git repository handover with commit history, so your team or another partner can maintain it

Data migration or backfill of existing zone, lot shelf-life and vehicle master data where you have it in a usable form

¿Para quién es esto?

Cold-storage warehouse manager

Runs multi-temperature chambers and needs put-away that physically cannot place a frozen pallet in a chilled bin, dock-to-stock timers on every receipt, and a defensible record of every chamber alarm mapped to the lots that were inside at the time.

Refrigerated transport operations lead

Plans reefer trips across multi-compartment vehicles, needs load sequencing that respects both drop order and thermal compatibility, and wants logger data landing against the trip in Business Central instead of a separate telematics portal.

Quality and compliance manager

Owns HACCP or GDP audit readiness. Needs excursion registers, attributable lot dispositions, and lot genealogy for a recall that can be produced from posted ERP data rather than reconstructed across a logbook and a monitoring portal.

IT lead or Business Central partner

Answers for what gets installed in the tenant. Wants a properly structured AL extension with permission sets, upgrade codeunits, Application Insights telemetry and a git repository handover — not undocumented customisations that break on the next release wave.

Cómo se compara Cold Chain Logistics for Business Central

Criterio	ECOSIRE	Construcción personalizada	Competidor	Nativo de Dynamics 365 Business Central
Temperature zones on bins and locations	Setpoint, tolerance band, permitted temperature classes and dwell limits on `Location` and `Bin`	Achievable, but the zone model is usually the part a first build under-specifies	Often a fixed zone list you must map your chambers onto	Bins have codes and capacity, no thermal attributes at all
Preventing a wrong-temperature put-away	Blocked in a codeunit on the warehouse activity events, before the line posts	Depends entirely on whether your developer subscribed to the right events	Usually a warning on a page, bypassable by a hurried operator	No concept of a wrong-temperature bin, so nothing to block
FEFO with customer shelf-life terms	Expiry ranking plus per-customer minimum remaining shelf life enforced at allocation	Buildable; the customer-contract dimension is what usually gets dropped for time	Expiry-based FEFO, contract shelf-life rarely modelled	`Pick According to FEFO` sorts by expiry only, with no customer terms
Excursion record and lot quarantine	Excursion document with affected lots, automatic quarantine and attributable disposition	Each build reinvents the disposition workflow and audit trail	Often an alert log without a posted link to the lots involved	No excursion object; the record lives in a logbook or monitoring portal
Reefer trip and compartment planning	Vehicle compartment layouts, multi-temperature assignment, thermally-aware load sequencing	A substantial sub-project on its own; commonly deferred to phase two	Sometimes a separate paid transport module or a different vendor entirely	Shipments and shipping agents, no vehicle compartments or setpoints
Logger and telematics integration	API pages on REST API v2.0 plus job queue polling, mapped to your vendor's payload	Feasible, but scoping the vendor API is where DIY estimates most often slip	Only the loggers the vendor already partners with	No inbound telemetry surface for temperature readings
Audit and compliance documents	Delivery certificates, lot genealogy and excursion registers as reports over posted data	Report layouts are usually the last thing built and the first thing cut	Generic templates you adapt to your regulator's expectations	Standard item tracking traceability only, no thermal evidence
Ownership and maintainability	Source code, git repo, technical docs, permission sets and upgrade codeunits handed over	You own it entirely, along with the whole maintenance burden	Licensed binary; you cannot read or extend it, and pricing is recurring	Nothing to maintain because nothing exists to solve the problem

Preguntas frecuentes sobre Cold Chain Logistics for Business Central

How long does delivery take?

This is build-to-order. After the scoping call we write a specification against your temperature classes, customer shelf-life terms and logger hardware. Typical delivery is 2-4 weeks from confirmed scope, covering build, sandbox install, UAT and production deployment. An unfamiliar telemetry vendor or a regulator-specific document format can extend that, and we tell you before you commit rather than after.

Is this an existing app I can download from Microsoft AppSource?

No. There is nothing to download today. ECOSIRE builds this extension for your tenant and your Business Central version after you request a quotation and confirm scope. If you want it packaged as an AppSource-shaped app for your own distribution, we can build it that way — say so during scoping, because it changes the object-range and validation work.

What happens to it when Microsoft ships the next release wave?

We build with upgrade codeunits and versioned data migration so zone configuration, excursion history and trip data survive an upgrade. Your post-go-live support window covers defects. Recompilation and validation against a future major release wave is handled as a separate maintenance arrangement — we quote it up front so there is no surprise a year later.

Does it work on Business Central on-premises as well as online?

Yes. The extension targets current release waves on both SaaS and on-premises. The difference is mainly integration plumbing: on SaaS, telemetry arrives through API pages on the REST API v2.0 surface or is polled by job queue entries; on-premises you have additional options for inbound connections from a logger gateway inside your own network.

Which temperature loggers and telematics systems can it read from?

Any system that can push JSON to an authenticated endpoint or expose a pollable API. We build API pages for inbound readings and job queue entries for scheduled polling, then map your vendor's payload to trips, compartments, bins and lots. Bring the vendor's API documentation to the scoping call — that is the single biggest factor in the estimate.

Will it change how our existing item tracking and warehouse setup works?

It extends rather than replaces. Lots, expiration dates, bins and warehouse documents stay standard Business Central; we add zone attributes, validation on the put-away and movement events, and the FEFO ranking layer on top. Existing posted history is untouched, and we can backfill zone and shelf-life master data during install where you have it in a usable form.

Who can release a quarantined lot after an excursion?

Only a user holding the QA releaser permission set. The disposition — release, downgrade or scrap — is written against the lot with user, timestamp and a reason code, and the operator who logged the excursion cannot self-approve it. That separation is configurable during scoping if your SOP defines the roles differently.