Cold Chain Management — Overview & module guide

Module: Cold Chain Management v1.4.0

Temperature-controlled supply chain monitoring, equipment tracking, and excursion alerts for BIXCRM

Screen-by-screen guides (each tab explained)

Click a menu item below for step-by-step instructions on that Cold Chain Management screen:

How to use in BIXCRM (daily operations)

  1. Sign in to the admin area with a role that includes Cold Chain Management permissions.
  2. Open Cold Chain (sidebar) or search for Cold Chain Management in the admin menu.
  3. Start on the Dashboard (if available) to see open tasks, pending approvals, and KPIs.
  4. Review Settings after upgrades — new options may need defaults for your company.
  5. Create or import master data first; most modules block transactions until masters exist.
  6. Run the main business flow (create → submit → approve → post/complete) using the screens listed in Admin menu below.
  7. Use Reports / Analytics screens to reconcile stock, finance, compliance, or SLA metrics.
  8. For integrations (API, EDI, gateways, tax), confirm credentials in Settings and monitor logs or webhook delivery screens.
  9. Train staff with role-based access — give approvers approve permissions only, operators create/edit on their area.
  10. If something fails overnight, check BIXCRM cron ran and open the module log / failed queue screen if present.

Admin menu — where to work

Open the Cold Chain Management section in the admin sidebar. Screens your staff may use (depending on role):

  • API Keys
  • Batch Traces
  • Bulk Import
  • Calibration Records
  • Chain of Custody
  • Cold Chain
  • Cold Chain Dashboard
  • Compliance Reports
  • Equipment
  • Excursion Alerts
  • IoT API & Webhooks
  • IoT Bulk Import
  • Maintenance Schedules
  • Monitoring Devices
  • Settings
  • Shipments
  • Temperature Readings
  • Temperature Zones
  • Webhooks

Detailed guide — features, workflows, API & FAQ

Phase 5 Features

  • Compliance Reports — GDP/GMP audit-ready PDF temperature logs
  • Chain of Custody — trace storage → transit → delivery with PDF export
  • Batch/Lot Tracing — link temperature readings to manufacturing batches
  • Multi-Plant Scoping — filter by active plant (Multi-Plant Management module)
  • Warehouse Linking — assign equipment to warehouses and bin locations
  • QMS Integration — optional auto-create NCR on excursion alerts
  • REST API — expanded read endpoints for zones, equipment, alerts, shipments
  • Webhooks — calibration.due and shipment.excursion events

Permissions

FeatureCapabilities
----------------------
Compliance Reportsview
Chain of Custodyview, create, edit, delete
Batch Tracesview, create, delete

Database Tables (Phase 5)

  • ccm_chain_of_custody
  • ccm_batch_traces

Also adds plant_id, warehouse_id, location_id to equipment; qms_ncr_id on excursion alerts.

Integrations

ModuleIntegration
---------------------
QMSAuto-NCR on excursion (Settings → enable)
Multi-Plant ManagementPlant scoping on equipment/shipments
Inventory ManagementWarehouse/location linking on equipment
Advanced WMSAuto chain-of-custody on shipment completion

Roadmap

All five planned phases are complete. See [docs/ROADMAP.md](docs/ROADMAP.md) for full history.

Features

Temperature-controlled supply chain monitoring, equipment tracking, and excursion alerts for BIXCRM

  • **Compliance Reports** — GDP/GMP audit-ready PDF temperature logs
  • **Chain of Custody** — trace storage → transit → delivery with PDF export
  • **Batch/Lot Tracing** — link temperature readings to manufacturing batches
  • **Multi-Plant Scoping** — filter by active plant (Multi-Plant Management module)
  • **Warehouse Linking** — assign equipment to warehouses and bin locations
  • **QMS Integration** — optional auto-create NCR on excursion alerts
  • **REST API** — expanded read endpoints for zones, equipment, alerts, shipments
  • **Webhooks** — `calibration.due` and `shipment.excursion` events

Permissions

Granular staff capabilities are registered on activation. Assign them under Setup → Staff → Roles for the Cold Chain Management capability group.

Typical capabilities include view, create, edit, delete, plus module-specific actions (approve, export, settings, API access).

Cron Jobs

Background tasks (if enabled) run through BIXCRM's main cron. Example crontab (every 5 minutes):

* * * * * php /path/to/bixcrm/index.php cron/index > /dev/null 2>&1

Check module settings for scheduled jobs (alerts, sync, reports, retention).

After activation — configuration checklist

  1. Go to Setup → Modules and activate Cold Chain Management.
  2. If prompted, click Upgrade Database or reload admin — migrations run automatically.
  3. Assign permissions under Setup → Staff → Roles.
  4. Open the module menu and configure settings.
  5. BIXCRM 3.0+
  6. PHP 7.4+ (8.1+ recommended)
  7. MySQL 5.7+ / MariaDB 10.3+ (InnoDB)
  8. PHP extensions: mysqli, json, mbstring, curl, fileinfo

Staff permissions (from module)

Assign under Setup → Staff → Roles. Each feature can expose different actions:

FeatureActions
Cold Chain Dashboard
ccm_dashboard
view
Temperature Zones
ccm_temperature_zones
view, create, edit, delete
Equipment
ccm_equipment
view, create, edit, delete
Monitoring Devices
ccm_monitoring_devices
view, create, edit, delete
Temperature Readings
ccm_temperature_readings
view, create, edit, delete
Excursion Alerts
ccm_excursion_alerts
view, create, edit, delete, resolve
Shipments
ccm_shipments
view, create, edit, delete
Calibration Records
ccm_calibration_records
view, create, edit, delete
Maintenance Schedules
ccm_maintenance_schedules
view, create, edit, delete
Settings
ccm_settings
view, edit
IoT API & Webhooks
ccm_iot_api
view, create, edit, delete
IoT Bulk Import
ccm_iot_import
view, create
Compliance Reports
ccm_compliance_reports
view
Chain of Custody
ccm_chain_of_custody
view, create, edit, delete
Batch Traces
ccm_batch_traces
view, create, delete

One-time setup (first time only)

  1. Setup → Modules → activate Cold Chain Management.
  2. Setup → Staff → Roles → assign Cold Chain Management permissions (view, create, edit, delete, approve, export, settings as needed).
  3. Open Cold Chain Management → Settings and complete company defaults, prefixes, integrations, and notification options.
  4. Create master data (warehouses, products, templates, accounts, routes, etc.) before processing live transactions.
  5. Enable BIXCRM cron (php /path/to/bixcrm/index.php cron/index) for sync, retries, alerts, and scheduled jobs.
  6. Optionally enable REST API / webhooks in module settings if you integrate external systems.

BIXCRM Knowledge Base — usage guide generated from module README and documentation.

Did you find this article useful?