SmartERP
Projects, sales, production, warehouse, documents and HR in one system — on shared navigation, shared tables and shared forms.
Open the live prototype erp.foxdim.ru
SmartERP brings together what usually lives in different programs: projects and tasks, sales and catalogue, production — work orders, workshops, process maps — warehouse, finance, document flow, personnel and counterparties. One designer means one interface language across all modules.
Why we took it on
ERP systems often grow as a set of modules from different years: each with its own tables, forms and menu. Here the task was the opposite — to set a common base from the first module and add sections without reinventing anything. So I started with the frame: left navigation by groups, the global search “Everywhere”, a theme switch, an “online” status — and a set of repeatable patterns.
What blocked — and what changed
What blocked
- There are many modules and a user works in several at once: projects, counterparties, documents, personnel.
- Complex forms — a counterparty card with dozens of requisites — easily turn into a wall of fields.
- A manager needs to see projects as a flow, not as table rows.
- Development and assessment of employees is separate work that shouldn't sit apart from daily tasks.
What changed
- A frame: collapsible left navigation by groups — Production, Document flow, Personnel, HR, Counterparties, Administration; global search over documents, employees and projects.
- A complex card splits into tabs and blocks: a counterparty has seven tabs, with “Main data” and “Requisites” side by side.
- Projects are a kanban in columns with cards where sum, deadlines, payment status and progress are visible without opening.
- The individual development plan is a table by competence with manager and employee statuses and a side form for a task.
How I worked
- 01
The frame before screens
First navigation, header and search; sections after. Any new module simply takes its place in a ready shell.
- 02
A set of patterns
A table with filters, a card with tabs, a side form, a kanban and status chips — built once and reused in all modules.
- 03
Density by task
Requisites and tables are dense because it's daily work; kanban and dashboard are airier, they're for overview.
- 04
Themes and novelty marks
Light and dark themes from one set of tokens; new sections are marked “Beta” so the user knows what is still evolving.
Screens that move the work
Projects: kanban
The “Projects” section is a kanban: “Column open” columns in different colours, one collapsed to a vertical strip. A card carries the number, the time left, the date, a red “Unpaid” chip, a name, the counterparty, tags “Design / Packaging / Delivery”, the direction, the sum, the number of positions, progress and assignee avatars. On top “New project”, search, tabs “All / Active / Closed”, filters, “Clear filter” and the counter “Total projects: 11”.
- Payment state and deadline right on the card
- A column can be collapsed without losing its place
Counterparty card
Card #7521 is split into tabs: general information, staff, bank details, projects, payments, documents, orders. The first tab holds the counterparty type, a “My company” switch, main data and requisites (INN, KPP, OGRN, OKPO…), contacts and manager data. “Delete counterparty” is pushed to a corner, “Save” and “Cancel” sit at the bottom.
- Seven tabs instead of one long form
- The dangerous action sits away from the main ones
Individual development plan
The “Development” section in the personal cabinet: 20% done, completion date 10.07.2026, a plan version picker “Chief specialist (version 1 of 08.05.2026)”, “Export”. Tasks are grouped by competence — critical thinking, problem solving, self-organisation — and show the manager's and the employee's status as icons, a link, a description, a comment and a date.
- Two statuses — manager's and employee's — in neighbouring columns
Development plan: the task form
A side form over the table. The top block “Task” is filled by the manager and is read-only for the employee. Below: competence, name, development format, a link, a control form, a completion date, the manager's assessment and the employee's “My report” with a mark and a comment.
The outcome in numbers
- Modules of different functions look and work as parts of one system.
- Complex cards and tables are relieved by tabs and side forms — work continues in context.
- A shared base speeds up adding new sections: the frame and patterns already exist.