Export (API)
For the order export there is a dispatch task that allows sending the consignment to Palletline; this means the same feature set is available (e.g. the task can be auto-completed to automatically send consignments to Palletline).:
Dispatch task configuration, the integration to dispatch to is “Palletline”:
The dispatch tasks will only be generated for subcontractor resources that have the Palletline integration active. The “Pallet network” toggle can be activated to hide the resources from the regular planning board and show them in the pallet network planning board.
In Qargo dispatching is always performed on trip level, and the Palletline API expects a single consignment, during dispatch there is verified that only a single consignment is present on the trip that is being dispatched.
It is thus not possible to consolidate multiple loads and sent them to the Palletline API together.
The depot codes passed to the API are:
as requesting depot: result of the Qargo gazetteering of the location on the stage you’re not exporting, or the default for exporting direct stages;
as collection depot: result of the Qargo gazetteering if exporting the delivery stage;
as delivery depot: never passed.
After the dispatch has been done, the Palletline API gives some information back to Qargo, i.e. the routing information and the pallet barcodes.
Import (API)
The order import happens over API. Every minute we poll the Palletline API to get the consignments assigned to one of the depots for the tenant.
The depot codes are taken over from the imported orders and not re-gazetteered in Qargo.
Orders coming in via API will get assigned the Palletline transport network because of the transport service configuration.
They follow the Palletline transport network configuration in terms of splitting in the depot & auto resource assignment:
the transport network is configured to be auto-assign a resource
the subcontractor assigned to the transport network has active resources with the “Palletline integration” toggle toggled off
Import (file) - ONLY WHILE ONBOARDING - NOT LIVE
During the onboarding period, we also allow the Palletline customers to import orders by file import, as it would allow them to generate a single invoice for their customers (containing both pre-Qargo and post-Qargo consignments).
Orders imported via file won’t have any data synchronisation from the Palletline system (e.g. status updates will be lost).
The consignments must be updated manually to get them in the correct state to invoice them.
