Available for Odoo 16-19OWL-first implementation studio

ERPFlows builds Odoo apps and OWL interfaces that operators adopt fast.

We design field widgets, action screens, and production-ready Odoo modules for teams that need cleaner workflows, better visibility, and implementation support that goes beyond code delivery.

OWL field widgetsClient actions and map screensOdoo Store-ready modules
Book OWL auditBrowse Odoo Apps
Live module snapshot
ERPFlows Fleet Traccar Connector (Two-Way Sync)
$89 on Odoo Store
ERPFlows Fleet Traccar live map screenshot
OWL actions
Leaflet
Fleet
Integration
Deadline approaching
Free
ERPFlows Advanced OWL Countdown Timer banner
Advanced OWL Countdown Timer
Real-time SLA and deadline countdown in OWL.
Aging signals
Free
ERPFlows Records Age Indicator screenshot
Records Age Indicator
Threshold-based status visibility without backend load.
3
Live modules

already packaged for the Odoo App Store

OWL
Frontend specialization

field widgets, client actions, and responsive operator flows

End-to-End
Delivery model

audit, implementation, rollout, and post-launch support
Live Odoo Store modules

Productized OWL modules built from real operational pain points

The current ERPFlows lineup covers deadline visibility, stale record detection, and fleet telemetry sync. Each module doubles as a proof point for the kind of OWL customization and Odoo delivery work we do for clients.

ERPFlows Advanced OWL Countdown Timer banner
Countdown widget showing remaining time in days and hours

Real-time timer in list or form views

Countdown widget updating time left inside Odoo

Second-by-second updates without page refresh

Countdown widget showing deadline status

Clear deadline-passed state for urgent work

Available for Odoo 16-19 | Productivity UX | OWL field widgetFree module

ERPFlows Advanced OWL Countdown Timer & Deadline Tracker

A real-time deadline tracker for Date and Datetime fields that keeps SLA pressure visible directly inside Odoo views.

This module computes countdowns in the browser with OWL and Luxon, updates every second, and flips visual state when the deadline is close or already missed.

OWLLuxonDate fieldsSLA tracking
  • Works on any Date or Datetime field
  • Second-by-second countdown updates in OWL
  • Client-side calculation reduces server load
  • Useful for deadlines, SLAs, renewals, and delivery promises
OWL proof point

Built as an OWL badge field registered in the Odoo field registry and mounted with component state plus lifecycle cleanup.

<field name="x_deadline" widget="counter"/>
Find on Odoo StoreCustomize this module
ERPFlows Records Age Indicator screenshot
Recent record badge in green

Recent activity stays visibly green

Warning record age badge in yellow

Warning thresholds surface aging work earlier

Overdue record age badge with pulse state

Stale records pulse when action is overdue

Available for Odoo 16-19 | User Interface | OWL field widgetFree module

ERPFlows Records Age Indicator

A color-coded age indicator for Date and Datetime fields so teams can spot stale, recent, or overdue records instantly.

The module extends Odoo badge fields with configurable thresholds, formatted tooltips, and pulse feedback for records that need attention.

OWLBadge widgetFrontend-onlyThreshold alerts
  • Works with any Date or Datetime field
  • Configurable recent and warning thresholds
  • Pure frontend extension for fast rendering
  • Strong fit for invoices, leads, tickets, tasks, and approvals
OWL proof point

Thresholds are passed as widget options, interpreted in OWL props, and rendered with status-aware classes for immediate visual feedback.

<field name="date_order" widget="record_age" options="{'recent_days': 0.5, 'warning_days': 2}"/>
View on Odoo StoreCustomize this module
ERPFlows Fleet Traccar live map screenshot
Fleet Traccar configuration and sync controls

Configuration and two-way sync controls

Live Traccar map inside Odoo Fleet

Live map with search, refresh, and vehicle markers

Trip replay route map for a tracked vehicle

Trip replay with route line and start/end markers

Available for Odoo 16-19 | Fleet | OWL action screens$89 on Odoo Store

ERPFlows Fleet Traccar Connector (Two-Way Sync)

A production-focused connector that syncs Odoo Fleet and Traccar in both directions with live map visibility and trip route replay.

It covers device import, vehicle push, company-level configuration, scheduled sync, live map actions, and date-range trip playback for operations teams.

OWL actionsLeafletFleetIntegration
  • Odoo to Traccar and Traccar to Odoo sync flows
  • Live map action with search and auto-refresh
  • Trip route replay by vehicle and date range
  • Company-aware configuration, cron sync, and status tracking
OWL proof point

The frontend uses OWL client actions, debounced search, map lifecycle handling, and incremental marker refresh against live Traccar data.

registry.category("actions").add("erpflows_fleet_traccar.traccar_trip_map", TraccarTripMapAction);
View on Odoo StoreCustomize this module
Need a variant?

ERPFlows extends these modules into client-specific workflows.

We adapt existing apps, build adjacent features, and connect them to the rest of your Odoo stack with a rollout plan your operators can actually use.

Request custom OWL consultation
OWL delivery model

ERPFlows combines product thinking, OWL engineering, and Odoo rollout work

The modules above are not isolated demos. They reflect the same approach we use for client work: identify the operational friction first, design the OWL surface carefully, then ship the surrounding Odoo implementation cleanly.

OWL UI engineering

Reusable field widgets, client actions, dashboards, and high-frequency screens that feel native to standard Odoo.

  • Custom fields and action screens
  • Stateful OWL components with clean lifecycle handling
  • Performance-minded rendering for busy teams

Odoo module delivery

From idea shaping to store-ready packaging, ERPFlows builds modules that ship cleanly and can still be maintained after launch.

  • Feature scoping and architecture
  • Manifest, assets, and Odoo Store readiness
  • Practical QA across real workflows

Implementation and rollout

We do not stop at code. Existing flows are audited, customizations are integrated, and teams receive a usable rollout plan.

  • Current-state workflow audit
  • Integration and migration planning
  • Launch support with operator enablement
From countdowns to record-age signals

Field widgets that solve urgency

ERPFlows uses OWL field components when users need live feedback in the exact view where they already work.

<field name="date_order" widget="record_age" options="{'recent_days': 0.5, 'warning_days': 2}"/>
Maps, replay, search, and refresh

Action screens for operational visibility

When the job needs more than a field widget, we build OWL actions that combine backend services with focused operator tooling.

registry.category("actions").add("erpflows_fleet_traccar.traccar_live_map", TraccarLiveMapAction);
UI signals
Records Age Indicator
Field widget
Overdue record age badge with pulse state
Advanced OWL Countdown Timer
Countdown widget updating time left inside Odoo
Fleet Traccar Connector
Fleet Traccar configuration and sync controls
What this means for clients

ERPFlows can start from a packaged module, a rough business requirement, or an existing Odoo codebase. The outcome stays the same: focused OWL interaction, maintainable Odoo code, and a delivery plan tied to actual user behavior.
From scope to go-live

A practical delivery sequence for custom Odoo and OWL work

ERPFlows is structured for companies that need more than a code patch. We connect discovery, UI implementation, backend integration, and launch support so the result survives outside a demo environment.

Step 01

Audit the workflow

Review your current Odoo models, user journey friction, and extension points before touching code.

Step 02

Prototype the OWL layer

Design the field widget, client action, or screen behavior with the same practical constraints users face daily.

Step 03

Implement and harden

Ship the module, wire backend services, validate edge cases, and keep the code maintainable for later iterations.

Step 04

Launch and extend

Handle handoff, enablement, and the next release so the customization remains useful after go-live.

What clients usually need

Module strategy

Clarify whether the fastest path is a new app, a store-ready add-on, or a surgical extension of what is already running.

OWL frontend work

Build the interaction layer users actually feel: field widgets, operator shortcuts, dashboards, and action screens.

Implementation support

Cover deployment, adoption, training, and the follow-up changes that usually appear after real users touch the release.

Engage ERPFlows

Start with an OWL and workflow audit, then decide the build path.

That keeps the recommendation grounded in your current Odoo model layer, data flow, and operator behavior instead of a vague feature wishlist.

Book discovery auditExplore OWL consulting
Insights

Odoo app growth and OWL implementation guides

Practical playbooks for teams shipping Odoo apps and custom OWL experiences.

Designing Odoo with OWL components

July 18, 2024

Designing Odoo with OWL components

A practical guide to structuring OWL components that stay fast, testable, and aligned with Odoo UX patterns.

Odoo 19 migration checklist for custom modules

September 9, 2024

Odoo 19 migration checklist for custom modules

What to audit before upgrading Odoo modules, OWL views, and integrations.

Performance tips for large Odoo databases

November 4, 2024

Performance tips for large Odoo databases

Indexing, caching, and OWL UI improvements that keep Odoo responsive at scale.

Browse all Odoo guides

Common questions

Odoo and OWL engagement FAQ

Can ERPFlows customize the three published modules for our workflow?

Yes. The published modules are a starting point, not a constraint. ERPFlows can extend their behavior, change the UX, add backend logic, or integrate them into a wider implementation plan.

Do you only work on app-store modules, or also on custom Odoo implementations?

We do both. Some clients want a store-ready module, while others need an internal customization, migration-safe extension, or a complete implementation track tied to operations.

What kind of OWL work do you handle?

ERPFlows builds OWL field widgets, client actions, dashboards, responsive operator screens, and frontend-heavy extensions where standard Odoo views are not enough.

Can you work with an existing Odoo codebase that already has custom modules?

Yes. We usually start with an audit of the current models, assets, and user flows so new OWL work fits cleanly into what is already deployed instead of fighting it.

Do you provide rollout support after the code is delivered?

Yes. ERPFlows can stay involved through testing, operator enablement, staged rollout, and the first improvement cycle after go-live.