8000 Feature: Support for custom input / product variants · Issue #68 · yournextstore/yournextstore · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Feature: Support for custom input / product variants #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
pdanysz opened this issue Nov 8, 2024 · 2 comments
Open

Feature: Support for custom input / product variants #68

pdanysz opened this issue Nov 8, 2024 · 2 comments

Comments

@pdanysz
Copy link
pdanysz commented Nov 8, 2024

Here's a proposal to add a product metadata/variant type that lets customers input text on the Single Product Page. This would enable selling customizable products where customers can provide custom text when ordering.

Example: I'm selling t-shirts and want customers to order with their own text during checkout.

Is it possible to implement this feature?
@pdanysz pdanysz changed the title Feature: Support for custom input custom variants Feature: Support for custom input / product variants Nov 8, 2024
@typeofweb
Copy link
Member

This is actually more challenging than I initially thought. From both UX/UI perspective, as well as technical difficulties.

Let's consider a scenario where I add the same item (a t-shirt) to my cart 5 times. Now, should the interface only show a single "custom field" or 5 of them? The latter means the UI could quickly become cluttered. And that's only assuming a single item has only one "custom field". What if there's more?

The other problem with this is that Stripe metadata is a simple set of key-value tuples. If we allow multiple "custom field" and multiple answers when the same product is added to the cart many times, we might have trouble saving it in cart's/order's metadata.

My initial thought was we could save customField_${productId}: ${value}, but that doesn't cover multiple products nor multiple questions.

I'm currently thinking of customField${fieldIndex}_${productId}${productIndex}: ${value}, but that seems to be somewhat brittle. The ordering of Stripe metadata fields is not guaranteed. What if it changes? Answer indexes won't match the questions!

I'd appreciate any help, thoughts, use-cases, etc. Maybe I'm thinking too big, and something much simpler would suffice.

Thoughts?

@sparkmagicllc
Copy link

see this: https://docs.stripe.com/payments/checkout/custom-fields?payment-ui=stripe-hosted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pdanysz @typeofweb @sparkmagicllc
0