Technician Movements

Technician movements record the daily flow of spare parts to and from field technicians, providing visibility into what parts each technician has and linking them to specific work orders.

Overview

Every time a technician takes parts for a repair or returns unused parts, a movement is recorded. This ensures the inventory system stays accurate and parts can be tracked through the repair lifecycle.

Load Parts

Record parts given to technicians

Unload Returns

Track parts returned after jobs

Order Tracking

Link movements to work orders

Movement Structure

interface MovimientoTecnico {
  // Movement identifiers
  id_movimientos_tecnicos: string;
  id_localizacion: string;
  id_repuesto: string;
  id_usuario_responsable: string;   // Who recorded it
  id_tecnico_asignado: string;      // Technician receiving/returning
  
  // Movement details
  concepto: ConceptoMovimiento;
  tipo: TipoMovimiento;
  cantidad: number;
  fecha: string;
  numero_orden: number;
  descargada: boolean;              // Inventory already updated?
  
  // Related data (from joins)
  referencia: string;
  nombre_repuesto: string;
  url_imagen: string;
  nombre_localizacion: string;
  nombre_responsable: string;
  nombre_tecnico: string;
}

Movement Types

Load Movement (Salida)

When a technician takes parts:

type TipoMovimiento = 'salida';
type ConceptoMovimiento = 
  | 'salida'        // General checkout
  | 'garantia'      // Warranty replacement
  | 'prestamo'      // Loan to technician
  | 'cotizacion';   // For customer quote

Select Technician

Choose the technician who will receive the parts

Select Spare Part

Choose the part from inventory

Enter Quantity

Specify how many units

Link Work Order

Enter the order number this is for

Set Concept

Specify the reason (repair, warranty, etc.)

Save Movement

System records but doesn’t update inventory yet

Load movements are initially saved with descargada = false. This means the parts are “allocated” to the technician but haven’t been deducted from inventory yet. This gives flexibility to cancel if the technician doesn’t actually take the parts.

Discharge/Unload

To actually deduct from inventory:

Find Load Movement

Locate the movement to discharge

Confirm Quantity

Verify the technician actually took those parts

Set Discharged

Mark descargada = true

Update Inventory

System automatically deducts quantity from location stock

Log Audit Trail

Movement appears in inventory history

Return Movement (Ingreso)

When a technician returns unused parts:

type TipoMovimiento = 'ingreso';
type ConceptoMovimiento = 'devolucion';

Select Technician

Choose who is returning parts

Select Spare Part

Identify what’s being returned

Enter Quantity

Specify return quantity

Reference Original Order

Link to the work order

Save Return

System automatically adds quantity back to inventory

Returns should match previous load movements. Verify the technician actually had these parts before accepting returns to prevent inventory inflation.

Sale Movement (Venta)

When parts are sold directly:

type TipoMovimiento = 'venta';
type ConceptoMovimiento = 'venta';

Sales immediately deduct from inventory and don’t require a discharge step.

Movement Concepts

The concepto field provides detailed context:

Concept	Description	Typical Type
`salida`	General technician checkout	salida
`ingreso`	Parts arrival from supplier	ingreso
`venta`	Direct sale to customer	venta
`garantia`	Warranty replacement part	salida
`prestamo`	Loan between technicians	salida
`cotizacion`	Parts for customer estimate	salida
`devolucion`	Return of unused parts	ingreso

Tracking Technician Inventory

You can view what parts each technician currently has:

Active Loads: Movements with descargada = true and type salida
Subtract Returns: Movements with type ingreso (returns)
Net Quantity: Total parts currently with technician

Example: Technician Part Balance

Technician: Juan PérezLoads (Salidas descargadas):

2023-03-01: +5 brake pads (Order #1234)
2023-03-02: +3 cables (Order #1240)

Returns (Ingresos):

2023-03-01: -2 brake pads (Order #1234 - unused)

Current inventory:

Brake pads: 3
Cables: 3

Work Order Association

Every movement links to a work order via numero_orden. This enables:

Cost Tracking: See all parts used on a specific job
Part History: Track which technician used which parts
Billing: Generate accurate invoices including parts
Warranty Claims: Identify parts used if a repair fails

View Order Details

Look up order by number

See Part Usage

View all movements linked to that order

Calculate Costs

Sum quantities and part costs

Verify Work

Confirm appropriate parts were used

Filtering and Search

Find movements with multiple filters:

interface MovementFilters {
  page: number;
  pageSize: number;
  technicianId?: string;     // Specific technician
  startDate?: string;        // Date range start
  endDate?: string;          // Date range end
  orderNumber?: string;      // Specific order
  concept?: string;          // Movement concept
  downloaded?: string;       // 'true', 'false', or 'all'
}

Common Queries

Technician's Open Loads

Filter by technician + descargada = false

Order Parts List

Filter by order number

Pending Discharges

Filter all movements with descargada = false

Today's Activity

Filter by today’s date

View complete information about any movement:

interface MovementDetailsModalProps {
  movement: MovimientoTecnico | null;
  open: boolean;
  onOpenChange: (open: boolean) => void;
}

Displays:

Full part details with image
Technician and responsible user
Order number and date
Concept and type
Discharge status
Location information
Timestamps

Editing Movements

Correct mistakes before discharge:

interface MovimientoEdicion {
  id_movimientos_tecnicos: string;
  id_repuesto: string;
  repuesto_referencia: string;
  repuesto_nombre: string;
  id_tecnico_asignado: string;
  tipo: TipoMovimiento;
  concepto: ConceptoMovimiento;
  cantidad: number;
  numero_orden: number;
}

Only undischarged movements (descargada = false) can be edited. Once a movement has updated inventory, it cannot be modified - create a correcting movement instead.

Inventory Impact

Load/Salida (Discharge)

Inventory -= cantidad

Return/Ingreso

Inventory += cantidad

Sale/Venta

Inventory -= cantidad

All changes are logged in logs_inventario with:

Movement ID as reference
Technician name
Order number
Full traceability

Permissions

Action	Required Permission
Create movement	`create_movement`
Edit movement	`edit_movement`
Discharge movement	`discharge_movement`
Delete movement	`delete_movement`
View movements	`view_movements`
View all technicians	`view_all_technicians`

Best Practices

Load Before the Job

Create load movements before technician leaves, but discharge only when they actually take the parts

Accurate Order Numbers

Always enter the correct work order number for traceability

Process Returns Promptly

Record returns the same day to keep inventory accurate

Discharge Regularly

Don’t let undischarged loads accumulate - process them daily

Verify Quantities

Double-check quantities before discharging to prevent inventory errors

Common Workflows

Daily Technician Checkout

Morning routine:

Supervisor reviews the day’s work orders
Creates load movements for needed parts
Technicians pick up parts from warehouse
Supervisor verifies and discharges movements
Inventory is updated, technicians leave for jobs

End of Day Returns

Evening routine:

Technicians return to shop
Supervisor collects unused parts
Creates return movements for each technician
Inventory automatically updated
Parts available for next day

Warranty Replacement

When a part fails:

Create load movement with concepto = 'garantia'
Link to warranty claim ID in notes
Technician installs replacement
Discharge the movement
Failed part returned separately via warranty flow

Reporting

Generate insights from movement data:

Technician Usage: Who uses which parts most frequently
Part Velocity: How quickly parts move through technicians
Order Costs: Total part costs per work order
Return Rates: Which parts get returned most often
Pending Discharges: Outstanding movements needing action

Inventory Management - View available stock
Warranty Management - Process failed parts
Request Workflow - Transfer between locations

Get Started

Core Features

Architecture

Guides

Deployment

Technician Movements

Overview

Load Parts

Unload Returns

Order Tracking

Movement Structure

Movement Types

Load Movement (Salida)

Discharge/Unload

Return Movement (Ingreso)

Sale Movement (Venta)

Movement Concepts

Tracking Technician Inventory

Work Order Association

Filtering and Search

Common Queries

Technician's Open Loads

Order Parts List

Pending Discharges

Today's Activity

Editing Movements

Inventory Impact

Load/Salida (Discharge)

Return/Ingreso

Sale/Venta

Permissions

Best Practices

Common Workflows

Reporting

Build docs developers (and LLMs) love

Get Started

Core Features

Architecture

Guides

Deployment

​Overview

Load Parts

Unload Returns

Order Tracking

​Movement Structure

​Movement Types

​Load Movement (Salida)

​Discharge/Unload

​Return Movement (Ingreso)

​Sale Movement (Venta)

​Movement Concepts

​Tracking Technician Inventory

​Work Order Association

​Filtering and Search

​Common Queries

Technician's Open Loads

Order Parts List

Pending Discharges

Today's Activity

​Movement Details Modal

​Editing Movements

​Inventory Impact

​Load/Salida (Discharge)

​Return/Ingreso

​Sale/Venta

​Permissions

​Best Practices

​Common Workflows

​Reporting

​Related Features

Build docs developers (and LLMs) love

Overview

Movement Structure

Movement Types

Load Movement (Salida)

Discharge/Unload

Return Movement (Ingreso)

Sale Movement (Venta)

Movement Concepts

Tracking Technician Inventory

Work Order Association

Filtering and Search

Common Queries

Movement Details Modal

Editing Movements

Inventory Impact

Load/Salida (Discharge)

Return/Ingreso

Sale/Venta

Permissions

Best Practices

Common Workflows

Reporting

Related Features