Stock cost and the week page on Rasoi

Rasoi is the kitchen desk at rasoi.lawazia.tech. The cook opens stock. The admin opens a week. A customer logs in and sees the family seats on that account. Four profiles already name the pieces they changed: the stock cost, the week and the tiffin balance, the week page and the seat list, and the purchase price with the barcode and the scanner.

Stock, weeks, and seats

A stock card is one bought item. Pack quantity is how much came in that pack. Purchase cost is what was paid for it. On 15 October 2026 the Rasoi stock page started showing that total cost, and the API that lists stock started returning the same cost on the list of every row. Varsha Kumari's profile says pack quantity and total purchase cost on the stock cards and in the stock table. The card and the table are two views of one row. The number on the card is the number in the table.

The admin speaks in weeks. Atul Kumar Rawani's profile says week numbers on the admin, and the tiffin balance API for a family seat. On 8 October 2026 the web repo gained tiffin counting. On 9 October 2026 the API update was the tiffin cycle for a family seat. A family seat is one place on the kitchen's list. The balance is how many tiffins that seat still has. A week number is how the admin opens that week as a page.

Habiba Yashmin's profile says the week page on the admin, and a customer login that shows every family seat. Her web commits through 12 October 2026 cover pause and resume, and buttons sized for a smaller screen. The profile sentence is the record of the week page and of the seat list after login.

Om Kumar Choubey's profile says the stock purchase price on create and update, the barcode field on stocks, and the kitchen scanner. The price is a field when the stock row is created, and the same field is there when the row is updated. That stored price is what the stock card later shows. The barcode is a field on the stock. The scanner reads the code so the person at the shelf does not type it. On 17 October 2026 the API also gained an office route that syncs kitchen spend. That route is office sync. The profile line is the price, the barcode, and the scanner.

Pack quantity, purchase cost, and the stock table.

Who changed it

Read the four lines as one kitchen day, and keep each sentence on the person who wrote it.

Someone creates a stock row. The fields Om's profile names are the purchase price and the barcode. Saving the row stores both. Opening the row later is the update, and the price is still that field. The scanner is how the barcode gets in when the code is in front of the person. After that, the stock list is the data from the list endpoint. Varsha's card draws the pack quantity and the total purchase cost from that data. The table draws the same columns. Her profile and his profile are the read path and the write path of one number.

The admin opens a week by its number. That page is the week page on Habiba's profile, and the week numbers are the labels on Atul's profile. On that page, family seats are the rows a person works through. The tiffin balance is the remaining count for one seat, read through the API his profile names. When a customer logs in, the screen lists every family seat on that login. A login with one seat shows one. A login with several shows several. The balance call then answers for a seat on that list.

A cook checking stock in the morning reads the pack and the cost before the kitchen buys the item again. An admin checking the week reads the seats and the balances before the round goes out. A customer sees the seats on their own login. The figures on this page are labels for those screens. They are a diagram, with the words the profiles already use. Prices and seat counts stay on the app, where the kitchen typed them.

Week page, family seat, tiffin balance, and the scanner.

Reading the four lines together

A company looking at four profiles can lose the order. Varsha's line is the number a cook reads on the card and in the table. Om's line is the number a cook writes, plus the barcode the scanner fills. Atul's line is the week label and the balance call for one seat. Habiba's line is the week page and the list of seats after login. Read in that order, the kitchen day holds together: write the stock, read the stock, open the week, see the seats, read a balance. The live app is where those screens sit. This page is the map of which profile owns which sentence.

What you can open

Pack quantity and total purchase cost on the stock cards and the stock table.

Open Rasoi

The date on this note is 15 October 2026, the day the stock cost display landed in the web repo and on the stock list API. Atul's tiffin counting is 8 October 2026, and the family-seat cycle is 9 October 2026. Habiba's admin button work runs through 12 October 2026. The office spend route is 17 October 2026, and it is named here so a reader can tell it apart from the purchase price on the stock form.

Open the live app and look at a stock card and the stock table. The profile says both show pack quantity and purchase cost. Open an admin week and look for week numbers and the seats. Open a customer login and look for every family seat on that account. The scanner sits on the barcode field. If a screen has moved since these days, the profile sentence is still the record of what that person changed.

Rasoi is Ambika's kitchen desk. This note adds no second client and no placement. The proof is the live app and the four sentences already stored on the profiles.