Romania - Point of Sale for Retail Shops (Marfa in Magazin)
A till attached to a shop whose goods are kept at the shelf price has to sell the way that shop keeps its books. This module makes it do so: a point of sale whose operation type belongs to a retail warehouse takes over that warehouse's fiscal position and its retail price list.
The fiscal position is what carries both halves of the setup. It maps the taxes the shelf price is split with - to the VAT included variants a till works with - and it maps the accounts the goods, the markup and the deferred VAT are kept on, so a shop that holds its merchandise on 371.01 rather than 371 has its sales land there too.
Only fields left empty are filled, on creation and when this module is installed, so a till deliberately run on another price list keeps it.
A note for the migration to 20.0
This module exists only because of where the pieces sit in the dependency graph. l10n_ro_pos depends on point_of_sale and l10n_ro_config, not on l10n_ro_stock_account_retail, so it cannot read the retail marking of a warehouse - and demo data of one module cannot reference records of a module that is not among its dependencies.
Making l10n_ro_pos depend on l10n_ro_stock_account_retail would be the wrong fix: a cash register does not need the accounting of goods held at retail in order to work. When the dependencies are reworked for 20.0, the better move is to push the marking of a shop down to where the point of sale can already see it - l10n_ro_retail, the retail price list and the fiscal position of the warehouse belong with the warehouse itself, in l10n_ro_stock, leaving only the valuation of the markup and the deferred VAT in l10n_ro_stock_account_retail. This bridge then has nothing left to bridge and can be dropped.
auto_awesome What this module does
AI-generated from the code · Odoo 20.0Links a point of sale to a Romanian retail shop so the till automatically uses that shop's fiscal position and shelf-price pricelist, making sales land on the right taxes and accounts.
This module connects a point of sale to a Romanian retail warehouse (a shop whose goods are kept at the price on the label). When a till is pointed at such a shop, it takes over the shop's setup automatically.
What it does: - When a point of sale is created, or when its operation type is changed to one belonging to a retail warehouse, Odoo proposes and fills in the shop's fiscal position and the shop's retail price list. - The fiscal position is what carries the shop's taxes (the ones the shelf price is split with) and the accounts where goods, markup and deferred VAT are kept, so sales from the till are booked the same way as the shop's books. - The retail price list makes the cashier charge the price on the label.
Business rule: only empty fields are filled. If a till already has its own fiscal position or price list, it keeps it — for example a staff canteen or a clearance corner.
On installation, the module also updates existing points of sale that are already attached to a retail warehouse, so they do not keep selling on ordinary taxes and accounts until someone opens and saves each one.
It touches the point of sale configuration (pos.config) and relies on the retail warehouse settings from the Romanian stock retail module. No new menus or screens are added; the effect is visible in the point of sale settings form and in the accounting entries generated by till sales.
Depends on
Models and fields (1)
- pos.config · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 20.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 20.0
Confirmed on 2026-11-03 in branch 20.0 of OCA/l10n-romania.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.