PN - Troubleshooting Palletline & Palletforce Imports and Allocations.

Qargo users might encounter issues with job allocations or imports related to Palletforce and Palletline networks. This article outlines the typical causes and provides actionable steps for resolution.

Palletforce exports may fail to allocate automatically if the pickup or delivery locations fall within your owned postcode list.

The system only performs automatic Palletforce (PF) allocations when the relevant postcode is not owned by your organisation. If ownership exists for the postcode, the system assumes you will handle the task and does not assign it to PalletForce.

Palletforce jobs might not appear in the API import.

The import process will only include jobs marked as "accepted" on the manifest date or within the three days preceding it. If a job meets acceptance criteria after its manifest date has passed, the system does not retroactively import it.

Hazardous jobs might be auto-assigned to the Palletline planning group rather than Hazchem.

This happens when routing rules in the planning groups prioritise Palletline over Hazchem. For example, specific rules for direct stages may exist in Palletline but not in Hazchem. The absence of supplementary Hazchem rules results in the job defaulting to Palletline.

Review and update routing rules in your Hazchem planning group to include conditions for all stages, including direct stages. This ensures proper allocation for hazardous jobs.

By understanding these common scenarios and their resolutions, Qargo users can effectively manage job imports and allocations in Palletforce and Palletline networks. Implementing these practices reduces risks of misallocations and import failures associated with automated processes.