RonOS is installed and open, but it needs a connection to load your data. It'll reconnect automatically the moment you're back online — no need to do anything.
Set up your food business and its administrator account. You can add your team afterwards.
You were invited to set up your business on RonOS. Fill this in and it is yours — the link works once.
Already have an account? Sign in
First-time setup: create the administrator account. You can add encoders and approvers afterwards.
That address is wrong — change it
Let's set up your company. You can change these anytime in Settings.
Pick one. We'll open just that, so there's less to learn. Everything else is one click away in Settings whenever you want it.
A branch, an outlet, a commissary — anywhere you keep stock or people.
Your main place is already set up. Name the others:
How do you want your spending split up? Pick the areas you would want to see on a report — you can add more later.
We’ll set up just these, so your forms aren’t full of methods you never use.
The places you’d actually count at the end of a day.
If you already keep a payroll sheet, send it over and we will read it — whatever shape it is in. You will see exactly what we found before anything is saved.
These are staff records — the people you pay and who clock in. They are not sign-in accounts, and nobody imported here can log in.
Count what is in each place and type it in. Without this the app starts you at zero, and closing your first day will ask you to explain a difference the size of your whole float.
Leave any of them blank if you don’t know yet — we will ask again before your first day close. A blank one is left unset, never recorded as zero.
Your account is ready to use. This is what is in it right now.
Your account is ready. One last thing that will save you hours: photograph a few receipts you already have, and we will work out what you buy and what it costs. Don't tidy them up — messy is fine.
Already keep a list?
Bring your spreadsheet straight in and match your own columns to ours — you will see exactly what we found before anything is saved. It just needs a column of item names, headed something like Item, Name, Product or Pangalan.
Reading a spreadsheet uses none of your free receipt reads.
You can do this any time from Expenses → Items.
We will set each person up with the right access. You can change any of it later in Settings.
Who approves receipts and spending?
They can see what has been spent and approve it. They cannot change your company settings.
We fill this in from their name — change it if you would rather. Leave the name blank to skip this person.
Who records receipts day to day?
They write down what was bought. Someone else approves it.
We fill this in from their name — change it if you would rather. Leave the name blank to skip this person.
⚠ You are choosing their password, so you will need to pass it on to them. They can change it once they sign in.
Jump through the sample business while you present.
| Item | Status | Category | Department | Type | Std ₱ |
|---|
| Item | Supplier | Category | Department | Type | Unit | Std ₱ |
|---|
| Item | On hand | Reorder at |
|---|
| Item | On hand | Last move |
|---|
| Sold on the menu |
|---|
| Date | Made | Expected | Actual | Variance | Why | By |
|---|
| Date | Item | Move | Reason | By |
|---|
Pick what you cooked and how many batches. RonOS takes the ingredients out of stock and puts the finished item in — and asks why if the amount you actually made isn't what the recipe expects.
Tick the POS products you physically keep in stock (bottled drinks, retail goods…). They join the Item List as stock-tracked and show in Inventory right away — classify them for expense reports later in Expenses → Items. Cooked dishes usually don't belong here.
Tick the people you schedule. Your grid, "Copy week → next" and cell edits then cover only your team. Untick everyone to see the full Schedule again (HR and admins always keep full access elsewhere).
| Employee | Days | At stake | Decided |
|---|
| Employee | Days | At stake | Decided |
|---|
| Date | Move | Reason | By |
|---|
| Site | Sales | Cash on hand | Labour cost | Profit |
|---|
| Category | Qty | Net |
|---|
| Item | Source | Priority |
|---|
| When | Activity | Module | User |
|---|
Choose which cards and sections everyone in your company sees on the Dashboard.
| Task | Due | Priority |
|---|
| Task | Due | Priority |
|---|
| Task | Assignee | Due | Priority | Status |
|---|
| Date | Title | Attendees | Status |
|---|
| File | Category | Size | Uploaded |
|---|
Encode the down payment to confirm this booking and add it to the calendar.
The menu the customer finalized for this event. Start typing an item to pick from your Recipe & Costing menu (price auto-fills), or type anything. Price is optional.
Approved receipt items typed ASSET that aren't in the register yet. Pick one to prefill the asset form — you add the useful life.
How much is close enough, in your numbers. Leave a box empty to use the built-in figure — a shop doing ₱2M a month and one doing ₱200k don't share a "close enough".
Send this to your team (e.g. in your group chat). They open it on their phone, type what they need in their own words, and it arrives here as a pending request — no account needed. Nothing is ordered until someone approves it.
Share this link with new staff (e.g. in Messenger). They fill in their own details — contact info, government IDs, emergency contact — and set their clock-in PIN. They arrive as Inactive; review the profile in Employees, then Activate to enable payroll and the time clock.
Share this link with customers (e.g. in Messenger). They fill in their booking details on their phone — it arrives here as a Pending reservation for you to review and confirm.
Give this link to other teams to subscribe in Google Calendar — confirmed bookings show up and stay updated. In Google Calendar: Other calendars → + → From URL → paste the link → Add calendar.
| Date | Supplier | Department | Encoder | Total | Status |
|---|
| # | Item description | Category | Subcategory | Department | Type | Qty | Unit | Unit price | Total |
|---|
| Date | Supplier | Department | Type | Items | Total | Payment | Status |
|---|
| Date | Supplier | Department | Type | Items | Total | Encoder | Status |
|---|
| Category | Amount | Share |
|---|
| Department | Amount | Share |
|---|
| Payment type | Transactions | Amount | Share |
|---|
| Wallet | Transactions | Amount | Share |
|---|
| Site | Transactions | Amount | Share |
|---|
One classification, applied to every item you ticked, and all of them approved. Any receipt held on these items is released straight away. Use this when the items genuinely share a classification — anything else, classify it on its own.
This classification becomes the single truth for the item — every receipt line with this name uses it automatically.
Merging keeps the item with the most history and removes the rest. Past receipts stay untouched; any Inventory stock moves to the kept item. Review each group before merging — Similar mode can group items you'd rather keep apart.
Read-only. Upload your BDO / GoTyme / GCash statement (CSV or Excel) — RonOS checks its money in/out against what you recorded for this wallet and flags anything in the bank but not encoded. Nothing is changed.
Enter what you physically counted for each item. Saving posts a Count adjustment so on-hand matches your count (over = added, short = shrinkage) and keeps the count as a record.
| Item | System | Counted | Variance |
|---|
For each bank/e-wallet account, enter the closing balance printed on the statement for the month. RonOS shows its own month-end figure and the difference — a ₱0 difference means your books match the bank. Marking it reconciled records the sign-off; a bank account must be reconciled before the month can be closed.
Set the % targets that color the health chips — these are your own goals. The defaults are common F&B rules of thumb. Applies to everyone in your company.
Present revenue in your own lines (e.g. Restaurant, Golf, Bar) instead of the POS categories. The total must equal POS net sales for the period to save.
Build a recipe from your ingredient list. Lines priced in grams/ml re-cost live off the Ingredient Prices tab; pick an ingredient and enter the amount used per serving.
| Ingredient | Amount | Unit | Cost ₱ |
|---|
Packaging, selling price and margin are set per dish in Menu Manager — a recipe here is just a costed building block.
These are the COGS line-items encoded in Expenses (each at its most recent purchase price). Tick the ones to add as costing ingredients — items you already have are pre-unticked. The price, unit and a suggested category are pre-filled; adjust anything on the Ingredient Prices tab afterward.
| Item | Price ₱ | Unit | Category |
|---|
Consolidate one or more recipes into a sellable dish. Its food cost is the sum of the recipe costs (× quantity) and updates live as recipe/ingredient prices change. Set the packaging and selling price here to see the food-cost % and gross margin.
| Recipe | Qty | Unit | Cost ₱ |
|---|
| Employee | Days | Late+UT (min) | OT (hrs) | OT pay | COLA | Night (hrs) | Night pay | Late/UT deduct |
|---|
| Employee | Cash Advance | AR | Loan installment |
|---|
PDF or Word (.doc/.docx), up to 10 MB.
The AI drafts the document grounded in the company documents you tick below. Review before issuing.
| Date | Type | Category | Channel | Wallet | Description | Amount | Encoder |
|---|
Day sub-totals exclude transfers between wallets and pending receipts. Wallet balance appears on the last row for each wallet and day.
| Wallet | Beginning | In | Out | Ending | Counted | Variance |
|---|
| Type | Description | Wallet | Amount |
|---|
| Date | From | To | Amount | Encoder |
|---|
No costing data yet. Add your own ingredients with their market prices — or pull them straight from your approved COGS purchases (the "From Expenses (COGS)" button on the Ingredient Prices tab) — then build recipes and dishes to see your true food cost.
| Ingredient | Market ₱ | Qty | Unit | Category | Waste % | Cost Price ₱ | Cost / unit ₱ |
|---|
| Item | Cost | SRP | FC % | Charges | True Cost | Net Margin |
|---|
| Name | Status | Kiosk link | Geofence |
|---|
| Date | Name | Type |
|---|
The 5 built-in roles have special behavior (admin = full access; cashier = cash inflows only; approver = can't approve own receipts). You can add your own custom roles here, then grant what they can access in the Role permissions panel below. A new role starts with no access until you grant it.
⚠ Only the built-in admin role can manage users and settings. A custom role cannot open Settings → Users, change anyone's role, reset a password or read the audit log — however many sections you tick for it, and whatever you call it. Keep at least two people on the built-in admin role: if your only administrator loses access, nobody inside the app can restore it.
| Role | Type | Users |
|---|
admin role has it.
| Name | Username | Role | Status |
|---|
| When | Who | Action | Details |
|---|
Groups classify your categories (COGS, OPEX, Salary…). Groups marked not an operating expense (e.g. ASSET, CREDIT PAID) are kept out of the expense P&L total in Reports.
| Group | Counts as expense? |
|---|
| Category | Subcategories |
|---|
| Department |
|---|
| Unit |
|---|
| Payment type | Cash flow | Wallet | Sites Each branch sees only its ticked types |
|---|
| Wallet | Type | Site |
|---|
| Category | Type |
|---|
| Supplier | You owe |
|---|
| Employee | Owes |
|---|
| Date | Customer | Amount | GCash ref | Receipt |
|---|
| Customer | Contact | Owes you | Oldest utang | Pending |
|---|
| Supplier | Bill date | Amount | Status |
|---|
| Due date | Status | Supplier | Payment type | Bill date | Amount |
|---|
| Paid on | Supplier | Reference | Payment type | Bill date | Amount | Paid via |
|---|
| Supplier | Every | Next due | Amount | Status |
|---|
| Site | Sales | Costs | Profit | Margin |
|---|
| Asset | Acquired | Cost | Salvage | Life (mo) | Dep / month | Accum. dep | Book value | Status |
|---|
| Date | Ref | Memo | Debit | Credit | Balance |
|---|
| Code | Account | Type | Debit | Credit |
|---|
| Month | Closed by | On |
|---|
| Code | Account | Type | Description | Status |
|---|
| Cash flow category | Type | Posts to |
|---|
Answer for the day your books began. Skip anything that doesn't apply (leave it blank or 0). Whatever's left over is automatically recorded as Owner's Capital — what's yours.
| Date | Type | Details | Amount |
|---|
For adjustments only (opening balances, corrections, accruals). Debits must equal credits — the entry can't post otherwise, and once posted it can only be reversed, never edited.
| Request | Items | Est. total | Needed | Requested by | Status |
|---|
| PO # | Supplier | Items | Total | Order date | Status |
|---|
| Date | Employee | Event | Details |
|---|
| Name | Position | Department | Site | Pay rate | Frequency | Hired | Status |
|---|
Set once, then it stays out of the way. All six sections below are saved together by the one button at the bottom.
The hours late, undertime and overtime are judged against when you Apply to payroll.
What a late arrival and an early finish are worth is your house rule, not ours. These change only how minutes become pesos — never how the minutes are measured.
Extra pay for hours worked late at night, on top of what the hour already earns. It is off until you switch it on.
How much of the monthly SSS / PhilHealth / Pag-IBIG contribution each cutoff collects.
The kiosk can photograph each punch for audit (no face recognition). Photos delete themselves after the retention window.
This covers both the supervised in-app pad and an unattended public kiosk tablet. At either one, a person can set a PIN for a listed name that has none; the public tablet is weaker proof of identity, especially when punch photos are off. An existing PIN can never be changed or reset at either pad.
| Shift | Start | End |
|---|
| Employee | Punch | When | Why it's here | Photo |
|---|
| Employee | Department | Site | Time In | Time Out | Status |
|---|
| Employee | Type | Dates | Days | Status | Reason |
|---|
| Employee | Leave type | Entitlement | Used | Remaining |
|---|
| Leave type | Default days/yr | Pay |
|---|
| Employee | Cash Advance | AR | Loan | Total owing | Entries |
|---|
| Date | Employee | Type | Kind | Amount | Description |
|---|
| Employee | Monthly salary | SSS | PhilHealth | Pag-IBIG |
|---|
| Issued | Document | By |
|---|
| Uploaded | Document | Category | By |
|---|
| Name | Position | Days | Rate | Allow. | SC | Incent. | OT | Gross | Deduct. | Net | Channel |
|---|
| Employee | Basic salary earned (year) | 13th month pay |
|---|
| Site | People | Days | Hours | Absences | Late + undertime | Overtime | Labour cost |
|---|
| Company | Plan | Last activity | Receipts | Cash | Bookings | Setup | AI today |
|---|
Tracking started 11 September — customers who set up before then are not counted here.
| Company | Status | Users | Sites | Created |
|---|
| Plan | ₱ / month |
|---|
| Company | Plan | Price | Discount | They pay | Active users | Est. cost | Margin | Margin % |
|---|
| Company | Source | AI | Calls / limit | Input | Output | Total / limit | In flight | Unknown | Failures | Status | Limits |
|---|
| Category | Qty Sold | Gross | Discounts | Net Sales |
|---|
| # | Item | Category | Qty | Sales |
|---|
| Item | Category | Qty | Sales | Last Sold |
|---|
| Site | Sales | Transactions | Refunds | Share |
|---|
| Till | Receipts | Last sale | Site |
|---|
| Date | Time | Receipt # | Store | Items | Payment | Subtotal | Discount | Total |
|---|
| Date | Site | Total |
|---|
| Item | Category | SKU | Price | Qty Sold | Total Sales | Last Sold |
|---|
| Category | Items Sold | Qty Sold | Total Sales | % of Sales |
|---|
| Payment Method | Transactions | Total Amount | % of Sales |
|---|
| Date | Receipt | Amount | Assign to |
|---|
| Date | Type | Processed | New | Updated | Status | Duration |
|---|
| Date | Event | Details | By |
|---|
| Date | Period | Rating | Reviewer | Summary |
|---|
| Date | Category | Severity | Status | Description |
|---|
{{placeholder}} inserts escaped text, {{{block}}} inserts a formatted block,
and {{#if key}}…{{/if}} makes an optional section.
| Date | Type | Kind | Amount | Description |
|---|
| Item | Qty | Unit | Unit ₱ |
|---|
Type what actually arrived. If a line is short, say why — the balance stays owed and the order stays open until it comes.
| Item | Ordered | Already in | Still owed | Arriving now |
|---|
Items on your approved Item List keep their own classification; these defaults cover the rest.
| Item | Qty | Unit | Est. ₱ |
|---|
| Your column | Sample values | What it is in RonOS | Match |
|---|
Every imported item is approved immediately so staff can pick it. Category, department and expense type are therefore required. A value in the row wins; the default fills only a missing or blank value.
| Row | Action | Item | Category | Subcategory | Department | Type | UOM | Std ₱ | Status |
|---|
Reopening lets this cutoff be edited again. Going back into a cutoff that has already collected is how a cash advance gets taken twice, so this is recorded: who reopened it, when, and why.
This adds new people and updates matching names. A blank cell leaves the saved value alone; removing a row never archives anyone. Clock PINs and photos cannot be imported. For SSS, TIN, PhilHealth and Pag-IBIG, numeric Excel cells are refused because Excel has already discarded leading zeros; format those columns as Text and re-export.
| Your column | Sample values | What it is in RonOS | What will happen |
|---|
| Row | Action | Name | Position | Department | Monthly salary | Pay rate | Allowance | COLA per day | SSS | TIN | PhilHealth | Pag-IBIG | Phone | Address | Birth date | Hire date | Bank name | Bank account no. | Employment status | RonOS status |
|---|
This is your Dashboard — your business at a glance. Come back here anytime to see how things are going.
Nine questions in three short steps, so attendance and payroll match how you actually run things. Every question can be skipped — leave anything on “skip” and that setting is not touched at all. You can come back from ⚙ Work hours any time.
This decides how much of the monthly SSS, PhilHealth and Pag-IBIG each payday collects. Only the number of paydays matters, never the dates.
Hours past the end of a normal day, once that day's overtime is approved. The rate multiplies the hourly rate.
A premium on hours worked inside your night window. Off unless you say otherwise.
What late, undertime and overtime are judged against. A scheduled shift, or an employee's own hours, still takes priority over these.
Minutes of leeway before an arrival counts as late, and before an early finish counts as undertime.
Your house rule, not ours. This changes only how minutes become pesos — never how the minutes are measured.
The time clock can photograph each punch for your own records. There is no face recognition of any kind, and photos delete themselves after your retention window.
Only do this standing at the workplace. It uses this device's current location as the centre, so setting it from home or another office will lock your staff out. Skipping is completely fine — the clock then works from anywhere, which is how it behaves today.
Printed on the documents RonOS generates. Leave blank for a blank signature line.
Anything you skip keeps working exactly as it does now, and everything here can be changed later from ⚙ Work hours.
Seven questions in three short steps, so the booking form matches how you actually take bookings. Every question can be skipped — leave anything on “skip” and that setting is not touched at all. You can come back from the Customer link panel any time.
Add one to start — a function room, a garden, a whole floor. You can add the rest from ⚙ Areas.
Customers pick from the times you offer instead of typing any time they like, and each time takes only as many parties as your kitchen can plate.
Customers cannot book it. Staff still can — they take the phone call that makes a closed day an exception.
The public form refuses less than this. Leave it skipped and any amount above zero holds a booking, exactly as now.
Pick one method and write what the customer should do. Both together — a method with no instructions shows a heading with nothing under it, so it is refused.
One rule per line. Customers tick to agree before the form will send, and the rules print on the Banquet Event Order. Skip it and the form submits straight through, as now.
Customers open it with no login and send you a booking request.
Customers can pre-order food on the booking form. By default they see your whole menu; to offer only part of it, use 🍽 Choose menu items on the Customer link panel. Nothing to answer here.
Anything you skip keeps working exactly as it does now, and everything here can be changed later from the Customer link panel.
Leave any of them blank if you don’t know yet — a blank one is left unset, never recorded as zero.
| Employee · debt | Planned | Collected | Not collected |
|---|
Posting records what is collected in the staff ledger as repaid.
| Date | What it was | Amount |
|---|
| Site | Amount | Share |
|---|
| Category | Amount | Share |
|---|
| Item | Amount | Site |
|---|