| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 439 |
| Technical Name |
mjb_activity_receipt_inspection |
| License | OPL-1 |
| Website | https://www.majorbird.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 439 |
| Technical Name |
mjb_activity_receipt_inspection |
| License | OPL-1 |
| Website | https://www.majorbird.com |
Activity: Receipt Inspection
Automatically schedules a To-Do inspection activity when an incoming receipt is validated — so quality checks never fall through the cracks.
$5 — Satellite Add-on Odoo 19.0by Majorbird — Odoo Silver Partner
⚠ The Problem
In busy warehouses, incoming receipts are often validated and put away before anyone performs a formal quality or quantity check. Discrepancies — damaged goods, wrong items, short shipments — are discovered days later, long after the supplier's dispute window has closed. There is no built-in Odoo mechanism to enforce an inspection step after validation. This satellite adds that gate automatically, with zero configuration required after installation.
What It Installs
This satellite installs 1 pre-configured activity rule for the
mjb_activity_rule engine. The rule is disabled by default
so you can review it before going live.
| Field | Value |
|---|---|
| Monitored Model | stock.picking (incoming receipts only) |
| Trigger | On write — when state = done and picking type = incoming |
| Activity Type | To-Do |
| Deadline | 1 day after validation |
| Assigned To | Picking's responsible user (fallback: current user) |
| Activity Note | “Inspect received goods and verify quantities and quality.” |
| Duplicate Prevention | Enabled — one activity per receipt, no duplicates |
| Default State | Disabled — enable after reviewing settings |
Requirements
Required Modules
- mjb_activity_rule — the activity scheduling engine (install first)
- stock — Odoo's built-in Inventory module
Works With Any Warehouse Operation Type
The rule filters by picking_type_code = incoming, so it applies to all
receipt operations across all warehouses. Outgoing deliveries and internal transfers
are not affected. You can create additional rules for other operation types directly
in the mjb_activity_rule engine if needed.
🆕 Version 19.0.1.0.0 — Feedback Welcome
This is the initial release of this satellite. The pre-configured rule covers the most common scenario. If you need the activity assigned to a QC team instead of the responsible user, a different deadline, or a specific activity type, please share your feedback — real customer input shapes our next iteration.
About Majorbird
Odoo Silver Partner — Manufacturing, Inventory & Accounting Automation
Offices in Vietnam, China, Mexico, and the Middle East.
www.majorbird.comOdoo 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