Skip to main content
GullySystem
Requirements checklist

What to ask for when choosing software for cold chain companies.

A checklist built from how cold chain companies work, to print or save as a PDF and bring to any supplier meeting.

Share your requirements

What the software should cover

Tick each one that matters to your business.

  • Chamber readings on one screen
  • Thresholds, alerts and escalation
  • Recording through network drops
  • Lots, chambers and part releases
  • Storage rent and handling bills
  • Reefer trips and delivery proof
  • Condition history for the client
  • Chamber defrost and maintenance log
  • Dock appointment and gate log
  • Insurance claim and loss record

Roles that need their own access

Who logs in, and what each person may see or change.

  • For shift supervisors
  • For maintenance in-charge
  • For plant heads
  • For owners and facility managers
  • For operators at the panel

Reports to ask for

Ask to see each one with your own sample data.

  • Run hours and downtime per machine, by shift
  • Stoppage reasons, counted for the month
  • Every excursion outside range, with its duration and who acknowledged it
  • Condition history against a batch, a consignment or a date
  • Energy, water and fuel per machine, line or block
  • Devices that stopped reporting, and the gap they left
  • Raw readings exported for any period you name

Systems it may need to connect to

Note which ones you already run.

  • Modbus and OPC UA devices
  • PLCs, drives and chiller controllers
  • Energy and water meters
  • WhatsApp
  • SMS and email
  • ERP and maintenance software
  • Panel hooters and indication lamps

Questions for any vendor

Put these to every supplier you are comparing.

  • Does it keep working when the plant internet drops?
  • Do you provide the sensors and gateways?
  • Can it read our existing PLCs, drives and energy meters?
  • How accurate will the readings be?
  • Can we export the data for our own analysis?
  • Can supervisors see it on a phone?
  • Can we bring in the readings we already have?
  • Does it connect to our accounting package or ERP?
  • Who owns the devices, SIMs and data?
  • What does it cost?
  • How long before the first screen shows live readings?
  • What does the plant need to prepare ahead of a site visit?

Where the work usually breaks today

Circle the ones you recognise. They set the order of the project.

  • Temperature registers are written up later
  • An excursion is found by the client
  • Part releases confuse the lot balance
  • Rent periods are argued at billing
  • Reefer trips leave no condition record

Check the difficult cases before choosing software.

Use examples from your own records to test the workflows that matter in your business.

Recording through network drops

Which actions still need a connection, even if the screen opens offline?

For “Recording through network drops”, interrupt a save on a test device and reconnect it. Agree how pending work and conflicting edits should be shown before promising offline operation.

Background reading: Android: offline data handling

Rent periods are argued at billing

Can you explain the balance from its original documents?

Select a partly settled example in “Rent periods are argued at billing”. Ask for the invoice, allocated receipts and remaining balance to be shown together before agreeing the opening figures.

Background reading: ERPNext: outstanding invoices

Prefer to talk it through? See the cold chain companies page.