Returns and exchanges are part of buying, too.
Product development during the first two yearsPROJECT CONTEXT
01 / THE STARTING POINT
8returns helps ecommerce brands manage returns and exchanges. My contribution covered the first two years of product development at Malindo, including the early versions before the product evolved through Aion and later became 8returns. The customer journey and the operational system were still taking shape together.
02 / THE PRODUCT IN PRACTICE
During those early years, customers could start a return with their order ID and follow a guided flow. Keeping that entry simple depended on connected experiences behind it: retailers managed the return workflow, while warehouse teams processed the physical items. The three applications served different people but needed to remain parts of one return journey.
Close work with the product team meant more than implementing a changing list of requests. Business needs had to become decisions about how the product should behave and what the system needed to support.
Speed mattered, but a new workaround for every iteration would make the next change harder. The work was to keep delivery moving without treating early assumptions as permanent.
As the platform matured, the work moved beyond proving the initial workflow towards a more complete returns experience. Requirements and flows became richer. Development had to carry those changes forward while keeping the product open to further iteration.
03 / A CLOSER READING
Malindo, Aion and 8returns describe stages of a product finding its shape. The important continuity was underneath the names: early work needed to support the next version without making the first version disposable.
04 / THE THROUGH LINE
The first two versions helped establish a foundation that could move with the product as its identity, requirements and reach changed. That early development contributed to the more mature platform that became 8returns.