You will get a two-way Odoo and Laravel sync that survives either system changing
Top Rated
Project details
Odoo integrations rarely fail loudly. A webhook gets replayed and you have two of the same customer. A two-way sync loops and quietly overwrites yesterday's edit. Six months in, nobody can say whether Odoo or the app holds the true number, and finance is reconciling by hand.
I've built this in production rather than in theory. I integrated Odoo v19 with a multi-tenant ERP/CRM used by more than 6,000 employees — two-way sync for clients and reservations over REST and webhooks — alongside HR document generation that reads salary from Odoo at render time and never stores it.
Four things carry an integration like that, and they are what you are paying for. Idempotency, so a retry costs nothing. Loop prevention, so both systems can safely write. Explicit conflict rules, so which side wins is a decision you made rather than a race you lost. And an audit trail, so when finance asks why a number changed, you can answer.
I work with Odoo 15 through 19 — self-hosted, Odoo.sh or SaaS — over REST, XML-RPC or webhooks. Laravel on the other side, or any PHP or Node service with an HTTP API.
Send me your model list and roughly how often each side writes, and I'll say which tier fits.
I've built this in production rather than in theory. I integrated Odoo v19 with a multi-tenant ERP/CRM used by more than 6,000 employees — two-way sync for clients and reservations over REST and webhooks — alongside HR document generation that reads salary from Odoo at render time and never stores it.
Four things carry an integration like that, and they are what you are paying for. Idempotency, so a retry costs nothing. Loop prevention, so both systems can safely write. Explicit conflict rules, so which side wins is a decision you made rather than a race you lost. And an audit trail, so when finance asks why a number changed, you can answer.
I work with Odoo 15 through 19 — self-hosted, Odoo.sh or SaaS — over REST, XML-RPC or webhooks. Laravel on the other side, or any PHP or Node service with an HTTP API.
Send me your model list and roughly how often each side writes, and I'll say which tier fits.
Programming Languages
PHP, JavaScript, TypeScriptCoding Expertise
Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$2,500
|
Standard
$4,800
|
Advanced
$9,800
|
|---|---|---|---|
| Delivery Time | 14 days | 21 days | 35 days |
Number of Revisions | 2 | 3 | 4 |
Design Customization | - | - | - |
Content Upload | - | - | - |
Responsive Design | - | - | |
Source Code |
Frequently asked questions
About Omar
Senior Full Stack & Shopify App Developer | Laravel, Next.js, APIs
100%
Job Success
Cairo, Egypt - 3:21 am local time
and I ship both halves: Laravel and PostgreSQL on the backend, React and Next.js
on the front.
Recent work:
• A published Shopify app for last-mile delivery — React Router 7 (Remix), Prisma,
Polaris and App Bridge — quoting live rates at checkout through the Carrier
Service API and writing fulfillments back to the merchant's order
• The delivery and inventory platform behind it: vendors, delivery agents,
warehouse staff and customers, with cash-on-delivery reconciled into vendor
wallets through a credit/debit ledger
• A travel booking platform running on Hotelbeds, with Stripe and PayPal behind
one gateway interface
• A multi-tenant ERP/CRM used by 6,000+ employees daily
What I'm good at: money arithmetic that can't drift, integrations that survive the
third party changing something without telling you, and taking over an existing
codebase without breaking it.
Shopify specifically — apps, not themes. Admin GraphQL, Carrier Service API,
fulfillmentCreate and delivery events, OAuth and session storage, and the
mandatory GDPR webhooks implemented properly rather than returning 200 and doing
nothing. I've also built a full Liquid storefront with Stripe, Klarna, PayPal and
Apple Pay in three languages.
Stack — PHP 8.4, Laravel 12, PostgreSQL, MySQL, Redis, Octane, Next.js, React,
TypeScript, Flutter, Docker, GitHub Actions, GCP.
Integrations — Shopify, Stripe, PayPal, Odoo, Microsoft Graph, Hotelbeds,
Meta Ads, Firebase, Twilio, Typesense.
Top Rated with 100% Job Success across 570+ hours.
If you're stuck on something specific, message me with what's broken and I'll tell
you straight whether I'm the right person for it.
Steps for completing your project
After purchasing the project, send requirements so Omar can start the project.
Delivery time starts when Omar receives requirements from you.
Omar works on your project following the steps below.
Revisions may occur after the delivery date.
Discovery: map your models, fields and write patterns
I read both schemas and confirm which models sync, in which direction, and how often each side writes. You get the field mapping in writing before any code is committed.
Identity and idempotency: safe writes in one direction
Every synced record gets an odoo_id so both systems agree on identity, and writes are made idempotent so a retry or a replayed webhook cannot create duplicates.