| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Inventory (stock) |
| Lines of code | 2475 |
| Technical Name |
pod_advanced_suite |
| License | OPL-1 |
POD Advanced Suite
Controlled proof of delivery routes, receiver evidence, incidents, returns, portal history, and POD PDFs for Odoo 19 Inventory.
Odoo 19 Inventory Portal No Sales dependency No Fleet dependency
Why This App
Delivery operations need proof that goods reached the intended customer, evidence was captured under policy, and exceptions were reviewed. POD Advanced Suite keeps that flow close to native Inventory operations while adding role-based execution and customer-facing delivery history.
Functional Flow
Supervisors plan delivery routes from outgoing transfers. Drivers process assigned stops, capture receiver evidence, register incidents when needed, and document operational return lines. Supervisors review exceptions and close routes through a controlled process.
Evidence ControlCapture receiver name/reference, signature, photo, GPS coordinates, timestamps, and evidence notes according to configurable policies. |
Inventory Pending VisibilityPOD delivery confirmation does not validate stock automatically. Delivered POD stops with pending Inventory validation remain visible and controlled during route closure. |
Operational ReturnsReturn lines document products and quantities not accepted or brought back by the driver. They are operational POD records and do not create automatic stock returns in this MVP. |
Role-Based SecurityDrivers work on assigned routes and stops. Supervisors manage routes and operational reviews. Managers configure POD policies. |
Portal POD AccessPortal customers can view only their own delivery history and download ownership-controlled POD PDFs. |
Safe AttachmentsSignature and photo evidence are embedded in authorized POD PDFs and are not exposed through raw public attachment URLs. |
Compatibility
Compatible with Odoo 19 Enterprise. Dependencies: Inventory, Mail, and Portal. The addon does not depend on Sales, Fleet, or Website.
MVP Scope Notes
This release does not include automatic stock validation, automatic inventory returns, route optimization, a native mobile app, advanced offline mode, continuous GPS tracking, or a full TMS. It focuses on Odoo-native POD governance for Inventory-led delivery operations.
Get Started
Install the app, assign POD roles, configure evidence policies, and start planning proof-of-delivery routes from Odoo Inventory delivery transfers.
Support
Support is provided for installation questions, reproducible module bugs, documented workflow questions, and compatibility issues related to the supported dependencies declared in the manifest.
Contact: support@tech.parnasostudio.com
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module