What the integration does at a glance
Consignments from Hazchem arrive in Qargo automatically via the API.
Qargo sends dispatch information, tracking milestones, and documents back to Hazchem as work progresses.
Labels, scan events, PODs, delivery images, and customer paperwork are exchanged so both systems stay aligned.
Work is managed in Qargo; the integration handles the data flow to and from Hazchem.
Who this guide is for
Depot and traffic office teams receiving Hazchem consignments
Planners allocating and sequencing Hazchem work
Drivers (via the Qargo driver app) executing deliveries
Customer service teams tracking progress and retrieving PODs or delivery images
Terminology
Term | Definition |
Consignment | A Hazchem shipment, typically one or more pallets under a single tracking reference. |
Hazchem reference | The unique identifier assigned by Hazchem, used to match records across both systems. |
Dispatch | The action of confirming a consignment in Hazchem's system, which generates pallet labels. |
COP (Customer Owned Paperwork) | Paperwork associated with the consignment, such as customs or delivery documentation. |
POD (Proof of Delivery) | Evidence of completed delivery — typically recipient name, signature, and timestamp. |
Delivery image | A photograph taken at the point of delivery, captured via the driver app. |
Status update | A tracking milestone (e.g., collected, in transit, delivered) sent from Qargo to Hazchem. |
Scan event | A barcode scan recorded at a handling step such as depot scan-in or scan-out. |
Push (data) | Data sent automatically from the source system to the destination. |
Pull / Sync | The destination system actively retrieves data from the source on a schedule. |
Prerequisites
An active Hazchem integration has been configured by the Qargo admin team
User roles in Qargo permit viewing and actioning Hazchem consignments
Devices used for scanning or capturing PODs are connected and synced to Qargo
Daily workflow in Qargo
Receive consignments
Hazchem pushes new consignments to Qargo via the API.
Consignments appear in the Orders or inbound work view with the Hazchem tracking reference visible.
Basic details include shipper, consignee, service type, pallet count, weight, and any special instructions.
Dispatch and print labels
When a consignment is ready for dispatch, the dispatch task in Qargo creates or confirms the consignment in Hazchem's system.
Pallet labels are generated as part of the dispatch step. Labels carry the Hazchem tracking reference and are used for scanning throughout the depot and delivery process.
Track and update status
As drivers and depot staff progress work, Qargo sends tracking milestones to Hazchem, including scan events such as:
Collection depot scanned out
Delivery depot scanned in
Delivery depot stored
Delivery depot scanned out
Status export
Qargo also sends out status to Hazchem on the following events:
Qargo event | Status event | Depot role |
POC | Collection stop is completed | Collection |
DONR | Delivery depot pickup has been completed | Delivery |
ARDL | At delivery stop | Delivery |
POD | POD has been created | Delivery |
📚 Key delivery milestones (out for delivery, delivered, failed delivery) are pushed to Hazchem in near real-time.
Capture and share proof of delivery
POD is captured in Qargo via the driver app or back office. Once uploaded, the POD
is sent to Hazchem via the API, giving network stakeholders immediate visibility.
Delivery images and customer paperwork
Delivery images (photos taken at point of delivery) and COP documents are exchanged in both directions:
When added to a consignment in Qargo, delivery images and COP are automatically uploaded to Hazchem via the API
Delivery images and COP documents from Hazchem are fetched back into Qargo automatically every 10 minutes via background sync
📚 Customer own paperwork (COP):
Only the requesting/collection depot can upload customer paperwork.
The signed COP flow is not supported via the API; only unsigned COP is transmitted.
Feature summary and data flow directions
Feature | Direction | Typical trigger | Where visible in Qargo |
New consignment | Push from Hazchem | Order created in Hazchem | Orders list / inbound queue |
Pallet labels | Generated in Qargo | Dispatch action | Order labels section |
Tracking milestones | Push from Qargo | Status change / driver app | Order timeline and activity |
Scan events | Push from Qargo | Barcode scan at depot | Scan history on the order |
POD (signature, name, timestamp) | Push from Qargo | POD captured in app or back office | POD section and attachments |
Delivery images (outbound) | Push from Qargo | Image uploaded to consignment | Attachments on the order |
Delivery images (inbound) | Sync from Hazchem | Every 10 minutes | Attachments on the order |
COP documents (outbound) | Push from Qargo | COP uploaded to consignment | Documents on the order |
COP documents (inbound) | Sync from Hazchem | Every 10 minutes | Documents on the order |
Consignment number (invoice matching) | Used in Qargo | Purchase invoice upload | Invoice matching / scan and match |
Working tips
Complete the dispatch step in Qargo before the consignment leaves the depot to ensure pallet labels are generated and tracking begins correctly.
Delivery images and COP sync automatically every 10 minutes — there is no need to manually request these from Hazchem.
When uploading COP, ensure the upload is performed by the requesting or collection depot; delivery depots cannot upload COP via the API.
For invoice reconciliation, the Hazchem consignment number is one of the fields used in the Qargo scan and match function when uploading purchase invoices.
FAQs
Why can't I see a POD in Hazchem?
Confirm the POD is present and attached in Qargo with a timestamp.
Check that the driver app was synced after the POD was captured.
Allow a short processing window for the API push to complete.
Delivery images from Hazchem aren't appearing — what should I check?
The inbound sync runs every 10 minutes. If images are not appearing after 10–15 minutes, confirm the consignment has a Hazchem tracking reference and that the integration is active.
Contact Qargo support if the issue persists.
Do PODs need to be rekeyed in Hazchem?
No. PODs captured in Qargo are pushed to Hazchem automatically — no manual re-entry is required in the Hazchem system.
Can I print Hazchem labels from Qargo?
Yes. Labels are generated as part of the dispatch step and are available on the order
in Qargo. Follow the depot printing process to produce and apply labels before loading.
Troubleshooting
Symptom | Steps to resolve |
New consignments not appearing in Qargo | Check filters on the orders view. Confirm the Hazchem integration is active and that the consignment has been created in Hazchem. |
Labels not generating | Confirm the dispatch action has been completed. Check whether any required consignment fields are missing. |
Tracking not visible in Hazchem | Ensure the consignment was dispatched in Qargo and that driver/app status updates were submitted. Verify connectivity. |
Delivery images or COP not syncing | Allow up to 10 minutes for the automatic sync. Verify the Hazchem tracking reference is present on the consignment in Qargo. |
POD not received by Hazchem | Confirm the POD is saved in Qargo with a timestamp and attachment. Contact support with the Hazchem reference if the issue continues. |
💬 If issues continue after the steps above, contact the Qargo support team and include the Hazchem consignment reference, relevant timestamps, and screenshots where possible.