Transformations - EnvaSistema

Overview

Transformations in EnvaSistema allow you to reverse the packaging process by disassembling finished product (PT) packages back into their component pieces. This operation is essential for inventory flexibility, allowing you to break down packaged goods when individual pieces are needed.

Transformations are currently one-directional: Desarmar Paquetes (Disassemble Packages). The reverse operation, assembling pieces into packages, is handled through Salidas → Armar Paquetes.

Desarmar Paquetes

Purpose

The Desarmar Paquetes (Disassemble Packages) operation allows you to:

Break down finished product packages into individual pieces
Deactivate the PT package QR code in the system
Automatically return component pieces to the parts inventory
Reallocate inventory from finished goods to raw materials or components

Disassembling a package permanently deactivates the PT QR code. The package identity is lost, though the pieces are preserved in inventory.

Use Cases

Order Cancellations

Customer cancels order after package assembly - break down to free up pieces

Inventory Reallocation

Need individual pieces urgently and packaged units are available

Error Correction

Package was assembled incorrectly and needs to be dismantled

Demand Changes

Market demand shifts from packages to individual piece sales

Workflow

Navigate to Transformations

From the main menu, tap Transformaciones to go directly to the Desarmar Paquetes screen.

Like Movimientos, Transformaciones navigates directly to a single operation screen without a sub-menu.

Review Operation Instructions

Read the “¿Qué hace esta operación?” (What does this operation do?) card which explains:

Step 1: Scan the QR code of the PT package to disassemble
Step 2: The system will deactivate the PT code
Step 3: Component pieces will be automatically returned to stock

This card includes an inventory icon and color-coded step indicators.

Scan Package to Disassemble

Press the lateral button to scan the QR code of the finished product package. The info banner states:“Escanee el código QR del PT a desarmar con el botón lateral del terminal”The scanning interface shows:

Standard scan area with QR icon
Counter labeled “PT a desarmar” (PT to disassemble)
Real-time feedback on each scan

Review Package Selection

Verify the scanned package count in the counter badge. Ensure only the intended packages were scanned.

Each scan represents a complete package that will be disassembled. Double-check before proceeding.

Execute Disassembly

Tap the “Ejecutar Desarmado” button (with Build/wrench icon) to perform the transformation.The system will:

Deactivate the PT package QR code
Identify all component pieces in the package
Automatically return those pieces to inventory
Update stock levels for individual pieces

Verify Transformation

After completion:

The PT package code is no longer valid
Component pieces are available in the parts inventory
Original package structure is recorded in history

Screen Layout

The Desarmar Paquetes screen (DesarmarPaquetesScreen.kt:23-113) features a distinctive design with educational elements.

Header Section

Title: “Desarmar Paquetes”
Subtitle: “TRANSFORMACIONES”
Color: Dark grey (Color(0xFF455A64)) instead of standard blue

Instructional Card

A prominent white card appears at the top with the heading: “¿Qué hace esta operación?” (What does this operation do?)

Card Header
Explanation Text
Process Steps

The header includes:

Dark grey rounded square icon background
White inventory/box icon (Icons.Default.Inventory2)
40dp icon container
Bold title: “¿Qué hace esta operación?”
Explanatory subtitle in gray

Description reads:“Escanee el Producto Terminado (PT) para dar de baja su código y reingresar las piezas que lo componen al inventario de partes.”(Scan the Finished Product (PT) to deactivate its code and return the component pieces to the parts inventory.)

12sp font size
Gray color (#757575)
16sp line height for readability

Step Item Component

Step Item Implementation

Each step uses a custom StepItem composable (DesarmarPaquetesScreen.kt:93-107):

@Composable
fun StepItem(number: String, text: String, isLast: Boolean = false) {
    Row(verticalAlignment = Alignment.CenterVertically) {
        Surface(
            color = if (number == "3") Color(0xFF4CAF50) else Color(0xFF0061A6),
            shape = CircleShape,
            modifier = Modifier.size(20.dp)
        ) {
            Box(contentAlignment = Alignment.Center) {
                Text(text = number, color = Color.White, fontSize = 11.sp, fontWeight = FontWeight.Bold)
            }
        }
        Spacer(modifier = Modifier.width(12.dp))
        Text(text = text, color = Color(0xFF757575), fontSize = 12.sp)
    }
}

Step 3 uses green (#4CAF50) to indicate successful completion, while steps 1-2 use blue.

Scanning Interface

Below the instructional card:

Info Banner: Light blue background (Color(0xFFE1F5FE)) with standard scanning instruction
Scan Area: Standard QR code scanning interface
Counter Label: “PT a desarmar” (PT to disassemble)
Empty State: “No hay códigos escaneados” when count is zero

Action Button

“Ejecutar Desarmado” (Execute Disassembly) button features:

Build/wrench icon (Icons.Default.Build)
Dark grey color (Color(0xFF455A64)) matching the header
56dp height with 16dp rounded corners
Disabled (gray) when no items scanned
Enabled (dark grey) when ready

Visual Design

Color Scheme

Unlike other operations that use blue, Transformations uses a distinctive dark grey theme:

Element	Color	Hex Code	Purpose
Primary Color	Dark Grey	`#455A64`	Headers and buttons
Step 1-2 Badges	Blue	`#0061A6`	Process steps
Step 3 Badge	Green	`#4CAF50`	Completion step
Info Background	Light Blue	`#E1F5FE`	Info banner
Text Primary	Dark Grey	`#455A64`	Titles
Text Secondary	Medium Grey	`#757575`	Descriptions

The grey color scheme visually distinguishes Transformations from Inbound (blue) and Outbound (blue/red) operations.

Icon Strategy

Inventory2 Icon: Represents package/inventory concept in the instructional card
Build Icon: Wrench/construction icon suggests assembly/disassembly work
QrCodeScanner Icon: Standard scanning interface icon
Numbered Badges: Custom circular badges with white numbers

What Happens During Disassembly

Database Operations

Package Lookup

System retrieves the PT package record using the scanned QR code

Component Identification

System queries which pieces comprise the package based on assembly history

PT Deactivation

The package QR code is marked as inactive/deactivated in the database

Piece Reactivation

Each component piece’s individual QR code is reactivated

Inventory Updates

Finished goods inventory decreases by 1 package
Parts inventory increases by the number of component pieces
Location tracking updates to reflect piece availability

Transaction Logging

The transformation is recorded in the transaction history for audit purposes

Data Preservation

Historical Records

While the package is disassembled, EnvaSistema maintains:

Assembly History: Original record of when/how the package was created
Component List: Which specific pieces were in the package
Disassembly Transaction: When and why the package was broken down
User Activity: Who performed the transformation

This historical data supports:

Audit trails for inventory management
Analysis of packaging/disassembly patterns
Traceability for quality control
Operational reporting

Best Practices

Before Disassembling

Verification Steps:

Confirm the package actually needs to be disassembled
Check if pieces are genuinely needed or if alternatives exist
Verify the package is physically accessible
Ensure you have authorization to perform the transformation

Documentation:

Note the reason for disassembly (order cancellation, error, etc.)
Record any external reference numbers if required
Communicate with relevant departments (sales, production, etc.)

During the Operation

Scanning:

Read the instructional card carefully if unfamiliar with the process
Scan only the PT packages you intend to disassemble
Verify the counter shows the correct number
Double-check package codes before confirming

Physical Handling:

Have a designated area for disassembled pieces
Keep component pieces organized during disassembly
Ensure QR codes on individual pieces are still readable
Tag or label pieces if they’ll be stored separately

After Disassembly

Inventory Management:

Verify pieces appear in the parts inventory
Check that piece counts are correct
Update any external inventory tracking systems
Ensure pieces are stored in the correct location

Communication:

Notify relevant teams that pieces are available
Update any pending orders that need these pieces
Document the transformation for shift handoff
File any required paperwork or reports

Error Prevention

Common Mistakes:

Scanning the wrong package code
Disassembling packages that are scheduled for shipment
Not verifying piece availability needs before disassembling
Losing track of component pieces after disassembly

Safety Checks:

Review the three-step process in the instructional card
Understand that PT codes are permanently deactivated
Confirm authorization before disassembling high-value packages
Keep physical packages organized during digital processing

Relationship to Other Operations

Assembly vs. Disassembly

Armar Paquetes (Assembly)
Desarmar Paquetes (Disassembly)

Location: Salidas → Armar PaquetesProcess:

Scan individual pieces
Create a new PT package code
Group pieces under the package ID
Remove pieces from individual inventory
Add package to finished goods inventory

Result: Multiple pieces → One package

Workflow Integration

Producción Nueva (Inbound)
    ↓
[Individual Pieces in Inventory]
    ↓
Armar Paquetes (Outbound)
    ↓
[PT Packages in Finished Goods]
    ↓ (if needed)
Desarmar Paquetes (Transformation)
    ↓
[Individual Pieces in Inventory] ← Back to starting point
    ↓
Venta de PT (Outbound) ← Alternative path

Disassembly allows you to return to an earlier state in the inventory lifecycle, providing operational flexibility.

Direct Navigation

Transformaciones, like Movimientos, provides direct access to a single operation:From AppNavigation.kt:101-103:

composable(Screen.Transformaciones.route) {
    DesarmarPaquetesScreen(onBackClick = { navController.popBackStack() })
}

Navigation Flow:

Home Screen → Tap “Transformaciones”
Desarmar Paquetes Screen → Opens immediately
Back Button → Returns to home screen

There is no sub-menu like Ingresos or Salidas.

Example Scenarios

Order Cancellation
Urgent Piece Demand
Assembly Error
Market Demand Shift

Situation: Customer cancels order after 5 packages were assembledSteps:

Navigate to Transformaciones
Read the instructional card to understand the process
Scan the 5 PT package QR codes
Counter shows “5 PT a desarmar”
Tap “Ejecutar Desarmado”
System deactivates 5 package codes
Component pieces return to inventory (e.g., 20 pieces if each package had 4 pieces)
Pieces become available for other orders

Result: Order freed up, pieces reallocated

Technical Implementation

ScanningLayout Integration

Component Configuration

The Desarmar Paquetes screen uses the reusable ScanningLayout with custom parameters:

ScanningLayout(
    title = "Desarmar Paquetes",
    subtitle = "TRANSFORMACIONES",
    infoText = "Escanee el código QR del PT a desarmar con el botón lateral del terminal",
    onBackClick = onBackClick,
    onSaveClick = { /* TODO */ },
    counterLabel = "PT a desarmar",
    saveButtonText = "Ejecutar Desarmado",
    saveButtonIcon = Icons.Default.Build,
    primaryColor = Color(0xFF455A64),
    infoCardBackground = Color(0xFFE1F5FE),
    extraContent = { /* Instructional card */ }
)

Key customizations:

Dark grey primary color instead of blue
Build icon instead of Save icon
Custom button text emphasizing “execution”
Instructional card in extraContent slot

Educational Design Pattern

The screen implements an educational design pattern with the “¿Qué hace esta operación?” card:

Purpose: Explains unfamiliar operation before execution
Location: Top of screen (extraContent parameter)
Components: Icon, title, description, step-by-step process
Visual Hierarchy: Icon → Title → Description → Steps

This pattern could be adopted for other complex operations to improve user understanding and reduce errors.

Armar Paquetes

Assemble pieces into packages (reverse operation)

Inbound Operations

Add pieces to inventory initially

Venta de PT

Sell individual pieces or packages

Summary

Desarmar Paquetes is a critical operation for inventory flexibility:

Key Function

Reverse package assembly to recover individual pieces

Impact

PT code deactivated, pieces returned to inventory

Use Cases

Order changes, errors, demand shifts, urgent needs

Design

Educational interface with step-by-step guidance

Remember: Package disassembly permanently deactivates the PT code. While pieces are preserved, the original package identity is lost. Use this operation deliberately and with proper authorization.

Get Started

Core Features

User Guide

Technical

​Overview

​Desarmar Paquetes

​Purpose

​Use Cases

Order Cancellations

Inventory Reallocation

Error Correction

Demand Changes

​Workflow

​Screen Layout

​Header Section

​Instructional Card

​Step Item Component

​Scanning Interface

​Action Button

​Visual Design

​Color Scheme

​Icon Strategy

​What Happens During Disassembly

​Database Operations

​Data Preservation

​Best Practices

​Relationship to Other Operations

​Assembly vs. Disassembly

​Workflow Integration

​Navigation Context

​Example Scenarios

​Technical Implementation

​ScanningLayout Integration

​Educational Design Pattern

​Related Operations

Armar Paquetes

Inbound Operations

Venta de PT

​Summary

Key Function

Impact

Use Cases

Design

Build docs developers (and LLMs) love

Overview

Desarmar Paquetes

Purpose

Use Cases

Workflow

Screen Layout

Header Section

Instructional Card

Step Item Component

Scanning Interface

Action Button

Visual Design

Color Scheme

Icon Strategy

What Happens During Disassembly

Database Operations

Data Preservation

Best Practices

Relationship to Other Operations

Assembly vs. Disassembly

Workflow Integration

Navigation Context

Example Scenarios

Technical Implementation

ScanningLayout Integration

Educational Design Pattern

Related Operations

Summary