DELIVERY
DELIVERY · JEDDAH, WESTERN REGION · 24 AUGUST 2026
Four Applications.
One Database.
The public showroom, the tool the floor uses, the event system and the dashboard everything reports into, built over one Supabase project, so that a car reserved on the website is gone from the salesperson's list in the same second.
WHERE IT RUNS
One Showroom In Jeddah And Everything That Reaches It.
Not a product for sale to other dealerships. One dealership, which is what removes multi-tenancy, billing, plan tiers and most of what would otherwise have taken the year.
Section 04
The Four Applications
The Website
Arabic and English, both first-class. Not a brochure, a shop that sells a specific car, at the price the sheet says today, to somebody who signed in with a phone number and no password.
- Five models, each with a 360° exterior spin in six colours at two resolutions, interior panoramas and specifications drawn from the price list rather than typed a second time.
- A shop that sells actual cars: a specific VIN, nine add-ons, a deposit policy and an order reference the customer can track.
- Compare and save against the browser, then adopted into the account the moment they sign in.
- Test drives against real slots, the calendar knows what is already booked and the booking is tied to one car on the floor.
- An assistant that answers from the dealer's own price sheet and hands over to a person the moment one is asked for.
The Showroom Tool
The same codebase as the website, built a second time with one environment variable set and locked to four screens. Every other path on that host redirects here and it refuses search engines outright.
- Registering a walk-in in the time it takes to ask: name, number, model, grade, colour and which car on the floor exactly.
- Taking a deposit and holding that VIN, with the salesperson taken from the session rather than typed into a box.
- A test-drive evaluation filled in with the customer while the car is still warm, tied to the unit they drove.
- A showcase mode to hand across the desk: the 360° spin, full screen, no navigation.
The Events System
Built first, before the rest of it existed, for a stand in a mall with a queue in front of it. Folded into the monorepo afterwards rather than left to drift.
- Self-registration at the stand and a live queue the staff work through.
- Campaign forms with financing questions and a leads list that says who has been rung and by whom.
- The stock screen, every car, its status and the deposit that is holding it.
11 of its 16 screens are behind a staff sign-in, this is as far as a stranger gets and the shot is honest about that.
The Dashboard
The largest of the four and the only one nobody outside the building can see. Twenty-five permissions across eight roles decide which of its thirty screens a given person gets.
- Today, what needs somebody right now, on one screen: chats waiting, deposits about to expire, leads nobody has rung, open orders, errors.
- Live chat: the queue grouped by whose problem it is, the whole customer history beside it, saved replies, tags, car cards sent into the conversation, transfer to a colleague and search across every conversation ever held.
- Stock by VIN, with ageing measured four ways, including from the people who actually drove it.
- Money: orders, deposits, reservations, financing applications and the price list itself, editable without a deploy.
- Traffic: Google Analytics and Search Console, a world map, landing pages and what people searched to arrive.
All 30 of its screens are behind a staff sign-in; this one was supplied for the handover, this is as far as a stranger gets and the shot is honest about that.
They Arrive And Are Remembered
The campaign, the landing page and the device are recorded against the browser before anything is asked of them. No form, no name, just the fact of the arrival, waiting to be joined to a person later.
record_attribution()visitor_attribution, written from the browser on first paint
They Ask And Get A Real Answer
The assistant answers from the price sheet. If they want a person, the conversation rings in the dashboard with everything already known about them sitting beside it.
chat_open()Gemini 2.5 Flash, grounded on the live price list and forbidden from quoting a figure the site does not also quote
A Specific Car Is Put In Front Of Them
An agent sends a card into the conversation: that VIN, that colour, today's price and a link that reserves that exact car. Not a model. A car.
chat_send_car()A message row whose payload is a vehicle_units id
They Pay A Deposit
From the website, or across the desk in the showroom. The same function, two doors, one set of rules. The car leaves the floor in the same second, there is no window in which two people can both be sold it.
reserve_unit()The storefront and the showroom tool both end at one function. The floor's key opens the same lock.
The Rest Is Paperwork With A Timer
Balance, purchase order, handover. Each stage moves the car and the money together, or neither. A hold nobody completes expires on its own and the car goes back on the floor without anybody remembering to do it.
expire_stale_store_orders()advance_store_order() and expire-store-holds sweeping every five minutes
And The Numbers Were Never Entered Twice
The sale is already in stock, in the customer record, in the salesperson's figures and in Sunday's digest, because it was one row all along. Nobody reconciles anything.
One write, six readers. This is the whole argument for one database.
BUILT WITH
© 2026 Motion Motors · Soueast Western Region