Skip to main content
Apragya AIFree quotation builderQuotation builderQuote builderno signup
Sign inRegister
How-to guide

How to Create Cold Chain Control in an ERP: Zones, Readings, Excursions and a QA Release

For dairy, frozen food, vaccine and pharma distributors: set up cold rooms so a real temperature break holds the right stock and a named person decides what happens to it.

Start freeTalk to sales
A worker in a padded jacket checking a wall sensor inside a dairy cold room

If you are working out how to create cold chain control in an ERP, start with one idea: the temperature record and the stock record must meet. A data logger can tell you a chiller warmed up at 2 am. Only the inventory system knows which batches were inside it, and only the inventory system can stop them being picked.

Most Indian cold stores still run on a wall logger, a printed chart and a supervisor's judgement. The chart is read the next morning, the affected cartons may already be loaded, and the decision to release them is a phone call nobody writes down.

This guide sets out the steps that make cold chain control work, an illustrative setup at a Pune dairy distributor, and how Apragya's inventory app ties readings to stock.

How to create cold chain control, step by step

Cold chain control in an ERP has four parts. Zones describe each cold space and its allowed range. Devices send readings into those zones. Rules decide when a breach becomes an excursion. Stock rules decide what happens to the batches inside when it does.

The design choice that matters most is the grace window. Chillers warm briefly every time a door opens, so a breach should count only if it lasts longer than normal handling. When it does, the exposure should be dated from the first bad reading, not from the moment the alarm fired.

The common mistakes are alarming on every reading, recording excursions without holding stock, and releasing stock because the room recovered. For regulated products, check the storage conditions your licence and your principals require before you set the limits.

  1. Map each cold room, chiller, freezer and reefer bay as a zone.
  2. Set the lower and upper limit for each zone from product requirements.
  3. Choose a grace window per zone from observed door openings.
  4. Connect sensors and confirm readings arrive for every zone.
  5. Store cold items by batch and location so a zone's contents are known.
  6. Hold stock on every confirmed excursion and name who decides its release.

What a cold chain without a system costs

Warm stock shipped

Cartons leave a failed room before anyone reads the chart.

Alarms nobody reads

Every door opening raises an alert, so real ones are ignored.

Unclear exposure

Nobody can list which batches sat in the room when it warmed.

No release record

Stock is cleared verbally, with no name against the decision.

An example: a Pune dairy distributor sets up two chillers

Take an illustrative distributor of milk, curd and paneer in Pune with two walk-in chillers and a small freezer. Retailers had returned sour curd twice in a month, and nobody could say which night the chiller had failed or which batches were affected.

From an empty setup to a held batch

  1. Zones defined

    Two chillers at 2 to 6 C, one freezer below minus 18 C.

  2. Grace window set

    Fifteen minutes, from a week of door openings.

  3. Sensors registered

    Each device linked to its zone.

  4. Excursion opened

    A compressor trip held every batch in chiller two.

  5. QA released

    Paneer released, one curd batch rejected.

The hold covered what was in the chiller when it warmed, not what was there by morning.

Three weeks after setup, chiller two tripped for fifty minutes before dawn. The morning dispatch could not pick its batches because they were already held. The QA lead reviewed the excursion, released the paneer, rejected one curd batch, and the record showed her name and reason.

Dairy items with green ribbons and one group of curd cups set apart on red cloth
The paneer was released after review; the curd batch on the red cloth was the one QA rejected.

How cold chain monitoring in ERP works in Apragya

Step 1 of 5

Create zones

Each cold room, chiller or freezer is a zone with a lower and upper limit and a grace window.

  1. Create zones: Each cold room, chiller or freezer is a zone with a lower and upper limit and a grace window.
  2. Register devices: Sensors are registered against a zone and send temperature, and humidity where available.
  3. Take in readings: Readings arrive through an ingest API and are stored against the zone.
  4. Open excursions: A breach that lasts past the grace window opens an excursion dated from the first bad reading, graded minor, major or critical.
  5. Hold and decide: Batches in the zone are quarantined and listed on the excursion; a person releases or rejects them.

Temperature excursion handling: logger, spreadsheet or ERP

A logger records temperature well, and a spreadsheet can list excursions. Neither knows what stock sat in the room or can stop a picker from sending it out. Holding the stock at the moment of the breach, and keeping that list, is what turns a temperature graph into a decision you can defend.

Ways to run a cold chain, compared with Apragya

FeatureLogger and chartApragya inventory
Door openingsAlert every timeIgnored within the grace window
Start of exposureWhen someone noticedThe first breaching reading
Affected stockWorked out by handBatches listed and held
Picking held stockPossibleBlocked by quarantine status
ReleaseA phone callA recorded QA disposition
Silent sensorsFound at auditVisible in the device list

Checked against public information on 16 September 2026.

Keeping a cold storage temperature log that means something

Batches by location

Quarantine applies to a batch at one location, not everywhere.

Snapshot kept

The list of held batches is saved, so moved stock is not forgotten.

People decide

Stock is never released just because the room cooled down.

AI you can put to work

An agent can summarise the week's excursions for review.

Audit log

Holds and dispositions are logged with user and time.

Per company

Groups keep each company's warehouses separate.

Cold chain control depends on batch tracking and sits beside regulatory compliance. For the feature itself, read cold chain software, and for what can run on its own, how to automate cold chain.

Getting started

  1. List every cold room, chiller and freezer as a zone.
  2. Record a week of normal readings before setting grace windows.
  3. Register each sensor against its zone.
  4. Make sure cold items are batch tracked by location.
  5. Name the people who may release held stock.

Most false alarms disappear once the grace window reflects how often the door really opens.

What it costs to start

INR 3,999
Starter, a month
Up to 10 users, CRM and HR plus Inventory and Warehousing
2,000
AI Credits a month
Included on Starter
Free
Up to 3 users
CRM, HR and Vendor Onboarding

Creating cold chain control, answered

Do we need particular sensors?
Any device that can send readings to an API can feed a zone. Check your sensor vendor's options for pushing data.
Is stock released automatically when the room recovers?
No. A returning temperature does not make stock good. A person releases or rejects it.
How is severity decided?
By how far the reading went outside the zone's limits. Severity orders the QA queue; any confirmed excursion holds stock.
What happens to stock moved after the breach?
The held list is saved on the excursion when it opens, so stock moved or shipped later can still be traced.
What does it cost to start?
Inventory and Warehousing is available from the Starter plan, INR 3,999 a month for up to 10 users, which includes CRM and HR plus a choice of enterprise apps and 2,000 AI Credits a month. Pro, at INR 7,999 a month, covers 25 users and every enterprise app.

Tie every reading to the stock in the room

Set up your cold zones, register the sensors and let breaches hold the right batches.

Start freeTalk to sales