A No-Backend Ordering Site: How It Works

A small African-cuisine food business needed to take structured orders online, full menu, portion sizes, delivery details, without the budget or need for a real backend, a database, or a payment-gateway integration. Délice Duo answers that need with a single page.

The bet: everything fits in one file

A single HTML file of about 50KB, CSS and JavaScript inline, no build step, no framework, no package.json, plus an images folder. The same approach as the TUM Corporation site, condensed into one page instead of several. The cart, category filters, portion and choice handling (Chicken or Fish depending on the dish), all of it runs client-side.

The real menu: 12 dishes across 4 categories (Attiéké, Foutou, Rice & Sauces, Other specialties), each with three portion sizes at different prices.

The real problem to solve: ordering without a server

With no backend, how does an order become real? The answer: WhatsApp as the order channel. The customer builds their cart, fills in their details (name, address, phone), picks a payment method, UPI scan (PhonePe, Paytm, Google Pay) or cash on delivery, and at checkout, a prefilled WhatsApp message opens automatically to the vendor with the full order details. No server needs to receive anything.

One detail that matters: the site only accepts orders on the business's real operating days (Tuesday, Saturday, Sunday). Outside those days, a clear message invites the customer to order in advance, with the next available date calculated automatically.

The challenge: proving a payment with no payment gateway

With no real payment integration, how do you know a scanned order was actually paid? The form asks for the last 4 digits of the UPI payment reference, and the flow explicitly asks the customer to also send a screenshot of the payment confirmation, directly in the same WhatsApp conversation that just opened. It's not an automated check, but a simple system that's honest about its limits, matched to the real scale of the business.

Other details built for real-world use: an order receipt generated automatically (rendered on a canvas, downloadable as an image) that the customer is asked to save, and a history of their orders kept locally in their browser.

The result

A working online ordering site for a small food business, with zero hosting cost beyond a plain static file host, and zero payment-gateway integration. Proof that a good user experience doesn't always need heavy infrastructure behind it.