Field service in Odoo: after the sale is where the margin lives.

Who this is actually for

Odoo Field Service is built for exactly the kind of business that dominates Bangladesh's equipment after-sales market: generator and genset dealers servicing standby power for garment factories and commercial buildings, industrial and textile machinery importers whose sales contracts include installation and ongoing maintenance, HVAC contractors maintaining commercial air conditioning across Dhaka's office towers and Chattogram's port facilities, agricultural equipment dealers supporting irrigation pumps and tillers across regional districts, and IT hardware and networking resellers running managed maintenance for corporate clients. In every one of these businesses, the equipment sale is often the smaller commercial event; the multi-year service relationship that follows it, particularly when sold as a paid Annual Maintenance Contract, is where sustained margin actually accumulates.

What these businesses tend to have in common in Bangladesh today is a genuinely capable technical team paired with an administratively primitive dispatch and record-keeping process: a service coordinator manually calling technicians to assign jobs, a WhatsApp group used as the de facto job tracking system, paper job cards that get filed (or lost) after a visit, and spare parts consumption that gets reconciled against inventory weeks after the fact, if at all. None of this is a technician skill problem. It is entirely a systems and visibility problem, and it is precisely what Odoo's Field Service app, combined with Inventory and Sales, is designed to fix.

A typical scenario I encounter: a mid-size generator and industrial engine dealer in Dhaka with 40-plus active AMC customers across garment factories, hospitals, and commercial buildings, running a service desk of two coordinators fielding calls on personal mobile phones and dispatching roughly 18 field technicians by voice call and text message. The business has good technicians and a reasonable spare parts stock, but has no reliable way to answer, on any given day, how many open service calls are outstanding, which are approaching or past their SLA response window, or which AMC contracts are due for renewal in the next month. That operational blindness is not a hypothetical inefficiency, it directly costs the business renewal revenue when a contract lapses unnoticed, and it costs customer goodwill when a critical breakdown call sits unassigned for hours because no single coordinator has visibility into the full technician roster's real-time status.

Technician dispatch across Dhaka, Chattogram, and regional coverage

A Bangladesh equipment dealer's technician pool is rarely a single undifferentiated team. A generator dealer headquartered in Tejgaon typically maintains a core Dhaka metro team, a smaller Chattogram-based team covering the port city and its surrounding industrial belt, and a thin, often subcontracted, network of regional technicians covering districts like Gazipur, Narayanganj, Bogura, or Sylhet where full-time headcount doesn't justify itself against call volume. Odoo Field Service handles this through service teams and technician skill/zone tagging: each field service request can be automatically or manually routed to the appropriate team based on the customer's district, the equipment type, and technician availability, rather than relying on a coordinator's memory of who happens to be near a given site that week.

The planning view in Field Service, which presents technician schedules as a calendar/Gantt-style board, is where the coordinator function actually changes character: instead of reactive phone calls when a breakdown call comes in, the coordinator can see every technician's committed jobs for the day and week, spot a technician who will be passing near a customer site for an unrelated call and bundle a preventive visit onto the same trip, and rebalance the following day's schedule when an emergency breakdown call comes in mid-morning. For a dealer running 15-30 field technicians across multiple cities, this scheduling visibility alone typically recovers meaningful technician-hours per week that were previously lost to inefficient routing and duplicate site visits.

Spare parts tied directly to field service work orders

The most persistent operational leak in Bangladesh after-sales businesses is the gap between spare parts leaving the warehouse (or a technician's van) and that consumption being reflected in both inventory and the customer invoice. A technician replaces a fuel injector or a capacitor on-site, notes it on a paper job card that may or may not make it back to the office that week, and by the time someone reconciles inventory, the part has been consumed for weeks with no corresponding stock movement or billing entry.

Odoo's Field Service work orders solve this by attaching an expected parts list to each job, which reserves stock either from a central spare parts warehouse or from a technician's own van/kit inventory location (modeled as its own Odoo warehouse location, a pattern that keeps each technician's carried stock visible and reconcilable). When the technician completes the job through the mobile app and confirms parts actually used, which may differ from what was expected, Odoo generates the stock move automatically and, where the part is billable under the service contract terms, creates the invoice line without a separate manual data entry step. This is the same discipline of connecting field activity to inventory movement that a preventive maintenance program depends on internally, covered for factory equipment in Odoo Preventive Maintenance Bangladesh; field service extends that same logic outward to the customer's site rather than the factory floor.

AMC contracts and renewal tracking

The Annual Maintenance Contract is the commercial backbone of Bangladesh equipment after-sales, and it is also the single most common source of quietly lost recurring revenue, because renewal follow-up is almost always a manual, memory-dependent process owned by whichever account manager happened to sell the original contract. When that account manager is busy, on leave, or has moved on, contracts lapse silently, and the dealer only discovers it when the customer calls for a breakdown visit and asks why they're suddenly being charged instead of receiving covered service.

In Odoo, AMC contracts are modeled either as recurring Sales subscriptions or as Field Service contracts linked directly to specific pieces of customer equipment, each with a defined coverage window, an included number of preventive visits per year, and a hard renewal date. The critical configuration is connecting this renewal date to automated reminders rather than leaving it to human memory: a scheduled action that fires email and SMS alerts at 60, 30, and 15 days before expiry, addressed to both the internal account manager and the customer directly, covered from the messaging infrastructure side in Odoo Email & SMS Setup Bangladesh. This single automation, in my experience implementing it for equipment dealers, is often the highest-ROI piece of the entire field service rollout, because it converts a leaking recurring revenue stream into a defended one without requiring any additional sales effort beyond the renewal call itself.

Customer-facing SLA commitments

Larger Bangladesh customers, particularly RMG factories running standby generators that cannot afford extended downtime during production hours, or commercial buildings with HVAC contracts tied to tenant comfort guarantees, increasingly negotiate explicit service level commitments into their AMC contracts: a maximum response time from call logged to technician dispatched, and a maximum resolution time from arrival to equipment back in service, often tiered by fault severity.

Severity	Typical response commitment	Typical resolution commitment
Critical (production down)	2-4 hours, Dhaka metro	Same day, or temporary workaround same day
High (degraded operation)	Next business day	Within 2-3 business days
Routine (preventive/scheduled)	Per agreed maintenance calendar	Completed within scheduled visit window

Odoo Field Service tracks these SLA clocks automatically once a work order is created from a customer call: the timestamp from ticket creation to technician assignment, and from assignment to job completion, both become reportable fields. Building a simple SLA compliance dashboard, using the same dashboard techniques covered generally in Odoo Dashboards & KPI Bangladesh, gives the dealer's management team an honest, real-time view of whether the business is actually meeting the commitments it has sold to customers, rather than discovering an SLA breach only when an angry customer escalates it. For dealers competing on service quality rather than just price, being able to show a customer their own historical SLA compliance record during a renewal negotiation is a meaningfully strong commercial argument.

The mobile app and technicians with unreliable connectivity

Field technicians in Bangladesh spend their working day inside factories, basements, and rural sites where mobile data coverage ranges from excellent (central Dhaka, Chattogram) to intermittent (industrial zones on the fringe of Gazipur or Narayanganj) to genuinely unreliable (parts of Rangpur, Bogura, Sylhet's tea garden areas, and coastal districts like Cox's Bazar). A field service system that assumes constant connectivity fails exactly the technicians who need it most.

Odoo's mobile app is designed with this reality in mind: assigned jobs, customer and equipment history, and expected spare parts data sync to the device and remain viewable and editable offline. A technician can open a job, view the equipment's service history and any relevant manuals or notes attached to the customer record, mark the job in progress, record parts consumed and time spent, and capture photos of completed work, all without an active connection. Once the phone reconnects, whether back at the depot, at the next site, or simply when a signal briefly returns, the data syncs automatically. The practical implication for rollout is to explicitly train technicians on this offline behavior during onboarding, since technicians accustomed to paper job cards sometimes distrust that offline data entry has genuinely been saved, and will default back to keeping a redundant paper note "just in case" unless shown clearly that the sync is reliable.

Reporting: knowing which contracts actually make money

A question I ask nearly every equipment dealer I meet in Bangladesh, and one that almost never has a confident answer, is: which of your AMC contracts are actually profitable once technician time, travel, and parts consumption are counted against the contract fee? Most dealers price AMC contracts using a rough rule of thumb set years ago (a percentage of original equipment value, or a flat regional rate) and never revisit whether a specific customer's actual service history justifies that price. A generator installed in a dusty brick-field environment near Bogura may need three times the technician visits and parts of an identical unit running in a climate-controlled Dhaka data center, yet both are frequently priced identically under a standardized AMC rate card.

Once field service work orders, technician time, and spare parts consumption are flowing through Odoo consistently, this becomes a solvable reporting question rather than a guess. A simple profitability report, grouping completed work order costs (technician hours at a loaded cost rate, plus parts consumed at cost) against AMC contract revenue recognized for the same customer and period, surfaces exactly which contracts are quietly subsidizing others. This is not a theoretical benefit: dealers who run this analysis for the first time after a field service rollout typically find a meaningful minority of their AMC book, often in the range of one contract in five, running at a loss once true service cost is counted, and use that data to reprice at the next renewal cycle rather than continuing to guess.

A realistic rollout sequence

• Phase 1: Equipment and contract master dataLoad every serviced customer asset into Odoo as tracked equipment records, linked to the customer and, where applicable, an active AMC contract with its coverage terms and renewal date.
• Phase 2: Dispatch and work order workflowStand up service teams by geography, train the coordinator on the planning/Gantt view, and move all new service requests through Field Service work orders instead of the WhatsApp group, running both in parallel for a transition period.
• Phase 3: Spare parts and technician stock locationsSet up van/kit locations per technician and connect work order parts consumption to stock moves and billing, starting with the highest-value or highest-turnover spare parts categories first.
• Phase 4: AMC renewal automation and SLA dashboardTurn on the 60/30/15-day renewal reminders and build the SLA compliance dashboard once enough work order history exists to make the numbers meaningful.

Frequently asked questions

What kind of Bangladesh businesses benefit most from Odoo Field Service?

Businesses that sell and service physical equipment with an ongoing after-sales relationship: generator and genset dealers, industrial and textile machinery importers, HVAC and air conditioning contractors, agricultural equipment dealers, and IT hardware and networking equipment resellers. The common thread is a customer base spread across Dhaka, Chattogram, and regional districts that needs scheduled maintenance visits, breakdown repairs, and spare parts fulfillment, often under a paid Annual Maintenance Contract (AMC) that creates a recurring revenue stream on top of the original equipment sale.

How does Odoo track AMC (Annual Maintenance Contract) renewals for Bangladesh after-sales teams?

AMC contracts are typically modeled as recurring Sales subscriptions or as Field Service contracts tied to specific customer equipment records, with a defined coverage period, number of included service visits, and renewal date. Odoo's automated activities and email/SMS integration can trigger renewal reminders 60, 30, and 15 days before contract expiry to both the account manager and the customer, which is critical in Bangladesh where AMC renewal is often a manual follow-up process prone to being missed, resulting in lost recurring revenue and customers quietly lapsing into unprotected equipment ownership.

Can Odoo Field Service work for technicians in areas with unreliable internet outside Dhaka?

Yes, with the right configuration. The Odoo mobile app caches assigned field service tasks, customer and equipment history, and spare parts data locally on the technician's phone, allowing the technician to view job details, mark tasks in progress, and record parts used even with an intermittent or temporarily absent connection. Data syncs back to the server once connectivity resumes. This is particularly relevant for technicians covering districts like Rangpur, Bogura, Sylhet, or Cox's Bazar where mobile data coverage can be inconsistent between industrial sites.

How does spare parts inventory integrate with field service work orders in Odoo?

Each field service work order can include a list of expected spare parts, which reserves stock from a dedicated spare parts warehouse or from the technician's own van/kit inventory location. When the technician completes the job and records parts actually consumed, Odoo automatically creates the stock move and, if configured, generates the customer invoice line for billable parts. This closes the loop between technician activity, inventory depletion, and revenue capture, which is commonly a manual and error-prone reconciliation process in Bangladesh after-sales operations still running on paper job cards.