zaiste

https://yournextstore.com https://github.com/yournextstore/yournextstore

I'm building Your Next Store (YNS); it's a Shopify alternative built with React and Next.js.

We provide an opinionated boilerplate tailored for tools like Claude or Codex, so designers and developers can build storefronts faster and more easily. It enforces a clear structure to start from while keeping full control over design, animations, and the overall storefront experience. It’s built on top of Stripe, with our higher-level commerce abstractions, like "add to cart", "checkout", "pay", "browse products" etc; plus a Commerce CMS so merchants can manage everything smoothly once their store is live.

If youre planning to sell something online and want a modern solution, hit me up! :)

Great!!

Thanks! Happy you liked it!

I can confirm the bug - thanks for the heads-up! We recently did a few iterations on that part, and it looks like something slipped through the cracks...

We're planning to stick around a bit longer :)

Is there anything I can do to help or convince you to give us a try?

Thanks! Could you describe your use case so that I could better understand how to implement this?

That's an interesting insight, and I'd like to learn more about it.

Off the top of my head, have you considered using the Stripe API directly in those other places? i.e. Stripe as the source of truth, with data being fetched to those other places as REST calls for example?

I imagine that linking those "other" orders with products might be a bit tricky, though

I completely agree with you on WooCommerce themes.

we're also working on themes, which will be based on shadcn UI.

Thanks!

We're experimenting quite a bit at the moment - starting with Umami, but we’re also considering developing a custom solution (analytics subset) specifically for e-commerce

Coupons are on our roadmap, and adding them should be relatively straightforward. Would you be interested in beta testing it with us? :)

A Dockerfile has been proposed by the community. I’ll review it today: https://github.com/yournextstore/yournextstore/pull/22/files

We started by storing data like stock as product metadata directly in Stripe. Plus, we’re developing a thin layer to manage the sync between individual stores and Stripe (e.g. atomicity)

This solution is not (yet) ideal, but works well for most small stores and we have some ideas how to improve it further - composability/headless can be overwhelming in many such scenarios.

Yes, we've had similar experiences and plan to address them to some extent. In certain cases, like with Facebook, it might not be straightforward, but we want to provide built-in alternatives e.g. analytics specifically tailored for e-commerce that cover ~80% of what you need, with the rest being a trade-off.

I also think Facebook, Google, Hotjar et al. will eventually get better with those scripts.

Congrats! Looking forward to your project! Let me know what's missing and what's not ideal and generally your feedback. You can contact me by email once you start building.

Thank you for the kind words! :)

we’re fully focused on Stripe and don’t plan to support other providers. This is because e-commerce is more than just a payment gateway. Our goal is to integrate various Stripe features into a comprehensive and convenient package for online commerce, while using the synergies between different Stripe products.

That said, the project is open-source, so the community could add support for something like Razorpay.

When you mention Stripe isn’t available everywhere, which country would you like to see added?

Thanks!

Yes, we’re working on this - we plan to start by enabling stablecoin-only payments. Would that work for your use case?

Using CSV is an interesting idea! I havent looked at your code yet - does it automaticaly sync when something changes in the file? Do you have an admin panel for end users? In YNS, we provide a dashboard that simplifies managing products and orders (though it’s not yet open-sourced)

Sorry about that! I'd need to learn a bit more about your setup.

For starters could you remove the `packageManager` from the `package.json` entirely and try again?

if you're available, we can do a quick video call and I'll see exactly what happens on your side as I cannot reproduce it atm

Stripe’s tax features have worked well for our use cases so far, and we also have experience with Avalara from previous projects. Would you be open to connecting over a video call to discuss your specific needs? I think it might be easier that way as it's a broad topic :)

Thank you! we initially focused on physical products, but adding features for digital products should be even easier. Could you point me to your ideal solution or describe how it would work in a perfect scenario? Something we could use as an inspiration for both: digital and lead magnet downloads

I can no longer edit the post, but here's the working demo of YNS https://demo.yournextstore.com

To see Stripe Link in action, use the email `test@test.com` and then enter `000000` when it activates.

This feature isn’t ready yet, but it’s something we’re actively working on. To have shipping right away, it could be outsourced to a third party, and some of our partners are developing such functionality this way.

In the long term, we aim to make it tightly integrated with Stripe, making Stripe the core infrastructure for your e-commerce needs.

Yes! One-page checkout has been, and continues to be, one of our top priorities. There are still a few minor improvements to be made, but I’m really happy with how smooth the experience is rihgt now.

Have you tried it with Stripe Link? This reduces the entire checkout process to just four (4) clicks; no need to fill out forms as long as your details have been saved from a previous purchase elsewhere on the Internet.

Thank you for the kind words!

Great! Let's do this. I'll send an email

Thanks for the kind words!

We use Stripe’s "Product Catalogue", a relatively old but, to our surprise, somewhat lesser-known feature. By leveraging metadata, you can represent most e-commerce concepts, and we’re actively working on expanding those capabilities even further, beyond products and orders.

And yes, caching is the key ingredient in YNS. The combination of RSC and Next.js Cache works really well - different React.js components can independtly fetch remote data and Next.js gives you great flexibility in managing that.

That sounds like a great idea!

Actually, my fiancée sells cosplay props on Etsy, and she was looking for a simpler solution - that’s partly how the idea for YourNextStore began.

Here's a prop she made for me :) https://www.instagram.com/p/C2fz0O8quhe/?img_index=1

Do you have a store with a smaller product catalog that we could use as a test bed for the migration?

We are still exploring. We don’t have any concrete data yet, but in some instances, we've observed reductions up to ten times. This seems especially relevant to specific areas, e.g. chatbots, where similar questions happen more often.

Hey!

My name is Jakub and together with my friend Michal we recently started on a mission to help improve the GraphQL tooling.

Our first initiative is to build a tool that can help «guess» the structure of internal APIs and combine it under a single GraphQL endpoint. We want to make this proces visual and as automatic as possible.

In the example posted above, we re-shape the responses so that a page in this web application can fetch only the fields it needs. This is just one of the things that can be done - there's more to explore.

Let me know what you think! (about this idea or about GraphQL in general)

Congrats to the whole team!

Is it possible to add a custom (3rd party) GraphQL endpoint to Netlify Graph at this stage?

Zapier on Steroids for programmers!

I like how Netlify went with a low-code approach that provides not only speed and flexibility, but also greatly helps with long-term maintenance. Web apps are now more connected and heterogenous than ever - there is a need to quickly and easily connect with various APIs. No-code falls short in providing performant and maintainable code bases. GraphQL-based tools could be the solution. Netlify seems to have taken the lead here. I only worry about potential vendor lock-in.

Congrats!

Congrats on the release! I like this browser a lot; it's a comprehensive, battery-included solution.

If they supported Firefox-like multi-account containers [1], it'd switch entirely to Vivaldi. Their tab grouping is really good, the session separation is the only thing missing here. :)

[1] https://forum.vivaldi.net/topic/25289/multi-account-containe...

An interview with the creator of Solid.js: https://www.youtube.com/watch?v=Dq5EAcup044