ERP - Windows to cloud

"Current project ran about local installations on windows. Users, sellers, warehouse managers, manages had dependence to physical devices to operate. Any update needed to a technical person for each machine. Workflow was slowly, few intuitive and it did not grew up”.

My Role

• I analyzed existing ERP legacy workflows to identify friction points, redundancies, and opportunities for improvement
• I defined the information architecture for the new cloud-based system
• I designed the main flows in Figma: item register, item types, warehouse management, serial tracking, dynamic entities, and the multi-parameter configuration hub
• I integrated AI agents into the prototyping process to generate base screens and automate repetitive system workflows
• I validated prototypes with area leads and stakeholders through iterative review sessions

The Process

Stage 1 — Discovery

Before designing a single screen, I mapped the existing system in full. I identified which functions needed to be migrated, which could be simplified, and which could be removed entirely. The goal was never to copy and paste the ERP — it was to rethink how those operations could live on the web.

Stage 2 — Information Architecture

I defined the navigation structure of the new system. The biggest challenge was redesigning the dynamic entities and the multi-parameter configuration hub — functions that in the legacy ERP were rigid and highly technical. The goal was to transform them into interfaces that any business user could operate without depending on the IT department.

Stage 3 — Prototyping with AI

I used AI agents to accelerate the creation of base screens and automate repetitive workflow patterns within the system. This allowed the team to iterate faster with development and bring functional prototypes to validation sessions in significantly less time.

Stage 4 — Validation

Iterative sessions with area leads and end users to validate navigation flows before development began. Each round of feedback was translated directly into prototype adjustments before anything moved to code.

The Key Decision — The Item Master

The most critical module in the entire system was the item master — the core of every commercial operation. Each item, whether a product or a service, is the starting point to which all system configuration is assigned: extensions, lots, warehouses, barcodes, item types, and more. In the legacy ERP, this was a dense, technically overwhelming screen with no visual hierarchy — the full weight of configuration was placed on the user from the very first interaction.

The design decision was to redefine the item master as a progressive configuration flow. Instead of presenting every parameter at once, the system guides the user through layers: first the essential item data, then extensions, then advanced configuration for warehouses, lots, and serials. Each layer activates based on the item type — a service does not require lot management, a physical product does. This dramatically reduced cognitive load and configuration errors.

Results

• Cloud system delivered with 5 core modules redesigned from scratch
• Item master redesigned as a progressive configuration flow, adaptive by item type (product / service)
• Advanced configuration — extensions, lots, warehouses, serials, barcodes — organized in accessible layers without overwhelming the user on first interaction
• Prototype validated with stakeholders prior to development, reducing correction cycles
• AI-assisted workflows that accelerated prototyping and base screen generation

What I Learned

"The item master taught me that in enterprise systems, the most important design is not the most visible one — it is the one that structures all the logic beneath. When the core is well designed, everything built on top of it flows naturally. When it is not, every module inherits the problem. I learned to identify that critical node before designing any other screen.