Files
Odoo-Modules/fusion_repairs/models/repair_emergency_charge.py
gsinghpal ebbadb3002 feat(fusion_repairs): Bundle 8 - rush service + emergency pricing + parts-ordered workflow
The grumpy-old-customer-with-broken-stairlift scenario. Four real workflows
the office faces every week, with comms baked in so the client never has to
call back asking for status.

NEW MODELS
- fusion.repair.emergency.charge (rate card)
  Per (category, tier) rate with per_tech_multiplier; 5 tiers
  (same_day / next_day / after_hours / weekend / holiday). Each category
  can have its own rates - bed motors need 2 techs, stairlift is single.
  Seeded with realistic Westin rates: stairlift same-day $250, weekend
  $450; porch lift same-day $300; bed same-day $175 with 0.6 multiplier
  (2-tech jobs frequent); powerchair same-day $200.

- fusion.repair.part.order (procurement-facing record)
  One per distinct part the tech needs from the manufacturer. Carries
  description + OEM # + manufacturer + quantity + photos + notes.
  4-state lifecycle: draft -> ordered -> received -> fitted (or
  cancelled). On state transitions:
    draft -> ordered:  email client "ordered, expected by X"
    ordered -> received: email client "arrived, scheduling return visit"
                         + auto-create follow-up dispatch task when ALL
                         outstanding parts on the repair have arrived.

REPAIR.ORDER EXTENSIONS
- Rush fields: x_fc_rush_requested, x_fc_rush_tier,
  x_fc_rush_techs_required, x_fc_rush_surcharge (computed via rate card),
  x_fc_rush_acknowledged_at + x_fc_rush_acknowledged_by_id (audit trail
  proving CS got verbal OK before charging).
- Parts-awaiting fields: x_fc_parts_awaiting + x_fc_parts_eta_date +
  x_fc_part_order_ids One2many + x_fc_part_order_count.

- New methods:
  * action_acknowledge_rush() - one-click "client agreed" with audit.
  * action_squeeze_into_today() - picks the lightest-loaded skilled tech,
    finds their first free 1-hour slot between 9am-6pm, schedules the
    task in it, sends:
      1) live bus.bus push to the tech (sticky notification in their
         web client - so they see it MID-SHIFT)
      2) rush-alert email (force_send=True - this can't wait in the queue)
      3) chatter post on the tech task itself
    Validates against fusion_tasks' time-conflict rule by passing
    force_schedule via context (intake.service honours it).
  * action_view_part_orders() - smart button.

WIZARD EXTENSIONS
- repair.intake.wizard:
  New rush_requested + rush_tier + rush_techs_required + rush_acknowledged
  controls. Live rush_surcharge_preview compute shows CS the price in
  real-time as they change category / tier / tech count. Yellow alert
  reminds CS to read the price to the client BEFORE submitting.

- repair.visit.report.wizard:
  New outcome radio: completed / parts_needed / rescheduled.
  When outcome=parts_needed, needs_parts_line_ids One2many appears for
  the tech to capture each part (description, OEM, manufacturer, qty,
  lead days, notes, photos). On submit each line creates a
  fusion.repair.part.order, the repair flips to x_fc_parts_awaiting=True
  with an ETA, and the client gets the "we found the problem, here's the
  plan" email immediately.

INTAKE SERVICE
- _create_dispatch_task now honours force_schedule (date + time_start +
  time_end) via context so squeeze + auto-redispatch don't crash on
  fusion_tasks' time-window validator.
- _create_single_repair carries rush_requested/tier/techs through to
  the new repair fields.

MAIL TEMPLATES (4 new)
- email_template_rush_tech_alert: red 4px accent, address + phone + the
  $surcharge - what the tech needs to know mid-shift.
- email_template_repair_awaiting_parts: amber accent, "we found the
  problem, parts ordered, return visit ~ETA, no action needed".
- email_template_parts_ordered: blue, per-part confirmation.
- email_template_parts_received: green, "arrived, office will call to
  confirm visit".

UI / NAVIGATION
- Backend wizard: rush controls + live surcharge preview + verbal-OK alert.
- repair.order form: new Rush / Parts notebook tab with all the fields
  + linked part orders list. Two new header buttons (Squeeze into
  Today / Client Agreed to Rush Price). Two new search filters
  (Rush, Awaiting Parts).
- Part Order form: statusbar with the 4 transitions + Cancel; notes +
  photos notebook tabs; full chatter for audit.
- Menus: 'Parts to Order' under root; 'Emergency Surcharges' under
  Configuration.

SECURITY
- 8 new ACL entries (emergency_charge user/manager; part_order
  user/dispatcher/manager/technician; visit_report partline for office
  and field tech). Office sees parts but only managers can edit
  emergency rates.

Verified end-to-end on local westin-v19 - all 4 scenarios green:
  S1 Same-day rush stairlift -> $250 surcharge, ack stamped, squeeze
     assigned garry@ at first free 1h slot today, alert email queued,
     chatter posted.
  S2 Next-day priority bed -> $0 surcharge (no rate seeded for bed
     next_day - office can configure), 4 emails queued (client + office).
  S3 2-tech weekend stairlift -> $675 (450 base + 0.5x base for 2nd tech).
  S4 Parts-needed visit-report -> 2 PART-#### records created, repair
     awaiting_parts=True, ETA=2026-06-06, office activity scheduled,
     client email sent. Marking part ordered -> client mail. Marking
     all parts received -> auto-dispatch follow-up + client mail.

Bumped to 19.0.1.9.1.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-21 01:28:13 -04:00

108 lines
3.7 KiB
Python

# -*- coding: utf-8 -*-
# Copyright 2024-2026 Nexa Systems Inc.
# License OPL-1 (Odoo Proprietary License v1.0)
"""Emergency / rush service rate card.
The pissed-off-grumpy-client scenario: stairlift dead at 5 PM Friday, needs
service yesterday. Office bumps them into today's route OR books them
priority for tomorrow OR (if after-hours / weekend) charges an emergency
surcharge. Sometimes more than one technician is needed (e.g. lifting an
adjustable bed back onto its frame) - per_tech_multiplier handles that.
Pricing logic on repair.order:
surcharge = base_amount + base_amount * per_tech_multiplier *
(techs_required - 1)
Example: same-day stairlift, 1 tech, base $250, multiplier 0.5
-> $250 surcharge
Example: same-day stairlift, 2 techs (one to hold, one to wrench)
-> $250 + $250 * 0.5 * 1 = $375 surcharge
"""
from odoo import _, api, fields, models
class FusionRepairEmergencyCharge(models.Model):
_name = 'fusion.repair.emergency.charge'
_description = 'Rush / Emergency Service Surcharge Rate'
_order = 'category_id, tier'
name = fields.Char(
compute='_compute_name',
store=True,
)
category_id = fields.Many2one(
'fusion.repair.product.category',
string='Equipment Category',
required=True,
ondelete='cascade',
index=True,
)
tier = fields.Selection(
[
('same_day', 'Same Day (during business hours)'),
('next_day', 'Next Day Priority'),
('after_hours', 'After Hours (5pm-9pm weekday)'),
('weekend', 'Weekend'),
('holiday', 'Statutory Holiday'),
],
string='Tier',
required=True,
)
base_amount = fields.Monetary(
string='Base Surcharge',
currency_field='currency_id',
required=True,
default=0.0,
help='Surcharge for ONE technician on top of the normal labour / parts cost.',
)
per_tech_multiplier = fields.Float(
string='Additional Tech Multiplier',
default=0.5,
help='Each additional technician adds base_amount * this multiplier '
'to the surcharge. Default 0.5 means tech #2 costs half the base.',
)
currency_id = fields.Many2one(
'res.currency',
default=lambda self: self.env.company.currency_id,
)
company_id = fields.Many2one(
'res.company',
default=lambda self: self.env.company,
)
active = fields.Boolean(default=True)
description = fields.Text(
help='Internal note - shown to CS when they pick this tier in the wizard.',
)
_cat_tier_unique = models.Constraint(
'unique(category_id, tier, company_id)',
'Only one emergency-charge row per (category, tier, company).',
)
@api.depends('category_id', 'tier', 'base_amount')
def _compute_name(self):
for r in self:
tier_label = dict(self._fields['tier'].selection).get(r.tier) or '?'
cat = r.category_id.name or '?'
r.name = f'{cat} - {tier_label} (${r.base_amount:.0f})'
@api.model
def calculate(self, category, tier, techs_required=1):
"""Return the surcharge for the given category + tier + tech count,
or 0.0 if no rate is configured."""
if not category or not tier or techs_required < 1:
return 0.0
rate = self.sudo().search([
('category_id', '=', category.id),
('tier', '=', tier),
('active', '=', True),
('company_id', 'in', self.env.companies.ids),
], limit=1)
if not rate:
return 0.0
extra = max(techs_required - 1, 0)
return rate.base_amount + (rate.base_amount * rate.per_tech_multiplier * extra)