> From https://brixsignage.com/guides/guide-pos-integration-toast-square-clover/ . All Brix pages as markdown: https://brixsignage.com/llms.txt

# POS Integration for Digital Signage: Toast, Square

How POS integration for digital signage works with Toast, Square and Clover, what data reaches the menu board, and how Brix connects to your POS.

Apps & Integrations 6 sections Updated January 13, 2026

A POS integration connects your point-of-sale system to your digital signage. The board then shows the real price from your POS, not one someone typed in by hand. Change a price at the register and every board that shows that item follows. Toast, Square and Clover all publish the menu data a signage platform needs. What differs between signage vendors is which fields they read and who sets it up.

## Show the real price from your POS

Brix connects to Toast, Square and Clover. Our team sets up the connection with you. [Talk to us](https://brixsignage.com/demo). The connected data drives live item names and prices onto a menu board or any other design.

## What a POS integration does for a menu board

-   **The board matches the register.** The price on the board comes from the same record as the price the customer pays.
-   **One edit, every location.** Change a price once in the POS and every board that shows the item updates.
-   **Sold-out items.** Where the POS tracks stock, some platforms hide the item or mark it sold out.
-   **Head office keeps the design.** The layout stays fixed; only the names and prices in it change, from each store's own POS.

A POS-driven board suits counter and drive-thru menu boards for [restaurants](https://brixsignage.com/industries/restaurants/), bar and cafe price lists, and salon or retail price screens.

## What data a POS integration can use

Which fields a signage platform reads depends on the platform. The data each POS publishes:

| POS | Where the menu lives | Stock or availability |
| --- | --- | --- |
| **Toast** | Menus, groups and items: name, price, description and calories | Toast marks a sold-out item "out of stock" |
| **Square** | The Catalog API: items, variations (such as sizes), prices and categories | The same Catalog API marks a variation sold out per location |
| **Clover** | The items endpoint: items, categories and prices in one call | The same call returns each item's stock count |

Things to know before you rely on it:

-   **Names in the POS are often short.** "LG LATTE OAT" works on a receipt, not on a board. Many platforms let you keep a display name on the sign while the price still comes from the POS.
-   **Sizes and variations.** A drink with three sizes is one item with three prices. Check how the platform lays out variations before you design the board.
-   **Per-location prices.** Airport or city-centre stores often charge more. The board for each store must read that store's POS location, not the head office menu.
-   **Calorie counts.** Most POS systems do not store them in a form a board can show. Chains of 20 or more US locations must show calories on menu boards (21 CFR 101.11), so plan where that number comes from. See calorie labeling on digital menu boards.

## Which digital signage platforms integrate with Toast, Square or Clover?

Toast lists its partners in its integration marketplace at pos.toasttab.com; Square and Clover run app marketplaces of their own. Two signage examples from the vendors' own pages:

-   **NoviSign** says its Toast integration syncs menu items, pricing and availability in real time.
-   **Wallboard** says its Toast integration syncs menu items, categories, pricing and modifiers, plus item availability.

Before you buy, ask each vendor these questions:

1.  Is the integration live today for my POS, or on a roadmap?
2.  Which plan includes it, and does it cost extra per location?
3.  Do I set it up myself, or does your team do it?
4.  Which fields does it read: names, prices, sizes, modifiers, stock?
5.  How long after a change in the POS does the board update?
6.  What does the board show if the POS cannot be reached? It should keep the last known menu, never go blank.

## If you do not want a POS integration

-   **A spreadsheet.** Keep the menu in a Google Sheet and let the board read it. Edit a price in the sheet and every board changes. This works with any POS, or none. See [show live data on screen](https://brixsignage.com/guides/live-data-on-screen/).
-   **Edit the board directly.** For one store with a menu that changes a few times a year, editing the design in the signage software is quicker than connecting anything.
-   **Your own data feed.** If your team already publishes menu data as JSON (for example from an online ordering system), most signage platforms can read it the same way.

## How Brix connects to your POS

In the CMS, the POS sources sit on the **Data sources** tab of **Templates**, under **Point of sale**.

![Point of sale in Data sources: Toast, Square and Clover under Request access.](https://brixsignage.com/images/screenshots/data-sources-pos-request-access.png)

Point of sale in Data sources: Toast, Square and Clover under Request access.

The rest of the board works as usual: menu templates, day-parting (breakfast and lunch menus by time), and content that keeps playing when the network drops.

What to have ready for the call:

-   **Which POS you use** (Toast, Square or Clover) and how many locations run on it.
-   **Someone with admin access to the POS account**, because connecting needs permission granted there.
-   **Which screens should show POS data**, and which items or menu sections belong on each.
-   **Your current menu board**, or a photo of it, so the design can be matched.

Brix is not the right choice if you need a self-serve POS connector you switch on alone tonight, or a POS other than Toast, Square or Clover. In that case, use a spreadsheet-driven board, or pick a vendor whose marketplace listing shows your POS.

Brix costs $6 per screen per month billed annually, or $8 billed monthly. Our team sets up the Toast, Square or Clover connection with you.
