Integration detail
Appetier + Square integration
If Square runs your counter, one Square sign-in keeps your storefront menu matched, with no keys to copy.
What works
With your access: Sign in with Square and approve Appetier on Square's own consent screen. Appetier reads items, modifiers, stock, orders, and sales, and changes a sold-out item or a price only after you approve it. Direct orders are fulfilled in Appetier, with no ticket sent to Square.
On our own: Appetier takes direct orders on your storefront and fulfills them on its order and kitchen screens. Or run Appetier POS, free in Growth, on your own hardware.
What it does
Appetier reads your Square catalog, modifiers, and item availability, and changes a sold-out item or a price after you approve it.
Who it's for
Square operators who want one account behind the counter and the storefront.
Your Square menu stays matched on your storefront
Appetier turns your Square categories into storefront categories and reads each item's price from its variation, like a small and a large. Modifier lists come across with the most choices a guest may pick, so "choose up to two sauces" at the counter reads the same way at checkout.
When Square says sold out
Square marks a variation sold out at a single location in two ways. It happens on its own when a tracked inventory count reaches zero, or a manager marks it sold out while stock remains. Either way, Appetier treats that item as unavailable at that location, and it drops off the online menu on the next sync. Your other locations keep selling it. Hours and sold-out flags reach the storefront without a publish step.
Changing Square from the chat
An owner can tell Sous to mark Fish Tacos sold out at Downtown. Sous shows the exact change on a button, and nothing happens in Square until the owner taps it or says yes. Staff can ask too. Their request waits for an owner. Say a manager changed the item at the register in the meantime, before anyone approved. Appetier refuses to overwrite it and shows the current value. Undo puts the item back only while Square still shows what Appetier set.
One Square sign-in, no keys to copy
You connect Square through Square's own sign-in and consent screen. Appetier keeps the tokens on its servers. No console page ever shows them. The Square card shows the connection date, the mapped locations, and the last error. Each Square location maps to one Appetier location, and an unmapped one doesn't sell online. If Square revokes access, the card says Square needs reconnecting. Stock counts, refunds, voids, discounts, and payouts stay in Square, untouched.
How Sous marks a Square item sold out
Square keeps its own sold-out flag read-only for apps. So Sous sets the item's stock count at that location to zero, and Undo puts back the count it took away. Sales rung up while the item was off stay counted.
Square stays connected on its own
Appetier renews your Square connection in the background, so nobody has to remember it. If Square revokes access, the owner gets one email that names Square and links to the integrations page.
Setup steps
Where it fits in Appetier
Menus stay matched to your POS, and direct orders print as tickets.
See POS sync- Connect your Square account
- Pick which Square locations sell online
- Confirm modifiers match
- Place a test order and find it in Appetier
Common questions
What happens to items we hide in Square?
Can we sell only some Square locations online?
Which permissions does Appetier ask Square for?
How far back can Sous read Square sales?
Related integrations
Launch first, then connect it
Your storefront goes live in minutes from your logo and a photo of your menu. Add this connection whenever you're ready.
