Store Sessions: A Manager’s Guide

Share

Oropos

Floor Plan

Cust

Inventory

πŸͺ Store Sessions: A Manager’s Guide to Opening & Closing

Every business day in ORO POS happens inside a Store Session β€” a defined period from when the store opens to when it closes. The session organizes all sales, drawers, tips, employee shifts, and reports into one neat package.

πŸ’‘ In Simple Terms

Think of a store session as a “workday container”. You open it in the morning, all the day’s activity happens inside it, then close it at night. When closed, it generates clean reports for that period and resets everything for the next session.


🎯 What Exactly is a Store Session?

A store session is a recorded operation period with a defined start and end time. While the session is open:

  • πŸ“‹ Servers can take orders
  • πŸ’° Cash drawers + staff banks process payments
  • πŸ‘₯ Employees clock in/out
  • 🍳 Kitchen receives tickets

When the session closes, ORO POS:

  • πŸ”’ Closes all open cash drawers automatically
  • πŸ‘‹ Clocks out remaining employees
  • πŸ“Š Generates reports for the session
  • πŸ“ Locks the period β€” no more sales can be added

⏰ Sessions Can Be Shifts OR Full Days

πŸ’‘ Flexible Timing

A session is not bound to a calendar day. It can represent a single shift, a 24-hour period, or even a multi-day event.

πŸ“Œ Common Patterns

Business Type Session Pattern
β˜• Coffee Shop One session = one full day (6 AM β†’ 9 PM)
🍴 Restaurant with separate Lunch/Dinner Two sessions: Lunch (11–3) + Dinner (5–11)
🍻 Bar (late-night) Session crosses midnight (5 PM Mon β†’ 2 AM Tue)
πŸͺ 24/7 Convenience Store One session per shift (morning / evening / overnight)
πŸŽͺ Festival / Event Vendor One session per event (could be 3 days)

πŸ”„ Visual: Session Lifecycle

πŸŒ…
OPEN STORE
Manager clocks in,
starts session

πŸ’°
ASSIGN DRAWERS
Cash drawers +
staff banks open

πŸ›’
SALES
Servers ring orders,
payments process

πŸ’΅
SETTLE TIPS
Pre-auth + tips,
capture cards

πŸŒ™
CLOSE STORE
Close drawers,
clock out, reports


πŸ“‚ Opening the Store

⚠️ Authorization Required

Only an authorized person (manager / admin / owner) can open the store. Set this in the user type’s permissions.

Step 1: Clock In as Manager

The manager taps “Open Store & Clock In” on the login screen.

Open Store & Clock In screen

Step 2: User Dashboard Prompts to Open

The user dashboard appears with the prompt to open the store.

Dashboard with Open Store prompt

Step 3: Permissions (One-Time Setup)

If the manager doesn’t see “Open Store”, check user-type permissions:

User type Open/Close permissions
πŸ€– Auto-Open Option (Latest Versions)

You can configure ORO POS to automatically open the store on the first employee clock-in, and close at a fixed time. Removes manual steps.


πŸ’° Cash Drawers vs Staff Banks (Important Concept)

πŸ’΅
CASH DRAWER
Tied to a Terminal
Shared by all cashiers
e.g., Cash register at counter
Best for: Counter service

πŸ’Ό
STAFF BANK
Tied to one employee
Server carries cash bag
Deposits at end of shift
Best for: Table service

Aspect πŸ’΅ Cash Drawer πŸ’Ό Staff Bank
Owner Terminal / Station Individual employee
Physical form Cash register at counter Server’s cash bag/apron
Best for Quick-service, counter sales Full-service, table service
Permission Anyone with terminal access Employee needs explicit permission
Reports Per drawer, per session Per employee, per shift
Initial balance Set when opened (e.g., $200 float) Often $0 β€” server collects from sales

πŸ“Œ Step: Assign a Cash Drawer

Assign cash drawer with initial balance
πŸ’΅ Set the Initial Balance!

By default, drawer initial balance is $0. Always set the correct opening amount (e.g., $200 in change for the day).

πŸ“Œ Step: Assign a Staff Bank

Staff Bank assignment
πŸ’‘ Auto-Open Banks

Staff banks can auto-open during clock-in if configured. If a server doesn’t open their bank, payments roll into the main cash drawer.


πŸ›’ During the Session

Once the store is open and drawers/banks are assigned, normal operations begin:

Activity What’s Tracked
πŸ“‹ Servers take orders Tickets, items, modifiers
πŸ’³ Cards processed Pre-auths held, transactions logged
πŸ’° Cash collected Goes to drawer or staff bank
πŸ‘₯ Employees clock in/out Hours worked, payroll data
🍳 Kitchen prep KDS or printer tickets

πŸŒ™ Preparing to Close

πŸ“‹ Pre-Close Checklist

Before pressing the big “Close Store” button, complete 4 things in order:

  1. πŸ“ Adjust pre-auth tips and capture credit cards
  2. πŸ’΅ Pay out tips to employees
  3. πŸ”’ Close all cash drawers + staff banks
  4. πŸ‘‹ Force-clock-out any employees still on the system

πŸ’³ Pre-Auth Tip Adjustments & Card Capture

πŸ’‘ What’s a Pre-Auth?

When customers swipe their card before adding a tip, ORO POS does a pre-authorization β€” holding the bill amount but not capturing it yet. After the customer writes in a tip, the manager finalizes (captures) the total with the tip included.

πŸ“Œ Real Example: Restaurant Dinner

Step Action
7:30 PM Customer dinner total: $80. Card swiped β†’ pre-auth $80
7:35 PM Customer signs receipt with $15 tip β†’ bill = $95
10:30 PM Manager closing β†’ enters $15 tip into ORO POS β†’ captures $95
10:32 PM Card processor finalizes $95 charge β†’ money settles to bank

Without this step, the original $80 hold expires and the tip doesn’t get processed.

Tip adjustment screen

πŸ’΅ Tip Pay-Out

After capturing pre-auths, pay tips to employees from the clock-in screen:

Tip pay-out screen
πŸ’‘ Why Pay Tips Before Closing?

If you skip this step, the Tips Differential in your session report will show unpaid tips. Best practice: pay tips daily so it always shows $0.


πŸ”’ Closing Cash Drawers & Staff Banks

Manager checks the Store Status page to see what’s still open. If any drawer or staff bank is open, close them one by one.

Closing a Cash Drawer

Close cash drawer button
Cash drawer closed report

Closing a Staff Bank

Each server declares their tips and deposits cash when closing their bank.

Close staff bank screen
πŸ’‘ Why Each Closes Separately?

Each drawer / bank produces its own report. This way you can see:

  • How much each terminal handled
  • Each server’s sales + tips + cash deposited
  • Discrepancies between expected vs actual cash

πŸ“Œ Real Example: Server Cash Deposit

Sarah’s shift summary:

Item Amount
Total cash sales (8 tables) $420.00
Cash tips collected $45.00
Card tips declared $80.00
Cash to deposit $420.00
Cash tips to keep $45.00

Sarah hands $420 to the manager β†’ bank closes β†’ manager prints her report.


πŸ‘‹ Clocking Out Employees

Notify all employees to clock out. If anyone forgot, manager can force-clock-out.

Clock out employees
⚠️ Manager Stays Clocked In

The manager closing the store should NOT clock out yet β€” they need to be the last one to do so, after the store is closed.


πŸŒ™ Closing the Store (The Big Button)

βœ… Final Checks Before Closing

  1. All tickets closed (no open tabs left)
  2. All pre-auth credit cards captured
  3. All drawers + staff banks closed
  4. All employees clocked out

Once everything’s done, click Close Store from Store Status.

Close Store button

The session closes. ORO POS generates the Session Summary Report.

Session closed confirmation
πŸ“Š What the System Does Automatically

  • πŸ”’ Forces close any drawers still open
  • πŸ‘‹ Clocks out any remaining employees
  • πŸ“Š Generates session-wide reports
  • πŸ“ Locks the period β€” no more sales can be added
  • πŸ”„ Resets for the next session

πŸ” Multi-Session Days

πŸ’‘ Same Day, Multiple Sessions

Some stores run multiple sessions in a single day (lunch + dinner, or three shift rotations). Each session generates its own reports independently.

πŸ“Œ Restaurant Example: Lunch + Dinner

Time Event
10:30 AM Open Lunch Session
11 AM – 3 PM Lunch service
3:30 PM Close lunch session β†’ Lunch Report generated
5:00 PM Open Dinner Session (employees re-login)
5 PM – 11 PM Dinner service
11:30 PM Close dinner session β†’ Dinner Report generated

Result: Two separate reports (Lunch / Dinner) for the day. Owner can compare lunch vs dinner performance.


πŸ’Ό Real-World Scenarios

πŸŒ™ Late-Night Bar (Crosses Midnight)

Bar opens at 5 PM Friday, closes at 2 AM Saturday. Session covers the entire shift even though it crosses midnight. One session = one report.

πŸͺ 24/7 Convenience Store

Store never closes. Use shift-based sessions: morning, afternoon, overnight. Each shift = own session = own report. Cash drawer reset between shifts.

🍴 Restaurant with Server Banks

5 servers, each with a personal staff bank. Each server closes their own bank at end of shift, deposits cash + declares tips. Manager closes the store after all banks are reconciled.

β˜• Coffee Shop (Single Session)

Opens 6 AM, closes 9 PM. One drawer, no staff banks. Manager opens in morning, closes at night. Simplest pattern.

πŸŽͺ Festival Vendor (Multi-Day Event)

3-day food truck festival. Open session Friday 4 PM, close Sunday 10 PM. One big session covers the entire event for unified reporting. Or 3 sessions (one per day) for daily breakdowns.


⭐ Manager’s Best Practices

Tip Why
Always set correct opening drawer balance Wrong start = wrong “expected vs actual” report
Capture pre-auths before closing Otherwise tips don’t get charged
Pay tips out same day Keeps Tips Differential = $0
Close ALL open tickets before closing store Open tickets create Receipt Differential
Use staff banks for table service Per-server accountability
Use cash drawer for counter service Multiple cashiers share the till
Manager clocks out last Need permission to be active until close
Verify physical cash matches reports Identify discrepancies same day

πŸ“š Related Guides

πŸ”— Continue Learning
β†’ Session Summary Report β†’ Differentials Explained β†’ Configure Cash Drawer

πŸ“ž Need More Help?

Was this artical helpful?