Digital signatures, also referred to as ePOD (electronic Proof of Delivery) signatures, are a core part of modern pallet network operations, providing verifiable proof that goods have been delivered and accepted. Each major UK pallet network—Palletforce, Palletline, TPN, Hazchem, and Pallex—has its own technical and operational requirements for capturing, exporting, and viewing these signatures, especially when integrating with transport management systems like Qargo. This report explains how digital signatures work per network, provides implementation details in Qargo, and highlights known limitations and troubleshooting steps for signature visibility issues.
📦 Palletforce
📦 Palletforce
How Digital Signatures Work
Digital signatures for PODs are captured at the point of delivery via the Qargo mobile app. These signatures are then uploaded to Palletforce as part of the POD data. Palletforce requires these signature images to be in .tiff format, so Qargo automatically converts signature images before upload. Only signatures captured by the Qargo app are supported for upload; signatures from other FMS systems are not currently supported. Metadata such as the consignee name, time, and location are also included in the upload, but coordinates are only available through the Qargo app.
Implementation in Qargo
Digital signatures are exported from the Qargo mobile app to Palletforce via the depot API.
The integration code handles conversion to
.tiffformat.Signatures are uploaded as soon as the image is available; subsequent updates to consignee details do not trigger a re-upload.
Troubleshooting Signature Visibility Issues
Ensure the depot API mode is enabled, as this functionality is not available in customer API mode.
Confirm that the delivery images feature is enabled on the Palletforce side during onboarding.
If signatures are not visible, verify that the signature was captured in the Qargo app and not in another FMS.
Check that file conversion to
.tiffwas successful. Failed conversions may prevent upload.
Known Limitations
Only signatures captured by the Qargo app are supported for export.
Upload of delivery images (photos) must be enabled by Palletforce and validated during onboarding.
No support for uploading signatures from external FMS systems.
Palletforce expects metadata (location, time, name), only available via Qargo app.
📦 Palletline
📦 Palletline
How Digital Signatures Work
Digital signatures (DSC—Digital Signature Capture) are collected via the Qargo mobile app during delivery and exported to Palletline’s Contrado platform. Palletline requires PODs to be in .jpg or .tiff format; PDFs are not accepted. Each signature complements a previously uploaded status update, and Palletline requests coordinates for dispute resolution.
Implementation in Qargo
Signatures captured in the Qargo app are exported to Contrado.
Only
.jpgand.tifffiles are exported; PDFs are ignored.Multiple file naming conventions exist in Contrado; only "Filename" and "Filename - PalletlineId" modes are currently supported.
Qargo supports full two-way status sync and automatic import/export of PODs.
For non-COP consignments, Palletline generates a delivery note from the received signature.
Troubleshooting Signature Visibility Issues
Ensure the Contrado configuration in Qargo matches the expected file naming convention.
Check that the signature file type is
.jpgor.tiff.If signatures are missing, confirm that the status update was uploaded before the signature.
For COP documents, ensure upload timing aligns with Palletline restrictions: COP is only imported after the ARRH scan, and if uploaded after the first ARRH update, it will not be imported into Qargo.
Known Limitations
Only "Filename" and "Filename - PalletlineId" file name modes are supported.
COP (Customer Own Paperwork) is import-only and must be manually uploaded via Contrado.
No automatic COP import; PDFs are not exported as PODs.
Some file name conventions are not supported.
📦 TPN(The Pallet Network)
📦 TPN(The Pallet Network)
How Digital Signatures Work
Digital signatures are captured at delivery and can be exported to TPN’s API via Qargo. ePOD signatures (with name, timestamp, GPS) are supported, but delivery images have historically not been transferable from Qargo to TPN due to API limitations. The TPN mobile app remains necessary for some operations, particularly for ETA management and cross-dock scanning.
Implementation in Qargo
Qargo exports ePOD signatures (name, time, GPS) to TPN’s API.
POD documents can be imported from and exported to TPN.
Delivery images are now supported by TPN’s API. Sending over delivery images when relevant from Qargo to TPN is possible(We currently do not support pulling delivery images from TPN, this flow is planned to be improved in the future).
Cross-dock scanning and ETAs must still be managed in the TPN app due to API restrictions.
Troubleshooting Signature Visibility Issues
If PODs or signatures are missing, first check the TPN portal to verify if the POD exists on the network side.
If delivery images are not sent from Qargo to TPN, confirm if the consignment has been marked as delivered. To do this a consignee signature needs to already be uploaded on the consignment.
For missing signatures, ensure the Qargo app was used for capture and export.
If order status or resource allocation appears inconsistent, verify that the correct network and depot allocations are set in Qargo.
Known Limitations
ETAs cannot be sent from Qargo to TPN API; must use TPN app for ETA management.
Cross-dock scanning is not possible via Qargo due to API restrictions.
Delivery images export is a recent addition, but we currently do not support pulling delivery images from TPN, this will come in a later date
TPNs API only accepts delivery images when the consignment has been marked as delivered. To do this a consignee signature needs to already be uploaded on the consignment. If a delivery image is uploaded and a consignee signature is not present, we will not upload it. We will however upload the delivery image once a consignee signature is uploaded. This only works for consignments where the tenant is determined to do the delivery.
All paperwork may be uploaded as POD due to API limitations.
📦 Hazchem
📦 Hazchem
How Digital Signatures Work
In Hazchem, digital signatures are referred to as EDC (Electronic Data Capture). Signatures, along with the name and coordinates of the signer, are captured via the Qargo mobile app and are mandatory for compliance. POD files must be in .tiff format; Qargo converts files before uploading to Hazchem’s FTP server. Document visibility is managed via FTP due to API file size limitations.
Implementation in Qargo
Signatures are captured with the Qargo mobile app only.
POD files are automatically converted to
.tiffand uploaded to Hazchem’s FTP.Only POD uploads are supported; other document types (COP, delivery images) are not currently supported for upload.
All other sync functions (statuses, ETAs, cross-docking) are via API.
Troubleshooting Signature Visibility Issues
Ensure the FTP endpoint for POD upload is correctly configured.
If signatures are missing, verify that all required metadata (name, coordinates) was captured.
Check that the signature was captured using the Qargo app; other FMS systems are not supported.
Document visibility is only available via FTP, so check FTP access and file presence if signatures are not visible.
Known Limitations
Only signatures captured by the Qargo app are supported.
Only POD document upload is supported (no COP or delivery images).
Document visibility is FTP-only due to API constraints.
Export only occurs when all required information is present.
📦 Pallex
📦 Pallex
How Digital Signatures Work
Pallex supports importing and exporting ePOD data (digital signatures with name, timestamp, GPS) via its API. Qargo can upload and download both POD documents and ePOD signatures. Delivery images are also supported for both import and export. For collections, the delivery address is not available, and the customer account code is used as the location alias.
Implementation in Qargo
ePOD signatures are exported from Qargo (driver app) to Pallex’s API with supporting metadata.
POD documents uploaded into Qargo can be exported to Pallex.
Delivery images are automatically uploaded/downloaded as required.
ETAs can only be provided twice per consignment and are managed via Optimize, not directly between Qargo and Pallex.
Troubleshooting Signature Visibility Issues
If signatures are not visible, confirm that the signature was captured in the Qargo driver app and that all metadata is present.
Ensure API credentials and permissions are up to date.
For missing delivery images or PODs, verify that the correct document type was uploaded and that the integration is not in a pending validation state.
For collections, remember that the delivery address is not available; check the account code alias mapping.
Known Limitations
ETAs can only be provided via Optimize integration, and only twice per consignment.
For collections, only one collection location per account is supported.
Some features (e.g., multi-depot support) are pending further validation.
Customer paperwork (COP) is not supported for upload; only POD and ePOD are fully integrated.
📦 Palletways
📦 Palletways
How Digital Signatures Work
Palletways supports importing the ePOD as a normal POD document into Qargo. However, Palletways does not allow Qargo to pull in eSignature metadata for use on custom document templates. Only the PDF POD that Palletways generates is available. Export of digital signature data (ePOD) from Qargo to Palletways is not supported.
Implementation in Qargo
Qargo imports the POD document from Palletways via FTP.
Only the Palletways-generated PDF is available; no metadata extraction.
POD documents uploaded into Qargo can be exported to Palletways via FTP.
Troubleshooting Signature Visibility Issues
If PODs are missing, check whether the document was uploaded to the correct location and in the correct format.
For missing ePOD metadata, note that Palletways does not support this functionality.
Known Limitations
No support for importing/exporting eSignature metadata.
Only PDF PODs generated by Palletways are available.
Customer paperwork (COP) is not supported.
No ETA support in the API.
Summary Table
Network | File Format Required | Qargo App Only? | Delivery Images | COP Support | ETA Support | Known Limitations |
Palletforce | .tiff | Yes | Yes (if enabled) | Yes (import/export) | Yes (3hr window) | Only Qargo app signatures, delivery images require config, no external FMS |
Palletline | .jpg/.tiff | Yes | Yes | Import-only | Yes | Limited file naming, no PDF export, COP manual upload |
TPN | .jpg/.tiff | Yes | Only from Qargo to TPN | In development | No | ETA/Cross-dock via TPN app, delivery images new, all paperwork as POD |
Hazchem | .tiff | Yes | No | No | Yes | FTP-only visibility, only POD upload, must use Qargo app |
Pallex | .jpg/.tiff | Yes | Yes | No | Optimize only | Only 2 ETAs/consignment, no COP, collection alias limitation |
Palletways | PDF (network-gen) | N/A | Yes | No | No | No eSignature metadata, only PDF, no COP/ETA |
Conclusion
Digital signature capture for PODs in UK pallet networks is tightly integrated with Qargo, but each network has unique technical requirements, limitations, and troubleshooting considerations. Most networks require signatures to be captured in the Qargo app, often in .tiff or .jpg format, and may impose restrictions on metadata, document types, and upload timing. Troubleshooting typically involves verifying correct app usage, file formats, API/FTP configuration, and document type handling. Awareness of these network-specific nuances is essential for ensuring signature visibility and compliance in pallet operations.