We currently have 4 to 5 physical products that we sell on our Square online website. One of those products is a calendar that we sell for $5.50 per item, with shipping. Another example is a decal that we sell for $1 per item, with shipping. We also sell dog collars for $5, with shipping, for the entire order. We use the shipping profiles in Square Online to set up these custom flat rates.
It appears that your March 7 change to Square Online to move those settings into the main Square Dashboard has broken the per-item custom flat rates. I went in to make changes to the rate we were charging for the calendars, and now I cannot select the country more than once without removing it from all of the other custom shipping rate profiles. The way this works has been completely inverted, but it’s not been done correctly.
The interface now directs you to create a profile specific to a geographic region rather than a type of rate. Once you use that geographic region, you can’t use it again on another profile. Furthermore, for a specific region’s profile, you can add multiple rates, but it only accepts one at this time. If you try and put multiple flat rates, it neither has the ability to save those additional rates nor assign them to the items that you’ve selected for the profile.
What’s even more challenging is that the March 7th notification of this change is mentioned on the Square Online menu item for shipping settings, and you can still manage those settings there, but they don’t seem to have any effect. So the original controls are still available, but they aren’t wired into the actual new shipping profiles that are back on Square Dashboard.
This feels like an incomplete feature release or a buggy feature release. I have had to remove all shipping profiles from my account, and we are currently no longer charging shipping. We’re a nonprofit that works on flat-rate shipping rather than having to give our volunteers scales and require them to ship merchandise in the same type of packaging every time we ship.
Please reply and/or get this fixed. cc’ing @heisel for assistance.
