What RevenArc’s read-only Square connection means for you
Your POS is part of a working service. It is reasonable to want a clear explanation before connecting another tool to it.
RevenArc uses a read-only Square connection to bring menu and sales history into your menu review. It does not use that connection to change item prices, rewrite the menu or make a decision on your behalf.
What the connection is for
The Square connection brings in the history needed to review how menu items are selling. Catalog information identifies the dishes and their variations. Completed-order history provides the item sales being reviewed, while location information helps put that history in the right context.
The connection uses Square’s authorization process. Read the permission request before approving it, and ask about anything that is unclear. A clear explanation of the access should be part of connecting the restaurant.
Once connected, RevenArc imports history and keeps syncing on a schedule. Check the data status before relying on a figure. If your venue uses Toast instead of Square, read how to run a menu review from a Toast CSV export. If the history is stale or incomplete, the review needs to show that limitation.
What stays in your hands
RevenArc does not write menu or price changes back to Square. It does not operate your payment terminals, change terminal settings, or rank individual staff.
If you decide to change a dish, you make the update yourself. That gives you time to coordinate the printed menu, kitchen preparation and service briefing as part of the same decision.
Approving a recommendation in RevenArc is not permission for the app to update your POS. Recording that a change has been applied keeps the review history clear.
What you can review after the history loads
You can examine item sales and the menu classification, with the basis of the figures shown. Current item costs make a contribution-based review more useful. When costs are missing, sales and prices should not be presented as actual contribution or profit.
The weekly brief and decision cards help organize the review. The outcomes ledger records what happened afterward, including corrections and external events you record. This steady routine is why a weekly menu brief beats a live POS dashboard for menu decisions. A before-and-after movement still needs context; it does not prove that the menu change caused it.
Formal result grades, advance measurement plans and a ranked agenda of zero to three decisions are planned. They are not part of the current connection’s promise.
See what a menu review looks like.
The sample shows how a review can bring an item's sales, missing information and next question together in one place. Its data is illustrative.
Questions operators ask
Can RevenArc change a price or mark a dish unavailable in Square?+
No. The connection is read-only, and RevenArc does not write changes back to the POS.
Does RevenArc rank servers or score staff?+
No. The review focuses on menu items and restaurant sales, not individual employee performance.
What if I use Toast?+
You can upload your Toast sales export (Item Selection Details).
RevenArc
Menu decisions and restaurant intelligence
We build RevenArc for restaurant operators who want a clearer view of their menu and a useful place to start the next review.
Follow the next article.
Email updates aren't available yet. You can follow RevenArc in your feed reader to see new articles as they're published.
Open the RSS feedKeep reading
How to price add-ons and sides on a restaurant menu
How to price add-ons and sides on a restaurant menu comes down to margin dollars and attach rate rather than target food cost percentage. How portion costs, modifier pricing, and guest uptake shape your weekly menu contribution.
What to do when beef goes up 12 percent
What to do when beef goes up 12 percent is a question most operators face when protein markets tighten. How wholesale protein hikes hit different plates, and your three operational options as an owner.