The problem
A restaurant purchasing stock is not browsing for dinner. Wholesale orders depend on credit headroom, minimum quantities and repeat purchases. A consumer storefront places discovery first, even when the buyer's actual task is to repeat last week's order.
Talabatty also serves different account structures. A single outlet needs a fast ordering flow. A chain needs branch-level ordering, permissions and consolidated reporting. Combining every control into one interface would make both experiences harder to use.
Constraints that shaped the work
The platform serves businesses in Kuwait in Arabic and English, including a complete right-to-left layout. Prices need an explicit unit and minimum quantity. Available account credit affects whether the buyer can complete an order at all.
Buyers, vendors and prospective partners also arrive with different tasks. The product could not treat them as one audience.
Put the repeat purchase first
The signed-in buyer lands on a dashboard with previous orders and frequently purchased items near the top. Search and categories remain available, but they no longer set the order of the whole experience.
This prioritises the common weekly task. The accepted trade-off is less prominence for discovery, in return for a shorter route to the products a business already buys.
Show constraints before the basket
Available credit is visible on the dashboard. Product cards pair price with the applicable unit and minimum quantity. These details help buyers judge an order before investing time in the basket, rather than discovering a restriction at checkout.
Order states are explicit and countable. The buyer can distinguish deliveries in progress, completed orders and exceptions without interpreting a vague status.
Give account types their own shape
Multi-branch accounts expose reporting and user management appropriate to a chain. Single-outlet accounts do not carry that extra interface weight. Prospective partners enter through a separate acquisition page rather than navigating a signed-in product.
Design and implementation scope
My published work includes the buyer dashboard, reorder flow, credit model, product cards, order states, reporting, RTL layout and design system.
Outcome and further questions
The resulting dashboard places the repeat order, credit context and quantity requirements together. Different account types see controls relevant to their work.
The published outcome is qualitative. Repeat-order time, quantity corrections and support requests would be useful measures for a subsequent evaluation; no numerical improvement is claimed here.
