Bar inventory with Toast

Toast documents Standard API access as a restaurant-managed credential, created in Toast Web under Integrations, Toast API access, Manage credentials. The public developer guide lists Standard API as GET-oriented access. ExactPour follows that path. It does not use Analytics API credentials, and the in-app setup says so.

Toast's own scope table lists `menus:read` for menus v2, `orders:read` for orders, and `restaurants:read` for restaurant data. ExactPour asks you to enable those read scopes and not to grant write access. Standard API cannot change menus, prices, or settings in your Toast account, which matches Toast's Standard API FAQ that POST is not the Standard API job.

Every Toast API call for a location needs the restaurant GUID as `Toast-Restaurant-External-ID`. Toast emails that GUID when credentials are created. A second bar needs a second GUID and a second ExactPour location. Connecting does not pull sales by itself. The first sync, Sync now or the next automatic run, imports up to the last 7 days.

After that, ExactPour runs Toast sync at 8:00 AM, 12:00 PM, 4:00 PM, 8:00 PM, and 11:00 PM in the location timezone, and again when you close a count. If a sync is more than 25 hours behind, the next run catches up. Variance is trustworthy after the next full count covering that window.

Toast can export reports from Toast Web for humans. ExactPour does not use a Toast CSV for the live connector. If you are not connecting, you could still count in ExactPour and read a Toast report by eye. The live path is the API.

Sign in to Toast Web as an owner or admin with the 8.4 Manage Integrations permission. Open Integrations, Toast API access, Manage credentials. Toast documents this path in its API access credentials guide.

Create Standard API credentials, not Analytics. Each location needs Toast Restaurant Management Suite Essentials or higher, per the in-app ExactPour steps. Name the credentials ExactPour. Enable only `menus:read`, `orders:read`, and `restaurants:read`. Copy the client ID and client secret. The secret is shown once.

Copy the restaurant GUID from the Toast confirmation email or the restaurant API access page. Paste client ID, client secret, and GUID into ExactPour for that location. ExactPour is not a Toast partner app you install from a gallery. It is Standard API access you create.

Choose which menu groups to import on the integration manage page, then Sync now. Map well drinks and signatures first. Unmapped Toast items make a careful count look like theft. Call-brand bumps are supported for Toast in ExactPour.

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 Toast side of the week is only useful if the physical count covers the same hours the tickets cover.

ExactPour already pulls Toast menus and orders on a schedule, and again when you close a count. You do not paste a weekly Toast total into a cell. You still have to close the session. A connected Toast 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 Toast 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 Toast 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 Toast story.

Poured versus sold is a recipe problem, not a Toast report setting. A house vodka soda that rings as one Toast 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 Toast 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 Toast 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 Toast. 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 Toast 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. Toast 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. Toast does not change that order.

Toast 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 Toast 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. Toast 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 Toast connector. Do not skip invoices while you wait on a menu map.

After Toast is connected, you still walk the rail. Scan barcodes. Tap fills. Receive distributor invoices. Close the session. ExactPour compares projected usage from Toast tickets to what you counted.

POS reconciliation is on Starter at $69 a month and up, and during the 14-day Pro trial. Free-tier counting does not include this Toast loop. Confirm the live plan grid on /pricing.

ExactPour reads Toast. It does not place distributor orders, rewrite the Toast menu, or file a liquor license. City liquor rules still live on [the city pages](/cities).

If you also ring Square or Clover in another room, that room gets its own connector. Do not paste a Toast weekly total into a Square location.

Toast 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 Toast that retires the rail walk, that is not what ExactPour ships and it is not what this page claims.

ExactPour reads Toast. It does not rewrite the Toast 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 Toast.

Unmapped house pours are the usual failure. A Toast 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. Toast 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 Toast 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 Toast. This page does.

Give each address its own ExactPour location. A second Toast 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 Toast and the next room is Square, do not share credentials. Connect Toast 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 Toast location, not the whole group. Map the rail. Then copy the habit.

Toast 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 Toast bottle-fill camera inside the POS, that is not what ExactPour ships and it is not what Toast documents as a replacement for a physical well count. Count the rail. Let Toast explain the tickets.