Question 1

Does Glacial Logix require IoT sensors or data loggers?

Accepted Answer

No. Predictions come from pickup time, service-level transit windows, route weather, and the as-packed pack-out specification you provide. No on-package logger, no reverse logistics. The math is conservative R-value heat-transfer plus coolant-capacity depletion — sufficient to spot at-risk vs nominal shipments without the $5–$50 per-shipment sensor cost.

Question 2

Who is Glacial Logix built for?

Accepted Answer

Food cold-chain SMB distributors moving 50–500 refrigerated parcels per day across 5–30 lanes. Operators planning a day's outbound queue, monitoring in-flight shipments, and procurement teams negotiating carrier and packaging contracts.

Question 3

Can the platform integrate with our TMS?

Accepted Answer

Yes. The REST API at /api/v1/* accepts token authentication and supports POST /api/v1/batches/plan (push raw orders CSV, get ranked recommendations back), POST /api/v1/batches (save pre-computed batches), and POST /api/v1/live-shipments (push in-flight shipments). Per-token IP allowlist supported. Docs include inline curl examples.

Question 4

Is Glacial Logix vendor-neutral on packaging?

Accepted Answer

Yes. We don't sell boxes or loggers. Pack-out recommendations compare insulation materials, coolant types, and service tiers across vendors without a channel-conflict bias.

Question 5

How does outcome calibration work?

Accepted Answer

Record what actually happened on delivered shipments (actual max temp, transit hours, coolant remaining, condition rating). The platform compares predicted vs actual per product and shows a per-product calibration delta — positive means the engine ran cooler than reality on that product / your lane mix and pack-out specs should be tightened.

Question 6

Where is Glacial Logix hosted? Where is my data?

Accepted Answer

All data is held in a multi-tenant Postgres with strict org-scoped query isolation. The application is hosted on Hostinger's Node.js infrastructure. API tokens are SHA-256 hashed server-side; passwords use bcrypt cost-11. Audit log captures every sign-in, role change, token mint, and data write for SOC-2 prep.