Integration detail
Appetier + Clover integration
Your menu stays matched to Clover with no double entry, and Clover stays your register. Connect with Clover's own sign-in, or paste a merchant API token from your Clover dashboard.
What works
With your access: Approve Appetier on Clover's consent screen, or paste a merchant API token you create in your Clover dashboard, one per merchant. Appetier reads items, prices, stock, and sales. It marks an item sold out or changes a price only after an owner approves. Direct orders are fulfilled in Appetier, with no ticket sent to Clover.
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 items, prices, stock, and sales for each merchant. When an owner approves, Sous marks an item sold out or changes its price in Clover.
Who it's for
Clover restaurants that want direct ordering on their own site and a chat that knows what the register sold.
What Appetier reads from Clover
Appetier reads items with prices, availability, and stock counts. Deleted and hidden items are skipped. It reads paid and locked orders as line items, and guest notes only as quoted text. Customers, payments, and cards are never read. Refunds, discounts, and payouts stay in Clover.
Changing Clover from the chat
An owner can tell Sous to mark the fish tacos sold out at Downtown, or to change a price. Sous shows the exact change on a button, and nothing happens in Clover until the owner taps it or says yes. If someone changed the item at the register first, Appetier refuses to overwrite it. A sold out item also comes off your online menu at that location.
Orders and payment stay in Appetier
Guests order and pay at your Appetier storefront. Appetier does not send an order to Clover as a ticket, and orders are fulfilled in Appetier. Your Clover register keeps taking counter sales as it does today.
Connect with Clover's own sign-in
The owner approves Appetier on Clover's consent screen, or pastes a merchant API token created in the Clover dashboard. A Clover merchant is one location, so a group connects each merchant and maps it to an Appetier location. Appetier keeps the tokens on its servers and no console page shows them.
Clover outside the United States
Fiserv's Latin America documentation lists Clover in Argentina, Brazil, and Mexico. Each country has its own Clover service, so you connect the Clover merchant your location already uses. Mexico's rollout is still growing, so ask Fiserv whether your location is live.
Setup steps
Where it fits in Appetier
Menus stay matched to your POS, and direct orders print as tickets.
See POS sync- Open your Appetier storefront and take direct orders
- Approve Appetier on Clover's consent screen, or paste a merchant API token
- Map each Clover merchant to an Appetier location
Common questions
Do we paste a Clover API token?
Does Appetier send our online orders to the Clover register?
Can Sous change a Clover price on its own?
Does our storefront depend on Clover access?
Is Clover available in Mexico and Argentina?
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.
