Field Service Tickets & Rate Cards
Field service tickets: site + equipment header, service-run metrics, rate-card line items (rental / field service / processing / personnel / mob / consumables / standby / cancellation), multi-currency, discount + tax, sign-off. A won opportunity becomes a service job; many tickets roll up under one tender. System-of-record only â billing is handed over to your invoicing entity / system, not invoiced here.
ARMKU LLC · Odoo 17.0 · version 17.0.1.0.0 · OPL-1
A lightweight system of record for field service jobs in Odoo 17: site + equipment header, service-run metrics, rate-card charges, sign-off and a clean PDF â feeding your billing entity or ERP, without invoicing here.
What it does
Adds an auto-numbered Service Ticket (ST00001, ST00002...) that captures a complete field job: who, where, with what equipment, what was done (service-run metrics) and what it costs (rate-card charge lines with discount, tax and multi-currency totals). Tickets link back to the CRM tender, a delivery project and the source quotation, and follow a simple lifecycle ending in a hand-over to billing.
Features
- Job header: customer, tender/opportunity, delivery project + field task, source quotation, site name, country, equipment/unit, site contractor, contract / PO / budget-code / client references, job dates, service line.
- Service-run metrics: interval from/to (metres or feet), length processed and recovered with auto Recovery %, number of service runs, tool/head type + serial, equipment days, personnel days.
- Rate-card charges by category (equipment rental, field service, processing/analysis, personnel, mobilisation/demob, consumables, standby, cancellation, other), free unit labels (Per Day, Per Run, Lump Sum...), optional personnel detail (name, arrival/departure), quantity x rate, ticket-level discount % and tax %, multi-currency.
- Lifecycle: Draft -> In Progress -> Signed -> Handover to Billing (+ Cancel / Reset), chatter + activity tracking, customer and service-company representative sign-off.
- PDF report: print-ready service ticket with header, run summary, charge table, totals and signature blocks.
- CRM integration: service-ticket counter + ticketed revenue on the opportunity, one-click delivery-project creation, billing-region routing (auto-suggested from the sales team name).
- Nothing is invoiced in this module â it is the operational system of record that feeds your invoicing entity/system.
Requirements
- Odoo 17 Community or Enterprise.
- Standard modules only:
crm,sale,uom,project.
Installation
- Copy the
field_service_ticketfolder into your addons path.
- Update the apps list and install Field Service Tickets & Rate Cards.
Configuration
- Menu: CRM > Service Tickets. Salespeople can create/edit; deleting is reserved to Sales managers.
- Ticket numbering: Settings > Technical > Sequences > "Field Service Ticket" (prefix ST, 5 digits) â adjust to taste.
- Optional: name your sales teams by region (e.g. "Middle East") so the billing region auto-fills from the opportunity.
Support
info@armku.us â https://armku.us
Tickets de Servicio de Campo y Tarifarios
Un sistema de registro ligero para trabajos de servicio de campo en Odoo 17: encabezado de sitio + equipo, metricas de corrida de servicio, cargos por tarifario, firma y un PDF limpio â alimentando a su entidad de facturacion o ERP, sin facturar aqui.
Que hace
Agrega un Ticket de Servicio auto-numerado (ST00001, ST00002...) que captura un trabajo de campo completo: quien, donde, con que equipo, que se hizo (metricas de corrida) y cuanto cuesta (lineas de cargo por tarifario con descuento, impuesto y totales multi-moneda). Los tickets se vinculan a la licitacion CRM, a un proyecto de entrega y a la cotizacion origen, y siguen un ciclo de vida simple que termina en la entrega a facturacion.
Funcionalidades
- Encabezado: cliente, licitacion/oportunidad, proyecto de entrega + tarea de campo, cotizacion origen, nombre del sitio, pais, equipo/unidad, contratista del sitio, referencias de contrato / OC / codigo presupuestal / cliente, fechas, linea de servicio.
- Metricas de corrida: intervalo desde/hasta (metros o pies), longitud procesada y recuperada con % de Recuperacion automatico, numero de corridas, tipo + serie de herramienta/cabezal, dias de equipo, dias de personal.
- Cargos por tarifario por categoria (renta de equipo, servicio de campo, procesamiento/analisis, personal, movilizacion/desmovilizacion, consumibles, standby, cancelacion, otros), unidades libres (Por Dia, Por Corrida, Suma Global...), detalle opcional de personal, cantidad x tarifa, % de descuento e impuesto a nivel ticket, multi-moneda.
- Ciclo de vida: Borrador -> En Progreso -> Firmado -> Entrega a Facturacion (+ Cancelar / Reiniciar), chatter + actividades, firma del representante del cliente y de la empresa de servicio.
- Reporte PDF: ticket listo para imprimir con encabezado, resumen de corrida, tabla de cargos, totales y bloques de firma.
- Integracion CRM: contador de tickets + ingreso facturado en la oportunidad, creacion de proyecto de entrega con un clic, enrutamiento de region de facturacion (auto-sugerido desde el nombre del equipo de ventas).
- Nada se factura en este modulo â es el sistema de registro operativo que alimenta a su entidad/sistema de facturacion.
Requisitos
- Odoo 17 Community o Enterprise.
- Solo modulos estandar:
crm,sale,uom,project.
Instalacion
- Copie la carpeta
field_service_ticketa su ruta de addons.
- Actualice la lista de aplicaciones e instale Field Service Tickets & Rate Cards.
Configuracion
- Menu: CRM > Service Tickets. Los vendedores pueden crear/editar; eliminar queda reservado a gerentes de Ventas.
- Numeracion: Ajustes > Tecnico > Secuencias > "Field Service Ticket" (prefijo ST, 5 digitos) â ajustable.
- Opcional: nombre sus equipos de ventas por region (p. ej. "Middle East") para que la region de facturacion se auto-complete desde la oportunidad.
Soporte
info@armku.us â https://armku.us
Support. Bugs and configuration questions are answered by the author. Write to rkong@armku.us quoting your order number.
© 2026 ARMKU LLC · armku.us
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Project (project) • Calendar (calendar) • Contacts (contacts) • Discuss (mail) • Invoicing (account) |
| Lines of code | 569 |
| Technical Name |
field_service_ticket |
| License | OPL-1 |
| Website | https://armku.us |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module