Hey yall, we are raising our prices and taking away your account managers. More on reddit.com

Ouch. 25% price hike along with increased fees. Lock into 3 year deal before April and they'll keep you on $2000. How is everyone reacting to... More on old.reddit.com

I'll do my best to answer this but the answer is nuanced so most accurate answer is, it depends. The advantages of headless is speed, flexibility, technical design and customization. The disadvantage is that it's hard, the developers who do it are skilled, so more expensive, and because literally anything is now possible, decision points are more challenging. Shopify and Moltin are all awesome solutions in the space, and any of them will do. If you're using Shopify already, imo, just continue using it. If you're building from scratch, maybe Moltin is better. If your integrations to a variety of backend systems, ERPs etc... are already in place, stay where you are. If the connections are all new, look towards a new headless first provider. They might (likely will) make that process straightforward so connecting to SAP isn't as absurdly expensive as it usually is. The next real benefit of headless is that it decouples content from presentation. So, as an example, you can use BigCommerce for your product data, but a serverless elastic search instance you manage for search to get custom results. If your customers need lots of image content, you can host all that on cloudinary. Technical products can use something like Contentful to convey more flexible information about products. And in this imaginary B2B site you maybe want to show tailored content and dynamic pricing, you can do this headless too. In the above scenario you're saving vs a traditional SAAS BigCommerce because you're not using apps. Everything you need is the best possible solution for you, not the 70% of the way there solution that most apps provide. This approach would mean that to update the technical content, you'd go to a different site completely than BigCommerce, because the technical content is decoupled from the product data. So an eCommerce manager or shop owner needs to be much more savvy. Okay, so how do you decide. Welp... You need to figure out the requirements first. What integrations do you need, start there. What's the ideal, wildest dreams front end experience. That should let you know what content services you'll need. What's hard about your backend systems (maybe search is very complex and expensive for example), that should guide you for the product portion. Headless is objectively the correct approach for eCommerce but, it's very much the beginning of this right now. The best way to make a decision then is to understand what the biggest most expensive pain points you have, and use those to guide the question set. I'd probably also hire a consultant who has been in this space a while who can guide you. If you're a new site, and you want to go headless and you are already using (Shopify, BigCommerce Magento...) you're in an ideal situation. Just go headless and use the SAAS platform you're on. As you grow, you can add services and decouple information from your SAAS and into a more appropriate headless offering gradually. I hope this answers a fee of your questions. Good luck! More on reddit.com

Better bandwidth, dedicated account manager, better tools and reporting. Largest feature though is going to be lower or no fees. When you're doing $20M a year, 0% transaction fees is a lot of money. More on reddit.com