Lokal

A customer finds a shop on Lokal and orders from it. This is everything between pressing “Place order” and the seller’s phone lighting up.

Read from orders.service.ts, migrations 033 and 036 and the push-dispatch Edge Function. Every name below appears in the source exactly as written.

1. 01

   Checkout needs a signed-in buyer

   The checkout page sits behind the authentication guard, and the delivery details are validated by a Zod schema before anything is sent.

   • RequireAuth
   • checkoutSchema

   ▸What it says when it refuses

   An anonymous visitor is sent to sign in first; a name under two characters or a phone number under six never leaves the form.

2. 02

   The client adds up; the database decides

   usePlaceOrder hands the basket to the orders service, which totals the lines and prepares the write. The total is a convenience — whether the order may exist at all is not the client’s call.

   • usePlaceOrder
   • orderItemsTotal
   • placeOrder
3. 03

   Two tables, prices snapshotted

   The order is written as pending, in rupees, with payment marked direct — Lokal holds no money. Each line keeps its own name and unit price, so a later price change never rewrites a past order.

   • orders
   • order_items
   • payment_method: 'direct'
4. 04

   Row-level security checks the buyer

   The insert policy requires that the buyer on the row is the signed-in user, and that the business is published.

   • buyer_id = auth.uid()
   • business_is_public

   ▸What it says when it refuses

   Ordering as someone else, or from a listing that is not active, is refused by Postgres itself — whatever the client sends.

5. 05

   …and then the business

   The same policy asks whether this business takes orders at all: its switch is on, it is on the Advanced plan and its subscription is active.

   • business_accepts_orders
   • plan = 'advanced'
   • subscription_status

   ▸What it says when it refuses

   A Basic listing, a lapsed subscription or a seller who has just switched orders off refuses the insert — even from a browser tab opened before the change.

6. 06

   The seller is told, in their language

   A trigger on the new order queues a notification for the seller, rendered from notification_copy in the language on their profile, with English as the fallback.

   • queue_order_notification
   • notify_user
   • notification_copy
7. 07

   Delivery that survives a failure

   The outbox row nudges the push-dispatch Edge Function at once, and a cron job drains anything left every minute. Each row is claimed once, sent to every one of the seller’s devices over FCM and retried up to five times.

   • notification_outbox
   • push-dispatch
   • push-dispatch-drain
8. 08

   Both sides stay in step

   Orders are published over Realtime, so the seller’s list updates live. When the buyer uploads their Juice proof, its timestamp comes from the database clock, not from the phone.

   • supabase_realtime
   • orders_stamp_payment_proof