Labeeni: Auto-parts marketplace

Who it is for

If you bring auto-parts stores into one marketplace, your first problem is the incomplete request. Car owners call store after store, send photos over chat, and leave out the model or year. In Labeeni the customer sends one request with the car's details, and stores reply with offers inside the app.

How a working day runs

The customer opens a new order and picks the car's make, model and year, or chooses “Other model” when theirs is missing from the list. They add the part name, a description and the quantity, plus the chassis number and part photos if they wish, and set the delivery address. The request lands among the stores' incoming orders, and a store reviews it and sends its price offer. The customer finds the offers in the app, with a count on each order, and follows the order until it arrives. Each store tracks its active and completed orders, the offers it sent and its statistics on the same screen. Admins manage stores and customers from the web dashboard.

What makes the difference

• Customers order by car make, model and year, so the store knows what fits before it replies.
• Each side has its own app: customers track their orders, stores answer incoming requests, and no one sees another's orders.
• Admins run the whole marketplace from one dashboard with set permissions per role, and no competitor sees a store's data.
• Store offers on each request gather in the customer's app, so every price for the part shows in one place.

How it is built

The customer and store apps share one Flutter codebase, so every fix reaches both. We built the admin dashboard in React, since admins need tables and permissions on a wide screen. A PostgreSQL database on Supabase holds all marketplace records. Row-level security (RLS) lets each store read only its own data, so the database refuses another store's data even if a screen gets it wrong.