What the integration does
Keep orders, consignments, and status updates aligned between Palletline and Qargo
Reduce double‑keying by creating and updating records automatically
Surface Palletline network data where you already work in Qargo
Maintain a clear audit trail of what came from Palletline and what was changed in Qargo
How data flows: push vs pull
Push: One system actively sends data to the other. Example: Palletline pushes a new order into Qargo.
Pull: One system requests or checks for data from the other. Example: Qargo polls Palletline for status updates after an order is accepted.
Many features use both directions: initial creation is a push, while updates are pulled on a schedule or triggered by user action.
Terminology
Term | Definition |
Network order | A consignment created and managed within the Palletline network, surfaced in Qargo. |
Push | Data sent automatically from one system to the other without an explicit user request. |
Pull | Data requested by Qargo from Palletline, either on a schedule or when you open or refresh a record. |
Milestone | A status or scan event from Palletline, such as Collected, At hub, Out for delivery, Delivered. |
POD | Proof of delivery, including signature and any delivery images or notes. |
Labels | Network‑compliant barcode labels required for scanning and routing. |
Exception | A non‑standard event, such as failed collection, damage, or miss‑sort, raised by the network. |
Where you work in Qargo
Orders and consignments
Create, view, and manage Palletline jobs in your standard Orders or Consignments views. Palletline‑originated items are flagged so you can filter or report on them.
Tracking and status
Live status, scan milestones, and exceptions appear on the job timeline and tracking panels.
Documents and labels
Network labels and PODs are attached to the job. Print labels from the job action menu or a batch print view.
Pricing and surcharges
Network tariffs and surcharges can auto‑apply. You can review and, if allowed by your configuration, override or add local charges.
Exceptions and queries
Exceptions raised in Palletline appear as alerts on the job and in your Exceptions list. Add notes and progress them as usual.
Feature summary: direction and detail
Feature | Direction | What it means in practice |
Order creation (Palletline to Qargo) | Push | New Palletline orders automatically appear in Qargo with key fields populated. |
Order field updates | Pull | Qargo periodically checks Palletline for changes to dates, services, pallets, and references. |
Qargo edits synced to Palletline | Push | Depending on your rules, certain Qargo updates (e.g., requested collection time) are sent back to Palletline. |
Status and scan events | Pull / Push | Qargo retrieves network milestones and shows them on the job timeline and tracking widgets. |
Labels (network) | Pull | Qargo fetches Palletline label PDFs for print from the job or batch view. |
POD (signature, images, PDFs) | Pull / Push | Final POD is retrieved and attached to the job for download and customer sharing. |
Exceptions and alerts | Pull | Network exceptions appear in Qargo. You can add notes and track resolution internally. |
Tariffs and surcharges | Pull | Qargo applies Palletline rating where configured. Local charges may be added in Qargo. |
Manifesting / trunk allocation | Push | Manifest choices in Qargo can be sent to Palletline, based on your workflow setup. |
Consignment cancellation | Push | Cancel in Qargo and the cancellation is sent to Palletline when allowed by status. |
Scheduled sync checks | Pull | Qargo performs background checks to keep statuses and documents up to date. |
Typical workflow
New job arrives
A Palletline order is pushed into Qargo. You’ll see it flagged as Palletline‑origin in your Orders or Consignments view.
Confirm details
Open the job to verify addresses, pallets, service level, and time windows. If your configuration allows, minor changes push back to Palletline on save.
Print labels
From the job, select Print labels. Qargo pulls the Palletline label PDF and sends it to your printer or download queue.
Track progress
Scan and network milestones are pulled into the job timeline. Use the Tracking tab or hover over timeline events to view detail.
Manage exceptions
If Palletline raises an exception, Qargo shows an alert. Add an internal note, adjust ETAs, or contact the customer as needed.
Complete and POD
Once delivered, Qargo pulls the network POD. It appears in the Documents section and can be shared or exported.
Configuration options that affect behaviour
Editable fields: Your organisation can choose which fields edited in Qargo push back to Palletline.
Sync frequency: Status and document pull intervals can be tuned to your operational needs.
Auto‑rating: Whether Qargo pulls and applies Palletline tariffs automatically or keeps rating local.
Cancellation rules: Which statuses allow Qargo‑initiated cancellation to push to Palletline.
If something doesn’t update as expected, check whether your configuration allows that change to push, or whether the update relies on the next pull cycle.
FAQs
Can I edit Palletline orders in Qargo?
Yes, within configured limits. Allowed fields will push to Palletline on save. Others will remain Qargo‑only.
How quickly do updates appear?
Pushes are immediate on save. Pulls follow your sync schedule or occur when you open a job.
Can I report on Palletline jobs separately?
Yes. Use the Palletline origin flag to filter lists and build reports.
Troubleshooting
I don’t see a new order
Refresh your Orders view and filter for Palletline origin. If still missing, confirm the order is completed in Palletline and check for integration alerts.
Labels won’t print
Open the job and try Print labels again. If the label isn’t available, the consignment may not yet be label‑ready in Palletline.
Status looks stale
Open the job to trigger a fresh pull. If it remains unchanged, check the Palletline milestone history or wait for the next scheduled sync.
POD missing
Some PODs publish after a short delay. Retry in a few minutes or download directly from Palletline if urgent.
Support
If you need help with configuration or behaviour that differs from this guide, contact Qargo support with a job reference, screenshots (where possitble), time of issue, and any other relevant details of the issue.