Square is the point-of-sale system a lot of retail, food and beverage, and service businesses start on because it’s easy to set up with almost no runway. The trouble shows up later, once there’s more than one location or a website selling alongside the storefront, and Square’s own reporting can’t answer the question “how did the whole business actually do this month” on its own.
Locations in Square need to become locations in NetSuite
Once a business runs Square across more than one physical location, per-store performance — sales, inventory, margin — only means something if each Square location maps to its own NetSuite location. Without that mapping, sales roll up into one aggregate number and you lose the ability to see which store is actually performing and which is dragging the average down. This mapping is usually the first structural decision in a Square integration, and it needs to happen correctly before order data starts flowing, since retrofitting location structure after go-live means reclassifying historical transactions.
Modifiers make restaurant and service items messier than they look
For restaurants and service businesses in particular, Square’s item structure includes modifiers — a burger with extra cheese, a haircut with an add-on service — that change price and sometimes inventory consumption without being a distinct item in the traditional sense. A naive integration treats every modifier combination as its own new item, which bloats the NetSuite item list into something unmanageable within a few months. We map modifiers to reflect how they actually affect price and inventory consumption rather than spawning a new SKU for every combination a customer could order.
Deposits and fees need to be unwound, not lumped
Square deposits into your bank account net of processing fees, and on a schedule that doesn’t necessarily match the day a sale happened, especially for weekend transactions that settle differently than weekday ones. If that deposit posts to NetSuite as a single number against revenue, gross sales and processing fees both end up misstated even though the net cash is correct. The integration needs to break the deposit back down into gross sales, fees, and any refunds or voids that occurred in that batch.
Refunds and voids happen at the register, and need to show up correctly
A void that happens before a transaction settles behaves differently from a refund issued after the fact, and Square distinguishes between the two. NetSuite needs to reflect that distinction rather than treating every after-the-fact correction the same way, particularly for businesses where refund patterns by location are something finance actually wants visibility into.
Customer records shouldn’t fragment either
Square captures customer information at the point of sale — repeat customer profiles, loyalty activity, contact details collected at checkout — and that record is often incomplete or duplicated against whatever customer database already exists in NetSuite from other channels. Syncing customer records, not just transactions, means a repeat customer who shops both in-store and online shows up as one customer history in NetSuite rather than two disconnected profiles that make it impossible to see their full relationship with the business.
Square plus a storefront
A lot of Square merchants also sell online, whether through Square’s own online store or a separate platform like Shopify. Once that’s true, the real value of the NetSuite integration is having one inventory number that both the in-store Square terminal and the online storefront pull from, so a sale at the counter is reflected online within minutes and vice versa — no more manually adjusting stock counts because two systems drifted apart.
Square is simple enough to run without an integration for a single location doing modest volume. The moment a second location, a modifier-heavy menu, or an online channel enters the picture, that simplicity stops being enough. For the details on what syncs and how, see the full Square integration guide, or contact us to talk through your current setup.