| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3785 |
| Technical Name |
github_product_document |
| License | OPL-1 |
| Website | https://www.ganemo.co |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3785 |
| Technical Name |
github_product_document |
| License | OPL-1 |
| Website | https://www.ganemo.co |
GitHub Product
Automated Module Delivery via ZIP
Link product variants to GitHub branches and deliver downloadable module ZIPs automatically when a sale order is confirmed.
What We're Solving
----------------
Branch-to-Variant Linking
Each product variant (e.g., "18.0", "19.0") can be linked to a specific GitHub repository branch. When a customer buys a version, they get the exact code for that branch.
Automatic ZIP Delivery
Uses Odoo's native product.document
with attached_on_sale='sale_order'. When a sale order is confirmed,
the customer automatically sees the download link in their portal.
Smart Staleness Detection
When a GitHub repository is synced and updates are found, the system automatically marks linked product variants as "Needs Update". No manual tracking required.
Background Cron Updates
A dedicated scheduled action runs every 12
hours looking for stale documents. It downloads fresh ZIPs from GitHub and updates
product.document records without blocking any process.
Setup & User Manual
Step-by-Step implementation
1. Configuration Guide
Set up module delivery in 3 simple steps:
- Go to Sales > Products > Product Variants.
- Select a variant (e.g., version "18.0").
- Set the GitHub Branch field to the matching branch.
- Click "Sync GitHub Doc" to generate the ZIP.
- Verify the product.document record is created.
- Sell the product. Customer sees download after confirmation.
2. Operating Manual (Workflow)
How the automated system works end-to-end:
Variant ↔ Branch
Each product variant has a GitHub Branch field. This establishes the connection between what you sell and the code repository.
ZIP Generation
When you click "Sync", the system calls the GitHub API
(get_archive_link) to download the ZIP and stores it as a
product.document.
Staleness Flag
During GitHub repo sync, if the
repository has been updated, linked variants are marked with
needs_update = True. This ensures ZIPs stay current.
Cron Auto-Refresh
Every 12 hours, a scheduled action finds all variants
with needs_update = True and refreshes their ZIPs from GitHub
automatically.
Global Ready | Multi-Language Support
This module is fully translated into English and Spanish (en_US, es_ES, es_PE, es_MX), ensuring a professional experience for international organizations.
Why Choose Ganemo?
----------------
Ganemo is the world's leading Odoo App developer and a multi-award-winning Gold Partner. For over 5 years, we have been recognized as the #1 seller of high-quality apps on the Odoo App Store. Trusted as the "Best Partner" in USA, Mexico, Chile, Spain, Colombia, Ecuador, and Peru, we deliver robust, secure, and localization-compliant solutions for global businesses.
Get a Quote & Resolve Commercial Doubts
Join thousands of satisfied clients on Odoo. Contact our sales team directly.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Schedule Meeting
Need More? We Do It All
Professional Odoo Services
ERP Implementation
Transform your business with a full Odoo implementation. We analyze, configure, and train your team to maximize productivity. From Accounting to Inventory, we handle the complexity so you can focus on growth.
Module Dev & Migration
Need a custom feature? Or stuck on an older version? We develop high-performance custom modules and migrate your existing code to Odoo 18 with zero data loss. Expert developers at your service.
QA / User Testing Scenarios
Enterprise Validation Plan
Scenario 1: Manual ZIP Sync (Single Variant)
- Go to Sales > Products > Product Variants.
- Select a variant and set GitHub Branch to a valid branch.
- Click "Sync GitHub Doc" in the form header.
- Expected: A
product.documentis created with the ZIP file. The Needs Update flag is set to False.
Scenario 2: Batch Sync (Multiple Variants)
- Go to the Product Variants list view.
- Select multiple variants with GitHub branches assigned.
- Click Action > Sync GitHub Doc.
- Expected: Each selected variant gets its own
product.documentwith the correct ZIP. All Needs Update flags reset to False.
Scenario 3: Automatic Staleness on Repo Sync
- Link a variant to a branch and run "Sync GitHub Doc" (so needs_update = False).
- Run GitHub Organization > Sync Repositories.
- Expected: The variant's Needs Update flag is now True, indicating the ZIP is stale.
Scenario 4: Cron Auto-Update
- Ensure at least one variant has Needs Update = True.
- Go to Settings > Technical > Scheduled Actions.
- Find "GitHub: Update Stale Product Documents" and run it manually.
- Expected: All stale variants get fresh ZIPs, and Needs Update resets to False.
Scenario 5: Customer Download After Sale
- Create a sale order with a product variant that has a synced ZIP.
- Confirm the sale order.
- Log in as the customer and go to the Customer Portal.
- Expected: The customer sees a download link for the ZIP file associated with the purchased variant.
FAQ & Troubleshooting
Common Resolutions
Sync button doesn't appear?
Reason: The button is only visible when a GitHub Branch is assigned to the variant.
Fix: Set the GitHub Branch field first, then the button will appear in the form header.
ZIP download fails with timeout?
Reason: Large repositories may take longer to archive on GitHub's side.
Fix: The system has a 120-second timeout. If the repo is very large, try syncing during off-peak hours or let the cron handle it automatically.
Customer doesn't see the download?
Reason: The product.document uses
attached_on_sale='sale_order'. The download is only visible after
order confirmation.
Fix: Make sure the sale order is confirmed (not just a quotation). The customer will see the download in their portal.
Does this work with GitHub private repos?
Answer: Yes!
Detail: The module uses the same GitHub access token configured in the GitHub Connector module. As long as the token has access to the repository, both public and private repos work.
Commercial & Sales
For inquiries about licenses, demos, or partnerships.
Official WhatsApp
Fastest response time.
LINK
+1 (828) 672-6150
Book a Demo
Let's explore your needs.
LINK
Technical Support
Existing customers regarding module functionality.
© 2026 Ganemo. All rights reserved. visit ganemo.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