Why is my shipping profile throwing a generic error and won't save?
A generic error on your shipping profiles during a Shopify incident usually isn't your configuration's fault - here's how to confirm it, avoid making it worse, and get support to act fast.
What's going on
Every so often, saving or updating a shipping profile in Settings > Shipping and Delivery throws a generic, unhelpful error - something like "Something went wrong," or the save just silently fails - with no indication of what's actually wrong with your zones, rates, or product assignments. Nothing in the configuration looks broken, retrying the exact same save sometimes works a few minutes later, and other merchants report the identical symptom around the same time in Shopify's community forums.
This pattern is a strong signal the problem sits on Shopify's side, not in your store's settings. Saving a shipping profile touches several backend services at once to validate rates and zones across your catalog, and when one of those services is degraded during a platform incident, the admin often can't produce a specific validation message - it just fails generically. Because the failure is intermittent and clusters around known incident windows, Shopify's own status page is usually the fastest way to confirm what you're seeing is bigger than your store.
Why it happens
Shipping profile saves in the Shopify admin trigger validation across your product-to-profile-to-zone-to-rate mapping, which touches several backend services at once. When one of those services is slow or unavailable during a platform incident, the admin UI typically can't surface a precise cause, so it falls back to a generic error rather than telling you which zone, rate, or product assignment supposedly failed.
These incidents are usually brief and often affect only a slice of merchants rather than all of Shopify at once, which is why the pattern looks intermittent: some merchants are affected and others aren't, and the same merchant may see it clear up on a retry a few minutes later. That's also why a quick check of the status page, or a search of the Shopify community forums for the same symptom, often confirms what's going on faster than troubleshooting your own settings from scratch.
5 ways to fix it
Check status.shopify.com first, and note the exact time
Before changing any settings, check status.shopify.com for an active incident affecting Admin, Shipping, or Checkout. Screenshot the notice if there is one, and write down the exact time, in your store's timezone, that the error first appeared for you. Having that timestamp ready turns a vague support ticket into a fast one if you end up needing to escalate.
Retry later rather than deleting or rebuilding the profile
A generic error on the Shipping and Delivery settings page during a platform incident is almost always the save request failing on Shopify's end, not a problem with your actual profile configuration. Deleting a shipping profile and recreating it, or mass-reassigning products between profiles while the platform is degraded, risks leaving products unassigned or duplicated across profiles - a mess that can outlast the original incident. Wait and retry the same save once things look stable again.
If it's not resolving, open a support ticket with specifics, not just a description
If the error persists after the status page shows no issues, contact Shopify Support through the Help Center or the admin's help widget. Give them the exact time of your failed save attempts, your store's myshopify.com domain, and whether the error happens while editing a shipping profile or while calculating rates at checkout. Concrete details like these help a support agent diagnose faster than a general description of the symptom.
Audit the profile once things are stable, since incidents can leave inconsistent state
Once you've confirmed the platform is healthy again, revisit Settings > Shipping and Delivery and check that every product is still assigned to the profile you expect. A save that partially failed during an incident can leave a product sitting in the default profile instead of the custom one you intended, or a zone or rate that reverted unexpectedly. It's worth a quick pass to confirm nothing shifted.
Test checkout directly to confirm things are actually fixed
Don't assume a resolved status-page incident means your store is back to normal. Add a product to a cart and walk through checkout with a real address (or place a test order) to confirm customers are seeing the shipping rates you expect. This is the only reliable way to know your specific store's data is behaving correctly again, rather than just trusting that the wider incident has cleared.
Bottom line
This is a platform reliability issue, not a configuration bug you can permanently fix on your end - the right response is a repeatable process (check status, note the time, retry, then escalate with specifics) rather than rebuilding your shipping setup every time it happens. If your team ends up firefighting these incidents often enough to want a standing checklist built into your workflow, that's the kind of narrow, one-time tool a shop like BesPoP would build as a problem-specific guide rather than a subscription app.
Browse the rest of the problem library, run a free storefront scan to catch issues like this automatically, or email us and we'll work out a custom solution for it.