What the integration does at a glance
Orders sent from Palletways appear in Qargo automatically.
Qargo keeps Palletways updated as you progress the job.
Labels, tracking events, exceptions, and PODs are exchanged so both systems stay in sync.
You work in Qargo; the integration handles the data flow to and from Palletways.
Who this guide is for
Depot and traffic office teams receiving Palletways consignments.
Planners allocating and sequencing work.
Drivers (via driver app) and traffic desk monitoring live progress.
Customer service teams tracking, resolving exceptions, and sharing PODs.
Specific terminology
Term | Definition |
Consignment | A Palletways shipment, often composed of one or more pallets under a single reference. |
Palletways reference | The unique identifier from Palletways, used across both systems. |
Service level | The agreed product or delivery speed (e.g., next day). |
Scan event | A barcode scan recorded at a handling step such as load, unload, cross‑dock, or delivery. |
POD (Proof of Delivery) | Evidence of delivery, typically recipient name and signature, with optional photos and notes. |
Exception | Any deviation from the normal delivery flow, such as failed attempt, damage, or address issue. |
Push (data) | Automatic data sent out by the source system to the destination. |
Pull (data) | The destination system actively retrieves or refreshes data from the source. |
Prerequisites
Your organisation has an active Palletways integration configured by your Qargo admin team.
Your user role in Qargo permits viewing and actioning Palletways orders.
Devices used for scanning or capturing PODs are connected to Qargo as per your operating procedure.
Daily workflow in Qargo
Receive consignments
Palletways pushes new consignments to Qargo.
You’ll see them appear in your Orders or Inbound work view with the Palletways reference visible.
Basic details include shipper, consignee, service type, pallet count, weight, and any special instructions.
Plan and allocate
Assign the consignment to a round/vehicle in Qargo.
If your flow uses scanning, scan labels to confirm load.
Qargo will push status updates back to Palletways where applicable.
Execute and track
As drivers progress stops, Qargo records time, status, and scan events.
Key milestones (e.g., Out for delivery, Delivered, Failed delivery) synchronise to Palletways.
Handle exceptions
Record reasons (e.g., customer closed, address issue, damage) in Qargo.
Exception details and any associated photos can be pulled/pushed based on configuration so Palletways and Qargo match.
Proof of delivery (POD)
Capture signature, name, photos, and notes in Qargo.
POD is sent to Palletways so customers and network stakeholders can view it.
Billing and close‑out
Delivery completion and final quantities in Qargo can be used for invoicing.
Where supported, charge‑affecting changes are synchronised to Palletways to keep records aligned.
Feature summary and data flow directions
The integration can both push and pull. “Push” means the source system sends data out automatically. “Pull” means the destination system looks for changes or requests data.
Feature | Direction | Typical trigger | Where you see it in Qargo | Notes |
New order / consignment | Push from Palletways | Order created in Palletways | Orders list or inbound queue | Appears with Palletways reference and service data |
Order updates (e.g., instructions, quantities) | Push from Palletways, Pull by Qargo | Edits in Palletways or Qargo scheduled pulls | Order detail panel | Qargo may periodically pull to ensure late edits are captured |
Label data / consignment refs | Push from Palletways | Order creation or print request | Order labels section | Use for scanning and load confirmation |
Planning status (allocated, on round) | Push from Qargo | Assignment to vehicle/route | Planning board and order timeline | Keeps Palletways aware of progress |
Tracking milestones (out for delivery, delivered, failed) | Push from Qargo | Driver/app status changes | Live tracking and order activity | Near‑real‑time visibility to Palletways |
Scan events (load, cross‑dock, POD scan) | Push from Qargo | Scan performed in depot or on vehicle | Scan history on the order | Improves audit trail across the network |
Exceptions (carded, address issues, damage) | Push from Qargo, Pull by Palletways | Exception recorded in Qargo | Exceptions panel on the order | Photos/notes included where supported |
POD (signature, name, timestamp, photos) | Push from Qargo | POD captured in driver app or back office | POD section and attachments | Shared to Palletways for customer access |
Consignment cancellations | Push from Palletways, Pull by Qargo | Cancelled at source | Order status updates or removal | Qargo honours the source of truth |
Charge‑related adjustments | Depends on configuration | Measured dims, regrade, surcharge | Pricing/charges view | When enabled, updates synchronise both ways or one way |
Working tips in Qargo
Always allocate Palletways work to a route before dispatch to ensure tracking updates flow promptly.
Record exceptions with clear reasons and photos; this reduces customer queries later.
Check for late edits: if you suspect changes in Palletways, refresh or reopen the order so the latest data is pulled.
Ensure drivers sync the app before and after routes, especially when working offline.
FAQs
What if an order looks incomplete in Qargo?
Try a refresh to pull any late updates from Palletways. If details still look wrong, check whether the order was recently edited at source.
Do I need to rekey tracking updates in Palletways?
No. Enter statuses and PODs in Qargo; the integration pushes the updates to Palletways.
Can I print Palletways labels from Qargo?
Where configured, label data is available in the order. Follow your depot process for printing and scanning.
How fast are updates?
Push events are near‑real‑time. Pull refreshes occur on action or on a schedule depending on your configuration.
Troubleshooting
I don’t see new Palletways consignments
Confirm you’re on a view that includes Palletways work and that your filters aren’t hiding new items. If the issue persists, contact your internal Qargo admin.
Tracking isn’t visible in Palletways
Check that the order was properly allocated and that the driver/app submitted the status. Verify connectivity and sync state on the driver device.
POD didn’t appear in Palletways
Confirm the POD is present in Qargo with a timestamp and attachment. Reopen the order to trigger a pull of any pending data and allow time for push processing.
Support
If issues continue after the steps above, contact the Qargo support team, including the Palletways reference, vehicle/route, timestamps, and screenshots where possible.