+91 98414 81435Free diagnosis
OdooBots
Loading
Integration · WordPress

Odoo WordPress integration

Most WordPress sites send their enquiries to an inbox, which is the quietest way to lose business. Nobody can say how many came in last month, which ones were answered, or which campaign they came from.

Connecting WordPress to Odoo turns that inbox into a pipeline. The same connection can carry portal logins, member records and content that sits alongside an Odoo shop.

Arun KumarOdoo Functional Consultant, 8+ years| Reviewed by Karthik Raj| Updated 20 October 2026| Covers Odoo 16–19, Community & Enterprise
Book a free Odoo diagnosis +91 98414 81435
0Odoo projects delivered
0Consultants & developers
Every enquiryA record, not an email
ChennaiAmbattur, Tamil Nadu
Odoo wordpress integration — a WordPress site sending form enquiries into Odoo CRM
630
630+ projectsdelivered on Odoo

Businesses running Odoo with OdooBots

Dhanalakshmi Industries logo Sanjeev Autoparts logo Electro Flux Equipments logo Anchor Marine Equipment Company logo NEXG logo PV Constructions logo SESS logo
Definition

What is Odoo WordPress integration?

Odoo WordPress integration turns site enquiries into CRM records and lets WordPress act as the public face of an Odoo-run business. Contact and quote forms create leads with their source and campaign attached, customers can reach an Odoo portal to see orders and invoices, member or subscriber records stay aligned, and content can sit alongside Odoo eCommerce where you want WordPress for the marketing and Odoo for the transactions.

If you also run WooCommerce, the shop side is a different piece of work with different rules — see Odoo WooCommerce integration. This page is about the site itself.

Lead source
Which page, form and campaign produced an enquiry. Lost entirely when forms go to an inbox.
Portal user
A customer with limited Odoo access to their own orders, invoices and tickets.
Form plugin
Contact Form 7, Gravity Forms, WPForms and others. Each posts differently, so each is mapped on its own.
Duplicate lead
The same person enquiring twice. Matched on email or phone rather than created again.
What syncs

What moves between WordPress and Odoo

Six things can move between a WordPress site and Odoo, and the first one is usually the only one a business needs on day one.

Form enquiries

Contact, quote and callback forms creating Odoo leads with the message, the page it came from and the campaign that brought the visitor.

LeadsSourceCampaign

Lead routing

New enquiries assigned by rule — by product interest, region or team — rather than by whoever happens to check the inbox.

RulesTeamsAssignment

Customer portal

A link from the site into the Odoo portal where a customer sees their own orders, invoices and support tickets.

OrdersInvoicesTickets

Members and subscribers

Membership or subscriber records aligned between the site and Odoo, with matching so one person is not created twice.

MembersMatchingStatus

Content with Odoo commerce

WordPress for marketing pages and blog, Odoo for products and checkout, with navigation and branding kept consistent across both.

BlogProductsConsistent

Tracking and attribution

UTM parameters and referrer carried into the lead record, so marketing spend can be judged on enquiries rather than on clicks.

UTMReferrerAttribution
How it works

How a record travels between WordPress and Odoo

A visitor arrives from a campaign, reads a page and submits the enquiry form. A lead is created in Odoo with the message, the page, the campaign and the referrer. An assignment rule routes it to the right salesperson, who follows up from the CRM where the history is kept. The marketing team can then see which campaigns produce enquiries rather than only which produce traffic.

Portal access, member sync and content alongside an Odoo shop are each a further step, worth adding when there is a reason rather than all at once.

  • Every form submission becomes a lead, not an email in a shared inbox
  • Page, campaign and referrer carried into the record for attribution
  • Leads assigned by rule so nothing sits unclaimed
  • Repeat enquirers matched on email or phone rather than duplicated
  • Portal, members and commerce added as separate steps when needed
Odoo wordpress integration showing synchronised records between the two systems
Connected systems — how wordpress and Odoo share one set of records.
Expertise · how we work

What we settle in week one of an Odoo WordPress integration

These are the decisions that are cheap to make now and painful to reverse once two systems have been exchanging records for a month.

  1. Which form plugin is in use

    Each plugin posts differently, so the mapping is built against your actual forms rather than a generic example.

  2. Field mapping per form

    Which form fields become which lead fields, including the ones that should go into the description rather than a column of their own.

  3. Duplicate matching rule

    How a repeat enquirer is matched on email or phone, so the pipeline does not fill with the same person four times.

  4. Assignment rules

    Who gets a new lead, by product, region or round robin, decided before go-live so nothing sits unclaimed.

  5. Attribution capture

    Which UTM and referrer values are stored, so marketing can be judged on enquiries rather than on traffic.

  6. Portal scope

    If customers get portal access, exactly what they can see, since this is a permission decision rather than a display one.

  7. Spam handling

    What stops bot submissions becoming leads, because an unfiltered form fills a CRM faster than a sales team can clear it.

Trust · honest advice

Where an Odoo WordPress integration needs work

We would rather say this before you buy licences than after. These are the areas where we scope real development, recommend a different tool, or tell you the connector will not reach.

WordPress stays WordPress

Themes, plugins and content management remain where they are. Odoo should not try to run your site.

Plugin-specific fields

Fields added by a third-party plugin need their own mapping and are scoped as development.

WooCommerce

The shop is a separate integration with its own rules. Treating it as part of the site connection is how scope goes wrong.

Membership plugins

Each membership plugin has its own model of a member, so alignment with Odoo is per plugin rather than generic.

Site performance

A slow or overloaded WordPress site produces failed submissions. Hosting problems appear as integration problems.

Two content systems

Running WordPress pages alongside an Odoo shop means two places to update branding. Worth choosing deliberately rather than drifting into.

Our services

Our Odoo WordPress integration process

Connecting WordPress to Odoo is less about the connector than about agreeing what is true where, and what happens when a record will not go through.

  1. What you are connecting

    Understand which form plugin you use, how enquiries are handled today, whether customers need portal access and whether a shop is in scope.

  2. Field and direction mapping

    Map each form field by field, agree duplicate matching, assignment rules and what attribution is captured, before anything is connected.

  3. Build and configure

    Connect WordPress to Odoo using the standard connector where one fits, and build only what the connector genuinely cannot reach. See Odoo customization.

  4. Test with your own data

    Your records, in a test database, including the awkward ones — the cancelled order, the partial refund, the product that exists on one side only.

  5. Error handling and alerts

    A queue for failed records with a named owner and an alert, because an integration nobody watches diverges quietly and the divergence is found at audit.

  6. Go-live and monitoring

    Cutover with a reconciliation on both sides, then hypercare, then ongoing support and AMC.

Trust · what it costs

What an Odoo WordPress integration costs

We do not publish one integration price, because the same connector costs very differently depending on the factors below. We do publish what moves the number, and the price is fixed in writing before work starts.

  • Number of formsEach form is its own mapping and its own routing rule.
  • Plugin varietySeveral form or membership plugins each need separate handling.
  • Portal requirementsCustomer portal access is a permission design exercise, not a switch.
  • Member synchronisationAligning membership records is per plugin and often the largest task.
  • Attribution depthFull campaign attribution needs tracking set up on the site as well.
  • Commerce alongsideRunning WordPress content with an Odoo shop adds design and navigation work.
Why us

Why choose OdooBots for your Odoo WordPress integration

We map every form against a real submission, including the spam, because an unfiltered connection fills a CRM faster than a sales team can empty it. Enquiries should arrive as a pipeline, not as a second inbox.

Based inAmbattur, ChennaiTamil Nadu 600053, India
Phone+91 98414 81435Mon–Sat, business hours IST
Delivered630+ Odoo projects30+ consultants and developers
Versions supportedOdoo 16 – 19Community and Enterprise
FAQ

Odoo WordPress integration: frequently asked questions

Why integrate WordPress with Odoo ERP?
Because form enquiries sent to an inbox cannot be counted, assigned or attributed. Connecting the site to Odoo turns each submission into a lead with its page, campaign and referrer, routed to a salesperson by rule, so marketing spend can be judged on enquiries rather than on clicks.
Can WordPress contact forms create leads in Odoo?
Yes, from Contact Form 7, Gravity Forms, WPForms or whichever plugin you use. Each posts differently, so the mapping is built against your actual forms, field by field, rather than from a generic example.
How are duplicate enquiries handled?
A repeat enquirer is matched on email or phone and the activity is added to the existing record rather than creating another one. Without this rule the pipeline fills with the same person several times over and the numbers stop meaning anything.
Can customers log in to see their orders and invoices?
Yes, through the Odoo customer portal linked from your WordPress site, where they can see their own orders, invoices and support tickets. Exactly what they can see is a permission decision taken during the project rather than a default.
Is this the same as WooCommerce integration?
No. The shop is a separate piece of work with its own catalogue, stock and order rules — see Odoo WooCommerce integration. This page covers the site itself: forms, leads, portal access and member records.
Can we keep WordPress for content and use Odoo for the shop?
Yes, and some businesses prefer it because their marketing team knows WordPress. The trade-off is two places to maintain branding and navigation, which is worth choosing deliberately rather than drifting into over time.
How is form spam prevented from filling the CRM?
With filtering on the site before the submission ever reaches Odoo. This matters more than it sounds: an unfiltered connection fills a CRM faster than a sales team can clear it, and the team then stops trusting the pipeline.
Can OdooBots build a custom WordPress integration?
Yes, including plugin-specific field mapping, membership record alignment, portal access and campaign attribution. See Odoo customization.
References

Sources and official documentation

Product capabilities stated on this page are documented by Odoo. The mapping advice, failure handling and limitations come from our own integrations.

Ready to connect WordPress to Odoo?

Tell us which form plugin you use and how enquiries are handled today. Those two answers shape the mapping, and the diagnosis call is free.

Book a free Odoo diagnosis +91 98414 81435