This Week in Square POS: What to Test Before Monday

Do not activate every Square change before your next busy shift. Test the updated Checkout grid only if staff already experience checkout friction, prepare QR dine-in tabs and kiosk upsells before exposing them to guests, and restrict unlinked refunds because they can send money to a card without an original Square sale.

Square’s September 10, 2026 release notes identify the release as Volume 12, version 7.24. The release covers many products, but four changes deserve a practical small-business decision: the updated Checkout grid, QR dine-in tabs, Kiosk Smart Upsells, and unlinked refunds.

This review does not assume that every feature is available or useful for every seller. Square ties some features to particular products, modes, permissions, or subscriptions. Confirm what appears in your own Dashboard and current Square documentation before changing a live workflow.

Use one rule: test according to operational risk

A reversible staff-facing layout change can usually begin with one device during a quiet period. A customer-facing ordering feature needs an end-to-end test because a guest will experience every unclear step. A refund tool deserves stricter access because an error can move money out of the business.

Use these three questions for each release item:

1. Does it solve a problem we can name? If there is no current problem, the feature can wait.
2. Who owns the test and rollback? A setting without an accountable owner should not enter a live shift.
3. What result means keep, revise, or stop? Decide this before staff become accustomed to the new workflow.

The goal is not to finish Square’s release list. It is to protect normal operations while testing the smallest change that could improve them.

Test the updated Checkout grid when modifiers slow the counter

Square says the updated Point of Sale Checkout grid makes items, categories, discounts, customers, and actions easier to find. The cart updates in real time, and the redesigned item-detail view keeps the cart visible while staff choose variations and modifiers. Square lists the update for Point of Sale on iOS and Android.

That description suggests a useful test for modifier-heavy orders, but it does not prove the layout will be faster for every catalog. A seller with a small menu and experienced cashiers may see little benefit. A café with sizes, milk choices, add-ons, and allergy-related modifiers has a clearer reason to test.

Square’s item-grid support page says sellers can switch back from Dashboard under What’s New > Early Feature Access. It also says the switch-back option is available for 90 days after the update is enabled, and changes made in the previous layout after switching back will not sync to the new one. Treat rollback as a controlled decision, not an invisible undo button.

A one-device café test

Hypothetical scenario: A lunch café uses two counter tablets. The repeat problem is a sandwich order with bread, protein, side, and allergy-related modifiers. The owner chooses Tuesday at 2:30 p.m., after the lunch rush, and enables the updated experience on one tablet only.

A lead cashier rings five test orders based on common tickets: two simple drinks, two modifier-heavy sandwiches, and one order that needs an item correction and the normal employee discount. No fake payment should be completed unless the business has an approved test procedure; the point is to observe navigation and cart visibility.

The observer records four results:

• the first step where the cashier hesitates;
• whether the cart remains clear while modifiers are selected;
• whether discounts, customers, and corrections remain easy to find;
• whether the problem comes from the layout or from poorly named catalog items.

Keep it when common orders are completed without new confusion and staff can explain the changed steps. Revise the catalog first when unclear item or modifier names cause the delay. Switch back when the new layout creates a repeatable checkout problem that cannot be corrected before the next busy shift.

Before enabling the grid, save the current checkout sequence and assign one manager to record the first point of friction and make the rollback decision.

Prepare QR dine-in tabs as a full payment journey

Square says QR dine-in tabs allow guests to open a tab from a table QR code, add to it during the visit, and pay once at the end. Opening a tab preauthorizes the guest’s card, while the full payment completes at close-out. Staff see one in-progress order and manage it through Open Tickets.

Square lists the feature for Square Plus and says sellers enable it from Online Ordering > QR Code Ordering. The release notes also say sellers can set a minimum preauthorization amount. These product conditions should be checked in the seller’s own account because subscriptions and interfaces can change.

Do not test this feature by confirming only that the QR code opens. Walk through the complete guest journey:

1. A guest scans the table code and opens a tab.
2. The guest adds a second round.
3. Staff find the order in Open Tickets.
4. The guest changes tables or asks whether the card was charged.
5. The assigned employee closes the tab and confirms the completed payment.

Choose one role that owns open-tab checks and one role that handles payment questions. Defer launch when staff cannot identify an open tab, explain the preauthorization, or close the order consistently. A customer-facing payment workflow should not become a live experiment during a rush.

Review Kiosk Smart Upsells before customers see them

Square says Kiosk Smart Upsells recommend related add-on items during ordering and are turned on by default, while sellers control whether the feature remains on. Square directs sellers to the Kiosk group settings profile in Dashboard to manage upsells.

The operational question is not whether upselling sounds useful. It is whether each suggested item is available, priced clearly, routed correctly, and practical for the team to fulfill.

Have the employee responsible for preparation review the live suggestions. A packaged pastry located near pickup may be easy to fulfill. A made-to-order drink suggested during a short-staffed period may create a ticket the team cannot complete at the expected pace. This is a fulfillment decision, not a revenue forecast.

Keep an offer only when the item is available at that location, reaches the correct prep station or ticket, remains visible during a rush, and clearly communicates that it adds cost. Remove or disable an offer when any of those answers is uncertain.

Open the kiosk’s live upsell list with the person responsible for fulfillment and remove any suggestion the current shift cannot reliably prepare and hand off.

Put the strictest controls around unlinked refunds

Square defines an unlinked refund as a refund that is not connected to an earlier payment made with Square POS. The September release notes say staff can issue one from Transactions even when Square has no record of the original sale. The refund can be made by amount or selected items, and the release notes say sellers can assign access by team-member permission and configure a per-transaction cap.

This is different from finding the original Square transaction and processing a normal linked return. Square’s return and unlinked-refund support page warns that issuing a refund without a transaction record presents risk of loss, including scams, fraud, error, and employee misuse.

The same support page lists current product, mode, subscription, and permission conditions. It identifies account owners or team members with permission to issue refunds and unlinked refunds, and it describes availability across specified Square and Square for Retail plans. Confirm eligibility in the current support page and your account instead of assuming the feature appears everywhere.

A practical small-team control is:

• search for the original transaction before using the unlinked path;
• limit access to the owner or a designated accountable manager;
• set a transaction cap appropriate to the business;
• require a detailed description, reason, and available evidence;
• review every unlinked refund the same day.

Square says refund records can show the reason, amount, date, time, and cashier, providing a review trail. That record is useful only when someone is assigned to inspect it.

Your focused plan before the next busy shift

Begin by marking which products the business actually uses: Point of Sale, QR Code Ordering, Kiosk, or retail-mode return tools. Ignore release items that do not touch the operation.

Then choose one action:

• Modifier-heavy counter: test the Checkout grid on one device during a quiet period.
• Table-service QR ordering: assign tab ownership and rehearse one guest exception before enabling it.
• Square Kiosk: inspect the live upsell list with the fulfillment team.
• Returns operation: review unlinked-refund permissions, limits, documentation, and same-day oversight.

Do not run all four tests merely because the features share a release date. Start with the change that addresses a documented problem and has a clear owner. Record what happened, decide whether to keep or reverse it, and only then consider the next feature.

Sources

• Square Release Notes, September 10, 2026 — product changes, access notes, and settings paths.
• Square Support: Set up item grid — rollback period and synchronization limitation.
• Square Support: Process a return, exchange, or unlinked refund — eligibility, permissions, risk warning, procedure, and review data.

Editor’s note: Product availability, subscriptions, interfaces, and terms can change. Verify settings and eligibility in your own Square account and current Square documentation before changing a live payment or refund workflow. This independent article is not affiliated with or endorsed by Square.