-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New: prepare for e-shipment (SQL part) #31773
Conversation
I validated PR but :
|
Ηι @eldy workflow example: In future this date(date_expedition) will be filled by e.g. shipment/delivery service driver by scanning QR CODE and transmitted to all related parties (The way this is designed based on EU VIDA proposal is that info provided to both vendor and mainly client will be in near real time so there will be no need for tracking number in future. Authorities need to fight illegal trade and vat fraud) |
So the issue date in your exemple seems to be the date of creation of shipment ? |
Yes ok we can use date_creation, thanks |
Related to #31652
Hi @eldy
My guess is that by 1/4/2025(compulsory date for Greece) v 22.0.0 will not have been released yet, so i kindly request for the inclusion to v. 21.0.0 of the minimum changes needed for e-shipment to work meaning this pr + #31701 first + a pr following to show fields in modules card.php
A few remarks
Right now shipment is treated as a secondary document by being dependant to sales orders.
Following comment seems wrong, warehouse is used for stock management and not for per product departure this is not how logistics work.
As per above examples a warehouse can be a starting point or a destination of a shipment
dolibarr/htdocs/install/mysql/tables/llx_expeditiondet.sql
Line 31 in 40aca28
Shipment address is used through contacts but is not recorded to shipment or invoice as it should. Same would apply to loading address
If you agree i will work for independent shipment creation for v 22.0.0 plus support for above use cases