Hi folks,
I wanted to flag an issue we’re running into when accessing shipping methods in checkout through checkout extensions.
As you may know, shipping method titles and descriptions can be translated using translation apps. This has an unfortunate side effect.
Say a merchant sets up a flat rate called “Home delivery” in their shipping settings, then uses a translation app to translate it to “Delivery to home”. In checkout, the customer sees “Delivery to home”, and the checkout extension also receives “Delivery to home” as the value. The problem is that once the order comes through, the Admin API reports the shipping method as “Home delivery” - the original, untranslated name.
This mismatch makes it difficult to reliably target a specific shipping method from a checkout extension, since the value we see at checkout doesn’t match what ends up on the order.
You might suggest we build a lookup table to map translated names back to their originals, but that’s hard to maintain in practice. We’d have to cross-reference each translated value we see at checkout against the table, and keep the whole thing in sync as merchants add methods, change translations, or enable new languages. That’s a lot of fragile overhead to work around something the platform already knows.
My ask: could the checkout extension receive the original (untranslated) shipping method name instead of the translated one? That would make it much easier to target specific shipping methods from checkout extensions.
Thanks!
