Systems

CrunchTime + Brink + Olo + ADP

If your stores run CrunchTime for the back office and scheduling, Brink at the register, Olo for online ordering and ADP for payroll, the costly problems often sit between the systems: hours that don't match, a pay rate that drifted, someone who left but can still clock in. Poros Ops reads all four and checks them against each other, store by store. It starts read-only.

Where the four meet

Each check below ties one of these systems to another and tells the right person what doesn't line up. They only read, unless the card says otherwise.

CrunchTime · Brink · ADP

Hours, three ways

A completed pay week's hours per person and store: CrunchTime's time clock against Brink's timecard and ADP. Mismatches, people missing from a system and duplicates are listed for the owner.

CrunchTime · ADP

The hours that reach payroll

A check that your CrunchTime-to-ADP link landed each company's hours in ADP's open payroll cycle, matching CrunchTime to 0.01 hour and the cent.

CrunchTime · ADP

Pay rates in step

Every week, each active employee's rate in CrunchTime against every active ADP position: differences over a tolerance, missing rates and people in one system only. It never changes a rate.

ADP · CrunchTime · Brink

People changes followed through

Every hour, each hire, termination, pay change, new title or new home store in ADP is watched until CrunchTime shows it, and each hire or termination until Brink does. Someone terminated who is still active on the POS, and could still clock in, is flagged.

CrunchTime · ADP · Brink

One person, one record

Once a day, every person lined up across the back office, payroll and the POS: in payroll but not the back office, no active POS profile, or two POS profiles for one person.

CrunchTime · Olo

86 by ingredient

Every week, CrunchTime's recipes are mapped to Olo's products and add-ins, so one approved "86 oat milk" takes every item made with it off online ordering at the stores you choose, each change read back. Anything it can't place is listed, never guessed.

Brink · CrunchTime

From the drawer to the deposit

Every night, Brink's till history, who had the drawer and its over/short, joined to CrunchTime's daily over/short and logged deposit. Connect your bank too, and each logged deposit is matched to what the bank shows.

CrunchTime · ADP

The payroll week on one board

Per store: labor and inventory posted in CrunchTime, the hours cross-check, the hours in ADP and ADP's run state, with what is blocking. Approval stays with you.

Within each system

CrunchTime

  • Midday labor pulse and overtime watch
  • Missed clock-outs, and time clock fixes you approve
  • A weekly labor-law and break sweep from actual punches
  • Next week's schedule pre-drafted from your forecast, and a publish check
  • Order status before each cutoff, and truck orders drafted from usage and pars
  • Inventory count checks, and corrections you approve
  • Weekly rollup, labor scorecards and a monthly P&L in your franchisor's line format

Brink

  • Who is clocked in, every 15 minutes in business hours
  • A monthly price and tax audit across every store
  • New, gone and renamed items, every week
  • Your franchisor's approved prices, pushed to every store once you approve the plan, and checked
  • Voids, discounts and promos per employee, every week
  • A monthly sales-tax workbook by filing entity

Olo

  • What is 86'd online, and for how long
  • Menu drift: new, gone and renamed products
  • Online hours checked three times a day against your store hours, holiday hours and closures

ADP

  • The employee roster, merged with CrunchTime's every day
  • Registration reminders until a new hire is set up
  • Paystub and sign-in help for employees
  • Transfers and rehires without duplicate records

The full list is on the automations page.

What it can write, and only when you say so

Nothing on this list writes until you switch it on, and every write is read back from the system before it counts as done:

  • CrunchTime: time clock fixes and count corrections you approve; an approved truck order saved as not sent, never submitted; an approved schedule saved as a draft, never published.
  • Brink: a new hire's clock-in PIN, inside the onboarding steps you switch on; your franchisor's prices, once you approve the exact plan.
  • Olo: an item 86'd or brought back, or a day's online hours changed, each approved by you, after a signed opt-in.
  • ADP: transfers and rehires without duplicate records, and terminations from signed forms, each sent only after you approve it. Poros Ops never calculates, approves or runs payroll.

Each automation has its own switch and runs in shadow mode first, logging what it would have done while nothing changes. Every write is logged: who asked, what changed, and what the system read back. More in Shadow mode: how to trust automation with your stores.

Which package reads which system

CrunchTime is the first connection on every package. Brink comes with Operator, and Olo and ADP with Custom, so most of the checks between systems on this page are on Custom. See packages and pricing.

How access works

  • Agreement first. We ask for access only after a written agreement is signed.
  • Your account, your user. You create a read-only user for Poros Ops inside your own CrunchTime, Brink, Olo and ADP accounts. You own each one and can remove it at any time.
  • Your vendors' terms. Some vendor agreements need the vendor's written OK before a service provider has a user. For Brink, please confirm your agreement allows one.
  • Writes are approved one at a time. If you later switch on an automation that writes, the access it needs is set up with you then, for that automation only. Approving one does not approve the rest.
  • Never passwords by email. Don't send passwords or account numbers through email or our forms. Access is set up with you, inside your account.

Questions

Do I need all four systems?

No. Each automation needs only the systems it reads. CrunchTime alone is enough to start, and the checks between systems switch on as each one is connected.

Does it replace the integrations between them?

No. It checks that what your integrations move actually arrived: CrunchTime's hours in ADP's open payroll cycle, each ADP change in CrunchTime, and each hire or termination on the POS.

Will it change anything in ADP?

Only what you switch on. Transfers, rehires and terminations are each drafted for your approval and read back from ADP. It never calculates, approves or runs payroll.

See it on your stores

If you'd like to see how these checks would run across your locations, we're happy to show you.

Book a walkthrough

CrunchTime, Brink, Olo and ADP are trademarks of their respective owners. They are used here only to identify compatibility. No partnership, sponsorship or endorsement is implied.