gonna leave that message even though I deleted the message from the scammer

I hope everyone here (who isn't spamming people in DMs) is having a wonderful day. 🙂

Apologies to anyone else receiving spam. Fortunately these people seem to be really good at DMing me, which gets them banned very quickly.

(I also say mean things to them, for good measure.)

the in-memory order updater is upon us. so far tests seem overwhelmingly positive. https://github.com/solidusio/solidus/pull/5872#issuecomment-4094840173

Been doing some cleanup of PRs and issues. If I "cleaned up" something of yours that you don't think I should have, don't hesitate to let me know.

👋 Hi everyone!

I posted a little announcement in case anyone wants to know why the project was getting all these AI-generated first-time contributions: https://github.com/orgs/solidusio/discussions/6472

Are there any Ruby “sister projects” (either literally or spiritually) to Solidus, but with a focus on subscriptions? I’m thinking about a backend for managing plan tiers, trial periods, recurring billing, updating prices over time (so older customers can stay on an older tier), that kind of thing. I had a look on Ruby-toolbox and couldn’t spot anything maintained, but maybe I’m overlooking something?

Ive built few stores 7 years ago using spree and solidus.. They were like 90% match.. I even could use same extensions on both! After all of these years i noticed sone dramatic changes, in core and direction! I would say, each can fit certain needs and requirements.. I don't want to install both and try every single feature or whether they offer certain setup. Is there a comprehensive comparison list for exampke that can tell which solution fits what? based on requirements? Which best for saas? Which gives more dynamics to do complex customization? Which offers more extension support!

Hello, it seems the community guidelines link for the contributing.md file is broken. Also is solidus good for a solo developer who wants to build e-commerce stores for small bussiness?

This message was deleted.

This message was deleted.

Hey Solidus community! We're working on a new release of Enthusiast, our open-source agentic AI toolkit for e-commerce, and wanted to share it here. Might be relevant if your team is working on agentic AI workflows - it integrates natively with Solidus and gives you: • 🔍 Natural-language product search across your catalog • 📄 Purchase order processing from unstructured inputs (PDFs, emails) • 🤖 AI-powered customer support grounded in your own product data • 🔧 Self-hostable, model-agnostic, fully under your control 👉 https://upsidelab.io/tools/enthusiast Happy to answer questions or hear what you're building!

This message was deleted.

This message was deleted.

I’m making a point of spending my weekly remaining Claude budget on open source every weekend. We’ll see if I’ll be consistent, but in the meantime I opened a this PR for getting the CI back to green plus a few other things, and gave a bump to the one for having a separate AdminUser class. Happy to discuss them or coordinate on other things more useful for the community. cc @kennyadsl @Jared Norman @mamhoff @tvdeyen

Hello everyone 👋 I'm developing an engineering strategy methodology, and to publish it, I need a few proof-of-concept examples of it applied to real systems (that are not under NDAs). So I went looking for open source projects to audit — and since I've always known about the famous Solidus vs Spree drama, I decided to make Solidus my first public report. It's built entirely from public evidence: the repo, git history, PRs, the Open Collective ledger, blogs and podcasts. The data sweeping and writing is mostly LLM work, but the reasoning is mine; that's the lever that makes a report like this possible in a day. What the public record shows, in short: the project is in excellent technical shape (CI tested against unreleased Rails and Ruby versions, machine-enforced deprecations, automated backports), but the new admin has absorbed most of the funded development since 2023 and is still at v0.4 with its main screens switched off. The July 2025 status update asked for "another developer to pick up this work" — and since 5 July 2025 no expense has left the collective, while ~$132k sits in it. My bet is that the admin is the most important surface in an e-commerce framework: merchants can rebuild a storefront they dislike, but they can't rebuild the admin — they use it as delivered. So while the new one stays half-built, everyone stays on the jQuery-era one. Also, your public blog has no recent info on future decisions or roadmaps. Before I publish, I'd much rather be corrected than confidently wrong. So, three questions that would fix or confirm the most load-bearing findings: 1. Why was the funded engagement not renewed after the July 2025 status update — no candidate, a deliberate pause, budget caution, or simply nobody proposing it? 2. Does the core team consider the new admin alive — intentionally paced, or stalled? 3. One of my conclusions on the new admin is that Nebulab started from the easy admin screens and then stalled on hard ones, but instead they should've started with the hardest ones to prove it is viable. If it works, it would be much easier to decide on the easy ones or even automate/speed up their migration with LLMs. I'll hold publication for a week in case anyone wants to comment, and I'm happy to share the full draft here first — every claim in it is tagged with where it came from (repo / web / inference). Thanks, and genuinely: the delivery machinery in this project is some of the best I've seen, which is exactly what made the rest of the picture so interesting. You've shipped two big replacements before: the storefront and the promotions engine. So I can't quite figure out what's different about the admin. Here's the draft report (75 min of reading) and a short complimentary slide deck (5 min). You can read them here or download them into a single dir so you can use cross-links from the deck to the report.

Interesting. Being based on publicly available information, it's not 100% accurate and I don't necessarily agree with all of the assessments here, but it is definitely helpful to see how the public state of the project looks when taken in aggregate. 1. No candidate. We have a new candidate in the works right now, but don't have anything to share other than that we are working on it. 2. Because of the approach we used, real stores are using it today even though it is incomplete. Work is moving slowly currently, but will resume at pace once we have our new candidate in place. 3. There's an argument to be made that we should have started with the hard stuff first, or at least got to it faster, but viability isn't a concern. Porting the more complex interface may create more churn in the new admin, but I don't think anyone is worried that building them isn't possible. As the project is pre-1.0, churn isn't that big of a deal. I'd also push back on this framing:

[...] I've always known about the famous Solidus vs Spree drama [...]

While collaboration between the projects eventually broke down and some of us are critical of how Spree has been run since the fork, there really wasn't ever a particular "drama". After the split the projects collaborated directly for a while, especially around security issues that affected both projects. Shifts in project strategy and the changeover in people handling this project caused those communication lines to break down. The only real "drama" is just that they use Solidus projects as case studies on the Spree site.

Am I right to assume that the admin is actually a priority and that the candidate is supposed to solve it? Why wouldn't SuperGood handle it as a paid initiative (as Nebulab tried once)? Nobody can deal with it better than actual users of the framework

On drama, I've meant more of Spree's recent revival. Seems like now Solidus is "you own everything" and Spree is "you own very little". Also, they bet heavily on TS, and you decided to remain hard on Rails Way.

Yeah, Solidus and Spree have very different approaches and disagree on licensing and technical strategy. There's no beef these days, though. Just different directions. The Admin is a priority. I prefer to avoid any perception that those of us maintaining Solidus are profiting directly from the OpenCollective funding. When we can find devs with Solidus experience who are independent, I prefer to give them an opportunity to work on Solidus. This allows us to focus more directly on our clients needs and let trusted third parties work on broader initiatives, like the admin.

And, to be clear, there's no real conflict with the agencies taking funds to do work as long as it's transparent and fairly priced. It's just preferable to create opportunities for skilled third parties.

Noted, thx, Jared! On "profiting," it is ridiculous; maintainers donated much more money and time than was extracted directly from OpenCollective, so it makes quite the opposite of "profiting", perhaps 😄 Also, thx for your work; personally, I resonate very much with Solidus and owning real stuff, especially today

Hello, the updated report (now with a proposed policy list and Jared's answers folded in) and a follow-up essay went live: vit-panchuk.com/writing/the-moneypot-nobody-spends-vs-the-work-nobody-does vit-panchuk.com/reports/solidus Some of the writing is blunt: I have no stake in Solidus, but I tried to help as if I had one.

I wrote a little bit about this on my newsletter, but we're putting some work into the roadmap between here and Solidus v5. If you have ideas for what you'd like to see, feel free to voice them here or reach out to me directly!

hi everyone, it looks like the github actions workflows are broken. this is related to today's release of

json

3.0.1. and some kind of incompatibility with rails. i just wanted to announce this in case anyone is confused about the failures. and i'm not sure whether the solution to this issue has to do with solidus or if it's more something to do with rails...

thanks @benjaminwil!

📣📣📣 Hey everyone, we've just released Solidus v4.7.1 and v4.6.2 to address security vulnerabilities. Please upgrade as soon as you can. You can find more information here and here.