Support

There are two ways in. From the Clover App Market: open the App Market from your Clover dashboard, search for “VenueCore Inventory,” and tap Install. Clover walks you through granting permissions and returns you to our app for a short setup. Directly from our website: go to venuecoreinventory.com, create an account with your email and a password (or with Google), and connect your POS yourself using an API token — see the next answer.

Yes. Open venuecoreinventory.com and choose Try the Demo. You get a fully working venue with sample stock, recipes, and sales — including a Simulate Sale button that deducts ingredients in front of you, which is the fastest way to see what the app actually does. The demo is completely separate from real accounts and touches no real data. Nothing is saved when you leave it.

If you signed up directly on our website, open Settings → Connect Clover and you’ll be asked for two things from your own Clover dashboard:

1. Sign in at clover.com → Account & Setup. Your Merchant ID is shown there.
2. Go to Setup → API Tokens → Create new token, and tick Read for Merchant, Inventory, Orders, and Payments. Save, then copy the token.
3. Paste the Merchant ID and token into VenueCore and press Connect.

Don’t skip Payments (read) — it’s what lets cash sales deduct reliably. We check your token’s permissions at connect time and tell you immediately if something is missing, so a bad token can never look connected. You can revoke the token at any time from the same Clover screen.

If you installed from the Clover App Market, Clover notifies us the moment an order is paid and deduction is typically within seconds. If you connected with your own API token, Clover does not send those notifications, so we check for new sales on a short cycle instead — usually a few seconds while you have the dashboard open, and about once a minute when nobody is watching. Cash payments occasionally take Clover several minutes to finalize; we keep re-checking until they do.

We request the minimum permissions needed for ingredient deduction:

• Merchants: Read — so we can identify your venue at connect time and pre-fill your business name, instead of asking you to retype information Clover already has.
• Inventory: Read — so we can pull your menu items and modifier groups, and let you attach recipes to them.
• Inventory: Write — so we can push updated stock counts back to your Clover items as ingredients deduct. This is the only thing we ever write to your Clover account.
• Orders: Read — so the order webhooks Clover sends us include line items, which is what triggers the deduction.
• Payments: Read — so we can confirm an order is actually paid before deducting (cash sales in particular don’t reliably show as paid without it) and detect refunds so stock is restored. We read payment status, result, and amounts only, and we don’t store payment records.

We do not request access to Customers or Employees, and we never see card numbers or any cardholder data.

If you install from the Clover App Market, Clover handles the trial and billing on our behalf and pricing is shown on the listing. If you sign up directly on our website, the current terms — trial length, price, and whether a card is needed — are shown to you at signup before anything is charged. We’re onboarding direct venues by invitation while the product is in early access, so if you’re joining that way we’ll confirm your terms with you in writing first. You’ll never be charged without agreeing to a price up front.

Open the Menu Items page in the app and tap Sync from Clover. This pulls every item and modifier from your Clover account. If sync still shows nothing, check the Connection page — you may need to re-install to refresh permissions.

Go to Recipes, tap a menu item, and add the ingredients with their quantities and units. The next sale of that item through Clover will automatically deduct the listed ingredient quantities from your stock.

The most common reason by far: the item has no recipe yet. We can only deduct what you’ve told us an item is made of, so a freshly connected venue deducts nothing until recipes exist. Open Recipes and check the item that sold. If your menu is large, start with your five or ten best sellers rather than trying to cover everything — that’s where almost all the value is, and you’ll see deductions immediately.

• The Clover order isn’t finalized and paid yet — for card sales that’s typically when the order locks; for cash sales, when the payment is recorded. We deduct only on completed sales to avoid deducting cancelled orders.
• The menu item exists in Clover but hasn’t been synced to our app yet. Hit Sync from Clover.
• The sale used a modifier that has its own recipe — check Modifiers as well as the base item.

Sales of items with no recipe aren’t lost. We record them so you can see exactly which items need recipes.

Set a par level on each ingredient. When current stock drops below its par level, we generate a low-stock alert visible on your dashboard, and a reorder request is created automatically.

It can, if your connection allows it. As ingredients deduct, we calculate how many of each menu item can still be made and push that count back to Clover. This requires Inventory: Write permission — App Market installs have it automatically, but an API token only has it if you ticked Write for Inventory when you created the token. Without it, deduction inside VenueCore works exactly as normal and only the push back to Clover is skipped. To enable it later, create a new token with that permission and reconnect — adding a permission to an existing token doesn’t change the token you already pasted.

On the login screen, click Forgot your password? and enter your email. We’ll send you a link to choose a new one. The link works once and expires after 60 minutes; requesting a new link cancels any earlier one. If the email doesn’t arrive within a couple of minutes, check your spam folder before requesting another. For your security, setting a new password signs you out everywhere else.

Yes. Use Forgot your password? with the same email address and set one. Google sign-in keeps working exactly as before — you’ll simply have both options.

Open Settings and choose to change your password. You’ll be asked for your current one first. As with a reset, changing it signs out any other devices.

When you sign up we send a confirmation link so we know the address really reaches you — which matters most when you need a password reset or a low-stock alert. It doesn’t restrict anything. Your account works normally whether or not you confirm, and you can dismiss the banner. If the email never arrived, use Resend on the banner.

Password resets, confirmations, and stock alerts come from [email protected]. If you don’t see one, check spam and mark it “not spam” so later alerts reach your inbox. For help, write to [email protected].

Installed from the Clover App Market: uninstall the app from your Clover dashboard. Cancellation takes effect at the end of your current billing period, and refunds are governed by Clover’s App Market refund policy. Signed up directly on our website: cancel from the billing area in the app, or email us. Your subscription renews automatically each period until you cancel, and cancelling stops the next charge while leaving you access through the end of the period you already paid for.

Open Settings inside the app and tap Disconnect. Your stored POS credentials are deleted immediately and sales stop deducting. Your ingredients, recipes, stock, and history are kept, so you can reconnect later. If you connected with an API token, you can also revoke it directly in your Clover dashboard.

Stored POS credentials are deleted immediately in every case. If you uninstall from the Clover App Market, all remaining data we hold for your account — ingredients, recipes, inventory, transactions, sync logs, and audit logs — is automatically and permanently deleted within 30 days. If you signed up directly and use Delete Account in Settings (which asks for your password first), everything is deleted permanently and immediately — that one cannot be undone. You can request deletion at any time by emailing the support address above.

In an encrypted PostgreSQL database hosted on Railway. POS credentials — both OAuth tokens and API tokens — are encrypted at rest with AES-256-GCM, and account passwords are stored only as one-way hashes that cannot be reversed. Session tokens stored in your browser are opaque random strings; your actual POS credentials never leave our servers.

We never sell or rent your data. It is shared only with the providers needed to run the service: our host (Railway), our backup storage (Cloudflare R2), our payment processor (Stripe, if you subscribe directly — card details go to Stripe, never to us), Google (only if you use Google sign-in, for identity), and our AI provider (only if you enable the Assistant, only for the request you make). Full details are in our Privacy Policy.

No, never. We read only whether an order was paid, the amount, and the line items sold — enough to know what to deduct. We do not receive card numbers, cardholder names, or any cardholder financial data, and we do not request access to your Clover Customers or Employees records.