Square for Restaurants on Android is locked to one Samsung phone. Phone orders reach Square anyway.
The Google Play listing for Square for Restaurants lists exactly one compatible device, the Samsung Galaxy A32 5G. Every other Android phone and every Android tablet reads as unsupported. That does not block phone ordering, because the phone order never touches the counter device. It lands through the Square Orders API, which is device-agnostic.
The anchor fact nobody writes down clearly
Search the top results for "square for restaurants android" and you will find the Google Play link, an AppBrain mirror, a couple of community threads titled the same thing, and a pair of review roundups. None of them lead with the one fact an operator needs before choosing hardware.
The Google Play compatibility footnote
Square for Restaurants (package com.squareup.restaurants) is Android-listed. Its device filter accepts one device, the Samsung Galaxy A32 5G. Every other phone and every Android tablet is marked unsupported by the Play Store.
- Target device: Samsung Galaxy A32 5G, 6.5 inch phone from 2021
- Not supported: Samsung Galaxy Tab S series, Pixel Tablet, Lenovo Tab, and the entire 10 to 13 inch Android tablet category
- Full-feature POS target: iPad running iPadOS 15+
Verify on Google Play or AppBrain for the app listingcom.squareup.restaurantsand read the device filter expand panel.
What operators type into search when the A32 limit bites
Where your phone order actually lives in the Square stack
The counter device is a view on top of a merchant account. That merchant account holds catalog, orders, inventory, transactions, and reporting. PieLine writes to that account, not to the device. Everything downstream still works.
Caller > PieLine > Square merchant account > every device
The three Android counter paths that actually ship today
If you are on Android and want to stay in the Square ecosystem, you have three honest options. Each one affects the counter UI differently. None of them changes what a phone order looks like inside Square, because that part is API-level.
Square for Restaurants on Samsung Galaxy A32 5G
The one Android device Square supports for the restaurant-specific POS. Small 6.5 inch phone screen, handheld-first. Works for line-busting, expo, or a server taking orders tableside. Not a replacement for a counter tablet.
Square POS (generic) on any Android tablet
Runs on Samsung Tab S, Lenovo Tab, Pixel Tablet. You get Square Point of Sale, not Square for Restaurants. You lose floor plan, course firing, and server assignments, but you keep payments, catalog, and reporting.
iPad on iPadOS 15+
The first-class Square for Restaurants surface. Full floor plan, course firing, server shifts, KDS, Square KDS displays. This is the build Square invests in.
Square Register (first-party hardware)
Purpose-built Square countertop device. Runs Square for Restaurants natively, no Android, no iPad, no tablet sourcing. One-time hardware spend, slower to repair.
PieLine on top of any of the four
Writes through the Square Orders API at the merchant account. Does not require a counter device to be present, powered, or online at the moment the call comes in. Same payload on every path above.
Before and after: where phone orders used to break on Android
Most guides on this keyword describe the device compatibility problem and stop there. The operational consequence is that phone ordering used to collapse when the Android counter app was not the proper restaurant build. Here is the shift.
Taking a phone order when Square for Restaurants will not install
Cashier answers the phone holding the Android tablet. The tablet is running generic Square POS because Square for Restaurants will not install on a Samsung Galaxy Tab. The cashier keys the order into the flat item grid, skipping half the modifiers because the screen layout does not surface them. The kitchen gets an incomplete ticket. The customer calls back 15 minutes later. The item is remade.
- Modifier depth limited by the device app
- Re-keyed phone orders create transcription gaps
- Missed modifiers print incomplete kitchen tickets
- Error cost: food waste + a dissatisfied customer
The payload that lands in Square, on the wire
This is what PieLine pushes when a phone caller finishes ordering. It reaches Square regardless of whether your counter app is the A32 5G build, generic Square POS on Android, or Square for Restaurants on iPad.
Counter device vs. phone ordering layer: what each one actually decides
Operators routinely conflate 'which Square app runs on my tablet' with 'where do phone orders go'. They are not the same question. The counter device picks the in-store UI. The API picks where orders land.
| Feature | Counter device alone | PieLine + Square Orders API |
|---|---|---|
| Depends on Android app compatibility | Yes. A32 5G only for restaurant POS | No. Works on any Square merchant account |
| Requires the counter tablet to be online | Yes at order time | No. API write lands first, device syncs later |
| Handles modifier trees from your Catalog | Depends on the device app build | Always, pulled from Square Catalog API |
| Handles 20 simultaneous calls | No. One cashier, one phone, one call | Yes, 20 concurrent slots per location |
| Goes live same day on Square | Depends on hardware procurement | OAuth + menu scrape, typically one day |
| Survives a counter app crash mid-rush | Order falls back to pen and paper | Order already written to Square cloud |
| Pricing | Hardware capex + Square subscription | $350/mo flat up to 1,000 calls |
Watch what happens when a caller dials while your Android counter app is busy
The decoupling between counter device and phone ordering shows up most clearly in the rush. The cashier is ringing up a walk-in on the Android tablet. The phone rings. Here is the sequence.
Frame 1: the cashier is mid-transaction
How PieLine connects to your Square merchant account
Forward your restaurant line to PieLine
Takes about 10 minutes. Set forwarding as the primary answer or as overflow when staff cannot pick up. The counter device (Android, iPad, Register) plays no role.
OAuth into your Square account
PieLine requests scopes for Catalog read, Orders write, and optionally Payments for over-the-phone card capture. You approve from your Square dashboard. No API keys pasted by hand.
Menu scrape and Catalog mapping
PieLine pulls your Square Catalog, including item variations, modifier sets, and category structure. Items that exist on your online menu but not in your Catalog get flagged for you to add before going live.
Rules configuration
Hours, pickup windows, delivery zones, minimum order, upsell pairings, escalation triggers. These are account-level config, not device-level, so they apply regardless of how the counter is staffed.
Go live, same day
PieLine starts answering calls, writing orders to the Square Orders API, printing kitchen tickets. Your cashier can still be running Square for Restaurants on an A32 5G, generic Square POS on an Android tablet, or Square for Restaurants on iPad. All three see the same orders.
Active refinement for the first month
PieLine monitors calls and retrains the AI on your specific menu phrasings and modifier edge cases. If accuracy does not clear the contract at your restaurant, the first month is refunded.
Operator checklist: should you even care about the Android restriction?
- Do you run a counter device at all? If yes, the Android restriction affects in-store UI, not phone orders.
- Are you currently buying hardware? If no, it is irrelevant to phone ordering.
- Does your phone order volume justify a dedicated channel? (30 to 40% missed calls during peak hours = yes)
- Is your Square Catalog up to date with modifier sets? The API write is only as rich as the Catalog allows.
- Do you care about warm transfer to a manager when the AI refuses an edge case? PieLine handles this regardless of device.
- Are you considering Square Register as a workaround? Worth pricing against an iPad + keeping the Android tablet for POS.
- Do you have an existing OAuth connection to a third-party app in Square? The process is the same for PieLine.
The numbers that decouple counter from call
Pulled from PieLine's Square-connected restaurant deployments and from the public Square for Restaurants Google Play listing.
Android devices supported by Square for Restaurants
0
Samsung Galaxy A32 5G, a 6.5" phone
Simultaneous phone calls PieLine handles
0
per location, regardless of counter device
Order accuracy on the API write
0%+
across Square, Clover, Toast, Aloha, Revel
What to actually ask Square support before you buy an Android tablet
If your instinct is still to solve the counter problem first, these are the three questions that determine whether Android is viable for you. None of them decide where your phone orders go.
Question 1
Is the Square for Restaurants Android compatibility filter still Samsung Galaxy A32 5G only?
The Google Play listing device filter is the source of truth. If Square broadens it in a future release, your Android tablet may suddenly qualify. If not, you are looking at iPad, Register, or the A32 5G.
Question 2
Which restaurant features are missing from generic Square POS on Android today?
At minimum: floor plan, course firing, coursing for multi-course tables, server assignments, split-check shortcuts. Payments, Catalog, reporting, and Orders API access are all there. That is why PieLine connects cleanly even on a generic-POS Android counter.
Question 3
Can my counter device read orders that were written to the merchant account by an external integration?
Yes for every Square-supported counter surface (iPad, Register, Android with generic POS, A32 5G with restaurant POS). This is the entire point of writing at the merchant account level. The counter is a viewer on a shared ledger.
Stop solving the Android question before you solve the phone question.
PieLine connects to your Square account via OAuth, scrapes your online menu, maps it to your Square Catalog, and writes phone orders through the Orders API. Your counter device (iPad, Android, Register) keeps doing what it does. Same-day go-live, $350/month up to 1,000 calls, money back on the first month.
Book a 15 minute Square-to-PieLine demo →Write phone orders to Square without the A32 5G
Fifteen minutes, an OAuth into your Square sandbox or production account, and a live phone call landing through the Orders API on whatever device your counter already runs.
Book a call →Frequently asked questions
Is Square for Restaurants available on Android?
Yes and no. The app (com.squareup.restaurants) is listed on the Google Play Store, but the Play Store device filter restricts installation to one device, the Samsung Galaxy A32 5G, which is a 6.5 inch phone from 2021. Owners on any other Android tablet or phone will see the app as unsupported. The iPad build of Square for Restaurants is the full-feature POS, and the Android listing exists primarily to support the A32 5G handheld form factor.
Can I run Square for Restaurants on a Samsung Galaxy Tab, Pixel Tablet, or Lenovo Android tablet?
Not as of the current Google Play release. The device compatibility filter excludes every Android tablet and nearly every Android phone other than the A32 5G. The typical workaround is to run the generic Square Point of Sale app on Android, which does not ship with the restaurant-specific flow (floor plan, course firing, server assignments, KDS). If you want the restaurant-specific flow, the supported path today is an iPad running iPadOS 15 or later.
Why does phone ordering work regardless of which Square app I run at the counter?
Because the order is written to your Square merchant account through the Square Orders API, not to the device. Your counter app (Square for Restaurants on iPad, Square for Restaurants on A32 5G, Square POS on Android, Square Terminal, Square Register) is a view into the same backend. PieLine calls the Orders API directly, so the phone order appears in your Transactions feed, your reports, and your kitchen printer setup the same way regardless of which device your cashier is holding.
Does PieLine need the Square for Restaurants app to be installed?
No. PieLine authenticates against your Square account via OAuth, pulls your Catalog (items, modifiers, categories, prices), and writes orders to the Orders endpoint. Whether you have the restaurant app on an iPad, the A32 5G, or nothing at all does not change what PieLine pushes to Square. The device question only matters at the physical counter for tableside, not for the phone ordering pipeline.
Which Square POS setup works best if my restaurant is Android-first?
Three patterns work. One, iPad at the counter plus Square for Restaurants, Android handhelds for line-busting running Square for Restaurants A32 5G. Two, Android tablet at the counter running Square Point of Sale (generic) and accepting that you do not get the restaurant-specific flows. Three, Square Register hardware, which runs Square for Restaurants natively without any iPad. In all three patterns, PieLine treats the Square merchant account the same, because the ingestion is API-level.
What happens to a phone order if my in-store device is offline or the Android app crashes?
The order still lands. PieLine writes to the Square Orders API first, which means the record exists in Square's cloud before any device syncs it. When your device reconnects, the order appears in the feed. PieLine also retries on transient Square API failures and logs a handoff event if the Orders write fails twice in a row, at which point the call escalates to a manager with the order payload attached.
How does PieLine price compared to adding another Android-capable Square hardware device?
PieLine is $350 per month flat for up to 1,000 phone calls answered (with money back on the first month), with $0.50 per call beyond that. A single Square Register runs in the $799 to $1,499 range as a one-time hardware purchase, plus software subscription. The comparison is not like-for-like, though, because PieLine replaces the dedicated phone employee at $3,000 to $4,000 per month and handles up to 20 simultaneous calls. The Android device question and the phone ordering question are separate budget lines.
Will PieLine work the day I switch from the generic Square POS Android app to Square for Restaurants on A32 5G or iPad?
Yes, immediately. Because the integration is at the API layer, changing your counter app does not require reconnecting PieLine. Your menu, modifiers, and discount structure in Square stay intact. You may want to resync if you change your catalog structure (adding modifier sets, renaming items), but the PieLine-to-Square link is durable across counter-device changes.
Bring your Square login. Watch a phone order land.
On the demo we will OAuth into your Square sandbox (or your production account, your choice), place a live phone call, and watch the order show up in your Dashboard, on your counter device, and on your kitchen printer. Your cashier does not have to change a thing.
Book the demo