I am really struggling to understand why these are inexorably linked in Automations.
At the moment, we have about 50+ automations for 4 shipping options (all based on Requested Service) and 14 box sizes. Really, we should have 100+ but I gave up creating one for every single possible option and we just have to manually adjust every day. (https://cdn.shopify.com/s/files/1/1421/4994/files/multiple_automations_for_one_mailer.png?v=17538867...)
What I don't understand is why the two options are sealed together in the automations.
Ideally, I could have a Store setting that just said: set service to Requested Service. OR, since there is Service Mapping, let the Service Mapping stand alone and then be able to just make automations based on weight or whatever for JUST package size. Instead, Service Mapping forces you to either set a package--which then doesn't work for a large number of orders and you have to manually reset the packages or do an automation that also include resetting the Service, so what's the point of the mapping?--or skip setting the package, but then you cannot set JUST a package in automations, you have to also reset the shipping service, which then, again, what's the point of the Mapping? (https://cdn.shopify.com/s/files/1/1421/4994/files/Service_Mapping.png?v=1753886861)
If the two were simply unlinked in automations and Service Mapping (like they are in the order settings!) then Service could be set in Service Mapping or Automations and Packages could be set in Automations without having to have 4 different services for every package size and content combination.
It's incredibly frustrating because we have done all the other things already.
It would be a total game-changer if we could just set up our box logic once based on weight, and let the Requested Service flow in naturally from the order data. No more duplicating rules for every combo. It’s such a clean and scalable approach.
Please tell me I am not the only one who finds this incredibly frustrating and time consuming?
Amy