One system for the whole business.

Through a connector that maps each record type and decides which system owns it. We publish the Live Odoo Connector for Shopify, and Odoo-side modules for Shopify, Magento 2 and WooCommerce. The work that matters is the mapping and the direction, not the install.

Yes. We publish Odoo modules for Magento 2 on the Magento REST API and for WooCommerce on the REST API v3, alongside the Shopify one. All three share one engine, so identity mapping and the job queue behave the same way whichever store you run.

Odoo 16, 17, 18 and 19, Community or Enterprise. Our published modules are certified against each listed version on every release.

Odoo Online cannot run third-party modules that contain Python, which is Odoo's rule rather than ours. Anything involving a connector or a custom module needs Odoo.sh or a self-hosted install.

Taxes and identity. An unmapped tax rate that quietly produces an invoice short by the tax, and a record matched on the wrong key so a re-run creates a second copy of an order. Both are avoidable, and both are cheaper to design for than to unpick later.

Odoo, in most businesses running it, because that is where purchasing, receiving and warehouse moves happen. The storefront then shows what Odoo says is available. Choosing one and holding to it is what stops the two drifting apart.

Yes, and it is usually the part worth the most care. Products, customers, open orders and balances each need a decision about what comes across and what is archived. Importing everything by default is rarely what anyone actually wants.

Often. The first step is reading what is already there rather than proposing a rebuild. A half-finished Odoo usually contains a lot of correct decisions worth keeping.

Somebody has to own the thing when a sync fails at 6pm. We stay on for that, and the job queue is built so a failure tells you what to fix rather than disappearing.

Community is enough for many businesses that need sales, inventory, purchasing, and basic accounting. Enterprise adds the modules most growing operations reach for within a year: advanced inventory routes, multi-company, full accounting automation, studio customization, and official support. Both expose the same external API, so a Shopify integration works either way. We confirm which edition your workflow actually needs during the audit rather than defaulting you to the larger one.

A focused implementation covering sales, inventory, and purchasing typically runs four to eight weeks from audit to go-live. Adding accounting, manufacturing, or a Shopify integration extends that. The variable that moves the timeline most is data quality: clean product and customer data migrates quickly, while inconsistent SKUs and duplicate customer records are usually the real bottleneck. We quantify that in the audit before committing to a date.

Odoo exposes an external API, so in principle anything with an API can be connected: ecommerce platforms, payment providers, bank feeds, 3PL and shipping carriers, CRM systems, and industry software. We build these integrations ourselves with retry logic and failure alerting. The one we know deepest is Shopify, where we build and operate the Live Odoo Connector in production, syncing products, variants, inventory, orders, customers, and invoices in real time, including Shopify Plus B2B.

No. Most Odoo work involves no storefront at all: inventory and warehouse configuration, purchasing and supplier management, quoting and invoicing, manufacturing routes, project tracking, accounting, and getting a team trained well enough to run the system without calling us every week. We work with wholesalers, manufacturers, distributors, trades, and service businesses. Ecommerce is one integration we happen to know unusually well, not a requirement.

Five stages. First an audit of your current process and data. Then configuration of the modules you need, in a test database rather than production. Then data migration, with a documented rollback path. Then integration work if Shopify or another system is in scope. Then training and support, because an ERP nobody on your team can operate is a failed project regardless of how well it was configured.

Yes, and this is where an engineering team matters. Odoo Studio handles lighter changes such as custom fields, views, and simple automation. Beyond that we write proper custom modules in Python against the Odoo framework, which is the right way to add genuinely bespoke logic, tailored reports, or a workflow standard Odoo has no concept of. Written properly, custom modules survive version upgrades. Written as quick hacks into core files, they do not, which is why we do not work that way.

New Zealand, working across NZ, Australia, the UK, the USA, and Canada. Odoo work is largely remote by nature: the system is browser-based and the integration work is API work. For New Zealand businesses that means local hours and local context; for everyone else it means we are awake when your overnight sync fails.