Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Laradoo Laravel Package

edujugon/laradoo

Laradoo is a Laravel package for integrating Odoo ERP. It provides an Eloquent-style query builder and models to query, create, update, and delete Odoo records via XML-RPC/JSON-RPC, making ERP data access feel native in Laravel applications.

View on GitHub
Deep Wiki
Context7

Odoo ERP API for Laravel

Frequently asked questions about Laradoo
Is Laradoo compatible with Laravel 10 and Laravel 11?
The package's last release was in 2020, so modern Laravel versions such as 9, 10, and 11 are not officially supported and will likely require patching or a fork. Validate your exact Laravel and PHP combination with a time-boxed compatibility spike against a staging environment before adopting it. If you are on a recent Laravel release, assume compatibility work is needed up front.
How do I install and configure Laradoo in a Laravel application?
Install it with Composer using the edujugon/laradoo package name, then publish and edit its configuration file to supply your Odoo host, database, username, and password. Keep those credentials in environment variables or a secrets manager and use a dedicated Odoo API user with the minimum permissions required. Check the README and config keys carefully, since the package predates newer Laravel configuration conventions and may need manual adjustment.
Which Odoo versions does Laradoo support?
There is no formal support matrix, and Odoo model schemas, authentication expectations, and error semantics change between versions. You must prove compatibility against your exact target Odoo version, hosting model, and database in a staging instance. Treat any unverified combination as a blocker until it has been tested.
Can Laradoo create, update, and delete Odoo records, or is it read-only?
Laradoo provides an Eloquent-style query builder and models for querying, creating, updating, and deleting Odoo records over XML-RPC or JSON-RPC. In practice, start with read-only operations such as partners, products, and invoices, then add controlled write-back behind an internal adapter. Writes need idempotency keys and reconciliation, because a successful Odoo call does not guarantee your Laravel-side persistence also succeeds.
Does Laradoo work with PHP 8.x?
That is not guaranteed. The 2020 release predates mainstream PHP 8 support, and its transitive dependencies may not be compatible with PHP 8.x runtimes. Pin your Composer dependencies, run static analysis and dependency audits, and patch or fork the package if the supported PHP versions do not match your platform.
What is the difference between Laradoo and a native Odoo XML-RPC or JSON-RPC client?
Laradoo is an opinionated Laravel wrapper that adds Eloquent-style models and a query builder on top of Odoo's external API, which cuts boilerplate for simple CRUD use cases. A native XML-RPC or JSON-RPC client gives you direct control over transport, retries, and error handling and is usually the better choice for greenfield or high-volume integrations. Many teams keep Laradoo as a reference implementation only.
How do I test Laradoo integrations without hitting production Odoo?
Run contract tests against a staging Odoo instance with a dedicated API user and a network path that mirrors production. Mocking the RPC layer alone will not catch schema or authentication drift between Odoo versions. Keep the integration behind an internal interface so unit tests can use a fake driver while integration tests exercise the real one.
Is Laradoo safe for high-volume Odoo synchronization in production?
No. Laradoo fits low-to-moderate volume, request/response CRUD, not high-volume synchronization, event-driven integration, or workflows needing distributed transactions across Laravel and Odoo. Synchronous latency, weak built-in retry and idempotency patterns, and stale maintenance make it a poor fit for those workloads. Prefer a maintained Odoo client or a queue-based integration for heavy traffic.
How should I handle failures and retries when writing to Odoo through Laradoo?
Hide Laradoo behind an application-specific adapter that owns timeouts, retries, idempotency keys, and reconciliation, and expose methods like createInvoiceDraft rather than raw Odoo model calls. Reconcile after every write, because a successful Odoo call can still leave your Laravel database inconsistent. Use feature flags and a documented rollback path so you can disable Laradoo without redeploying application logic.
Is Laradoo still maintained, and can I fork it?
The last release was in 2020, so the project is effectively stale by Laravel and PHP standards and should be treated as unmaintained. The MIT license does permit a fork, but doing so transfers maintenance and on-call ownership to your team. If you fork, pin the dependency, document a Laravel, PHP, and Odoo support matrix, and plan for ongoing security and compatibility patches.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
3mdikram/worldmoneywords
snowsoft/config
itmosoft/laravel-subscriptions
larva/laravel-ai-qwen
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib