CurryDash: our curry-first ordering and delivery marketplace

The challenge

Mainstream delivery marketplaces model a menu as a fixed list. The customer selects a listed item, and the kitchen cooks what the listing says. That model suits standardised products and the chains that sell them.

Curry is ordered differently. The same dish is prepared differently from kitchen to kitchen and varies from order to order, so what the customer actually wants sits in the configuration rather than in the listing. A platform that carries fixed items only pushes that detail out of the ordering flow.

We saw a marketplace built for that behaviour from the start. Customisation as a first-class part of ordering rather than a comment box, and delivery on the same platform, so a merchant does not have to run a storefront on one service and fulfilment on another.

What we built

CurryDash, our own food ordering and delivery marketplace for local, independent curry shops. Built in the model of the mainstream delivery platforms, with the product shaped around configuration.

• Dish configuration. Customers build a dish instead of choosing a finished one. Options sit against each merchant’s own menu, so a shop keeps its own recipes and variations rather than being flattened into a standard catalogue.
• Customer ordering. Browse participating shops, configure items, and place an order.
• Merchant management. Shop and menu setup, option definitions, and handling of incoming orders.
• Order routing. Orders pass to the correct merchant and into the delivery workflow, with the configured detail attached.
• Delivery tracking. Order state visible from acceptance through to delivery.

How we worked

Funded, specified and built in house. We owned the customer ordering experience, the merchant side and the delivery workflow, with no external client setting scope.

Outcomes

• Built a working marketplace in which dish-level customisation is part of the ordering flow, not a note attached to a fixed menu item.
• Merchants defined their own options against their own menus, so variation was set up once in the platform instead of being handled per order.
• Ordering, merchant management and delivery ran on one platform rather than across separate services.
• Consumer marketplace and delivery capability held in-house: a two-sided product with a transactional ordering flow and a fulfilment workflow behind it.
• CurryDash is archived. It is presented as evidence of marketplace and delivery platform capability, not as a live service.