Connect Clover and ShelfCount learns what you sell, the same way it does with Square. Map each menu item to a recipe once, and every sale is costed down to the ingredient, modifiers included.
Cafes and restaurants that run Clover and want food cost from real sales, not from a guess. If your Clover items use modifier groups for milks, sizes and add-ons, ShelfCount reads them and lets you give each one an ingredient effect.
One ShelfCount account is one business, at $50 a month. It can watch several Clover merchants of that business, each with its own token. There is no combined report across separate businesses.
Today you connect with a Clover dashboard API token. A one-click connect is coming once Clover approves our app listing: we submitted it to the Clover App Market for review on 2026-10-08, and it is still pending. The token method keeps working after that.
Stuck on any step? Email hello@getshelfcount.com.
You create an API token in your Clover dashboard with read access to Inventory, Merchant and Orders. One-click connect waits on Clover App Market approval.
What it reads
Never writes anything to Clover.
ShelfCount only reads from your POS. It never changes an item, a price or a sale there. A purchase order goes to a vendor only when you send it, or when you have switched on auto-send for that vendor.
That list is the whole of it. A test fails if the code that talks to Clover starts making a call that is not on it.
In Clover, an item can have modifier groups (Milk, Extras), and each group has modifiers (Oat, Extra shot). Each Clover item points at a recipe, or straight at an inventory item for simple retail products. Unmapped items still sync, and a running to-do shows what is left.
Example: a customer buys a Latte with the Oat modifier from the Milk group and an Extra shot. The Latte item points at a recipe with whole milk and two shots. Oat replaces the whole milk with oat milk, and Extra shot adds a third shot. The sale is costed as that drink.
Each modifier gets one or more of five effects, applied in order. You set them once, and every sale after that is costed with them.
Orders are pulled about every 15 minutes. Once one-click connect is live, Clover webhooks will nudge a sync sooner when something changes; the webhook is only a signal, and ShelfCount pulls the real data from Clover's API.
No. It reads your merchant details, items, modifiers and orders. It never writes anything to Clover.
Create an API token in your Clover dashboard with read access to Inventory, Merchant and Orders, then enter it with your merchant ID in ShelfCount.
Not yet. We submitted our listing for review on 2026-10-08 and it is pending. Until it is approved, you connect with the API token.
Yes. Each modifier can add, replace or change an ingredient, so an oat milk swap or an extra shot shows up in the cost, not just the price.
Yes, if they belong to one business. One account is one business at $50 a month, and each merchant has its own token. Separate businesses are separate accounts, with no combined report across them.
Connect Clover with an API token during the trial and see your sales costed to the ingredient. Or look around the demo first.