Skip to main content
GullySystem
Manufacturing

Business solutions for Commercial refrigeration companies

Explore software for work such as “Cold rooms for fruit, vegetable and flower traders”. Review each business function below, including when it fits and what to check before implementation.

Commercial refrigeration companies

How the business operates.

A customer with a failed cold room has stock at risk within hours. The call is urgent. The unit dates from years back, and the engineer needs its make, its refrigerant type and what was done last time before leaving the yard.

Customer sites and unit register

Keep each site with its units by make, model, serial number, refrigerant type and install date, so history opens in one tap.

Fault calls and dispatch

Log a breakdown with the unit, the symptom and the stock at risk, then send the nearest qualified engineer.

Planned maintenance and contracts

Set visit calendars by contract and unit, record each visit, and flag renewals before they lapse.

Refrigerant and gas log

Record gas added, recovered and returned by unit and cylinder, so a record exists when a regulator or customer asks.

Van and store stock

Track compressors, motors, controllers and valves in the store and on each van, and reorder before a common part runs out.

Installation jobs and commissioning

Quote and run new cold rooms and cabinets in stages, with commissioning readings and handover documents held on the job.

Service reports and invoices

Leave a signed service report with readings and parts used, then invoice the call-out, labour, parts and gas.

Temperature logger records

Readings from cold room and display case loggers are filed against the unit with alarm times. A rise above the limit links to a fault call. Managers see the history during a food audit.

Supplier warranty claims

A failed compressor, evaporator fan or controller is logged with serial, install date and fault finding. The claim goes to the supplier with photos. Stores staff see which replacement is awaited.

Technician licence and tool register

Each technician’s refrigerant handling certificate, manifold gauges and vacuum pumps are listed with expiry or calibration dates. Dispatch skips a technician with an expired certificate. The service head sees renewals coming up.

The records that hold the operation together.

  • Customer sites and unit register. Hold each site with its cold rooms, cabinets, evaporators and condensing units, including serial numbers, refrigerant types and install dates.
  • Fault calls and dispatch. Log breakdowns with the unit, symptom and stock at risk, and assign the nearest engineer who holds the right skill and the right parts.
  • Planned maintenance calendar. Generate visits by contract and unit, with checklists for filters, coils, door seals, defrost cycles, drain heaters and controller settings.
  • Maintenance contracts and renewals. Record cover, visit counts and fees by contract, and flag each renewal before it lapses.
  • Refrigerant and gas log. Record gas added, recovered and returned by unit, cylinder and engineer, with leak test results and tare weights, and print a record on request.
  • Van and store stock. Track compressors, fan motors, controllers, solenoid valves, contactors and gas by van and store, with reorder levels for common parts.
  • Installation jobs and commissioning. Quote and run new installations in stages, with brazing, nitrogen pressure tests, commissioning readings, drawings and handover documents on the job.
  • Service reports and signatures. Capture readings such as superheat and subcooling, work done and parts used on a phone, and take the customer’s signature at the site.

Operational bottlenecks to check

Unit history lives in memory

The engineer who installed a cold room knows its quirks, its awkward valves and the pipework behind the wall, and none of it is written anywhere. Once that engineer is away, whoever opens the plant room next starts with guesses and rings a customer who cannot say either.

Refrigerant is not traced to a unit

Gas is bought in cylinders, topped up on site and recovered from old plant. Without a record by unit and cylinder, an audit request becomes a search through job sheets.

Urgent calls compete for the same engineer

A failed freezer and a routine service are both on the board for today. The dispatcher decides from a phone list, not from the value of stock at risk, the position of each engineer or the parts that each van is carrying.

Contract renewals are missed

Planned visits and renewal dates live in a diary or on a sheet. A customer discovers the lapse when a unit fails.

Parts on the van are unknown

An engineer drives out to a customer’s site and finds the van has no fan motor, though the store holds one on its shelf. The second visit costs a day. It could have been avoided.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Site and unit setup

    A customer site is added with each cold room, cabinet, evaporator and condensing unit, with its serial number, refrigerant type and contract cover.

  2. 2. Call or scheduled visit

    A breakdown is logged by phone, message or monitoring alert. Otherwise a planned visit comes due from the contract calendar, and the unit’s earlier faults are shown beside it.

  3. 3. Dispatch

    The dispatcher assigns an engineer by location and skill, with the unit’s history and the parts likely to be needed, such as a fan motor, a contactor or a defrost heater.

  4. 4. Visit and report

    The engineer records pressure readings, superheat, faults found, parts fitted and gas added. A service report follows for the customer to sign.

  5. 5. Invoice

    Call-out, labour, parts and gas are billed. A planned visit under contract is booked with no charge.

  6. 6. Renewal and follow-up

    Contracts are renewed before they lapse, and repeat faults are reviewed by unit, make and compressor model.

Roles and responsibility boundaries.

For owners

See calls open, contracts due, gas used, parts on hand and balances by customer.

For dispatchers

Log calls, pick engineers by location and skill, and tell customers who is on the way and which part is in the van.

For engineers

Open the unit history on a phone, record readings and parts, and get the customer’s signature before leaving the site.

For stores and purchasing

Track van and store stock, receive from wholesalers and reorder common parts such as contactors, glycol and fan motors.

For accounts

Invoice visits and contracts, post receipts and follow up overdue balances.

Reports your managers need.

  • Fault calls broken down by unit, type and engineer
  • Recurring faults, by make and model
  • Planned visits completed against missed
  • Contracts approaching renewal
  • Gas charged and recovered, unit by unit
  • Leak test results by unit and date
  • Parts used, and lines that have fallen below reorder level

Connections to scope

  • WhatsApp or other messaging
  • SMS
  • Email
  • Temperature monitoring alerts
  • Online payment gateway
  • Accounting export

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your units and customers

Every make, model, condenser and customer site is loaded, so the unit register is useful from the first fault call.

Visit checklists

Checklists for each type of unit, from a walk-in cooler to a display case, are set to match what your engineers check on a planned visit.

Contract terms

Visit counts, response promises and renewal rules are entered as each customer’s contract states them.

Gas and record rules

Refrigerant categories, leak test fields and the fields your regulator expects are reviewed during implementation.

Currency, tax and language

Invoices, tax lines and customer messages are worded in your currency and language.

Hosted by GullySystem

GullySystem looks after hosting, giving the dispatcher, engineers and accounts clerk one shared set of records. Changes are made when you ask.

Limitations to settle before implementation

  • A lone engineer who attends only a handful of breakdowns each week can get by with a phone and a pocket diary.
  • Companies mainly installing and servicing air conditioning for comfort cooling may prefer HVAC Service Management Software.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • Cold rooms for fruit, vegetable and flower traders
  • Walk-in coolers and freezers for hotels and restaurants
  • Display chillers and counters for bakeries, sweet shops and supermarkets
  • Bulk milk coolers and dairy chilling units
  • Ice plants, ice-cream and cold drink outlets
  • Pharma and vaccine cold storage rooms
  • Blast freezers for meat, fish and ready-to-eat food
  • Annual maintenance contracts and spare parts
  • Retrofit and energy-saving upgrades for old compressors
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements