When testing an Account UI extension that renders on the Profile page target (ex: customer-account.profile.company-details.render-after) for a B2B customer the extension is loaded correctly in the preview link. When trying to activate the extension block in the checkout and customer account editor the extension is not available (as the B2B Profile page seems to be a different page). This is true whether on the development store or a live, Plus, storefront.
Hello @Simon_Maze, Thanks for flagging this. It’s on the teams radar to support adding the B2B specific via the editor. No timeline for this yet. In the meantime, you can achieve the same thing by using a different target, and only rendering the content for B2B customers.
1 Like
We experience the same here @Sylvain. The other targets on the profile page don’t work for us because then we cannot display/access companyLocation specific content.
Hi @Sylvain
Same here, I need the conpanyLocationId to do validations on the selected company location level. Other targets won’t do the work.
We’re experiencing the same issue. Is there any ETA yet, or atleast some kind of “hack” to actually activate these targets on live stores? @Sylvain
Hello everyone,
The root cause will be addressed once the Editor can be contextualized based on different merchant markets (e.g., D2C vs. B2B), which is expected to be supported in the coming months.
In the meantime, we recommend relying on Profile targets. You can conditionally render your extension content to only target B2B customers.
How to check if a customer is B2B?
- Query the companyLocation field in the Customer Account API;
- Or call the useAuthenticatedAccountPurchasingCompany hook.
1 Like
Appreciate the detailed response 