OPERATIONS FOR FOOD BUSINESSESA BUSINESS DAY JOURNAL 01 / 05

One business day.One clearworkflow.

From the first order to daily closing. Connect your POS, stock, and branch operations in one workflow.

POS · Stock · Operations · Reports

One connected workflowUI illustration · Sample data
Explore the workflowOperations moving together.01 — 05 Sample data
ONE OPERATIONS SYSTEM
POS & ordersBranch stockDaily operationsDaily closingReports

A DAY WITH OWITE

Many moving parts. One connected story.

Follow a day at a sample branch. See how each step leaves a record for what comes next.

Local simulation/Sample dataChoose a step to explore
Start the day01

Start with a clear stock position.

Open a branch stock session to begin operations. This stock informs menu availability at the POS.

Opening stock for the branch business day.
South BranchUI illustration
Branch opening stock
ItemQuantity
Chicken30portions
Tea40portions
Stock session open
Sample business dayOWITE / 01
An order arrives02

Order recorded. Stock updated.

Save an order for two Fried Chicken dishes. The counted chicken item in the menu composition decreases by two portions.

This example is paid in full with cash.
South BranchUI illustration
#001Cash · Paid
Fried Chicken2 × Rp18.000
Rp36.000
Order totalRp36.000
Chicken stock3028
Sample business dayOWITE / 02
During the day03

Each event has its own record.

Keep packaging expenses and ingredient purchases separate. Daily Purchases records purchases; stock additions are managed separately.

Expenses and purchases are different records.
South BranchUI illustration
ExpensesPackaging
Rp12.000
Daily purchasesDaily ingredients
Rp70.000

Expenses and purchases are different records.

Sample business dayOWITE / 03
Service is done04

Check the status. Then close the day.

Close stock, orders, and expenses before closing the branch day. This example has no transfers awaiting receipt.

Outstanding orders are shown as information when closing orders.
South BranchUI illustration
Daily closing checklist
StockClosed
OrdersClosed
ExpensesClosed
Branch day closed
Sample business dayOWITE / 04
Look back05

From the overview to the details.

Explore sales, payments, expenses, purchases, and stock movements for the active branch. Prepare a printed report when needed.

Operational figures remain separate; they are not a profit calculation.
South BranchUI illustration
Branch overview
SalesRp36.000PaymentsRp36.000
ExpensesRp12.000
Daily purchasesRp70.000

Sales and payments are recorded separately.

Sample business dayOWITE / 05

DETAILS THAT WORK TOGETHER

Behind a smooth day, a considered workflow.

Explore the mechanisms connecting your team’s work.

01 /

Every order leaves a trace in stock.

Menu availability follows the counted stock in its composition. Saving an order records the stock movement.

  1. Prepare opening stock

    30 chicken portions inform branch menu availability.

  2. Save one order

    Two Fried Chicken dishes are recorded at Rp36.000.

  3. Deduct counted stock

    Two chicken portions become a recorded sales movement.

  4. Read the balance and history

    28 portions remain, linked to the recorded order.

Explore one business day
28 portions remainingUI illustration · Sample data
02 /

Before closing, see what is still open.

Stock, orders, and expenses each have a closing status. Close all three, then close the branch business day.

  1. Review the business day

    Stock, orders, and expenses each have their own status.

  2. Close stock

    This example has no pending manual transfers.

  3. Close orders

    Outstanding order balances are still shown when present.

  4. Close expenses and the day

    Once all three parts are closed, close the branch day.

Close expenses and the dayUI illustration · Sample data
03 /

Figures have context. Details can be traced.

Read reports for the active branch, explore transaction details, and prepare A4 printouts. Sales, payments, and costs retain separate records.

  1. Choose the branch context

    The overview follows the active branch and selected period.

  2. Explore sales and payments

    Order values and payment amounts are read separately.

  3. Review operational records

    Expenses and purchases each retain their own details.

  4. Prepare the print view

    Bring the overview and selected detail type into A4 format.

owite.

Branch overview

SalesRp36.000
PaymentsRp36.000ExpensesRp12.000Daily purchasesRp70.000
A4 print view
01Sales02Payments03Expenses04Purchases05Internal use06Stock movements07Transfers08Daily closing

ONE BUSINESS, MULTIPLE BRANCHES

A shared catalog. Each branch’s rhythm.

Set menu prices and visibility per branch. Manage team access and record stock transfers between branches.

  1. Choose the destination

    This example moves stock from South to North.

  2. Send five portions

    Origin stock decreases when the transfer is created.

  3. Await receipt

    Manual mode keeps the transfer awaiting receipt.

  4. Receive at the destination

    Receipt adds five portions to destination stock.

Dashboards and reports follow the active branch.

Stock received by the branchUI illustration · Sample data
Fried ChickenSample dataSouth BranchRp18.000North BranchRp20.000

FOR THE PEOPLE BEHIND OPERATIONS

Different jobs. Connected workflows.

Cashiers

Build orders, add notes, and record payments using the branch payment configuration.

Branch managers

Review stock, transfers, expenses, and the closing status of the business day.

Owners & admins

Read branch reports, manage the catalog, and configure access within your permissions.

Access depends on configuration and user permissions.

BEFORE THE NEXT STEP

A few things you might wonder.

01What kind of business is OWITE for?

The workflows shown focus on food businesses such as restaurants, food stalls, and cafés managing menus, stock, and branch transactions. Specific needs should be discussed against the product scope.

02How do orders connect to stock?

Menu availability uses counted stock items in the menu composition at the active branch. Saving an order deducts those items according to the menu composition rules.

03Can it manage multiple branches?

OWITE includes a shared catalog, menu price and visibility settings per branch, user access, and stock transfers. The dashboards and reports shown follow the active branch.

04Do purchases automatically add stock?

Daily Purchases records purchase transactions. Stock movements and additions are managed separately, so a purchase record does not automatically change stock.

05Which reports can I explore?

Branch operational reports include sales, payments, expenses, purchases, internal use, stock movements, transfers, and daily closing. These are not accounting statements or profit calculations.

06Does this example create real transactions?

No. This page is a local simulation using synthetic data and UI illustrations. It does not create production orders, payments, or stock changes.

START WITH THE WORKFLOW

Picture one day at your business.

Explore how POS, stock, and daily closing connect. Discover the workflow behind your team’s day.

081-903-706-506

Menu