Run sales, inventory and accounting in one Odoo, with an implementation partner for US businesses.

No. Azinove Group has two companies, Azinove SAS in Strasbourg, France, and Azinove W.L.L in Bahrain, which is the group’s headquarters. We do not have a US office, a US entity or US clients we can name, and our engagements in the US do not include on-site work. What we offer instead is a process designed for remote delivery: written scoping, configuration demos by video, user acceptance on a test database and decisions kept in writing, so nothing depends on being in the same room.

Central European time is six hours ahead of US Eastern time, so a US morning lines up with a European afternoon. We schedule workshops, demos and acceptance sessions in that overlap and handle the rest asynchronously, through written notes and recorded videos your team can watch when it suits them. For companies further west the overlap is shorter, so we agree meeting times at the start of the project and put them in writing, along with support hours and the go-live window.

It can, but how depends on your situation. Some companies manage with Odoo’s own tax configuration and fiscal positions; others with obligations in many states are better served by a dedicated sales tax connector. We look at where you sell and ship, then choose the approach with you during scoping. Which states you owe tax in, and at what rates, is for your CPA or tax adviser to confirm. We configure Odoo to match their answer.

Nothing moves until we agree what is worth moving. Typically that means customers, vendors, products, open invoices and bills, and opening balances, with older transactions kept in an archive rather than imported line by line. We map each source file to Odoo, load it into a test database, and your team checks the numbers against the old system. The cutover date is usually set around a period close so the books carry over cleanly.

Yes. Odoo can hold several companies in one database, each with its own books, bank accounts, document numbering and currency, and give you a consolidated view across them. The decisions that matter are made at the start: which products, contacts and users are shared, how sales and purchases between your own companies are recorded, and what each entity reports. Those choices are hard to change later, so they go into the written scope before configuration begins.

Yes, in-house, but only when the standard modules cannot express a real business rule, such as a pricing method, a production step or an approval specific to your company. Every customization adds work at upgrade time, so we first check whether configuration or a well-maintained existing module does the job. When we do build, the module is written in Python, kept under version control and handed over as source code, which belongs to you once the project is paid in full.

Yes. For an older Odoo we start with a review of its configuration and custom code, then decide for each customization whether to keep it, replace it with a standard feature or drop it, before moving the data. For another ERP we map its data structure to Odoo and run test loads until the figures reconcile. In both cases your team validates the result on a test database before anything changes in production.

Odoo can run on Odoo’s own hosting or on a server or cloud account you control; if you need custom modules, that narrows the options, and we explain the trade-offs during scoping. The Odoo licence is a subscription with Odoo, separate from our implementation and support work, and our proposal states clearly which costs are ours and which are not. Backups, access and where the data sits are written into the engagement.

Your users are trained on their own workflows, using recorded sessions and short written guides they can return to. After launch we stay on under a written support arrangement covering fixes, questions, adjustments as the business changes and planning for future Odoo upgrades. Support hours are agreed with the time difference in mind. The same team that configured your system supports it, so you are not explaining your setup to someone new.