Odoo Addon Development for WiFi Vouchers
Budget: $170 – $210 USD
Develop odoo addon for auto generating wifi voucher
We are using odoo 17.0 as POS, and we would like to generate wifi vouchers specifically customers who have bought our product, in order to prevent free roamers.
odoo is installed using this script as a proxmox container
https://github.com/minhng92/odoo-17-docker-compose
Router os used is RouterOS v6.49.17 x86, must be compatible with this version
The addon should consists of same menu as vougen (python based)
https://github.com/scriptik/vougen?tab=readme-ov-file
The rest api command can be gotten from there as well :
https://github.com/scriptik/vougen/blob/master/main.py
A modification to use userman command instead of mikrotik command is needed to simplify radius management,
and also to include number of shared user is needed, as explained in 3b below.
Some reference :
https://help.mikrotik.com/docs/spaces/ROS/pages/2555940/User+Manager#UserManager-Batchusercreation
The workflow is :
1. A Transaction takes place,
2. Count the number of ordered items flagged as wifi-eligible product category for that transaction
Suggested method is to use a custom domain view, as documented here
https://www.odoo.com/documentation/17.0/developer/tutorials/server_framework_101/06_basicviews.html
For example, only products in "coffee" category is eligible for wifi voucher
3. Run userman api commands through vougen addon above :
a. username password, etc specified in vougen addon above
b. shared user # equals amount of items ordered in the first step
c. set profile 3hr
4. Store the username, password and shared user value
5. Print wifi username password and shared on odoo receipt print page, must be customized beforehand
https://www.odoo.com/documentation/17.0/applications/sales/point_of_sale/receipts_invoices.html
Using the header is feasible if it's possible, e.g calling value from #1-#4 above so that the printed receipt has a header saying username password like this:
https://imgur.com/uhvVvd7
6. If the radius server / printer / other factor is not reachable due to hardware / software error,
the process would be skipped and show error message box so that the cashier workflow doesn't stop
7. Must have logging page in case of error
8. 7 days testing period is needed after stable version i.e no bugs found. If bugs found 7 days must be restarted again,
because it must be bug free to ensure smooth cashier workflow.
We are using odoo 17.0 as POS, and we would like to generate wifi vouchers specifically customers who have bought our product, in order to prevent free roamers.
odoo is installed using this script as a proxmox container
https://github.com/minhng92/odoo-17-docker-compose
Router os used is RouterOS v6.49.17 x86, must be compatible with this version
The addon should consists of same menu as vougen (python based)
https://github.com/scriptik/vougen?tab=readme-ov-file
The rest api command can be gotten from there as well :
https://github.com/scriptik/vougen/blob/master/main.py
A modification to use userman command instead of mikrotik command is needed to simplify radius management,
and also to include number of shared user is needed, as explained in 3b below.
Some reference :
https://help.mikrotik.com/docs/spaces/ROS/pages/2555940/User+Manager#UserManager-Batchusercreation
The workflow is :
1. A Transaction takes place,
2. Count the number of ordered items flagged as wifi-eligible product category for that transaction
Suggested method is to use a custom domain view, as documented here
https://www.odoo.com/documentation/17.0/developer/tutorials/server_framework_101/06_basicviews.html
For example, only products in "coffee" category is eligible for wifi voucher
3. Run userman api commands through vougen addon above :
a. username password, etc specified in vougen addon above
b. shared user # equals amount of items ordered in the first step
c. set profile 3hr
4. Store the username, password and shared user value
5. Print wifi username password and shared on odoo receipt print page, must be customized beforehand
https://www.odoo.com/documentation/17.0/applications/sales/point_of_sale/receipts_invoices.html
Using the header is feasible if it's possible, e.g calling value from #1-#4 above so that the printed receipt has a header saying username password like this:
https://imgur.com/uhvVvd7
6. If the radius server / printer / other factor is not reachable due to hardware / software error,
the process would be skipped and show error message box so that the cashier workflow doesn't stop
7. Must have logging page in case of error
8. 7 days testing period is needed after stable version i.e no bugs found. If bugs found 7 days must be restarted again,
because it must be bug free to ensure smooth cashier workflow.