Skip to content

Restaurant software engineering

Restaurant ordering, apps and integrations.

I help restaurant software teams build and improve customer apps, merchant dashboards and the systems behind them.

Discuss your projectSee selected work

Need a restaurant website? Websites & online ordering

Quick Food sandbox menu on a phone
Nomly by Crave public sample conversation on a tablet
Quick Food sandbox · Nomly by Crave

Selected work

CraveUp · Restaurant platformHow it works

One order. A connected team.

Guests orderBrowse, choose & pay
Staff prepareReceive & handle orders
Merchants manageMenus, orders & locations
Connected through menus, orders and payments
Simplified system view · Employer work at Crave

Employer work · Crave

One platform for guests, staff and merchants

CraveUp: customer ordering, merchant dashboard, staff app and Square and Clover integration engineering, within the Crave team.

My role
Full-stack engineer, now Director of Engineering
Tech stack
  • Next.js
  • React Native
  • Node.js
Read the case study: CraveUp - Restaurant Ordering & Management Platform
Multi-location orderingHow it works

From a nearby location to an order in progress.

Pick a locationFind the store & its menu
Place an orderChoose items & check out
Follow progressSee status & past orders
Customer apps and restaurant tools share order updates
Simplified system view · Client work through Crave

Client delivery through Crave · brand withheld

Ordering across restaurant locations

A Flutter and web ordering platform with an Express API, delivered through Crave for a multi-location brand.

My role
Full-stack & mobile engineer
Tech stack
  • Flutter
  • Next.js
  • Express
Read the case study: Multi-Location Restaurant Ordering Platform
All twelve case studies

Production problems I have fixed

  1. Customers charged but shown an error: a dropped null in the checkout session, fixed, no recurrences.
  2. Order history empty for thousands of customers: restored, and a wildcard email match that could expose other accounts caught in review.
  3. Every signed-in feature down until a restart: a half-open Redis connection made self-healing.
All five stories, with what I did and did not doSee what happens after a customer orders

“Umar is a high skilled professional always looking to reach the project goals and quality in all the areas. He is a team player and I have seen him growth with high expectations.”

How we work together

Ship a product feature

Customer app, merchant dashboard or backend work inside your existing product, with tests and a reviewable pull request.

Improve a restaurant website

A clear mobile site connected to a suitable ordering provider, tested end to end. For restaurant owners.

  • Unclear problem → a read-only audit and a written repair plan.
  • Clear need → one scoped milestone with tests and a handoff.
  • Every project: written scope, visible progress, your accounts and code.
Umar Farooq

Umar Farooq

Restaurant websites, apps & integrations

I joined Crave in May 2020 and now lead engineering there while staying hands-on. I have worked on CraveUp, the guest app for an 80-location restaurant brand, Nomly and CaterVox, and I contribute to Crave’s open-source restaurant tooling. Stack: Next.js, React, TypeScript, Node.js, PostgreSQL, Flutter, React Native, Stripe, Square and Clover APIs.

Crave’s products; my role is contributing engineer.

More on LinkedIn, opens in a new tab

A few practical details

Before we talk.

Do you work with restaurant SaaS companies too?

Yes. I work with restaurant owners and the teams building software for them. For SaaS companies, that can include ordering apps, merchant dashboards, multi-location workflows, POS integrations and ongoing product engineering.

How do we contract and pay?

New clients usually work with me through Upwork. If we meet elsewhere, we can check eligibility for an Upwork Direct Contract. Fixed-price work is split into funded milestones with written deliverables and acceptance criteria before work starts.

Who does the work?

I lead discovery, architecture, implementation or review, and final QA. If a collaborator is needed, we agree that before work begins and name their role in the written scope. Material team involvement always requires your agreement.

How much does a project cost?

The price follows a written scope. We start with a read-only audit when the problem is unclear, or one scoped milestone when the need is clear. After a short discussion I provide the scope and quote; domain, hosting, ordering subscriptions and payment-processing fees are separate costs you pay to the providers.

How do we work together internationally?

I work remotely from Pakistan (PKT / UTC+5). We agree on call windows that suit both time zones, and I keep progress visible through written updates and review links. You do not need to be technical to take part.

Let’s talk

What are you
building next?

Share your SaaS product or restaurant website, and the part you need help with. A rough idea is enough to start.

Based in Pakistan · Working internationally
We agree on a time that works for both of us.

Email

develop.umar@gmail.com

Send product context, links, or a short brief.

Write email

Book an intro call

A 30-minute conversation about your current setup and the next useful step.

Opens in a new tab