Romania - Point of Sale Partner
A company buying over the counter identifies itself by its CUI, and that code is rarely on file before the first sale. Searching for it in the Choose customer dialog of the Point of Sale would normally end on “no customers found” – yet the company is public record at ANAF.
This module turns that dead end into the way company customers are added at the till:
a search that reads as a Romanian CUI is recognised as one, with or without the RO prefix, since the customer reading it off a document does not know which of the two the shop keeps;
a customer already on file under that CUI is offered straight away, even when the cashier would never have found them by name;
when there is none, a Create from ANAF button fetches the company – name, VAT status, registration number and registered address – creates it and puts it on the order in one step. The same ANAF history the partner form keeps is recorded, so it does not matter that the customer came in through the till.
Choosing a company as the customer does not turn the receipt into an invoice. In Romania the fiscal receipt is what the till issues and it settles the sale on its own; the invoice is asked for, not assumed.
Table of contents
Configuration
Nothing to configure in the Point of Sale. The lookup uses the ANAF web service configured for Romania - Partner Create by VAT, so a company customer added at the till is the same record the back office would have created from the partner form.
Usage
In the Choose customer dialog of the Point of Sale, type the customer’s CUI, with or without the RO prefix.
If a customer is already on file under that code, they show up in the list as usual. If none does, the dialog offers Create from ANAF: it fetches the company from ANAF, creates it with its registered name and address, and puts it on the current order.
A CUI that ANAF does not know is refused with that reason, and no customer is created – the receipt should not go out to a company named after a number.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
-
Fekete Mihai <feketemihai@nexterp.ro>
Sima Elisabeta <elisabeta.sima@nexterp.ro>
Do not contact contributors directly about support or help with technical issues.
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/l10n-romania project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Release files for odoo-addon-l10n-ro-pos-partner 19.0.1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_l10n_ro_pos_partner-19.0.1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_l10n_ro_pos_partner-19.0.1.1.0-py3-none-any.whl
| Download URL | odoo_addon_l10n_ro_pos_partner-19.0.1.1.0-py3-none-any.whl |
|---|---|
| Size | 33.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0753031db271ca0a5a646a9cef6cf0074e311e153640a9f8e633d8224d868f2b
|
|
BLAKE2b-256 checksum How to use checksums |
b80e3a6f04daddb072662bd3d71a570506d89b51aa8ea2056ad788f492610b98
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|