It seems that some checkout UI extension targets show up in D2C checkouts but not B2B checkouts. For example, purchase.checkout.delivery-address.render-after. However, I can’t seem to find any documentation stating which targets B2B checkouts do/don’t support. Does that resource exist somewhere? If not, is there any target that is near the delivery address section and works in both versions of checkout?
Hi Alex - can you share the store where you’re not able to access purchase.checkout.delivery-address.render-after in a B2B context? And also can your check that the B2B checkouts have a delivery address?
Hey Liam, since your response seemed to suggest that it should work, I used the checkout blocks app to put a static content block in the same target as our app, and the static block does seem to appear as expected.
Since our app only shows the block if certain address conditions are met, I am thinking that perhaps the issue is instead related to differences in how we must read/process address data in B2B checkout.
Thanks for your help!