31 articles tagged odoo.
Decouple the storefront from Odoo and you get a faster, safer, upgrade-proof shop. DragonflyDB caching, island architecture, GitHub version control, PR previews, VPN-isolated ERP, PWA mobile UX — everything we ship on every headless e-commerce project.
A nightly export ran green for six weeks while sending nothing, because the API key it used had an expiration date on it and a housekeeping cron deleted the record the day after it lapsed. The three ways a credential dies, why only one of them is loud, and the register, the gauge and the authenticated probe that turn a surprise outage into a calendar entry.
A technician stood outside a locked building at seven in the morning because a recurring visit had been expanded into absolute instants six weeks before the clocks went back. The three kinds of "when" that don't convert into each other, why a recurrence rule is not a list of timestamps, what Odoo hands you over the API, and how to test a bug that only reproduces twice a year.
Raising the body-size limit is the fix that keeps working right up until it doesn't. Why buffering user files through your application is a dead end, the presigned handshake that replaces it, the checks that still have to happen after the bytes land, and why the ERP should be handed a pointer instead of a payload.
Belgium's structured e-invoicing mandate landed on 1 January. Switching it on was an afternoon; everything it exposed was the quarter that followed. What Peppol actually addresses, why the failures live in your contact records rather than your ERP, what UBL refuses to carry, and why 'sent' stopped meaning 'delivered'.
A phone system knows a number. An ERP knows a customer. In most companies nothing knows both, and closing that gap is a harder problem than the vendor demo suggests — nine years of phone numbers nobody normalised, an event stream instead of a polling loop, and a screen pop that must never be able to stop a call.
A rename is the cheapest thing a database does and one of the most dangerous things a deploy does, because two versions of your application are always live at once. Expand, backfill, contract — the release boundary that makes it safe, the locks that bite anyway, and what changes when Odoo owns the schema.
A reminder tells the customer something. A confirmation tells your calendar something — and only one of those lets you refill the slot. The virtual number that makes replies possible, the matching problem nobody warns you about, parsing what people actually type in three languages, and the Odoo automations that reschedule without a human.
We bill seven minutes when we work seven minutes. The timesheet-to-invoice pipeline in Odoo — billable rules, approval flows, and the client-facing detail line that makes the number defensible.
Processes live in Notion, specs in Confluence, manuals in Drive — and the ERP itself stays undocumented. Odoo's Knowledge app lets you put internal documentation next to the workflows it describes, with live data embedded instead of stale screenshots.
Every form submission is not equal. Scoring rules on source, behaviour and firmographics that push the right leads to the right salesperson while they're still warm.
SaaS-style billing inside an ERP: recurring plans, automated renewals, failed-payment retries, and the MRR and churn numbers finance actually asks for.
Work orders, van stock, mobile timesheets and customer signatures — Field Service keeps technicians inside the same database as invoicing. Where that earns its licence, and the two things it still needs help with: route optimization and offline reliability.
The OCA ecosystem is Odoo's superpower and its minefield in equal measure. The checklist we run — maintainer activity, test coverage, migration history — before a community module ever reaches a client's production database.
Custom modules without tests are upgrades waiting to fail. Our pytest-odoo setup, the fixtures worth writing, and the CI gate that blocks a merge when a workflow breaks.
Every integration starts with the same question: how do we talk to Odoo? The honest trade-offs between the stock JSON-2 API, community REST modules and a purpose-built gateway — and the one question that picks the right door per consumer.
Management wants dashboards, not ERP seats. How we wire a Postgres read replica to Metabase for self-service BI — and the row-level care that keeps payroll off the office TV.
The quote is the most-read document your company produces, and the default Odoo template screams default. How we build QWeb reports that match brand guidelines exactly — headers, fonts, terms — without losing the fight against wkhtmltopdf.
Most Odoo installs run with everyone as admin until the first incident. How we design permission groups that mirror the org chart, record rules that hold up under audit, and logging that answers who changed what — before anyone has to ask.
Contacts, deals, invoices, historical documents — the export/transform/import pipeline we run when a company outgrows its starter tools, and the data you should deliberately leave behind.
Odoo's point of sale keeps ringing up orders when the internet doesn't. How the browser cache, order queue and payment terminal fallbacks actually behave when the line drops — and the drill we run before every opening day.
Running two or ten legal entities from one Odoo database sounds simple until inter-company invoicing, shared warehouses and per-company charts of accounts collide. The setup decisions we make on day one so consolidation stays painless.
Storefront, mobile app, carrier webhooks, marketing tools — everything wants to talk to Odoo. Let them all speak JSON-RPC directly and every consumer inherits Odoo's internals. We give them one door instead.
Studio is brilliant for a field and a filter — and a trap for business logic. The boundary we draw between no-code tweaks and real modules, and what each choice costs at upgrade time.
Your ERP answers in 800 ms and no amount of React tuning changes that. What does: not asking twice. The query-key, staleTime and invalidation patterns we use in front of Odoo.
A production Odoo container is not `docker run odoo`. Multi-process layouts, odoo.conf mounts, and why your Dockerfile should not install modules at runtime.
New developer, new laptop, same Odoo in ten minutes. Our standard Compose setup for local Odoo with Postgres, Mailpit, and hot-reloaded addons.
Build tools and git history do not belong in production images. How we use multi-stage Dockerfiles to ship lean Odoo containers under 500 MB.
Server logs tell you something broke after a user calls. Error tracking tells you first, with the full traceback and context. How we wire Odoo to Sentry or self-hosted GlitchTip with the OCA sentry module.
Custom Odoo development is easy to start and easy to regret. A field guide to building modules that still work after the next major version.
The cheapest moment to discover a problem is before anyone writes code. What a fit-gap analysis actually is, what it produces, and why Code Agency won't scope an implementation without one.