One location
One shop or one restaurant, one catalog. Additional shared-menu locations are quoted before anything begins.
One connected platform
Your business, beautifully connected.
Every detail, connected. Explore all features.
Built around your business
Your business has its own rhythm.
Ready to begin? Get started online.
Explore at your own pace
See the possibilities. Find your next step.
Looking for a definition? Browse the glossary.
Square configuration
Anyone can take a payment on Square in an afternoon. That is the point of it, and it is genuinely well made. The trouble arrives about four months later, when the item library has grown sideways, three people have built the same modifier three different ways, and the reports cannot answer a simple question.
This page covers how Square is put together underneath, which settings decide what, and where the register and the website stop agreeing with each other.
Tell us what is happening on your floor →What does a Square POS setup consultant do that I cannot do myself?
The work is structure, not typing. Categories drive kitchen routing and reporting. Modifier sets carry selection rules, defaults, per-channel visibility and nesting limits. Menus carry dayparts. Online visibility depends on five separate settings agreeing. Most owners can build all of it; few have a spare week to discover which decisions are hard to reverse.
Square keeps one item library and everything reads from it: the register, the online site, the kiosk, the delivery integrations, the reports. That single source is the best thing about Square and the reason a sloppy library hurts in six places at once.
Three concepts do most of the work, and mixing them up is the most common structural mistake we find. Variations are versions of the same item chosen before the sale, each with its own price, cost and SKU. Options are reusable attribute sets that generate those variations by combination, so a Sizes set of three and a Colors set of three produces nine variations without you typing nine rows. Modifier sets are choices made during the sale, like adding cheese.
Categories are the other one. An item can sit in more than one, and Square uses categories for reporting, for kitchen routing to specific printers, and for organizing the register in standard mode. In the restaurant modes, customer-facing organization moves to menus, and categories keep doing the back-of-house work. Owners who never set categories properly end up with a sales report that cannot tell them what food did versus what drink did.
A variation is what they ordered. A modifier is what they changed. Reports go strange when a shop confuses the two.
A modifier set attaches to many items at once, which is the whole point, and then can be customized per item. Square calls the behavior controls selection rules: you can require a selection, allow more than one modifier, and set minimum and maximum quantities, so a build-your-own bowl can demand one base and permit at most three toppings.
Modifiers can carry a negative price, which is how removing something takes money off rather than pretending it is free. They can be marked as a default selection so the standard build is pre-chosen and the server only touches the exceptions.
The limits are worth knowing before you design around them. Square documents a maximum nesting depth of three levels for nested modifiers, a maximum of five child modifier sets per modifier, and a 150-character maximum on text modifiers, which is the field your kitchen reads as a special request. Modifier sets also carry their own location and channel availability, and a set can only be assigned to an item whose locations and channels it matches. That mismatch is a frequent cause of a modifier that exists on the register and vanishes online.
In the restaurant modes, a menu is a set of menu groups and items that appears on the POS, the online site, the kiosk, your ordering profile and delivery apps. Menus can be scheduled, and menu groups can carry their own hours inside the menu hours, which is how a lunch menu with a happy-hour group behaves correctly without anyone remembering to switch anything at four.
The channels behave differently and it catches people out. On the POS, the menu picker shows the right menu automatically and a passcode lets a manager override it. On online ordering and kiosk, menus stay visible but are only orderable during their hours. Delivery apps are configured separately.
A small trick that makes a build safe: a menu with no sales channels assigned is a draft. You can construct next season entirely in the open, look at it, hand it to the owner, and publish it by assigning the channels on the morning it starts.
Square Online reads from the same library, so when an item is missing from the site the instinct is to blame the sync. It is almost never the sync. Square lists the reasons, and in our experience they land in this order: the item is not assigned to that site as a channel, the item is set to be discoverable via direct link only, a variation has no price, inventory is not being tracked with a stock number entered, pickup and delivery hours are undefined, the location is not enabled for site visibility, the location is a mobile location rather than a physical one, or the site simply has unpublished changes.
Eight settings, one symptom. This is exactly the kind of thing that is thirty seconds to fix and a lost afternoon to find, and it is why a written configuration beats a clicked-together one.
A short list of the ones we find switched to something nobody chose.
We start from your actual menu or catalog rather than a template, because the structure has to match the way your staff already speak about the food. Then the library, the categories, the modifier sets and the menus get built in that order, since each one depends on the one before.
Then taxes, service settings and permission sets with you on the call, because those are business decisions and we are not going to guess at them. Then online ordering, then the quick-start guides and video walkthroughs for each role, and a setup record in your portal so somebody on your side can change a price on a Tuesday without booking us.
And a caveat we would rather say early: if you are a full-service restaurant with coursing, seat-level ordering and a bar that needs deep routing, we will tell you on the call what Square for Restaurants handles today and what it does not. We support Toast for restaurants already on it, so that conversation costs us nothing to have honestly.
Stated in numbers, so nobody has to guess where it ends.
The bounded scope from our rate sheet, in plain numbers. There is a fixed price for it and it lives on the pricing page.
One shop or one restaurant, one catalog. Additional shared-menu locations are quoted before anything begins.
Built with variations where variations belong, categories set for routing and reporting, and the duplicates removed rather than carried across.
Reusable modifier sets with selection rules, minimums and maximums, defaults and per-channel availability configured deliberately.
Dining options, tax behavior, service charges and gratuity handling decided with you on a call, then written down so the next person can read it.
Permission sets that match your floor: who comps, who voids, who refunds, who sees the numbers.
Two standard integrations connected and tested end to end. More than two is quoted up front, never discovered at invoice time.
Online ordering configured and checked against the item library, quick-start guides and video walkthroughs for each role, and a setup record in your portal.
Anything past these limits is quoted before it starts, never after. Every published price is on one page.
Be honest with me
Your Square account is opened under your legal entity on your billing, and it stays yours whether you keep working with us or not. We charge you for configuration work at a published price.
Sometimes, and sometimes not, which is why we sell a health check as a separate small thing. Roughly half the reconfigurations we are asked about turn out to be four settings and an afternoon of deleting duplicates. We would rather tell you that than take the larger invoice.
Yes, and it is usually the same job, since the site reads the same item library. What we will not pretend is that a Square Online site is the same product as a designed website. If you want a site you fully control the design and structure of, see restaurant website design and we will talk through the trade-off.
From quick-start guides and short video walkthroughs written for your setup, one for each role, so front of house and management are not sitting through each other’s material. The setup record in your portal is aimed at one specific outcome: somebody on your side can add an item and change a price without calling anyone. A configuration only one vendor understands is a configuration you do not own.
You tell the support team in your portal, and it is worked from the setup record until it is fixed. Anything that is blocking sales comes first. After launch we check the setup with you, review how it is running once the team has lived with it, and talk about what comes next.
A short call, a screen share, and an honest read. If the answer is that your setup is fine and the problem is the online ordering link or the Google listing, that is what we will say.
Platform pricing and features change; where a platform does not publish a number we say so rather than guessing.
Shop & Table connects with supported commerce platforms. Square and Toast are trademarks of their respective owners.
You are leaving shopandtable.com
We link out when a vendor’s own documentation or a regulator is the right source. The site you are about to visit has its own terms, its own privacy practices and its own content; none of it is covered by our Privacy Policy or Terms of Service, and a link is not an endorsement. It will open in a new tab.