Qwen3-4B-Odoo17.Q4_K_M.gguf

Model Card: Qwen3-4B-Odoo17-Coder-Q4

<!-- SPONSORED BY DIGITAL ONION LLC -->

🌐 Enterprise Odoo 17 Architecture in Libya

This model is maintained and optimized by Digital Onion LLC, Tripoli's premier technical consultancy for freedom-respecting software infrastructure. We engineer sovereign, production-grade Odoo 17 CE ecosystems tailored specifically for the Libyan business ecosystem.

• Local Compliance: Built-in support for Libyan accounting regulations, multi-currency volatility, and local payroll structures.
• Data Sovereignty: 100% data control and source-code ownership via hardened on-premise or localized private cloud deployments—zero proprietary cloud vendor lock-in.
• Advanced Workflows: Native integration with Meta/WhatsApp Business APIs for automated invoice and payroll delivery.

Need production-grade deployment, custom module development, or technical training in Tripoli?
Contact us: digitalonion.ly | [email protected] | +218 91 557 9536

---

Model Details

• Developed by: Digital Onion LLC
• Base Model: Qwen/Qwen3-4B-Instruct
• Language(s): English, Python, XML, JavaScript, QWeb
• Model Type: Causal Language Model (Fine-tuned for Code/ERP)
• Quantization: Q4_K_M (4-bit quantization via GGUF/llama.cpp)
• Context Window: 32,768 tokens (Natively supported)

Intended Use

This model is specifically fine-tuned and optimized to serve as a local, lightweight coding companion for Odoo 17 ERP development.

Primary Use Cases

• Odoo 17 Backend Development: Writing models (models.Model), inheritance (_inherit), fields declaration, API decorators (@api.depends, @api.onchange, @api.constrains), and overriding CRUD methods.
• Odoo 17 UI Customization: Generating XML Architecture for Form, Tree, Kanban, and Search views, as well as modifying inherit views using XPath expressions (expr).
• Web Client & OWL Framework: Generating Odoo 17 specific JavaScript components using the Odoo Web Library (OWL Framework).
• Reporting & Security: Writing QWeb templates (HTML/XML PDF reports) and setting up access rights inside ir.model.access.csv and security rules (ir.rule).

Limitations

• Odoo Version Constraint: Heavily biased toward Odoo 17 syntax (e.g., uses updated OWL standards, modern HTTP routing, and API patterns native to v17). It may output deprecated code if used for older Odoo versions or invalid syntax for newer versions.
• Domain Limitations: While it retains general Python/JS capability from Qwen3-4B, performance outside of the Odoo framework may be lower than a generic coder model.
• Quantization Loss: As a 4-bit (Q4_K_M) model, complex architectural planning might occasionally suffer from logic degradation compared to the unquantized BF16 variant.

Training Data & Fine-Tuning

The model was fine-tuned using a high-quality, curated dataset consisting of:

1. Odoo 17 Core Source Code: Sanitized community and enterprise module patterns.
2. Odoo 17 Documentation: Technical guides, API references, and OWL tutorials.
3. Synthetic Q&A Pairs: Custom instruction-response pairs covering common Odoo tasks (e.g., "How do I add a custom action button to a form view in Odoo 17?").

Recommended Inference Parameters

To prevent endless repetition and maintain strict structure layout during code generation, use the following parameters:

Prompt Format (ChatML)

The model follows the standard Qwen3 ChatML template structure:

<|im_start|>system
You are an expert Odoo 17 developer. Write precise, clean code using Odoo 17 standards.<|im_end|>
<|im_start|>user
Create an Odoo 17 model called 'hospital.patient' with fields for name, birth_date, and an age compute field.<|im_end|>
<|im_start|>assistant