Bebubam

Bebubam is a Vietnamese retail chain selling mom and baby products, dozens of physical stores across the country, plus a centralized online shop. They were growing fast, and the cracks were starting to show. Inventory tracked in spreadsheets, HR in one tool, accounting in another, sales data fragmented between in-store POS and e-commerce. Nothing talked to each other.

BBS Ltd. brought us in to design a custom ERP system that would tie all of it together, a single platform their teams could actually use day-to-day, without needing a manual or an IT degree. That last part mattered a lot.

The tricky thing about Bebubam's situation wasn't that they had one big problem, it was that they had a dozen smaller ones all compounding on each other. Stock levels were being reconciled manually across multiple warehouses. Finance and operations weren't looking at the same numbers. Store staff and HQ were working in completely different systems, which meant decisions were always a step behind reality.

On top of that, the people who needed to use this system weren't developers or power users. They were store staff, warehouse operators, accountants, and executives,. each with completely different workflows, different levels of tech comfort, and very little tolerance for a system that slows them down. Getting the UX wrong here didn't just mean frustrated users; it meant real operational errors, financial losses, and a system nobody would actually adopt.

The challenge was to design something that could handle serious operational complexity while still feeling approachable enough for a store associate on a busy Saturday.

The first big decision was modular architecture. Rather than one monolithic interface, we structured the ERP into self-contained modules, inventory, HR, CRM, accounting, marketing, QA, and order management, each following the same interaction patterns. The benefit of this wasn't just visual consistency. It meant that learning one module made the next one easier. Onboarding new staff became faster, and adding features later didn't require redesigning the whole thing.

We also built the entire permission model into the interface logic itself. A warehouse operator doesn't see the finance approval flow. A store associate doesn't see HQ-level reporting. Navigation, dashboards, and available actions all shift based on who's logged in, so people only deal with what's relevant to them. This wasn't just about access control; it was about reducing cognitive noise for everyone.

For the actual interface design, we went deliberately functional. This is software people use for hours at a stretch, so heavy visual decoration would've been a distraction. Persistent sidebar navigation, fixed-header data tables for long lists, clear status indicators, and consistent page layouts across every module, the kind of decisions that don't look flashy in a screenshot but make a real difference at hour six of a workday.

Every major workflow was also mapped out from real operational steps, not from what seemed logical on a whiteboard. Take inventory management: a user selects a location, sees live stock levels, spots what's low or mismatched, triggers a transfer or replenishment, and tracks it through approval and fulfillment, all in one place, in the order they'd actually think about it. We used inline actions, confirmation states, and progress indicators so that at every point, users knew exactly what they'd done, what the system was processing, and what came next. For a business-critical tool, that kind of feedback isn't a nice-to-have.

After deployment, the numbers told a pretty clear story. Common inventory and reporting tasks were getting done around 40% faster than before. Inventory reconciliation errors dropped by roughly 60%, largely because everyone was finally looking at the same real-time data instead of comparing spreadsheets. New staff onboarding time came down by about 35%, which makes sense when users have role-tailored interfaces rather than a wall of features they'll never touch.

But honestly, the outcome that matters most for Bebubam's future is the foundation it created. The system is designed to grow with them,  new store locations, new product categories, new regulatory requirements — without needing to be rebuilt each time. They went from duct-taped tools to a platform built for where they're headed, not just where they were.