commerce.js VS Sass

This! Medusa or 🤩Commerce.jj are the best options I have seen to date. Also depends on complexity of use case. I would run one of the known solutions so you can focus on your business.

Commercejs: https://commercejs.com The problem here is that we can manage multiple merchants, however, each merchant has its API private/public key combination, payment integration, customer list, etc, So we don't have centralized customer lists for us but only for each merchant we create. Otherwise, it would be cool. Not sure about payment integration as a marketplace from Stipe/Adyen as it seems only to support normal payment acceptance but not a model in which we have commissions enable

With Commerce.js, you’ll have a modern, API-driven headless commerce infrastructure for developers. Founded in 2016, it focuses on being able to help eCommerce businesses, from startup to enterprise-sized, create great digital commerce experiences.

If you really just want to sell a simple basic product and want to just add that ability to a next js site use snipcart https://snipcart.com even some lite e-commerce use https://commercejs.com.

Commerce.js, founded by Andrew Underwood and Devan Koshal in 2016, is an API-driven infrastructure for developers. It boasts helping any business, from startup to enterprise, build purchasing experiences across channels, including VR commerce.

I am using Commerce JS and Chec

For the other approach, here is the docs: https://commercejs.com/

Commerce.js

If you really want to build everything from scratch, take a look at headless commerce solutions. https://commercejs.com/ could be good for your use case.

SASS(.scss) [ https://sass-lang.com ]

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these days are Sass, Less, and Stylus. Any examples I give going forward will be about Sass as that's what I'm most familiar with.

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below.

Scss

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers.

Sass is also a css preprocessor. Op is likely confused

sass -> An improvement over CSS. It provides nice features for managing CSS. good for mid-sized or even larger projects.

Sass (Syntactically Awesome Style Sheets) - A CSS preprocessor that simplifies and enhances your CSS workflow. Website: https://sass-lang.com/

Personally, my preference is Sass: I find that the mixins, partials, and operators are hugely useful when it comes to creating re-usable snippets of code for a design system. And, since it’s “just” a pre-processor and not a framework, it’s not opinionated in a design sense and there’s no default values (colors, spacing values, etc.) that will need to be overwritten.

Preprocessors: SSGs leverage preprocessors to streamline the development process. Preprocessors like SASS for CSS or Babel for JavaScript offer additional features and simplify code development.