Technical specifications, standard operating procedures, and regulatory checklists for warehousing and cargo handling infrastructure.
This document outlines the step-by-step protocol for reconciling physical inventory against the WMS database. It covers RFID tag scanning sequences, barcode fallback procedures, and automated discrepancy flagging. Special attention is given to high-value cargo segregation and Transport Canada's minimum documentation requirements for warehoused goods.
Read full article
The track-and-trace system is built on an event-sourcing model where each cargo movement generates a cryptographically signed log entry. This article details the schema for location events, custody transfers, and environmental sensor readings. It also explains how the architecture supports real-time querying for compliance audits and retrospective chain-of-custody reconstruction.
Read full article
This guide consolidates the key compliance requirements from Transport Canada's Transportation of Dangerous Goods (TDG) regulations and the Canada Transportation Act. It covers segregation rules for incompatible classes, placarding standards, emergency response information placement, and documentation retention policies. Each item includes a reference to the relevant regulatory clause and an internal audit procedure.
Read full articleCommon questions about warehousing documentation, track-and-trace architecture, and Transport Canada compliance.
| What documentation is required for warehoused cargo? | Each storage unit must have a warehouse receipt, a bill of lading, and a cargo inventory manifest. For hazardous materials, a Transport Canada TDG declaration and safety data sheet are mandatory. All documents must be retained for at least two years after the cargo leaves the facility. |
|---|---|
| How does the track-and-trace system log custody transfers? | Every custody transfer generates an event record containing the previous and next custodian identifiers, a timestamp, GPS coordinates of the transfer point, and a cryptographic hash linking it to the prior event. The event is written to an append-only ledger before the physical transfer is authorized. |
| What are the segregation rules for incompatible cargo classes? | Transport Canada mandates that dangerous goods of incompatible classes (e.g., oxidizers with flammables) be separated by a minimum of three metres or a fire-rated barrier. Our WMS enforces these rules at the bin level, preventing co-location and generating a compliance report for each storage assignment. |
| How are inventory discrepancies flagged and resolved? | When a cycle count or receiving scan produces a quantity mismatch against the WMS record, the system creates a discrepancy ticket. The ticket is routed to the floor supervisor, who must perform a recount within two hours. If the discrepancy exceeds 0.5% of the item value, a formal investigation is opened and logged for Transport Canada audit purposes. |
| What environmental data does the track-and-trace system capture? | For temperature‑sensitive and hazardous cargo, the system logs ambient temperature, humidity, and vibration levels at fifteen‑minute intervals. Sensor readings are appended to the cargo’s event stream and can be queried to verify that storage conditions remained within the limits specified in the safety data sheet. |
| How long must compliance documentation be retained? | Transport Canada requires that all cargo safety documentation, including TDG declarations, inspection reports, and training records, be kept for a minimum of two years after the cargo is released. Our document management system automatically applies retention policies and purges records only after the statutory period expires. |
For further clarification on specific compliance scenarios, contact our regulatory affairs team at info@thanosqr.com.
These clarifications govern the interpretation of warehousing documentation, inventory track-and-trace architecture, and Transport Canada cargo safety compliance as referenced in the thanosqr operational framework. All terms carry the meaning assigned under the Canada Transportation Act unless otherwise noted.
For the purposes of this document, “warehousing documentation” means the electronic and physical records generated at each custody transfer point within a thanosqr facility. This includes the inbound receiving report, the storage assignment log, the cycle count reconciliation sheet, and the outbound loading manifest. Each record must be timestamped, signed by the responsible operator, and retained for a minimum of three years per Transport Canada record-keeping requirements. Discrepancies between the WMS database and physical inventory trigger an automatic hold on the affected SKU until a root-cause analysis is completed.
The inventory track-and-trace system is built on an event-sourcing architecture where each cargo movement generates a cryptographically signed log entry. A “location event” is defined as any scan that updates the geospatial or facility-zone position of a unit load device (ULD) or individual package. “Custody transfer” refers to the handoff between two authenticated operators or between an operator and an automated handling system. The event log is immutable; corrections are appended as reversal events with a reference to the original entry. Real-time querying is supported via a read-optimised projection that aggregates the latest state per SKU without altering the source event stream.
Compliance with Transport Canada’s Transportation of Dangerous Goods (TDG) regulations is assessed at three checkpoints: receipt, storage, and dispatch. At receipt, the consignor’s shipping document is verified against the dangerous goods list in Schedule 1 of the TDG Regulations. During storage, incompatible classes (e.g., Class 4.3 water-reactive substances and Class 5.1 oxidizing agents) are segregated by a minimum of three metres or a fire-rated partition. At dispatch, the vehicle’s placarding and emergency response information (ERI) are confirmed against the current TDG Clear Language standard. Any deviation is logged as a non-conformance and escalated to the facility safety officer within one business hour.
Retrospective chain-of-custody reconstruction relies on the event-sourcing log described above. For audit purposes, a “chain segment” is defined as the sequence of location events and custody transfers between two consecutive inventory snapshots. Each segment must contain at least one scan per 24-hour period for non-hazardous cargo and one scan per 12-hour period for dangerous goods. If a segment contains a gap exceeding the threshold, the system automatically flags the affected ULD for a physical recount. The reconstruction output is a time-ordered list of events that can be exported as a PDF or CSV for submission to Transport Canada or the facility’s insurance provider.
Inventory discrepancies are classified into three categories: scan omission, mis-scan, or physical loss. A “scan omission” occurs when an operator fails to record a custody transfer within the required window; the system logs a missing-event alert and prompts a manual entry. A “mis-scan” is defined as a barcode or RFID read that resolves to an incorrect SKU or location; the operator must perform a re-scan and submit a correction event. “Physical loss” applies when the WMS record shows inventory that cannot be located after two consecutive cycle counts. In all cases, the discrepancy is resolved within 72 hours, and the resolution is appended to the event log with a reference to the original discrepancy flag.
All operational procedures referenced in this document are aligned with the following standards: Canada Transportation Act (S.C. 1996, c. 10), Transportation of Dangerous Goods Regulations (SOR/2001-286), and Transport Canada’s Standard for the Storage of Dangerous Goods (TP 10377). Where a conflict arises between these clarifications and the regulatory text, the regulatory text takes precedence. thanosqr’s internal compliance team reviews these clarifications quarterly and updates them to reflect any amendments to the referenced standards.