The problem was a lack of visibility, not a lack of tools

As orders grew, some of them fell between the stages. To understand what happened during the day, the team and I often had to open several places, review different sheets and ask several people. The details were scattered, so there was no single clear picture of the business.

It showed up in very practical ways:

  • Returned orders forgotten or not followed up properly.
  • Some orders not getting enough follow-up attempts.
  • Difficulty tracking an order through its lifecycle — dispatch to delivery or return.
  • Ads running on a product while stock could run out — without clear visibility.
  • Weak inventory counting and stock visibility.
  • Data fragmented across many sheets, and sometimes the knowledge itself lost.
  • Unstructured employee access.
  • Hard to distinguish what left the warehouse, what’s with the carrier, and what returned.
  • Management reports needing significant manual assembly.

The first system: Order Management

The first system I built was Order Management. The important shift wasn’t just “digitizing orders.” Before the system, many decisions depended mainly on the team leader’s opinion — valuable, but sometimes subjective. After it, my decision model became: data + team context.

The number shows what’s happening; the team explains the context. The result is what I call a helicopter view: the owner sees the business from above, knows where the problem is, then drills into detail when needed — instead of living inside every order all day.

Better visibility exposed hidden problems

The system didn’t just organize what I already knew — it exposed things that were harder to see: problems in returns, orders that hadn’t had enough attempts, and weakness in long-term customer value (LTV). That last one reinforces an important idea: not every growth problem is solved with more ads.

From an internal tool to a product

I built these systems inside Rebhni to run my own brands first — then started making Rebhni available to others. It grew because I wanted to turn recurring e-commerce operational problems into reusable technology, instead of solving them manually every time. Every e-commerce business brings different use cases and problems, and those become learning that improves the product over time.

Operational pain → internal systems → structured data → clearer decisions → reusable software → learning from more businesses.

What I’d hate to go back to

If I had to return to the old way, three things I’d particularly dislike:

  • Moving between many spreadsheets just to produce a management report.
  • Manual inventory counting and reviewing comments/statuses across orders to know what happened.
  • Losing track of shipments between warehouse dispatch, carrier possession and returns.

The systems I built inside Rebhni: Owner dashboard · Warehouse system · all systems