Bar inventory with Clover

Clover merchants generate API tokens in the Clover Dashboard. ExactPour's in-app steps send you to clover.com/dashboard, then Account and Setup, API Tokens (or Settings, API Tokens, depending on the merchant). You create a token named ExactPour with Read for Inventory, Orders, and Merchant. The token is shown once.

The merchant ID is the code in the dashboard URL after /setupapp/m/. ExactPour needs that ID plus the region because Clover hosts US, EU, and LATAM environments. Pick the region that matches the merchant.

ExactPour validates against Clover, stores the token encrypted, and only reads items and orders. First import is the last 7 days, then nightly catch-up. Call-brand bumps are supported for Clover in ExactPour.

Clover Reporting can export activity for humans. ExactPour does not ingest a Clover CSV for the live connector. The live path is the API token.

Sign in at clover.com/dashboard with the owner or admin account. Open Account and Setup, API Tokens. Create a read-only token for Inventory, Orders, and Merchant.

Copy the merchant ID from the dashboard URL. In ExactPour, pick US, EU, or LATAM, paste merchant ID and token, then Connect.

Choose menu groups on the manage page. Sync now. Map well drinks first. Unmapped Clover items make a careful count look like theft.

Pick a night the room can repeat. Many bars use early Monday. Write the cutoff in ExactPour before anyone restocks the well. Then walk one route. The Clover side of the week is only useful if the physical count covers the same hours the tickets cover.

ExactPour already pulls Clover menus and orders on a schedule, and again when you close a count. You do not paste a weekly Clover total into a cell. You still have to close the session. A connected Clover location with no closed count is a menu import, not poured versus sold.

Do not mix locations. If the group also rings Toast in another room, that room has its own ExactPour location and its own connector. A Clover sales total pasted onto a Toast well will make both rooms look dishonest. See POS integrations for the live four (Toast, Square, Clover, GoTab).

City liquor rules are not a Clover setting. License-state rooms photograph wholesaler invoices. Pennsylvania control-state rooms photograph PLCB and beer-distributor paper. The POS still only knows what rang. Use [city pages](/cities) for the buying story, and this page for the Clover story.

Poured versus sold is a recipe problem, not a Clover report setting. A house vodka soda that rings as one Clover item has to name the spirit in ExactPour. Soda is not liquor inventory. If the recipe is blank, ExactPour cannot deplete the bottle from that ticket, and the next count will look like theft.

Map the drinks that actually sell. Well vodka, well whiskey, well tequila, house gin and tonic, and the two signatures the room cannot stop ringing. Rare bottles can wait. A Clover menu with 200 items is not a reason to skip the well map. It is a reason to start with the rail.

Call-brand bumps are supported for Clover in ExactPour. If a guest pays for a named vodka on a well drink, that bump has to match how the ticket is built in Clover. If the POS rings well vodka and the bartender poured the call bottle, the count will show the call bottle short and the well bottle long. That is a ringing problem, not a camera problem.

Modifiers matter. A Clover ticket that adds an extra shot, a double, or a different spirit is a different depletion. If those modifiers are ignored, the well looks generous on paper and empty on the rail. ExactPour can only deplete what you mapped. Clover can only report what rang.

See poured versus sold for the formula and how to reduce liquor shrinkage for the coaching order: recipes, comps, waste, then theft. Clover does not change that order.

Clover does not replace receiving. A case that lands during the count window has to be received in ExactPour or the session is wrong. Photograph the distributor ticket (or the PLCB ticket in Pennsylvania). ExactPour extracts lines so bottle cost is the paper cost, not a memory.

A Clover sales mix cannot tell you that well vodka went up $4 a bottle last Tuesday. The invoice can. Keep both. Bar invoice management is the capture path. Clover remains the ticket path. ExactPour is the count path.

ExactPour prices in USD are Free, then Starter $69, Pro $99, and Scale $129 a month. POS sync is on Starter and up, plus the 14-day Pro trial. Confirm on /pricing. Invoice capture and counting exist without POS sync. Poured versus sold is the part that needs the live Clover connector. Do not skip invoices while you wait on a menu map.

Clover does not replace the walk. Scan the rail in ExactPour. Tap fills. Receive invoices. Close the session so Clover tickets become projected usage.

ExactPour prices in USD are Free, then Starter $69, Pro $99, and Scale $129 a month. POS sync is on Starter and up, plus the 14-day Pro trial. Confirm on /pricing.

A Clover room and a Toast room in the same group each keep their own connector. See Clover liquor inventory for the companion lander, and this page for the connector facts.

City liquor rules are not a Clover setting. See [city pages](/cities).

Clover will not count the well for you. Item stock in a POS is a catalog unit, not a fill level on an open bottle. ExactPour is the fill. If someone promised a camera inside Clover that retires the rail walk, that is not what ExactPour ships and it is not what this page claims.

ExactPour reads Clover. It does not rewrite the Clover menu, take payments, place distributor orders, or file a liquor license. If a recipe is wrong, fix it in ExactPour. If a price is wrong, fix it in Clover.

Unmapped house pours are the usual failure. A Clover item named "Well" or "Rail" or "Vodka Soda" with no recipe will show as sold product that never left a bottle. Map it. Then recount. Then coach. Do not start with a theft meeting.

Comps, spills, and staff drinks need a code in ExactPour. Clover may already void or comp tickets. If those voids never become waste codes, the well still dropped and the sales side looks clean. Log the waste. The next Clover comparison will make sense.

For the physical walk, see bar stocktaking and bar inventory software. For a sheet you can print this afternoon, see the liquor inventory template. Those pages do not depend on Clover. This page does.

Give each address its own ExactPour location. A second Clover merchant, restaurant GUID, Square location, or Clover merchant is a second connect (or a second export ritual). Rollups compare reconciled dollars. They do not merge two wells into one clipboard.

If this room is Clover and the next room is Square, do not share credentials. Connect Clover here and Square there. ExactPour already supports Toast, Square, Clover, and GoTab as live connectors. Mixing tickets across those systems by hand is how groups invent shrinkage.

Book a 20-minute walkthrough on /demo or /contact if you want the mapping reviewed. Bring one Clover location, not the whole group. Map the rail. Then copy the habit.

Clover remains the system of record for tickets. ExactPour remains the system of record for open bottles. That split is the whole product. See POS integrations for Square, Clover, and GoTab on the same pattern, or [city pages](/cities) if you also need the local liquor-license story.

ExactPour prices in USD are Free, then Starter $69, Pro $99, and Scale $129 a month. POS sync is on Starter and up, plus the 14-day Pro trial. Confirm on /pricing.

If you expected a Clover bottle-fill camera inside the POS, that is not what ExactPour ships and it is not what Clover documents as a replacement for a physical well count. Count the rail. Let Clover explain the tickets.