Hi!
Is there a way for the CarrierService to populate delivery group metafields for the custom shipping methods that it returns so checkout extension could access them?
As I understand this is not possible, am I right?
Hey Stan,
Would the metafields be created during the checkout process - and the checkout extension should access the values in the same checkout session?
Hey Liam, yes, CarrierService will create/update metafields so they would be available on the delivery group level for the checkout extension in the same checkout session
Have you tried having CarrierService execute metafieldsSet immediately after determining the custom shipping methods? I believe the metafields should be available then.