One of the issues marketplaces face when managing payments is the need to reconcile their accounting. Balanced solved this acute pain point by introducing ”orders,” an API resource that mapped corresponding debits and credits, ensuring funds are properly earmarked for the appropriate seller. This new feature required numerous dashboard modifications from the presentation of these new order pages to helping users visualize the relationship between a parent order and its associated transactions and customers.
To assess the feasibility of this feature, we spoke to select customers to understand their payment model (i.e. one buyer to one seller vs. multiple buyers to one seller) and determine if there were any breaking constraints that would prevent them from adopting the feature. Some of the concerns raised forced us to revisit the specifications. A few marketplaces had already implemented some form of transaction linking, so it was important to view their internal dashboard and see how they were presenting their own information.
After outlining the scope of the project and the necessary additions to the dashboard, I began exploring multiple layout options, organizing transactions by customer name, transaction type, or customer role. I evaluated different ways to navigate between an order page and transaction page, the table structure for displaying the two, and the presentation of the order summary, details, and relevant actions. Design mocks were then previewed with customers via feedback sessions and through Github.
The new design created a consolidated view of an order that shows all the associated debits and credits, the addition of an order balance to indicate if money is owed to the seller, and new table views to clarify the hierarchy between orders and transactions.
view live orders page
VIEW LIVE DASHBOARD
