GPone has begun internal testing of selected core platform functions. This round covers the end-to-end business flow, from user registration and product browsing to subscription requests, order status changes and updates to asset information.
Validating connections across systems
Rather than testing individual pages or features in isolation, this phase focuses on whether the different systems work together according to the defined business rules.
Checks include whether a user action is promptly recorded in the order system, whether information displayed to users remains consistent when an order’s status changes, and whether the corresponding data is synchronized with asset records.
These are key areas to validate before the platform enters operational use.
Improving readability on mobile
During testing, the team has also made several adjustments to mobile pages. Some earlier layouts contained too much information, making the main content harder to read on a phone screen.
Subsequent versions are progressively reducing repetitive explanations and giving greater prominence to amounts, product terms, key dates and times, and order status.
Preparing consistent user guidance
In parallel, work has begun on compiling instructions and frequently asked questions for customer support and the help center. The aim is to provide users with a consistent source of information as more platform functions become available.
Refining the platform through testing
Internal testing does not mean that all platform functions are final. Some pages, data fields and user flows will continue to be adjusted in response to issues identified during testing.
GPone plans to make additional services available gradually once the foundational processes are stable.