Story

Ayam Gepuk Artisan Seksyen 7

One outlet, three kinds of user — customers, crew and a manager — and a single link that serves all of them.

LiveOutlet buildRestaurant · customer site + staff system
Ayam Gepuk Artisan Seksyen 7
ayamgepukartisan-seksyen7.vercel.appDesktop · 16:9
Ayam Gepuk Artisan Seksyen 7 on a desktop screen
Ayam Gepuk Artisan Seksyen 7 on a phone
Phone
Live now

These are screenshots until you press the button. Then the real site loads in both frames — scroll it, tap it, use it.

Open in a new tab

If a frame stays blank, that site is not allowing itself to be shown inside other pages yet. “Open in a new tab” always works.

At a glance

The short version.

What
Customer site + staff operating system
Where
Seksyen 7, Shah Alam — one outlet of a national brand
Pages
19: customers 8, crew 10, manager 1
Languages
Bahasa Malaysia first, English alongside
Built with
HTML, CSS, JavaScript, Google Forms + Sheets
Hosted on
Vercel
The brief

The problem.

New crew, often
Every hire trained by whoever was on shift
Info in three places
National site, WhatsApp group, SOP sheets taped to the wall
Outlet-specific questions
The national site could not answer local ones
No safe till
A new cashier’s first order was a real order
Hours by memory
Attendance chased at the end of the month
Written from the floor
The person building it works shifts there
The build

What we built.

Menu and set builder

Categories you can filter, and a set builder that shows how the plate is laid out before you order.

Booking on the floor plan

Pick a real table on a drawing of the outlet, see which hours are busy, and confirm on WhatsApp.

Feedback with a ticket

Praise, complaint or suggestion — each gets a ticket number, and a promise: read within a day, answered within two.

SOPs by station

Frying, prep, plating, floor, counter, opening and closing — as steps, timers and checklists, not walls of text.

Practice till

A copy of the counter screen, takeaway charges and all, where mistakes cost nothing.

Manager console

Behind its own password: attendance board, break schedule, cleanliness matrix, training tracker.

Pages

A closer look.

The menu
The menuFilters by category, and a set builder that shows how the plate is laid out.
Table booking on the floor plan
Table booking on the floor planPick a real table, see the busy hours, confirm on WhatsApp.
About the outlet
About the outletWhat gepuk means, the outlet’s own details, its compliance in plain view.
Architecture

Who touches what.

Three kinds of user, one system, one set of records.

Customer
menu · booking · feedback
Crew
SOPs · practice till · attendance
Manager
console · attendance board · training
One set of records
bookings, feedback and hours all land here
Outcome

What changed.

One link
Instead of three people and a wall
Local truth
Outlet details stopped being a guess
Safe training
Mistakes moved off the live till
Hours in a sheet
Attendance lands where the owner already looks
How it is put together
  • Plain HTML pages — nothing to install, fast on a phone with weak signal in a busy shop.
  • Crew and manager areas are separate, each behind its own password.
  • Attendance goes into a Google Sheet through a Google Form — tools the owner already knows.
  • The customer side follows the parent brand’s look, with this outlet’s own details on top.
  • Hosted on Vercel — a change is live within a minute.
On our plans

This is Run territory, toward the upper end.

Customer tools, staff portal and SOPs, attendance, a practice till and a manager view are what the Run plan covers. The floor-plan booking and the till copied from the real counter would be custom work on top.

Plus custom work, agreed first
Floor-plan bookingTill copied from the real oneSOPs written from the floor

Being straight with you

This is an internal prototype for the Seksyen 7 outlet, built from the inside by someone who works shifts there — not a project commissioned by the brand’s head office. The sales figures on the staff side are sample data. We show it because it is the clearest example of what we mean by “the systems behind the website”.

Next step

Need something like this?

Tell us what you run. We reply with the plan that fits and anything that would be custom — in writing, before anything starts.

No-obligation first chatEverything agreed in writing