Food & restaurant technology
Ordering, delivery and export platforms that survive a lunch rush
Three food businesses on three continents, each with a different problem: a bakery that kept selling out, a marketplace starting from nothing, and a 36-year-old exporter running on paper. All three still run on what we built.
The problem
Food software fails at the busiest hour, not the average one
Every food platform looks fine in a demo. The test is Friday at half past twelve, when orders arrive faster than the kitchen can acknowledge them, a courier goes offline mid-delivery, and a payment provider times out. What breaks then is rarely the app. It is the assumption that each step completes before the next begins — an order confirmed before payment settles, a courier assigned before the restaurant accepts. We build for the opposite: every step can fail, arrive twice, or arrive out of order, and the system still has to reach one correct answer. That is why ToOrdr is on its third generation and still running six years later, and why Arabian Food Corp’s operation moved onto one system without a break in trading.
What is included
What we build for food businesses
01
Customer ordering apps
iOS and Android, built offline-first so a weak signal in a basement restaurant does not lose a basket. Scheduled pickup, live status and repeat ordering as first-class features rather than additions.
02
Courier and driver apps
Assignment, route handoff and proof of delivery, designed for one hand and a phone mount. Every action is queued locally and reconciled, because couriers lose signal constantly and the order still has to be right.
03
Restaurant and kitchen dashboards
Accept, reject, adjust timing and go offline when the kitchen is drowning. The single most requested feature in every food build we have delivered, and the one most often missing.
04
Enterprise and canteen ordering
Account-based ordering, pre-order windows and volume handling — what ToOrdr grew into when corporate canteens started using it.
05
Export and wholesale platforms
Order capture, catalogue and ERP integration for businesses selling by the pallet rather than the portion, as built for Arabian Food Corp in Jeddah.
06
Payments and settlement
Multiple providers, partial refunds and the reconciliation nobody demos. Getting the money exactly right is the part that ends relationships when it is wrong.
Typical outcomes
What good looks like
One backend, several front ends
Customer, courier and restaurant apps are different jobs but one truth. Lejo runs three apps against a single set of shared services — the alternative is three products that disagree about the same order.
Offline-first, always
A phone in a lift or a basement kitchen is the normal case, not the edge case. Actions queue locally and reconcile on reconnect.
Idempotent order handling
Every write can be retried safely. Double-tapping Pay at a bad moment must not create two orders, and a retried webhook must not refund twice.
Built to be handed over
Six years and three versions of ToOrdr later, the same platform is still being extended. That only happens when the code was written to be read by whoever comes next.
Proof
Food & restaurant technology we have shipped
Real engagements, with the numbers the clients measured. Each one links to the full write-up.
Food ordering · Germany · iOS + Android + Backend
From bakery pickup to an enterprise canteen platform
ToOrdr began in Germany in 2019 as a way to reserve fresh bread before it sold out. Six years and three major versions later the same platform runs staffed canteens and corporate lunch programmes for third-party employers. It was the first product LexicMedia built, and the client is still with us.
App downloads
Third generation
Continuous development
Food export · Jeddah · Web + Apps + ERP
A 36-year-old exporter, rebuilt around one system
Arabian Food Corp came to us in 2019 for a brochure. They wanted something their export peers would take seriously. That brochure became the website, then mobile apps, then third-party integrations, then the ERP the business now runs on. We are still working on it.
App downloads
Orders processed
Client trading history
Marketplace · Canada · iOS + Android
“I want a product like UberEats” — and then we never stopped
One line from the client started it. What followed was a full three-sided delivery ecosystem for the Canadian market — customer apps, courier apps, restaurant tooling and the operations behind them — built, scaled and rebuilt as demand and local expectations moved.
App downloads
Orders delivered
Sides of the marketplace
Related services
Most engagements combine more than one
Work rarely stays in a single lane. These are the disciplines that most often sit alongside this one.
Web Development
Sites and applications engineered for speed, search and conversion.
Mobile Development
iOS and Android apps that ship on schedule and survive store review.
Blockchain & Web3
Smart contracts and on-chain integrations, specified and audit-ready.
AI & Automation
Workflow automation scoped against the hours it actually saves.
Digital Marketing
SEO, content and paid acquisition measured in pipeline.
FAQ
Food & restaurant technology questions
Yes — that is precisely what Lejo is. A three-sided marketplace with customer, courier and restaurant apps sharing one set of services, built for the Canadian market and delivering 10K+ orders. The clone question is usually the wrong one though: the apps are the easy half, and dispatch, settlement and support tooling are where the work is.
Usually yes, because the three audiences want opposite things — but they must share one backend. Customers want speed and reassurance, couriers want one-handed operation, kitchens want to control their own load.
A single-restaurant ordering app is measured in weeks. A three-sided marketplace with dispatch and settlement is measured in months. We scope both against a written specification and quote a fixed price before starting.
Yes. Arabian Food Corp’s ERP integrates the third-party services already in use rather than demanding they be replaced — that is normally the difference between a system that gets adopted and one that gets worked around.
Portfolio
A decade of work still in production
Selected engagements across software and growth. Many of these systems have been running — and being maintained by us — for years.
Field operations platform
Venaxx Logistics
A dispatcher platform and driver app built in 2014 and still in daily use across three countries. We have maintained and extended it continuously since launch.
Subscription commerce storefront
OrdrrPay
Headless storefront with subscription billing, rebuilt for speed and paired with the acquisition programme that grew it. Now in its fourth year of retained work.
Regulated onboarding flow
Wassira Fintech
A fourteen-step KYC journey rebuilt as a saved, resumable process — completion up substantially without weakening a single compliance control.
Clinic network consolidation
Medcross Healthcare
Nine competing location sites consolidated into one architecture with proper local schema, then a condition-led content library mapped to patient intent.
Next step
A 30-minute call will tell you more than any deck
Bring the problem you are actually trying to solve. We will tell you what it takes, what it costs, and whether we are the right people for it.
Not ready to brief a project?
Ask one question. A senior person answers it — no pitch, no call booked.