Just an idea: when this is customer facing you should also remove the label "Custom Fields". I believe it's confusing (or just not relevant in the best case). "Custom Fields" as a label is of no interest for them - they don't care how things are called inside of Polar. IMHO you should just remove it. Keep the single label value and that's fine. Nothing else needed.

To my defence, this was designed to be displayed in the table, not in a modal with plenty of space 😅

Just an idea: when this is customer facing you should also remove the label "Custom Fields". I believe it's confusing (or just not relevant in the best case). "Custom Fields" as a label is of no interest for them - they don't care how things are called inside of Polar. IMHO you should just remove it. Keep the single label value and that's fine. Nothing else needed.

Just to clarify the screenshot is from the dashboard and what the developer/seller sees and not the end customer. They only see the field on checkout as an input like the others.

I still hear you though, but I think it's less obvious to not distinguish them since the feature is Custom Fields that the developer can setup themselves. That said, they'll recognize that and perhaps we can distinguish it more with an icon / link to edit the custom field or equivalent vs. the title.

Hi @birkjernstrom, it seems the described functionality is already implemented - unless I'm misunderstanding the issue?

The dummy data used in the above recording can be found in this commit.

Definitely fixed 👍