sefirosweb/laravel-odoo-connector

Driver to connect Odoo using ORM of laravel

v12.0.3 2026-04-23 19:26 UTC

Requires

• php: ^8.2
• laravel/framework: ^12.0

Requires (Dev)

• orchestra/testbench: ^10.0
• phpunit/phpunit: ^11.0

MIT

• Sefirosweb

README

Use Laravel's Eloquent ORM against an Odoo instance, through Odoo's JSON-RPC API.

Reference: Odoo Web Services Documentation (JSON-RPC).

Why JSON-RPC instead of a raw PostgreSQL connection?

Connecting Laravel directly to Odoo's Postgres database is simpler on paper but bypasses Odoo's business logic. Every time Odoo's ORM handles a write it runs a chain of Python-side triggers — invoice generation, stock moves, mail activities, etc. — that a raw SQL INSERT will silently skip.

This package goes through Odoo's JSON-RPC layer so those side effects still fire. It also lets you call model actions (the equivalent of clicking a button in the Odoo UI), which is impossible from raw SQL:

$saleOrder = SaleOrder::find(1);
$saleOrder->action('action_confirm');
// Triggers the "Confirm" button on sale.order — see Odoo's sale/models/sale_order.py

Requirements

• PHP ^8.2
• Laravel ^12.0
• An Odoo instance with JSON-RPC access enabled and valid credentials (username + API key or password).

Installation

composer require sefirosweb/laravel-odoo-connector:^12.0

The service provider auto-registers via Laravel's package discovery and registers an odoo driver on Laravel's connection manager.

Configuration

1. Declare the connection in config/database.php

'connections' => [
    // ...
    'odoo' => [
        'driver'   => 'odoo',
        'host'     => env('ODOO_HOST',     'https://your-odoo-host.com'),
        'database' => env('ODOO_DB',       'db_name'),
        'username' => env('ODOO_USERNAME', 'user'),
        'password' => env('ODOO_PASSWORD', 'api_key'),
        'defaultOptions' => [
            'timeout' => 20,
            'context' => [
                'lang' => 'es_ES',
            ],
        ],
    ],
],

And in .env:

ODOO_HOST=https://your-odoo-host.com
ODOO_DB=db_name
ODOO_USERNAME=user
ODOO_PASSWORD=api_key

2. (Optional) Publish the config to override shipped models

php artisan vendor:publish --provider="Sefirosweb\LaravelOdooConnector\LaravelOdooConnectorServiceProvider" --tag=config --force

Then in config/laravel-odoo-connector.php:

return [
    'ProductProduct'  => App\Odoo\CustomProductProduct::class,
    'ProductTemplate' => Sefirosweb\LaravelOdooConnector\Http\Models\ProductTemplate::class,
    'ResLang'         => Sefirosweb\LaravelOdooConnector\Http\Models\ResLang::class,
    // ...
];

Every model in the package resolves related classes through this config, so replacing ProductProduct here propagates to any relation that targets it.

3. Test the connection

php artisan test:odoo

This runs a smoke test that fetches the first MrpProduction and dumps its mrp_immediate_production_lines relation. It's a quick way to verify auth + connectivity.

Usage

Basic Eloquent

The shipped models under Sefirosweb\LaravelOdooConnector\Http\Models\* cover the most common Odoo models (product, mrp, sale, purchase, stock, mail, etc.). Use them like any Eloquent model:

use Sefirosweb\LaravelOdooConnector\Http\Models\ProductProduct;

$products = ProductProduct::where('name', 'like', '%widget%')
    ->with('mrp_bom')
    ->get();

$product = ProductProduct::find(1);
$product->name = 'New name';
$product->save();

$created = ProductProduct::create([
    'name'        => 'Product X',
    'description' => 'Flagship SKU',
    'list_price'  => 100,
]);

Supported Eloquent methods include find, where, whereIn, whereNotIn, whereNull, whereNotNull, with, create, update, delete, get, first, limit, offset, orderBy, etc.

Known limitations

Odoo's domain filter language is more restrictive than SQL, so a few Eloquent primitives cannot be translated:

• whereHas() / has() / whereDoesntHave() — these compile to a correlated EXISTS subquery which Odoo cannot express. The driver throws OdooUnsupportedOperationException with an actionable message pointing you at the workaround: resolve the related ids first and pass them to whereIn():

  // ❌ Will throw OdooUnsupportedOperationException
  $orders = SaleOrder::whereHas('sale_order_lines')->get();
  
  // ✅ Two-step pattern that works
  $orderIds = SaleOrderLine::select('order_id')->pluck('order_id');
  $orders   = SaleOrder::whereIn('id', $orderIds)->get();

• many2one fields are returned as [id, display_name] tuples, not plain ids. This is how Odoo JSON-RPC serialises them and the driver does not unwrap them for you. If you need just the id, access [0]:

  $line = SaleOrderLine::first();
  $orderId = is_array($line->order_id) ? $line->order_id[0] : $line->order_id;

• Empty char / text fields come back as false, not null / "". Another Odoo serialisation quirk; check with === false when that matters.

• between, whereDate, whereYear, raw SQL expressions and other where types that require SQL-side evaluation will also throw OdooUnsupportedOperationException at compile time.

Customising a model

Extend the shipped model and register your override through the config:

namespace App\Odoo;

use Illuminate\Database\Eloquent\Relations\BelongsTo;
use Sefirosweb\LaravelOdooConnector\Http\Models\ProductProduct as BaseProductProduct;

class CustomProductProduct extends BaseProductProduct
{
    protected $table = 'product.product';

    public function our_custom_belongs(): BelongsTo
    {
        return $this->belongsTo(OurCustomModel::class, 'our_field_id');
    }
}

Then point config/laravel-odoo-connector.php:ProductProduct at App\Odoo\CustomProductProduct::class.

Soft-deletes (the Odoo active flag)

Odoo's equivalent of a soft-delete is the active boolean column. Mirror it with the shipped trait:

use Sefirosweb\LaravelOdooConnector\Http\Models\OdooModel;
use Sefirosweb\LaravelOdooConnector\Http\Traits\SoftDeleteOdoo;

class MyModel extends OdooModel
{
    use SoftDeleteOdoo;
    // ...
}

Fetching large collections

Odoo JSON-RPC times out on unbounded queries. Use get_all to chunk automatically (500 records per batch by default):

$products = ProductProduct::get_all('id', 'name', 100);
// Behaves like ::all() but paginates under the hood.

Model actions (Odoo server-side buttons)

Trigger the equivalent of a UI button:

$saleOrder = SaleOrder::find(1);
$saleOrder->action('action_confirm');

Pass extra arguments when the action needs them:

$args = [[['id' => 1]]];
SaleOrder::model_action('action_custom', $args);

Multiple Odoo connections

Define multiple odoo connections in config/database.php and target one from a model:

use Sefirosweb\LaravelOdooConnector\Http\Models\OdooModel;

class SecondaryOdooModel extends OdooModel
{
    protected $connection = 'other_odoo';
}

Or run a one-off query against a named connection:

ProductProduct::on('other_odoo')->where(...)->get();

Testing

The test suite is split in two:

• Feature — offline smoke tests (service provider boot, DB::extend('odoo', …) registration). Always run; no external dependencies.
• Integration — hit a real Odoo instance over JSON-RPC. Cover authentication, ResPartner, ProductProduct, SaleOrder + relations, PurchaseOrder, and the actionable error paths (whereHas / bad credentials). Auto-skip when the ODOO_* environment variables are not set.

Run the offline suite only

composer install
./vendor/bin/phpunit --testsuite Feature

Run the integration suite

Set the four required variables in your shell or load them from a local .env.testing:

export ODOO_HOST=https://your-odoo-staging.example
export ODOO_DB=odoo_staging
export ODOO_USERNAME=[e-mail]
export ODOO_PASSWORD=your-api-key
# Optional:
export ODOO_TIMEOUT=20
export ODOO_LANG=en_US

./vendor/bin/phpunit --testsuite Integration

Integration tests are read-only — they never create, update or delete rows — so they are safe to run against a production-copy Odoo, though a staging instance is preferable.

Run both suites

./vendor/bin/phpunit

When working from the laravel-test harness with Sail, pass the env vars through docker exec:

docker exec -w /var/www/html/packages/laravel-odoo-connector \
  -e ODOO_HOST=$ODOO_HOST \
  -e ODOO_DB=$ODOO_DB \
  -e ODOO_USERNAME=$ODOO_USERNAME \
  -e ODOO_PASSWORD=$ODOO_PASSWORD \
  laravel-test-laravel.test-1 ./vendor/bin/phpunit

Roadmap

• Add the remaining Odoo models that individual projects depend on (custom Odoo installs vary per client, so the package ships only the "standard" models).
• Optionally auto-unwrap many2one tuples to plain ids inside OdooProcessor (would change the public contract, so gated behind a config flag).

Versioning

Major versions are aligned with Laravel majors (12.x, 11.x, 9.x …). See the root CLAUDE.md of the test harness for the full policy.

License

MIT.