Warehouse scanning
Receiving, putaway, picking, packing, and counts with barcode validation.
Odoo's web interface is built for desks. Warehouse pickers, drivers, and technicians need big buttons, scanners, and offline mode. We build apps for exactly that.
Three taps instead of twelve, a scanner instead of a keyboard, and offline as standard.
Receiving, putaway, picking, packing, and counts with barcode validation.
Route lists, signatures, photos, and failed-delivery reasons.
Job details, checklists, parts used, and timesheets.
Catalog, stock availability, and quotes for reps at customer sites.
Odoo works in a mobile browser, and for occasional use that is often enough. But people who work on their feet all day, such as warehouse staff, technicians, drivers, and sales reps, need fewer taps, bigger buttons, barcode scanning, and the ability to keep working without a signal.
A purpose-built companion app focuses on the few tasks those users do repeatedly and talks to Odoo through its API. Odoo remains the system of record for stock, orders, and invoices; the app is a faster, simpler front door for specific jobs.
We design these apps around the real workflow, test them with the people who will use them, and handle the hard parts of syncing data with Odoo reliably.
| App | Users | Odoo data |
|---|---|---|
| Warehouse scanner | Pickers and receivers | Transfers, lots, locations |
| Field service | Technicians | Tasks, timesheets, parts, signatures |
| Sales on the road | Sales reps | Customers, products, prices, orders |
| Delivery and proof of delivery | Drivers | Deliveries, routes, photos, signatures |
| Inspections and audits | Quality and safety staff | Checklists, findings, photos |
A dedicated integration user with only the permissions the app needs.
Queued changes, retries, and conflict rules agreed with the business.
Per-user authentication tied to Odoo users and roles.
Changes from the app appear in Odoo's usual screens and chatter.
Step 01
Shadow users and define the core tasks.
Step 02
Agree endpoints, data, and sync rules with Odoo.
Step 03
App screens, offline storage, and integration.
Step 04
A small group uses it in real work.
Delivered
Training, wider release, and support.
The first pitfall is rebuilding all of Odoo on a phone. Companion apps succeed by doing a few tasks extremely well, leaving everything else in Odoo.
The second is underestimating sync. Two people updating the same record, or a phone offline for a day, needs agreed rules rather than luck.
The third is ignoring Odoo upgrades. The integration is built on stable APIs and tested against new Odoo versions before they go live.
| Measure | Why it matters |
|---|---|
| Task time | Speed of the core job compared with before |
| Sync failures | Problems moving data to Odoo |
| Adoption | Share of users on the app daily |
| Data errors | Mistakes the app prevents, such as wrong items picked |
Consider a distributor whose drivers phone the office to confirm deliveries. A driver app lists the day's deliveries from Odoo, guides each stop, captures a photo and signature, and marks the delivery done.
The update appears in Odoo immediately, or as soon as the phone has signal, so customer service can answer “where is my order?” without making a call.
Success is field staff who prefer the app to paper or phone calls, with Odoo updated in real time and fewer errors to fix later.
| Need | Odoo side |
|---|---|
| Read products, prices, stock | Standard models via the external API |
| Create orders and deliveries | Standard models with validation |
| Complex actions | Custom endpoints in a small Odoo module |
| Attachments and signatures | Attachments linked to records |
| Notifications to the app | Webhooks or polling for changes |
Myth: A companion app duplicates Odoo.
Reality: It reuses Odoo's data and rules, adding a faster interface for specific tasks. Odoo stays the system of record.
Myth: Offline use isn't possible with Odoo.
Reality: The app stores what users need locally and syncs with Odoo when online.
Myth: Field staff won't use apps.
Reality: They resist slow, complicated apps. Simple flows designed with them get adopted.
The app talks to Odoo through a thin, documented API layer, so Odoo upgrades and app releases can happen independently. Integration tests run against a staging Odoo database before every release.
Mobile apps talk to Odoo through an API layer. Odoo's external API exposes models over XML-RPC, with API keys usable in place of passwords, and on Odoo Online data access through it requires a Custom planSource [1]. We often add a thin backend between the app and Odoo to shape data for mobile, enforce permissions, and keep credentials off devices.
Mobile connections drop mid-request constantly, so every write carries a unique key and the server returns the original result for repeats, the idempotency pattern used by mature APIsSource [2]. A delivery confirmed twice is still one delivery.
Offline-first sync
Offline-first mobile architecture: local databases, operation queues, conflict resolution, retries, and clear sync status for users.
IndustriesFreight & logistics
Odoo for logistics: warehouse management with barcode scanning, fleet tracking, carrier integrations, and real-time shipment status.
OdooOdoo integrations
Connect Odoo to Shopify, Stripe, banks, 3PLs, and legacy systems with signed webhooks, idempotent sync, retries, and reconciliation.
Next step
Thirty minutes with an engineer, no slide deck required. You'll leave with a clearer picture, whether or not we work together.