Bugs

What is the shop or customer experiencing? When adding images with the recommended dimensions (2000px W by 1000px H) to the new Advanced Slideshow widget, the images display perfectly within the Site Creator preview. However, once published, the images appear heavily cropped on the live webstore for anyone viewing at a standard 100% browser zoom. Interestingly, if the viewer zooms their browser in to 150%, the image adjusts and displays correctly without cropping. What is the expected behavior? Images sized at 2000x1000px in the Advanced Slideshow should scale dynamically and display without cropping on the live webstore at a standard 100% zoom level, exactly as they appear in the Site Creator preview. What error messages are there? NA Did you replicate? Yes. The exact same behavior was replicated on our internal test account using the same image dimensions within the new Advanced Slideshow widget. What settings were checked? Navigate to Site Creator and add the Advanced Slideshow widget. Upload images formatted to the correct dimensions (2000px W by 1000px H). Observe the preview within the Site Creator (images display correctly without cropping). Publish the site. Open the live webstore in a new tab and view the slideshow at 100% browser zoom. Observe that the images are cropped. Change the browser zoom to 150% and observe that the images adjust and are no longer cropped. Provide examples, sku, order #, customer names, and screenshots where possible. NA

What is the shop or customer experiencing? The shop is reporting a critical checkout issue: whenever a customer tries to complete their purchase, they get stuck on a completely White screen and are unable to type in any numbers to complete the payment. What is the expected behavior? The customer must be able to check out via app or website easily. What error messages are there? "White Screen" Did you replicate? Yes, everything processed smoothly on my side. What settings were checked? I have checked the customers details and the app version. Provide examples, sku, order #, customer names, and screenshots where possible. First customer, jparmer1@stx.rr.com ), Julie A Jones & Second one is tlangston41@yahoo.com

What is the shop or customer experiencing: The shop is unable to update the price of an existing gift card from $160 to $200. Furthermore, when they try to add a new denomination to the gift card, the newly added denomination fails to appear or reflect anywhere on the shop's dashboard even after attempting to save it. What is the expected behavior: The system should allow shops to successfully edit gift card prices/denominations or add new variants to pre-existing gift cards, and these changes should immediately reflect on the shop's dashboard. What error messages are there: The dashboard throws a "Whoops, something went wrong" error when trying to edit the price column on an existing gift card. Furthermore, when testing variant creation in OPS, the denomination field triggers a validation error stating the input must be "more than 3 numbers" (which can be bypassed by hitting the spacebar at the beginning of the field) Did you replicate: Yes. Replicated successfully on our internal test shop. During testing on a sandbox shop, I confirmed that a gift card can be created successfully the first time by inputting the price in the Sale Price column and the face value in the main amount field. However, once the gift card is created, any attempt to edit the price field or add new variants results in a hard system error. What settings were checked: Checked the gift card creation and variant workflows across both NPS and OPS. Specifically tested the cross-platform behavior of the Sale Price column and the main Amount/Retail value fields during initial creation versus subsequent edits, highlighting the breakdown when moving from an NPS-created card to the OPS backend tool. Provide examples, sku, order #, customer names, and screenshots where possible. SKU: 12348

What is the shop or customer experiencing? The shop is unable to update the sale price for a product. Additionally, after deleting a product to try and recreate it, they are blocked from updating the Sales prices because the system flags it as already in use. What is the expected behavior? According to the latest system update, users should be able to successfully reuse an SKU from a deleted product. Furthermore, updating a product's sale price should save smoothly without triggering an SKU conflict error. What error messages are there? "The SKU has already been taken." Did you replicate? Yes. After deleting the recent product and attempting to add a new one using the same SKU, the system blocked the creation and threw the "SKU already taken" error. What settings were checked? Checked both the active Products tab and the Deleted Products tab. Provide examples, sku, order #, customer names, and screenshots where possible. SKU: 41800188

Boutique did a sale using a scheduled live. Items reverted back but TikTok did not update to show the retail price after the schedule sale ended

What is the shop or customer experiencing: shop reported an issue regarding insight tab under MSM section. When the shop created a custom date for the key focus date section and hit or load the Focus date filter is showing an incorrect ending date. For example: If a shop creates a custom date as July 1st 2026 to July 7th 2026 then the ending date for Key Focus Dates is shown as July 1st 2026 instead of July 7th 2026. However, data is showing correct as per the custom date. What is the expected behavior: Ending date for Focus Date Filter should show as per the end date of custom created date. What error messages are there: No error message just ending date showing in correct. Did you replicate: Yes, I replicated and same showing to me. What settings were checked: I have checked Insights tab > MSM and then Key Focus data and custom date filter. Provide examples, sku, order #, customer names, and screenshots where possible: Attaching Screenshot

What is the shop or customer experiencing? The shop is reporting a recurring issue where multiple customers encounter errors during the pre-authorization process. Uninstalling and reinstalling the mobile app serves as a temporary workaround, but the issue eventually returns. What is the expected behavior? Customers should be able to successfully pre-authorize items on the mobile app without hitting error blocks. What error messages are there? Oops! Invalid Waitlist items. Did you replicate? Not successfully replicated yet. There is a working theory that the error might trigger specifically when a customer has a prior order placed with coverage (e.g., Redo) and is subsequently trying to authorize a waitlisted item. What settings were checked? App Version: Confirmed that this shop was one of the first to receive the 5.1 app update, and the issue is actively affecting multiple customers on this updated version. Provide examples, SKU, order #, customer names, and screenshots where possible. : Pending - An email has been sent to the shop to gather specific product names, SKUs. These will be added as soon as the shop replies.

What is the shop or customer experiencing? The Inventory Snapshot is not showing data, it is empty when select a date and click on Generate What is the expected behavior? It should show data when Generating as there are items showing inventory in them. What error messages are there? NA Did you replicate? Yes, faced the same issue, the CSV file is empty. What settings were checked? Checked the Reporting then CSV New then Inventory Snapshot Report Provide examples, sku, order #, customer names, and screenshots where possible. CSV files attached

Orders that have Redo or Seel coverage on them and are not paid by Square are not syncing to square. When you click the 'Sync to Square' button on the orders tab, you get an error banner that reads "This order could not be exported." Orders with neither coverages export fine.

What is the shop or customer experiencing: Shop confirmed that the customers facing issues while adding a product add on "Something went wrong" What is the expected behavior: As per the feature behavior with add-ons, shoppers can add additional elements to a purchased product without giving any error. What error messages are there: Something went wrong. Please try again. Did you replicate: Yes, I tried on both app and website and I'm also getting the same error. What settings were checked: Checked the product and Product Customization section to see if Include Product Add-Ons is enabled and add on added. Provide examples, sku, order #, customer names, and screenshots where possible: Product name: cheer + football LR graphic SKU: LRG220 Customer name’s: Jennifer Ortega, Ashley Rogers