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.
Postcode-Based Allocation for Palletforce Exports
Issue
Palletforce exports may fail to allocate automatically if the pickup or delivery locations fall within your owned postcode list.
Explanation
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.
Conditions for Successful Job Imports via API
Issue
Palletforce jobs might not appear in the API import.
Explanation
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. Additionally, jobs or orders with manifest dates in the past are completely blocked from import, regardless of their acceptance status. This ensures that only current or future-dated jobs are processed, maintaining operational accuracy. Additionally, location data errors, such as unrecognized pickup or delivery points, can prevent jobs from being imported. Ensuring that all location data is correctly configured and recognized by the system is crucial for successful imports.
Prevention Measures
Ensure that all jobs are marked as "accepted" by the manifest date or within three days prior.
To re-import a rejected job or one not captured within the current import window:
Update the manifest date to a valid one within the window.
Make a minor change (e.g. add a consignment note) to retrigger API import.3. If the manifest date is in the past, request the relevant depot or team to update it to today or a future date (up to three days ahead). This will make the job or order searchable and importable in Qargo.
🧰 Permissions might be needed to update the manifest date.If the manifest date cannot be updated, consider manually creating the job in Qargo to ensure it is processed. While this requires additional effort, it allows you to handle the job or order despite the date limitation.
Understanding Job Allocations in Planning Groups
Issue
Hazardous jobs might be auto-assigned to the Palletline planning group rather than Hazchem.
Explanation
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.
Recommended Action
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.
Troubleshooting Order Visibility in Contrado
When importing orders from Contrado into Qargo, users may encounter issues such as jobs not importing or not being visible after import. This guide provides an overview of common causes and troubleshooting steps to resolve these problems.
Jobs Not Importing - Cause: The manifest date is set beyond the allowed future window (e.g., more than a few days ahead).
Solution: Wait until the manifest date falls within the allowed window, at which point the jobs will import automatically. Alternatively, update the manifest date in Contrado to a date within the allowed window for immediate import.
Jobs Imported but Not Visible - Cause: The job may be in an error state, such as a location data error (e.g., "Unknown Location").
Solution: Investigate the job’s status and error details in Qargo. Correct any location data issues, ensuring that pickup and delivery locations are recognised and mapped correctly. Reprocess or save the job to clear the error and make it visible.
In Qargo, navigate to: LOCATIONS > Transport Networks > Palletline > Hubs and Depots.
Locate the Delivery depot used for these orders.
Check if the depot is marked as "Internal."
If it is, update the configuration so the Delivery depot is not set to "Internal."
Save the changes. Future imports will now come in as "Delivery," allowing you to plan them on a manifest.
Troubleshooting Steps
Follow these steps to resolve order import issues:
Check the Manifest Date
Verify that the manifest date in Contrado is within the allowed import window. - Adjust the date if necessary to ensure the job imports into Qargo.
Review Location Data
Check for errors related to pickup and delivery locations.
Correct any discrepancies in location data to ensure they are recognized by Qargo.
Verify Configuration Settings
Ensure that depot codes and other configuration settings match between Contrado and Qargo.
Reprocess Jobs:
After correcting any errors, reprocess or save the job in Qargo to clear the error state and make it visible.
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.
Always aim to keep manifest dates current or future-dated to avoid import issues. By addressing limitations imposed by past manifest dates, users can ensure smoother operations and minimise disruptions.
Regularly review and update configuration settings in both Contrado and Qargo to ensure compatibility.
Validate location data during job creation in Contrado to prevent errors during import.
Ensure all depot configurations align with your operational requirements.
Monitor manifest dates and adjust them as needed to align with Qargo’s import window.
💬 For unresolved issues, consult the system documentation or contact support.