Odoo, deployed, configured and extended for your business
An ERP that installs app by app: you switch on only what your business uses, and add the rest when it earns its place. We deploy it, configure it around your business and bring it in line with the law that applies to you.
What Odoo covers as standard
Compliance, where you operate
The platform is the same whatever the country. What changes is the configuration: chart of accounts, tax rates, exchange formats, transmission obligations. We set out France and Switzerland below because they are the two our clients meet most often. For another country the principle does not change: we start from what local law requires, and configure accordingly.
France
Transmission starts from the ERP: your invoices are issued and received where they are produced, with no third-party platform to connect and no separate portal to keep running. Incoming invoices are accepted in Factur-X, UBL and CII; outgoing ones are sent in UBL. We configure issuing, receiving and e-reporting, carry over your statutory invoice details and check your tax mapping before go-live. We claim no accreditation, neither for ourselves nor for the publisher.
Switzerland
The Swiss chart of accounts and the QR-bill are part of the core: they are configured, not developed. We set your QR-IBAN on the bank journal and complete your partners’ addresses — your invoices then read correctly at Swiss banks, and incoming payments reconcile on their own. VAT rates and reporting grids ship as standard; the VAT return itself belongs to the Enterprise edition, and we tell you so before you choose your edition. For payroll, the core is Swissdec-certified — withholding tax at cantonal rates, occupational pension, electronic salary declaration — again on Enterprise.
Each country you operate in is handled on its own terms, with its own rules and formats. You still deal with one person, however many of them there are.
How we work
Integration in practice
Odoo installs app by app: you switch on only what earns its place. We start from your real flows — quotation, order, purchase, stock, invoice — to assemble the smallest core that carries them, then configure permissions, numbering, tax rates and document templates around your habits rather than around the defaults. History is carried across and checked before go-live: data entered once travels, and the gap between recorded and actual becomes visible rather than being discovered at month end.
Where the standard stops, we build. The full e-invoicing chain — issuing, receiving, evidential archiving — is handled in the ERP rather than in a separate portal, and detailed on our page devoted to electronic invoicing. Subscription proration mid-period, which the core reserves for service-type products, is another. And where a trade has no standard equivalent at all, we build it: hotel management is one, since neither the reservation plan nor charging a restaurant bill to a room exists in the core — hotel management systems and Restaurant & Hotel POS.
How we build is set out on Custom Development, and how we look after what we deliver on Support & maintenance.
The modules we have built around the core
The standard covers a great deal. It stops at a few specific points: those are the ones we build.
E-invoicing, the whole chain
Issuing, multi-channel receipt and evidential archiving, handled in the ERP rather than in a separate portal.
Electronic invoicingSubscriptions, proration throughout
The core prorates a mid-period change, but on service-type products only: the publisher expressly excludes goods, where the interface suggests otherwise.
PMS — hotel management
The core covers sales and invoicing, not the booking plan: rooms, arrivals, departures and seasonal rates have no standard equivalent.
Management Systems (PMS)Restaurant till linked to the hotel
The point of sale covers the floor, the tables and sending to the kitchen; the room it does not — with no hotel management, there is no bill to charge and no payment to split.
Restaurant & Hotel POSOdoo after go-live
Odoo releases a major version every year. Applications you had not enabled become relevant, bespoke configuration needs revalidating, and invoice issuance follows a shifting regulatory calendar.
We prepare each upgrade in advance, we check your configuration on a separate environment, then we switch over. BUILD installs Odoo; RUN keeps its calendar from becoming yours.
Support & maintenance