---
title: "FAQ – Hazchem: delivery image and COP visibility"
description: "This article explains that delivery images and customer-owned paperwork (COP) are now automatically sent to Hazchem through its API for better data visibility and exchange."
url: https://help.qargo.com/us/articles/500462-faq-hazchem-delivery-image-and-cop-visibility
locale: us
updated: 2026-03-17
---

# FAQ – Hazchem: delivery image and COP visibility

### Q: How are delivery images and customer-owned paperwork (COP) files shared with Hazchem? {#h_a4376bb0fa}

**_A: Delivery images and customer-owned paperwork (COP) are automatically sent to Hazchem when they are uploaded._** This data exchange gives Hazchem greater visibility into shipment operations, delivery images and customer-owned paperwork (COP).\
Essential documents, such as proof of delivery images and related paperwork, are transferred immediately and securely. This streamlines the reconciliation and verification process for Hazchem.

### Summary:  {#h_cbdae71adc}

-   Delivery image and COP uploads are sent through the Hazchem API.
-   POD uploads can also be sent through the API.
-   Images are automatically compressed to meet Hazchem's file-size requirements.
-   Only the unsigned customer paperwork flow is supported.
-   Only the requesting/pickup terminal can upload customer paperwork through the API.

* * *

### Q: How are delivery images and COP documents from Hazchem made available in Qargo? {#h_7a2c89138f}

**A: In addition to sending documents _to Hazchem_, Qargo also automatically retrieves delivery images and customer-owned paperwork (COP) _from Hazchem_ on a regular sync cycle.**

-   The sync runs in the background every 10 minutes
-   It pulls in newly available documents from the Hazchem API
-   Documents are attached directly to the relevant Hazchem shipment in Qargo:

    -   **Delivery images:** retrieved as JPEG files and attached to the shipment as delivery photos.
    -   Requesting and pickup terminals see delivery images fetched from Hazchem as part of the shipment record.
    -   **Customer-owned paperwork (COP):**retrieved as TIFF files.
    -   Delivery terminals receive COP documents to print and give to the driver at the point of delivery.

* * *

## Summary of the two-way document flow: {#h_dc0f7f7b63}

| **Direction** | **Document type** | **How it works** |
| --- | --- | --- |
| Qargo → Hazchem | Delivery image, COP, POD | Uploaded automatically through the API when added to a shipment |
| Hazchem → Qargo | Delivery image, COP | Synced every 10 minutes by a background process |

:::callout{tone="info"}
📚 **COP uploads:**

-   Only the requesting/pickup terminal can upload customer paperwork through the Hazchem API. This is the **_"unsigned" COP flow_**.
-   Signed COP documents are not uploaded by the delivery terminal, so they are not synced back to the pickup/requesting terminal.
:::


## Related articles

- [PN - Hazchem overview](https://help.qargo.com/us/articles/609628-pn-hazchem-overview.md)
- [Customer own paperwork (import only)](https://help.qargo.com/us/articles/143897-customer-own-paperwork-import-only.md)
- [PN - Digital signatures (POD) in UK pallet networks.](https://help.qargo.com/us/articles/518421-pn-digital-signatures-pod-in-uk-pallet-networks.md)
- [PN - PalletForce: POD import/export](https://help.qargo.com/us/articles/143859-pn-palletforce-pod-import-export.md)
- [Export customer paperwork from Qargo](https://help.qargo.com/us/articles/140554-export-customer-paperwork-from-qargo.md)
