You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Normally product slug is formed of a product name and might be appended by -1...-n. I can't think of a case where customer could possibly refer the product to CSR by its slug instead of specifying product name. However what you saying sounds somewhat reasonable.
At the same time, I think product slug should be treated as some kind of a service property, not something customer is supposed to refer to.
Since it's mostly a UX question, I wonder what's @bswineford opinion on this.
I might be such a case, e.g. when I’m shopping online, and have a question, I usually find their email & paste the link to the product there. Still, they could click on that link, and then search by name.
But, as an admin, I think I’d be the happiest with:
That's how I do it in real life: I provide a unique code or number of the product along with the question. In case of the Fox, I guess it should be product's id. Now I wonder if we should disclose it to a customer putting it somewhere on PDP. As for the product variants - for admin user it shouldn't be hard to find which exactly SKU customer is referencing to, since Ashes PDP is clear about that.
Say, a customer sends me a link to a product.
Wouldn’t that be useful to have in this view: https://stage.foxcommerce.com/admin/products/ ?
/cc @alexanderfc @Anna-ZZZ
The text was updated successfully, but these errors were encountered: