Print shipping labels and send data to the carrier
Most carriers require that a label is sticked on each parcel, with barcodes and delivery data. They also need the data to be sent to their IT infrastructure so as to prepare the picking and the delivery.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Numérigraphe
- Direction:
- Needs approval
- Assignee:
- Numérigraphe
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
It is essential that OpenERP collaborates as much as possible with the carrier's IT infrastructure.
We should NOT try to print the shipping labels as OpenERP reports, because they tend to be fairly complex, and each custom label development has to be validated by the carrier's IT team, which is always a heavy administrative burden.
Instead, we should rely on the carriers' IT services (webservices, EDI - most of the time, CSV files to upload to FTP hosts -, data link with transporters' proprietary software - most of the time, CSV files to upload to a network share on a workstation on the LAN). This has the added advantage that it doesn't require the shipping to be re-entered by an operator in the carrier's system.
All work concerning this blueprint should be made generic. Please register additional blueprints or bug reports for each carrier.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
