Book a demo

CLOSE / PROFITABILITY & COSTS

CLOSE THE SHIFT.CHECK THE DETAILS.

A planned profitability and costs agent for end-of-day review. Bring sales, payments and available cost records together without treating every total as the same thing.

Planned / Coming soon No live or pilot release confirmed.

Two restaurant supervisors comparing till cash, receipt records and payment totals after service
“What still needs checking before we close?”

The till is closed. The numbers still need a second look.

Sales, collected payments, refunds, cash counts and bank settlements can differ for good reasons. Close is designed to make the differences visible and flag the checks that still belong to your team.

CHECK WHAT WAS SOLD.CHECK WHAT WAS COLLECTED.

Start with your restaurant’s profitability & costs work. Close is planned to help your team check the records, prepare a useful next step and review the result. Available modules and actions need confirmation for your venue.

Prepare the close review

Summarise the recorded sales, payment types, refunds and unresolved items for the selected service window.

Bring exceptions forward

Identify missing cash counts or unsettled records instead of hiding them inside one reassuring total.

Explain the cost boundary

Use recipe, stock and other cost records where available; make clear when the information is not enough to establish profit.

FOUR QUESTIONS FOR CLOSE

BEFORE YOU LOCK UP.ASK CLOSE.

Choose a sample chat. Check its records, review the next step, or use STOP. Nothing connects to or changes a real restaurant.

CHOOSE A RESTAURANT JOB

These examples use sample data. Nothing is sent to a restaurant or changed in ERPFY.

Ask ERPFY / CloseINTERACTIVE EXAMPLE
  1. Ask
  2. Check
  3. Preview
  4. Done & logged

What still needs checking before we close?

CLOSE

The right specialist picks it up.

Close would check the connected restaurant records before answering. Start with the example data below.

  • Sales, payments and refunds
  • Cash and settlement records
  • Available cost records

THE RECORDSBEHIND THE ANSWER.

Close needs the right information, not access to everything. These are the proposed inputs; a module listed here is not proof of a live connection.

Sales, payments and refunds
Recorded transactions, service windows and payment states without sensitive card information.
Cash and settlement records
Verified cash counts and settlement records where connected, kept distinct from sales.
Available cost records
Recipe costs, stock movements and other costs actually recorded for the venue.

THE PROPOSED APPROVAL BOUNDARY

READ THE RECORDS.REVIEW THE CHANGE.

Reading, preparing and acting are different permissions. The live role controls and supported actions need confirmation during setup.

Read what is permitted

Read financial reports allowed by the operator’s role.

Review before acting

Sharing close notes or making any supported adjustment needs the relevant review. A sample approval does not post an accounting entry.

Keep the human responsibility

Your team owns final reconciliation, financial decisions and accounting review; missing costs must never be invented.

PLANNED / COMING SOON

INTERESTED INCLOSE?

Tell us where this job could help your restaurant. The ERPFY team will discuss timing, required records and supported actions before any pilot or live access is confirmed.

Register interest

This opens the contact form with Close in your enquiry. It does not activate an agent or confirm a place in a pilot.

Before you get started

BEFORE YOU ASKCLOSE.

START WITH THE JOBYOUR TEAM NEEDS HELP WITH.

Bring us your restaurant’s profitability & costs questions. Let’s discuss what Close would need to work well for your venue.

Register interest