$ 22.97
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) • Barcode (stock_barcode) • Purchase (purchase) • Sales (sale_management) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 505 |
| Technical Name |
hdk_stock_kit_product_restriction |
| License | OPL-1 |
| Website | https://www.hamdek.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) • Barcode (stock_barcode) • Purchase (purchase) • Sales (sale_management) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 505 |
| Technical Name |
hdk_stock_kit_product_restriction |
| License | OPL-1 |
| Website | https://www.hamdek.com |
Stock Kit Product Restriction || Restrict Over-Delivery and Over-Receipt (BOM/kit support)
Extends Restrict Over-Delivery and Over-Receipt with full kit (phantom BOM) support via Manufacturing (MRP). When a SO or PO line is a kit product, component products defined on the phantom BOM are treated as allowed on the picking, and their allowed quantity is derived from kit quantity × BOM component quantity—both on Validate and in Stock Barcode.
🔗 Restrict Over-Delivery and Over-Receipt (No BOM/Kit)
Key Features
Phantom BOM Component Lines
If the order line is a kit (phantom bill of materials), warehouse can add or process moves for each component product on that BOM—even though the component SKU does not appear as its own line on the SO/PO.
Demand from Kit Mathematics
Maximum done quantity for a component equals ordered kit qty × BOM line qty (per matching kit line on the order). Prevents shipping or receiving more components than the kits imply.
Backend & Barcode Parity
The same kit rules apply when validating from the picking form and when operators use the barcode app: allowed products and quantity ceilings stay consistent across channels.
Layered on Product Restriction
Requires Hamdek Stock Product Restriction and MRP. Non-kit behaviour is unchanged: plain SO/PO lines still allow only those exact products and quantities unless they are valid kit components.
How to Configure
- Install Restrict Over-Delivery and Over-Receipt (BOM/kit support).
- Define kit products using a phantom BOM in Manufacturing; list each sellable/buyable component on the BOM with correct quantities.
- In Inventory → Configuration → Settings → Hamdek Inventory Configuration, enable the same SO/PO restriction toggles as in the product restriction module—this module extends their meaning for kits.
- Create SO/PO lines with the kit product; confirm. Open the delivery or receipt and process component lines or scan components in barcode—limits follow kit × BOM math.
Workflow Highlights
Kit on Order, Components on Picking
Customer orders 2× “Table Kit”. The SO shows one kit line. The delivery order can list Wood Panel and Bolt as separate moves; validation allows them because they belong to the kit’s phantom BOM—not because they were typed on the SO as separate products.
Quantity Ceiling from BOM
Example: 2 kits ordered, BOM says 4 Bolt per kit → up to 8 Bolt may be validated. Entering 9 triggers a validation error on validate, and barcode blocks over-scanning the same way.
Purchase Side: Kit on PO
When a vendor ships a kit as separate SKUs, incoming receipts linked to a PO that lists the kit product can receive each component in proportion to the ordered kit quantity—mirroring the sales-side logic.
Quantity Validation Kit Components
Operators scan component barcodes; the app recognises the product as part of an on-order kit and applies the correct demand. Random products still fail the “not on order” check unless they are kit components.
Support & Expert Services
sales@hamdek.com
www.hamdek.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