You should also take a look at the guide and building your own extension.

Currently I'm planning to use the starter storefront, but we'll see what happens. We need an ecommerce/storefront for the application we're building, so I'm doing a spike to see what we can do with solidus

So different auth simple shop or do you need also subscriptions and everything?

I think "different auth simple shop" is what we're looking for. As yet I'm not aware of any subscriptions or anything like that

Hey, we reached some backlog on the PRs. What would be a realistical time frame for you guys to go down the blocks and comment so that we can make adjustments on names and taxes.

This message was deleted.

@Jared Norman How do you handle remote areas with shipping surcharge in the US? Do you use zip code based zones as well? I have the feeling everybody uses it in some way and we should consider bringing it into core.

We should maybe consider renaming products inside the mainmenu of the new admin to catalogue. Main menu items and the contained sub detail pages and table views should not have the same name.

Also changing the icons promotions and orders to something more related (eg 🛒 for orders and % for promotions seems indicated)

Hey, the easypost extension is largely broken, we have fully restored it but it seems like that it’s not realistic to make a PR against the current version. The changes where immensely complex as multiple iterations of Solidus as well as Easypost APIs had to be skipped. We have no intention of doing all incremental steps of solidus but would make the current version available. Changes: • The extension also supports inbound and outbound shipments now • products can be configured for reverse economy (I buy instead of selling), the feature can also be fully ignored • shipment methods can be created manually now (before only automatically) • tresholds for shipment co pay for remote areas is supported (if shipping costs less than x make free, otherwise x €) Do you people want it as an extension?

We are in the middle of the process of toying around with meta data having already pushed a trade-in and inbound sales process (buy a repair and ship in your smartphone). We felt a need for a PO-Number field that stores the customer reference in order meta data. Should we bring that to core and starter? The field looks up if the address field is filled out and offers a PO field if company is not empty.

Hi! I am trying to compare Shopify with Solidus. Currently I am trying to compare architecture of both solutions. Where can I find documented architecture of Solidus?

Hey, is there any chance to receive feedback following stale PRs: • 6169 • 6168 • 6159

#6159 I’d like to know if the maintainers rally behind the solution, as it seems from the comment the solution was not fully understood. #6168 and #6169: have received some comments, but I believe the authors were not fully aware that the data added to address is not relevant to privacy.

I’d really appreciate if we could work towards a definitive solution to either close or proceed to have them made fit for upstream.

Can somebody open up a branch in the starter for TW 4.0?

We are looking into this.

Hey Guys, I am happy to announce that solidus_static_content has been restored. Some questions: • Should we drop unsupported versions from the master / main and make a new release? • I have never updated a gem to a new version, could one of you handle that?

Out of curiosity: how many of you use webhooks? Is that something rarely used or very common? I assume most of us use services that allow tracking. Maybe it would be good to allow a setting that adds two additional shipping states (in_transit and delivered).

I saw that most stores doesn’t use the prefix

/t/

for taxons and

/products/

. Given that most stores probably don’t meet really performance hindering amounts of store categories and pages that hinder performance, do we want to remove it from the starter with maybe some comments or a configuration?

This message was deleted.

Hey, we should use the redesign to also solve following two issues: there should nerve be two menu options with the same name: 1. I suggest to rename Side Bar Main Menu “Products” to “Catalogue”

Hey, we are working out tailwind and schema on frontend, could somebody invest two minutes to merge this: https://github.com/solidusio/solidus/pull/6209 It adds brands to products made identically to primary taxon.

We have implemented groups separately from pricelists to have the possibility to provide it upstream more granular. It allows to assign default groups at sign up, has a group management interface and has been stripped of pricelists. This enables merchants to segment customers for analytical purposes by store or any metric they see fit. Do you want this into core?

👋 Hi everyone!

This message was deleted.

Holy hell, the spam won’t stop.

I wish it were more convenient to disable accounts from my phone… the spammers clearly noticed I was travelling in Japan and came out in full force.

This message was deleted.

I really wish the Solidus Rubydocs were hosted somewhere on Solidus.io, rather than on rubydoc.info. I always find Rubydoc really slow.