Elvis Beauty

ERP Upgrade: Security, Full Redesign & Commerce Integrations

Elvis had a working in-house ERP. They brought Atmiz in to secure it, redesign every screen from scratch, and build the WhatsApp and ad attribution integrations their growth required. Their own team kept shipping features throughout. We worked alongside them the whole way.

Role

Security review and fixes, full product UI redesign, WhatsApp BSP and Libromi integration, Meta ad attribution, TeleCRM expansion, reporting and logistics UX, and ongoing alignment of new features as they shipped

Timeline

Multi-phase engagement: security and stability fixes, then full redesign, then TeleCRM and attribution work, then ongoing collaboration as new features were added

Key Technologies

Django 4.2 / Django REST Framework / PostgreSQL (Supabase) / Celery + Redis / Tailwind CSS / WhatsApp Cloud API and BSP (Libromi) / Meta Conversions API (click-to-WhatsApp attribution) / Shopify webhooks / Fernet encryption, HMAC webhook verification

A Working Platform, Taken to a Much Higher Standard

Elvis already had a Django-based ERP running their beauty brand. Orders, leads, WhatsApp campaigns, inventory, Shopify sync, logistics. It worked. But the system had grown fast with little structural care, and the cracks were showing: security gaps, inconsistent screens across modules, and a product that was becoming harder to use as it grew. They brought Atmiz in to fix all of that without touching what was already working. We secured the platform, redesigned every screen, and shipped the integrations their growth needed, all while their engineering team continued adding new features on the same codebase.

The Challenge

A Fast-Moving Product With Growing Pains

The ERP was built in-house by Elvis's own engineering team and it served the business well. But moving fast had come at a cost. Security shortcuts had accumulated: credentials were hardcoded in places, incoming webhooks had no verification, and sensitive data was stored without encryption. The product interface had also grown inconsistent as new screens were added module by module without a shared design system. Rebuilding from scratch was not an option since the ERP was too embedded in daily operations. But leaving things as they were meant a platform that was both risky and increasingly difficult to work with.

The Solution

A Trusted Partner, Not a Replacement

Atmiz did not take over or replace Elvis's team. We joined as a parallel partner while their engineers continued shipping new features at their own pace. To do that well, we had to understand the entire system: every business domain it covered, how the database was structured, and the logic behind each part of it. That depth meant that the changes Atmiz made, whether to security, design, or architecture, went into production cleanly without disrupting the client's own ongoing work. Every screen in the product was redesigned. Every new feature Elvis's team shipped, we brought up to the same design standard.

Collaboration

How We Worked Together

Two Teams, One Product

Elvis's engineers and Atmiz worked on the same codebase at the same time. Their team focused on new features. Atmiz focused on security, design, and integrations. Neither team blocked the other.

We Learned Their System First

Before changing anything, we mapped every part of the ERP: every module, every database table, every integration. That groundwork is what made it possible to ship changes that merged cleanly with no surprises.

Design Kept Up With Development

When Elvis's team shipped a new screen, Atmiz aligned it to the design system before it reached users. The product stayed consistent throughout, even with two teams building it.

"A working system with bigger ambitions. We secured it, redesigned it end to end, and built the integrations that made real growth possible."

Under the Hood

Technical Execution

A breakdown of the core systems engineered to deliver performance and scalability.

Security Fixes

Moved all credentials to environment variables, removing hardcoded secrets from the codebase
Added HMAC signature checks to every incoming webhook endpoint, which previously had none
Encrypted sensitive auth tokens stored in the database using Fernet encryption
Set up automated smoke tests on key routes so broken pages get caught before they reach users
Migrated the database to managed PostgreSQL on Supabase with a clean, documented deployment setup

WhatsApp, Ad Attribution & Integrations

Built a portal where operators can connect and configure any WhatsApp messaging provider without touching code
Integrated Libromi as a messaging provider: inbound messages, contact sync, broadcast campaigns, and bot-captured leads all flow into the ERP
Built the Meta Conversions API setup for click-to-WhatsApp campaigns: the right click ID is captured, conversions are tagged with the WhatsApp source, and cash-on-delivery orders are not counted as website purchases
Added a clear interface for copying webhook URLs when setting up new integrations, removing the need for developer help for basic setup

Full Product Redesign

Built a complete design system: fonts, spacing, card layouts, tables, modals, animations, and export templates. Applied to every screen in the product.
Redesigned the login and authentication screens
Rebuilt the CRM and lead management views for clarity, designed around the pace of a real tele-sales team
Expanded the TeleCRM module with call queues, agent assignment, call logs, and team performance dashboards
Redesigned logistics and reporting: delivery manifests, packing lists, channel breakdowns (Flipkart, Meesho, Swiggy), and order analytics
As Elvis's engineers added new features, we brought every new screen into the shared design system so the product stayed unified

Gallery

Visual
Architecture

A curated selection of key platform interactions.

Confidentiality NoteConfidentiality Notice: To protect client privacy, all customer details, revenue metrics, and sensitive information in these interface previews have been replaced with sample data.