Show HN: I'm building an open-source Amazon (openship.org)

1335 points by theturtletalks ↗ HN
A couple of years ago, I had an interesting idea. What if there was a marketplace where all the underlying tech was open-source? The order management system, the storefront, customer support, etc.

The marketplace would simply connect to the seller’s infra instead of locking them in. If, for some reason, the seller is removed from the marketplace, their software stays with them and they can continue accepting orders directly.

This model can be used to disrupt any marketplace from AirBNB to UberEats: building tech for home renters and restaurants and later, leveraging that to build a competing marketplace.

In 2019, I started building the first piece, Openship, an order management system that lets you source orders and fulfill them from anywhere. Now that that’s in stable release, next up is Openfront (an e-commerce platform for storefronts) and Opensupport (ticketing software for customer support). Together, they provide the staples for any modern business: sales, fulfillment, support.

Let me know what you guys think of the idea and if you see any potential pitfalls.

308 comments

[ 2.8 ms ] story [ 291 ms ] thread
Quick note, the third submission was automatically blocked by the HN algorithms. Posting the same three times in 24h is too much.

> Show HN: I'm building an open-source order management system and marketplace API

> Show HN: I'm building an open-source Amazon

> Using open-source to disrupt marketplaces

Yes I saw that. The last one was a blog post I made in 2019 describing the vision in detail.
> a blog post I made in 2019 describing the vision

Hence I think you have, regrettably, answered your own question.

Its all very well having a vision, but executing it is a different question.

The sort of thing you propose requires a lot of time and a lot of money to develop. Let alone maintain. Let alone market and sell.

Look, its like all those "Bloomberg killers" that come out of the woodwork as often as the seasons in the financial world. There is a reason why only Bloomberg and Reuters are at the top tier, why the second tier is so narrow and why everything else is junk. To replicate Bloomberg would take years in time and billions in cash.

I admire your ambition, but perhaps rein it in a little ?

Execution starts with vision. I don't see a problem with thinking big, it inspires others that want to help become part of something great.
> Execution starts with vision.

Yes I agree.

But the OP had the vision in 2019.

We are now at the tail-end of 2022.

I still see a vision and not much execution.

Meanwhile, the Amazon that the OP is pitching themselves against has continued to move onwards and upwards....

As I said. The vision is fine. But the OP needs to realise that executing it will require a lot of time and a LOT more money !

I think if you start with vision, and you have passion for something the logistics around making it happen will manifest, or it won't if its not ready/needed. It depends on where your idea takes you and sometimes ideas need to be iterated to figure out where you are going. IMHO is too early to be focusing on the negatives of what may or may not happen. That comes later and it should be made in a positive direction, "Where are we going to get the money to make this happen", rather than, "Yea man, that's going to cost you a lot money". When comming up with ideas, the latter doesn't really help, for me.
> I admire your ambition, but perhaps rein it in a little ?

As much as people may say they hate salesmen, we still want to be sold something. As a consumer, it's your job to be skeptical. It's their job to sell.

Engineers have this self regarding view of every other side of the tech business. That actually -- "Only the tech matters" while being incredulous as to why certain tech succeeds while others fail. It's because vision and sales and business acumen really matter.

I think of it this way. Launching a marketplace today is very difficult, but what if we made the backend of a marketplace open-source and used that as leverage. One that could be your backend for all operations. You can choose to enable the integrated marketplace or not, but the system is yours. It’s about bringing power back to the sellers.

Never doubt that a small group of thoughtful committed citizens can change the world; indeed, it is the only thing that ever has. - Margaret Mead

> It’s about bringing power back to the sellers.

But let's be honest here. What sellers really want are buyers.

That's why sellers list on Apple, Amazon, Ebay etc. despite the fees.

They are paying for the virtual equivalent of a shop-front in the premium mall. They get the payment handling. They get the anti-fraud technologies. And with Amazon they get the forward and reverse logistics.

Its about SO much more than how open the backend software is.

> Its about SO much more than how open the backend software is.

Wrong. I own a small shop in Vermont and I love recompiling my shop software every morning to get customers. I tweak a couple of things - - yesterday I lowered tcp_orphan_retries - - and, boom, more customers!

You're right, but sellers are realizing that they are helping Amazon, eBay, etc. more than those platforms are helping them. For example, if you use FBA to fulfill outside orders, Amazon charges a higher rate. You're locked into their pricing and their marketplace.

I would say 85% of sellers on eBay and Amazon have their own storefront now to be in more control. They also funnel these orders into an OMS.

Yes and no. What I want is buyers and reasonable fees.

I stopped putting stuff on Ebay due to ridiculous fee schedule ( listing is free, but then you get hit with tons of seemingly random invoice, which is automatically deducted without a real way to challenge it ) and I was regularly thinking of putting a store up myself, but I don't sell often enough to justify it. I once played with an idea of a weird garage sale app that basically let your address list what you have available for sale, but it seemed like a lot more work than I was willing to put forth.

This.. could work. I will admit I am tempted to try the self-hosted version.

edit: changed sellers to buyers

> Its all very well having a vision, but executing it is a different question.

This also relates to the clickbait-y "I'm building an open-source Amazon" positioning, which I don't think serves you well.

You're building (I think) an e-commerce platform upon which someone can build online shops ("nano-Amazons"?). Where the "open-source Amazon" pitch is difficult to take seriously, I think there probably is space for new e-commerce platforms.

This is just one piece of the puzzle. I explained it in another comment:

> I think of it this way. Launching a marketplace today is very difficult, but what if we made the backend of a marketplace open-source and used that as leverage. One that could be your backend for all operations. You can choose to enable the integrated marketplace or not, but the system is yours. It’s about bringing power back to the sellers.

> This is just one piece of the puzzle.

Yes! That is the point, which is why over-selling this as an "open-source Amazon" will backfire spectacularly with anyone who understands what they're talking about.

It's important to know what you're building (from the POV of potential customers) and who your competitors are. https://www.forbes.com/advisor/business/software/best-ecomme...

Is my understanding correct that: The leverage comes from lowering the seller’s switching cost to go to/add another market place by intermediating the seller/market place relationship with open-ship. That way when you release the open marketplace open-front you can get easy discoverability and a very low switching/adding cost from an existing set of sellers?
You nailed it! Existing and future marketplaces would adapt to your system, not the other way around.
> I admire your ambition, but perhaps rein it in a little ?

Yeah, how dare they have ambition.

I bet they haven't even applied for their Ambition Licence or submitted their "permission to try and make something cool" (PTTAMSC) paperwork.

/s

> I admire your ambition, but perhaps rein it in a little ?

Maaaan if we were in the same room. Don't belittle someone who's trying to accomplish something (and following through with it).

I think this might have brought on more by the multiple submissions but I do agree that it's in HN's spirit to support ambitious endeavors.
> Maaaan if we were in the same room. Don't belittle someone who's trying to accomplish something (and following through with it).

I'm not belittling. I'm just saying set realistic goals. "Build an open-source Amazon" without the budget or the manpower ? Its simply not realistic unless you have very deep pockets and a team of hundreds of full-time staff.

If you think I'm being unduly harsh, what sort of grilling do you think the OP will be subjected to when they rock up at a bank or VC fund looking for a few hundred million ?

Just as a quick counter-argument. Amazon did not become today's behemoth overnight. It started as a source for books and then slowly expanded into other sectors as it perfected its execution.

I might agree that the characterization is a little bombastic, but:

1) It is oddly good marketing if mildly misleading ( as discussed in other posts it is not exactly a 'replacement for Amazon store for seller' as I would have initially thought from the initial presentation )

2) Here we are discussing its merits or lack thereof

In short, I agree with your general point, when compared to today's Amazon, but I think it was more of a rhetorical device rather than a 'factual statement'.

No, you're setting limits on another human being, likely because you're intimidated by them even having the stones to go through with it (and you won't/can't). Folks like you are a dime-a-dozen and they are always hollow souls who can't accomplish a fraction of the people they push down.

> what sort of grilling do you think the OP will be subjected to when they rock up at a bank or VC fund looking for a few hundred million ?

Appropriate grilling (financial prospects, executive potential, etc), not being told to "lower your ambitions."

It's amazing how many people condescend to others on here and then are surprised when someone else defends them.
I feel like I should bookmark this thread so I can come back in a few years when this dude is huge and say "Geez, I bet you wish you kept your yap shut" to all these people telling him to reel his ambitions in.

I still smirk at the chucklehead who dismissed Drew Houston when he "Show HN: Dropbox"

It's not the concept of defence I was commenting on. It's the nastiness.

As for condescension: that's in the eye of the beholder. When the OP said "Let me know what you guys think of the idea and if you see any potential pitfalls" do you think that was a mistake to ask for feedback? Should they have only asked for affirmation?

You're 100% condescending and unduly harsh. Obviously the dude is not 'replacing amazon' that's a mischaracterization on their part, but they are doing something definitely legit, and within scope of what a small team can do to start with.
That's why theturtletalks should apply to YC first! I'm sure YC would love to fund an open-source Amazon competitor if they believed in the execution enough to give it, say, a 1% chance of success (or even much less than that, given Amazon's size).

That "bank of VC fund" you speak probably looks at a startup like this very differently after they've been through YC, not just because of YC's reputation but also because YC can do a lot to help a startup like this after funding it.

> Maaaan if we were in the same room.

What does that part mean exactly? Sounds a bit threatening.

> I admire your ambition, but perhaps rein it in a little ?

I hope whatever happened to you to make you think like this is resolved, because it saddens me to see people tell others to pipe their ambitions, goals and visions down because THEY don't see it as a reality.

If everyone believed this, we'd have never advanced at all as a society because nobody would push the boundaries.

Nothing wrong with wanting to showcase what you're working on but don't spam HN when you're not pleased with the amount of eyeballs on it (At least not multiple times within 24 hours with varying titles like you're trying to AB test)
Even if you say that, it totally worked, so they have little incentive to take your advise.
I don't do any selling on Amazon, mostly purchase, but the interface and the tools for what I understand is to aggregate products for selling into one place is spot on.
I think this is a good solution for businesses that are starting to outgrow their home garages. Here's my feedback:

When I read this post and looked at the site I thought you were offering a turnkey drop shipping solution service. I also had the impression that you offered warehousing and other logistical services.

I know this is not the case, but it took me several minutes to figure out what exactly was happening.

Wouldn't this be more of an open source Ebay then, if the logistic components, which make up much of Amazon's value, are not there?
I instinctively like this idea a lot, and the website does a really good job of explaining the concept.

Good luck with it!

i haven’t visited your site yet, but i’ve long thought something in this vein has been missing.

imagine if taxi companies could make use of it, or a group of friends could start their own GNUber.

or a group of high school kids who want to deliver groceries/items to the elderly as volunteer work.

or a bunch of middle school friends wanted to do a lawn mowing service.

or…

of course, anyone in the industry knows how many unpredictable pitfalls reality will throw at it, but we also know very well these kinds of ideas, if followed through can be remarkable and truly can change the world.

it’s been like tiny little pinpricks at me for years that apps like Uber, Lyft, door-dash, etc… don’t have a scaled down open-source alternative — a decent Configure, Describe Services Offered, Spin-Up-An Instance and Go.

i’ll take a look later today when my schedule loosens up.

edit: just reread your post and looked at the comments, i misread what you were doing, sorry bout that. still sounds interesting tho, good luck!

People are going to hate on me, but web3 makes this absolutely trivial to build. If you try to build this as another centralized service, you just end up in the same place but a new dominant owner.

Don't get me wrong, there IS a wrong way to build this in web3 where it's just a web2 service on-chain. But designed correctly, it can avoid the pitfall.

> web3 makes this absolutely trivial to build

So good to hear. Put differently: are you insane?

ps. I built the original Amazon. On top of that, I have a brother who builds web-stuff related to decentralized coordinated activities and has done for many years. I didn't check in with him, but I'm pretty sure that we both think that you're insane.

lol, do you end every technical argument with "I'm Paul Davis, don't even try to debate me!"
I try not to. But when someone claims that building a platform for distributed, cooperative, coordinated action is "trivial", and it's in the context of "I'm building an open source Amazon", it is a little hard not to fail at this goal.
I used to work in large scale eCommerce too, I would never claim distributed supply chains is trivial. But this was not in reply open source Amazon, this was a reply to the idea of a distributed Uber (the parent comment to mine).

That to me, feels quite in line with Web3's capabilities. The hard problems to me don't seem to be technical in nature. I think the bigger hurdles will be business related. But this is a tech conversation, so here is my thoughts.

The way I see it, Uber enables 3 primary capabilities, for which it takes a major cut, and commands total control over drivers:

1. Driver Ratings

2. Payments

3. Match Making

I think web3 can solve 1 and 2 on-chain using smart contracts relatively simply. and if you use a chain like Avalanche, it can be done with low fees (cents) and with fast transaction finality (seconds).

The match making capability should not be on chain. For that i'd design a simple rest API using traditional technologies that consumes configuration from the chain. This service can be deployed on Akash, and paid for by taking a small cut off each transaction or devaluing a utility token... i'd build a DAO to govern the whole thing, and i'd distributes votes based on activity in the drivers pool.

Are there probably problems here? yeah, this is 3 minutes of thought. But i'm sure if I cared to, I could design a functional system in a weekend.

You gotta take out that fade out effect. It’s terrible for usability.

Otherwise great work!

Good luck and I hope you succeed, but the (unfortunate) reality check I'll give you is that money rules everything, and if you get even the slightest bit of traction, there is more than a trillion dollars in market cap behind ensuring you (and nobody else) will ever succeed.

The only way to get ahead these days is to either 1) flout the laws or 2) have enough capital and political influence to force your way to success, such as with regulatory capture.

That is a very pessimistic way of looking at things. While it is true that there are entrenched interests that do what they can to prevent any new entrants from disrupting their dominance, I feel obligated to point out that this has always been the case. Just to point to how bad things in US have been at one point, I would like to point out the oft-discussed robber barons and the origin of antitrust laws.

Edit: I forgot to add a conclusion somehow.

And yet, somehow we ended up with Googles, FBs, Amazons, Teslas and multiple other in tech sector alone over the past few decades. Neither of those started even close to existing dominant forces in the market.

I don't understand your objection. The country was run by robber barons and started to move toward some sort of revolution (however you would describe FDR getting four terms), then antitrust laws ended it. Then we stopped enforcing antitrust laws, and got Google, Amazon, Disney, etc..

> That is a very pessimistic way of looking at things.

This isn't a real criticism. It's either an accurate way of looking at things or not. And I think the obvious odds that Amazon wouldn't just buy it and shut it down if it made it up the difficult road of getting any significant traction are 1. That's how business works now, that's actually success. Tech companies are making this exact argument during antitrust hearings - that not allowing them to buy businesses up and shut them down would destroy the startup scene.

edit: it would have a lot better chance if somebody would paint Amazon as either being intolerably liberal, intolerably conservative, or both at the same time. Open the angry Boomer spigot.

<< I don't understand your objection.

Tesla exists. Cars are an existing and crowded market. And yet, despite that, Tesla managed to not only enter, but survive. If that is possible, parent's claim that:

"The only way to get ahead these days is to either 1) flout the laws or 2) have enough capital and political influence to force your way to success, such as with regulatory capture."

is simply not accurate.

<< It's either an accurate way of looking at things or not.

Based on example of Tesla, it is not accurate.

This is a fantastic idea, and you're off to a great start.

I've spent 6 years building a similar thing for local business in my area, just not quite this polished and expansive.

I will be keeping an eye on this for sure, love it!

I really like the look of the site. And seems like wonderful work.

I see no base for your claim however: "This model can be used to disrupt any marketplace from AirBNB to UberEats".

A tech stack is hardly what makes platforms, it's the consumer side of things that disrupts.

So just to make it more fair to the suppliers of the marketplace would not really lead to a disruption imo. Not saying it's not worth it.

A few points I'm skeptical of:

  simply connect to the seller’s infra instead of locking them in.
One of the value-adds of Amazon is there's a whole bunch of tech sellers don't need to know how to write, run, and maintain. You'd need to understand how big the niche "technically literate to run their own e-commerce business, but selling on Amazon for other reasons" is, then how your operation would answer those "other reasons" to make you competitive to the niche.

  If, for some reason, the seller is removed from the marketplace, their software stays with them and they can continue accepting orders directly.
Apart from the software systems, there's a whole bunch of basic business processes that Amazon takes care of, which are less portable. Using FBA? Leaving means learning how to run a warehouse, shipping logistics, pricing, staffing, etc. Not using FBA? How's your Marketing department doing? Hopefully you didn't let it get too anemic or too fitted to "people who are good at gaming Amazon's algorithm."

In short, if your value add is: "Amazon, but you get to take the tech home with you if you leave the platform," then that feels like a small niche of highly competent businesses, then you're stuck with "well if they could do all this on their own anyway, why are they choosing Amazon?"

Hope that helps and wasn't just me blabbering. Good luck!

re " how big the niche "technically literate to run their own e-commerce business, but selling on Amazon for other reasons" is,

As the platform matured, the level of technical literacy could decrease over time. e.g. the more technical aspects get abstracted away from the users.

Furthermore, users who are motivated enough would begin to extend their technical reach by means of self education, and/or collaboration with more technical party/(ies).

This is a common arc in technology.

i think the branding "open source Amazon" is just way too ambitious/big. invites a lot of confusion/criticism if Amazon is different things to different people.
I think it’s good marketing.

Amazon’s primary source of revenue is as a market-maker/logisticics provider, so why not position yourself as a competitor if it gets contributors interested?

I had thought until now that Amazon primary revenue stream is running a good chunk of the internet. Quick research tells me, you are right.
Revenue for Amazon is in the retail business. The margin however is a lot better in the AWS side. Warehouses and logistics cost real money to operate.
(comment deleted)
should start small, like an open source Google, then work your way up to an open source Amazon.
Harsh, but true
Nobody ever wants to open source Pornhub. Wide consumer interest, no physical products to worry about, lots of advertising potential - and your not competing with Amazon, Wal-Mart, Google, Apple, or Target. Sounds like a better deal to me.
Constant hassle with payment processors deciding to ban smut once you get too big, though.
> Constant hassle with payment processors deciding to ban smut once you get too big, though.

Not doing something because you might get too big is not sound reasoning.

When you get too big, that's the time to worry about it.

The payment processors will shut you down even for your first payment if it's for porn. More likely - you'll never get to a first payment anyways, they won't sign the contract.
> The payment processors will shut you down even for your first payment if it's for porn. More likely - you'll never get to a first payment anyways, they won't sign the contract.

If that was even occasionally true, the tons of paid porn sites wouldn't exist. The fact that they both exist and take popular cards tells me that that cannot possibly be true.

There are special payment processors catering to porn/etc, but the problem is that they require extremely large collateral and have other unusual requirements that are untenable to new businesses. Most probably they won't even talk to a startup (I tried, didn't get a reply). There's a reason why startups like OnlyFans used normal payment processors and tried to convince them they're not porn instead of beginning with these specialized ones.

Edit: BTW, a large portion of seemingly independent porn sites are actually run by only few companies. Especially the Xvideos corporation.

So we should pivot to building an open source payment processor for porn?
A payment processor is an entity that handles bureaucracy. It's not a piece of software you can run and forget about. It is many people working around the clock taking phone calls.
I should have been clearer and said "software to aid in running a payment processor" but I used "payment processor" as a shorthand. Just as "open-source Amazon" is shorthand for "software to aid in running an entity like Amazon."
If someone got it to be popular enough, MindGeek would buy it and you'd be back at square one.
Maybe practice creating an open source Microsoft before quitting your day job?
Many have already done open source Google and MS. We have those solutions already, and they are great though not yet pervasive. We need open source market place and logistics, and that is where they should stay focused.
Probably for this crowd anyway. My first thought at seeing the title was AWS, not the store front.
For some blissful seconds I thought this post would be related to reforestation efforts.
Amazon to most is primarily a website where you get everything mostly reliable and mostly with a consumer focussed service (I for one never had any issues when returning things, any problem was like "yeah ok, send it back, we send you a new one or do you want a refund?" ... For sellers they play a different game with their market power, discounts or they won't offer your things or rank competitors higher)
They previously submitted the same link with a different title and got... 3 upvotes.

The Amazon comparison clearly helped to get on the HN front page.

> Show HN: I'm building an open-source order management system and marketplace API

https://news.ycombinator.com/from?site=openship.org

Just goes to show that for all of HN's hyper ad awareness, we still fall for basic click bait in our own territory.
Another way to frame it (from the opposite direction) is a collective failure on "our" part (if there is such a thing as "us") to explore and promote genuinely interesting things just because they lack the sparkle of click bait on the outer surface.

Maybe it isn't that we "fall for" click bait, it's that we very loudly ignore stuff that isn't.

Either that we actively (doubtful) ignore non-click-bait, more that we are programmed (in some sense) to only pay attention to click-bait.

It is genuinely difficult to ignore things which sound alarming but usually either nonsense or much less alarming, than it is to actively investigate everything, whether it seems alarming or not.

The later is much more difficult but also a lot more fruitful - it is why Google News was so good, a simple collation of all news instead of only click-bait-y news, and why it is genuinely terrible now (mostly dominated by click-bait-y news again).

And again, an illustration of active versus passive - actively filtering google news feeds was fruitful, passively filtering led to algorithmic optimizations which ultimately favored high click counts and therefore more click-bait-y news...and ultimately at this point to being "click-bait highlights of the day", akin to some nonsense like yahoo or msn news.

An open source order management system is interesting to a certain number of people, but probably doesn't affect me personally. It sounds like another open web storefront builder if i had to guess based on the title.

An open source Amazon is a big deal, it implies that it aims to do what Amazon does, not just a repo you can clone and build an online store, and I might be placing orders there someday.

A distributed open source Amazon. Storing goods in people's rooms. Creating a distributed worldwide warehouse, kinda like P2P. With a fleet of uber-like delivery persons. Each participant gets a share of the profits.
Sometime I feel like submitting to blackhole when not receiving any comments, but I've adjusted the expectation over time
I think we get excited by big ideas, and things that sound like big ideas. That makes us a great sounding board. On another forums it'd be 'i like amazon, down vote' or 'i don't need that, ignore'.

At least here, we move on perceived merit, however superficial

"Show HN: I'm building an open-source Amazon in Rust" would be even better
I would be down for an open source AWS services. Shouldn't be to hard to make web front end to the fire cracker instance, but make everything in the backend open source, so any one can run the community edition.

Any thoughts on that?

Yeah, and then you run your "open source AWS" on AWS xD. I believe what you mean it's called Open shift, kind of.
Also very difficult to compete with Amazon. Amazon makes their operating profits from cloud computing and subsidizes their retail market with it. That is how they keep prices so low.
The result is a form of predatory pricing which should be illegal.
Instead a company should subsidize their product with VC funding like every single company on YC does..
More of your storefront being portable is a big plus for any business that fears lock-in or unwanted removal from Amazon.

I haven't looked into the specifics of this offering, but if you were able to use your own custom domain for your storefront, minimise the platform's insights into your actual sales (i.e. to prevent a similar case to Amazon launching products in your niche), etc and mainly leveraging a centralised platform for the audience, then that's the best of both worlds.

You can always do what bookshop.org did and appeal to social justice and hipster oppression. Talk about supporting "small business" and pretend that everyone's not just dropshipping from asia.
I don't think you know too much about how the book retail industry works. If people are dropshipping from anywhere, they're dropshipping from Ingram, which is in the US. Some of the stuff they carry might be printed in Asia, but it's not shipping directly from there to individual US customers. If I had to guess, this is how I'd expect bookshop.org to be fulfilling orders that they fulfill themselves. I can't remember if bookshop.org kicks any fulfillment to its indie bookstore partners, but if they do, those stores are almost certainly using Ingram dropshipping or fulfilling from the store's in-store inventory.

That said, it's still not nearly as good for indie bookstores as just buying directly from the indie bookstore, but it's pretty far from your characterization.

I was referring to OP's product. The non-book part of Amazon sources the majority of their products from asia. Bookshop was just a point of comparison. Their schtick is to complain on media (said media is conveniently on an anti-big tech crusade right now) about small indie book stores being oppressed by Amazon while ignoring the fact that most publishing is centralized upstream.
I see your point, though it wasn't as clear from your first post.

To be fair, publishers being consolidated is much smaller problem for bookstores than Amazon is. While publisher consolidation is real (Penguin Random House is quite a beast!), it is not total; many publishers exist that have not been absorbed by the major publishers. And there are multiple major publishers a tier below the aforementioned PRH. Whereas when it comes to sales, the main competitor for _all_ bookstores is pretty definitively Amazon. So there is some merit to what Bookshop is doing, and it's not quite as hypocritical as you seem to make it out to be.

It's the word "simply" that usually raises all the red flags :-)
>One of the value-adds of Amazon is there's a whole bunch of tech sellers don't need to know how to write, run, and maintain. You'd need to understand how big the niche "technically literate to run their own e-commerce business, but selling on Amazon for other reasons" is, then how your operation would answer those "other reasons" to make you competitive to the niche.<

The bigger stores with IT staff and budgets would be first to join and contribute. Some of us consultants could help the smaller shops and possibly combine energies into communities or coops using shared resources.

My first reaction to the idea a few hours ago was along those same lines.

Coming back to the ShowHN just now, I thought “China.”

By which I guess I mean manufacturing, and not drop shippers, middlemen, importers, etc.

To me, it seems like this matches the way manufacturers multi-channel their sales, and fits the IT priorities a manufacturer is likely to have…bills of materials, inventories, forecasting, design, etc. and not a big emphasis on the web, saas, and building websites.

YMMV.

Particl.io does this on the blockchain. It's fully anonymous
Love open source projects in the eCommerce domain, especially ones that are JavaScript instead of PHP! Two pieces of feedback:

- Using a copyleft license like AGPL makes this an automatic non-starter for most businesses, no matter how impressive your tech might be. You'll have a lot more luck with mid-size and enterprise adoption with an MIT license.

- You've really built an Order Management System for marketplace use cases, which is in industry typically a distinct domain from a Warehouse Management System (WMS) or a Transportation Management System (TMS) which at large-scale tend to handle how orders actually get fulfilled and shipped to customers. Your naming is a bit misleading - at the very least I'd emphasize somewhere on your landing page that this is an open source Order Management System if you want eCommerce domain folks to grok quickly what you've built and how it plugs into a broader architecture.

> - Using a copyleft license like AGPL makes this an automatic non-starter for most businesses, no matter how impressive your tech might be. You'll have a lot more luck with mid-size and enterprise adoption with an MIT license.

What makes the AGPL unattractive? I thought it was basically just the GPL with a limitation on using the software to provide a SaaS product. You don't even have to contribute unpublished changes, right?

Before reading your comment I actually checked the licensing in the repo because I was thinking the exact opposite; using MIT would be a mistake because it's too easy to undermine the turnkey offering by selling a competing service without the cost of development.

My 2 cents :

In an ecosystem like this you may want to have businesses build extensions or plugins that they'd sell. GPL has this reputation of spreading to everything it touches, and as such would scare them away.

like wordpress plugin marketplace?
AGPL is banned from every corporation I have ever seen.

Because it's viral even when it is used internally, you might end up having to release things you never expected and that are very sensitive.

It would be insane to allow anyone to use AGPL code in any corporate environment.

MongoDB is effectively licensed under the AGPL and seems to have no problem being used by corporations of all sizes.
Wouldn’t those corporations just purchase the commercial license MongoDB offers, though?
Maybe? The commercial version has some extra features, but if you don't need them then there's probably no need to. I imagine there is more value in paying for a support contract.
MongoDB is licenses as SSPL which is non Open Source license all together

BUT this is only if you are not paying for MongoDB. If you do chances are you're using MongoDB Enterprise which is licensed under commercial license or MongoDB Atlas all together

SSPL is a nearly verbatim copy of AGPL, except one section. It is more restrictive than the AGPL, in a way that many feel is anti-competitive, which is why it's not considered Open Source by many, but also in a way which doesn't really change the argument here IMO.
MongoDB - the application is. MongoDB - the service isn't.

You can use an Oracle database (however ugly its licensing is) without having an oracle license on every piece of data you expose. The same is true of Mongo license and the data it exposes as a service.

The AGPL in this case is "you use MongoDB - someone wants to know about it, the source for MongoDB is over there." MongoDB AGPL doesn't 'infect' the application it is part of.

Now, if you were to fork MongoDB and do something with that fork (FongoDB), and that deployed FongoDB would need to make it's source code available if it was accessible - not the entire application that it is part of or components that use the data that it provides.

Yes, that's the entire purpose of the AGPL. If that's the outcome this person wants for their project, they should consider the AGPL.

I'm attempting to counter the narrative that no corporation would touch any AGPL software, because it's clear that how you are using the software is an important part of the equation.

MongoDB no longer uses the AGPL licence.
Looking at https://webassets.mongodb.com/_com_assets/legal/SSPL-compare... and in particular section 13, this is an attempt to squash a cloud service from packaging MongoDB and their own custom backup and UI software without offering the backup and UI software also under the license.

https://techcrunch.com/2018/10/16/mongodb-switches-up-its-op...

> MongoDB is a bit miffed that some cloud providers — especially in Asia — are taking its open-source code and offering a hosted commercial version of its database to their users without playing by the open-source rules.

> So while the SSPL isn’t all that different from the GNU GPLv3, with all the usual freedoms to use, modify and redistribute the code (and virtually the same language), the SSPL explicitly states that anybody who wants to offer MongoDB as a service — or really any other software that uses this license — needs to either get a commercial license or open source the service to give back the community.

If I was to write blog software that is backed by MongoDB, that blog software doesn't have to be released under the SSPL.

That said, the license and its application to patches on older versions would raise some eyebrows in legal with (likely valid) concerns that an upgrade of a point release may change the license on them as it was done before. In the interest of minimizing risk for the organization, the license and the company that changes its license so easily would be ones that would get extra scrutiny and developers using it would likely be advised to ask permission rather than forgiveness when dealing with it (rather than the other way around) as the risk to the org is greater than accidentally incorporating some GPL code in a service.

There's a lot of FUD out there about GPL licenses and they've become pretty unpopular over the last decade. There are trade-offs, but there's nothing wrong with using the AGPL if that aligns with your own goals and values.
Here's Google's stance on why they ban AGPL software: https://opensource.google/documentation/reference/using/agpl...

> The primary risk presented by AGPL is that any product or service that depends on AGPL-licensed code, or includes anything copied or derived from AGPL-licensed code, may be subject to the virality of the AGPL license.

> This viral effect requires that the complete corresponding source code of the product or service be released to the world under the AGPL license. This is triggered if the product or service can be accessed over a remote network interface, so it does not even require that the product or service is actually distributed.

> Because Google's core products are services that users interact with over a remote network interface (Search, Gmail, Maps, YouTube), the consequences of an engineer accidentally depending on AGPL for one of these services are so great that we maintain an aggressively-broad ban on all AGPL software to doubly-ensure that AGPL could never be incorporated in these services in any manner.

FWIW, every company I've ever worked at bans AGPL products / code.

> This viral effect requires that the complete corresponding source code of the product or service be released to the world under the AGPL license. This is triggered if the product or service can be accessed over a remote network interface, so it does not even require that the product or service is actually distributed..

This is the entire point. The goal is to stop the SAAS loophole.

the toxic combination is (a) virality and (b) remote end user access triggering the GPL rights.

You could have one but not the other. We really need "LAGPL" to parallel LGPL, to make it clear that there is a clear and well defined way to stop the "remote access" part of AGPL from propagating accidentally into proprietary code.

In other words, to stop the process of people no longer owning their software and data and being subjected to someone else's decisions about whether a feature or service is important or should be deprecated.
> FWIW, every company I've ever worked at bans AGPL products / code.

Is every company you've ever worked for a software vendor? Because those are the only companies that would be impacted at all by using AGPL products/code.

Any business that uses AGOL software needs to be able to provide the source code of that AGPL software to people who use their services

That is… just not something most online stores are interested in adding to their compliance burden.

And of course they will have changes. It’s a business software platform, the only way to accomplish some things is going to be through adding or modifying code.

> Any business that uses AGOL software needs to be able to provide the source code of that AGPL software to people who use their services

Step 1: add GitHub link to footer on website

...that's it, you have achieved compliance.

This "wah the AGPL is too viral" argument is the same FUDdy duddy nonsense Microsoft was whining about back in the early 2000's about the original GPL - and it's even less of a valid argument now than it was then, thanks to the existence of umpteen bajillion Git repo hosts that will gladly handle distributing said source code (and therefore making you compliant with the terms of said code's license) at zero cost to you.

Step 2: take responsibility for all the content of that GitHub link being free of copyright infingements, patent violations, etc.

And you missed step 0: convince the boss there’s a good reason why your e-commerce storefront needs to have a link to a GitHub page on it.

> Step 2: take responsibility for all the content of that GitHub link being free of copyright infingements, patent violations, etc.

You already do this when using any open-source software (because your legal right to use it depends on upstream's legal right to distribute it to you), so if any other FOSS license is okay then so is AGPL by this metric.

> And you missed step 0: convince the boss there’s a good reason why your e-commerce storefront needs to have a link to a GitHub page on it.

You already do this for license text / copyright info when using software under nearly any other FOSS license (unless you thought those attribution requirements in the MIT/ISC/BSD/etc. licenses were mere suggestions?).

that really give one a sad state on the reality of business.

the fact that google is against AGPL, makes it even more important to use it! Whatever is good for google, it is not good for humanity, and whatever google doesn't like is beneficial for humanity. Support AGPL!

I always cackle a bit when someone points out that GPL-family licenses are incompatible with large-scale enterprise heavily relying on proprietary technology for value extracting. Obviously GPL is incompatible and that's a feature and not a bug.

If Google truly had to be competitive, they surely could figure out ways to make AGPL work. But they don't have to because for now they're just taking everyone's data practically for free.

> The primary risk presented by AGPL is that any product or service that depends on AGPL-licensed code ... _may be_ subject to the virality of the AGPL license.

This is aggressive scare tactics. It's very straightforward when this is triggered.

When you're using code unmodified as a library (whether source or binary) it's not triggered at all.

When you _do_ make upstream modifications, it's triggered. That is the specific risk, and it is easily satisfied by open-sourcing the full modified version.

The whole "if a remote user uses it" argument is FUD. It closes a loophole in GPL where remote use != distribution.

Google is hostile to copyleft full stop. So are other bigcos and cargo-culting smallcos/startups. That doesn't make it right.

There is no such thing as virality, you always retain your own copyright over the code if you don't publish it under the AGPL. If you use AGPL code in a non AGPL codebase you are merely violating copyright and must remove the AGPL code from your codebase.
In this case, there is nothing at all wrong with a GPL license. Everyone is answering from the perspective of a software company. That isn't who this product seems to be targeting. It's targeting businesses that sell physical goods and need a virtual storefront to do that. They aren't looking to fork this and repackage it as a different product. The purpose of it being open source at all is so they can more easily self-host it. If you self-host an application you don't fork and modify, there is nothing for you to publish. The source was already published by the person you got the code from in the first place.
Thank you for adding practical sanity to this thread.
This ignores the fact that AGPL has no strict definition of “forking/modifying”.

So, adding text/marketing copy (see user comment on a restaurant app use case) can be seen as a modification.

For an app like this, that would typically be configuration in the database. (Think WordPress; are you writing your marketing copy in plugin source code or are you writing it using the page editing functionality?) The AGPL doesn’t require you to publish your database.
(comment deleted)
> What makes the AGPL unattractive? I thought it was basically just the GPL with a limitation on using the software to provide a SaaS product. You don't even have to contribute unpublished changes, right?

The things AGPL adds to GPL don't just affect people trying to do a SaaS offering of the program. If you modify it and users interact with it over a computer network you have to make source for your modified version available to them.

For example suppose it was software to add online ordering to restaurants. A restaurant modifies its copy so that it can be given the recipes of the items they sell and the modified software uses that information to allow customers to easily exclude items they might be allergic to or that violate their religious or ethical eating rules.

If that restaurant wants to use that as a competitive advantage over other restaurants they aren't going to want to have to give away their modifications, so aren't going to want to use AGPL software. They'd probably be fine with GPL software.

> If that restaurant wants to use that as a competitive advantage over other restaurants they aren't going to want to have to give away their modifications, so aren't going to want to use AGPL software.

That's exactly the kinds of scenario the AGPL was written to avoid, right? The free software movement doesn't see software as a competitive advantage worth protecting; software is information that should be free.

To put it another way, if somebody releases software under a license that says "You may use and modify this for free, but you must contribute your changes back to the world," then your scenario seems perfectly fair.

The kind of arguments you raise here have always, to me, basically looked like:

"I want something for nothing"

Or in more detail:

"I want to take something you created and agreed to share with me (on the proviso I like-wise share any changes as an exchange of value). I deem your software valuable to me but I won't be paying you money for it. I'll add something else to it so it fits my use-case. But, I refuse/object to sharing my changes because they're valuable."

It's not just sharing the changes. You have to be really careful how you integrate/modify the source. If you aren't you could accidentally expose proprietary information within those modifications. It's that kind of headache that means it is just easier to avoid.
As someone working on a product that uses open source, GPL makes development more complex.

With a permissive license, I can make a decision, with my manager, to use a technology based on its merit.

Office bureaucrats get weird when you talk about the GPL. When using it, I have to involve lawyers in the company, they don’t understand why the technology is important, but they have a bunch of questions, and to answer them it takes up time from my team. Upper management is involved and wants to know if we can use anything else, or they’ll phrase it as a question like: why can’t you use anything else? You have to deal with a lot more office politics when you use GPL instead of doing development work. So I’d say that’s the biggest downside for developers is that it wastes their time.

Exposing the API/Web pages is considered distribution.
"What makes the AGPL unattractive?"

I won't pretend to be a lawyer, but I do know that when we were acquired we had to list ever piece of software we used and which licence it was under. They were very concerned about copy left. We didn't have any, so I don't know how that would have changed things. MIT was what they were hoping to see.

>What makes the AGPL unattractive?

My two cents: it juts isn't in business culture to contribute to public good.

js has come a long way but i'm skeptical that it's maturing fast enough for this to be the right medium- to long-term language/platform choice for something that's meant to be more infrastructure than just web app. and while php[0] is long past the hype cycle, it's more proven in this role than js, but even that is usually superceded, or at least augmented, by more "industrial" languages when approaching amazon's scale. for instance even mid-market WMS systems are often written in compiled languages like C# because of the need for speed and robustness.

[0]: nowadays i prefer ruby/rails, which can also get you pretty far before needing extra help.

Isn't this project mostly about interfaces for businesses to connect their guts? The language used to implement services behind common interfaces shouldn't matter all that much. It's just the reference implementation in js, no?
i didn't examine deeply but it seemed to me the backend is running on node, and that it was meant to be the implementation, not just a reference.
AGPL by default with a paid, non-copyleft license would be a good business model.
>Using a copyleft license like AGPL makes this an automatic non-starter for most businesses, no matter how impressive your tech might be.

Maybe some (but certainly not most!) tech businesses, but what makes you think that vendors of real-world products give a shit about AGPL?

https://drewdevault.com/2020/07/27/Anti-AGPL-propaganda.html

> Using a copyleft license like AGPL makes this an automatic non-starter

Completely disagree. It protects the end user, and if another license is absolutely necessary, they can negotiate for it or create a different service tier.

AGPL with paid alternative licensing is strictly superior to MIT for start-ups.

(comment deleted)
> especially ones that are JavaScript instead of PHP why?
Akin to saying: "You should not ask businesses for money for your work, because they do not like it."

Greedy businesses not wanting to contribute back can buy another license and have their way, at least paying the maker(s) of this project.

This is really high quality work, great job!

> Let me know what you guys think of the idea and if you see any potential pitfalls.

Yes, so I don't agree with this:

> This model can be used to disrupt any marketplace from AirBNB to UberEats: building tech for home renters and restaurants and later, leveraging that to build a competing marketplace.

Because the value in a marketplace is the people, not the tech. Here's a thought experiment: if Amazon were to open-source their entire marketplace tomorrow, what would change? My answer is: close to nothing.

What makes marketplaces so hard is that you need people - on both the demand and supply sides.

You seem to have a good handle on the tech and the way that businesses use it, so keep talking to people and I'm confident that you'll find a valuable niche! People will find the quality of your work very compelling.

Saying that you're building an open source Amazon to complete with Amazon is like saying that you're working on an audio player skin to compete with Winamp.

Amazon isn't a web site. It's the one of the most sophisticated supply chain systems on the planet. The website is what people interface with, but it's also one of the most inconsequential parts of the system with regards for why people use it.

One of these day someone will do OpenBazaar (https://en.wikipedia.org/wiki/OpenBazaar) right. They were on to something, and just possibly, all this infrastructure built around web3 might not be completely useless for that kind of a distributed marketplace.
The change in your past HN posts from "open source order management system" to "open-source Amazon" is a great case of vision selling better than the product itself.
When I read the title, I assumed they were taking on AWS, not setting themselves up to sit between a business and their customers.
Those efforts look impressive but no service will be a version (open source or otherwise) of Amazon until it can place a single tube of toothpaste in my garage 18 hours after I ordered it, which it just did thirty minutes ago.

Amazon’s “tech” stack, both consumer- and seller-facing is horrible and borderline irrelevant.

Their fleet of trucks and aircraft is not.

Amazon.com is likely the most a/b tested piece of software on the planet. It is ugly and clunky because that's what _works_ - same with Alibaba and Yahoo JP.
i read somewhere that bezos personally controls the look and feel of amazon and thats why it looks like that. some amazon UX/UI director even quit over it
That is not true, some parts might be clunky because that works, but there's also many parts that are clunky simply because it's hard to make a change without breaking anything. But amazon doesn't care due to their strong position in the market and because AWS is their cash-cow anyways.
It's ugly and clunky because a) Jeff used to guard it fiercely, b) because a/b testing is not guaranteed to get the best results, and c) you might just be on the "ugly" a/b test.
They could make the UI better if they wanted to, but they don't, because of reliability.

For most enterprises, if it works, don't touch it.

its not what works, its whats good enough, or not bad enough to cause an obvious problem. well maybe thats what you mean by "works" i dunno
> Amazon.com is likely the most a/b tested piece of software on the planet. It is ugly and clunky because that's what _works_ - same with Alibaba and Yahoo JP.

This was on the HN frontpage yesterday: "Be good-argument-driven, not data-driven" https://news.ycombinator.com/item?id=32651763

I’ve seen countless bad decisions being taken because the A/B test was badly done. You can’t assume that some decision was good JUST because they A/B-tested it.

"It is ugly and clunky because that's what _works_"

It's a legacy code nightmare, but customers are used to it and this is #1 reason why it will not be changed anytime soon.

It's been ugly forever, and there have been several wholesale rewrites (C++ -> Perl -> Java, and JavaScript and whatever is in native apps)
A lot (most?) of that is contractor based now, though. At least the last mile. And from the sounds of it, most of the contractors aren't huge fans of Amazon anyways. Seems like it would not be insurmountable to leverage that market for similar delivery times.
Most contractors also don’t care.
18 hours — Or ~ 4 hours if you're in Japan.
It’s sweet, definitely helps that most people live near one of a handful of cities.
You're right, amazon is a logistics company first and foremost. But if you can replace the website with something like this and then let all the other logistics providers (ups, USPS, FedEx, dhl unfortunately) handle the logistics you can re-enable competition in this space.
18 hours is a pretty stupid selling point IMO. You either need something immediately or you can wait. Rarely do I need anything 18 hours from now.

I think many sellers would love to not be locked into Amazon and at least use something like this as an additional alternative. I'm on the other side of the table where I avoid buying from Amazon as much as possible.

18 hours is overnight.

Last night "Hmm. Toothpaste almost gone. Let me check the linen closet. Nope. Excuse me while I whip this out. (gasp) Swipe, tap, tap, t-o-o-t-h (autocomplete), scroll, tap, tap, tap. Done."

Used the last this morning, new toothpaste delivered at noon.

I shop online exclusively because one of my first jobs was in retail and it is my solemn duty to do everything I can to annihilate the brick and mortar store, to erase it from existence to the point that it remembered only as a distant cultural echo by future generations.

This is all I can do, and it is enough.

I even get booze delivered so I don't have to stand in line as some tweaker tries to buy lottery tickets with handfuls of quarters at the liquor store.

Despite what the internet might have you think, fulfillment centers for every single distributor or retailer are run the same so I choose amazon because they can get many things here in 4-6 hours, most of the rest the overnight, and weird stuff in two days.

If he’s the one who gets pizzas delivered at the party, then yeah!
You have an interesting (and I find pitiable) perspective here. I live in a small town, and brick and mortar stores are how many folks survive here.

I, and many other townfolk go out of our way to expressly shop in town. This helps create an interesting, culturally vibrant downtown, filled with shops and restaurants.

My saturday mornings usually involve me walking the town, poking my head into shops, saying hi to folks I might know along the way, and supporting a local business here or there.

I can't imagine wanting to get rid of all of this, possibly even irreversibly so, for the sake of efficiency.

Who hurt you?

You obviously live in a much nicer place. Sounds like the GP lives in a rougher neighborhood in a larger city, which if you’ve never experienced, can definitely leave you wanting to avoid having to shop in public.
It is crazy how things are different around the world. I can't imagine buying something online what I can just walk 6 mins and buy in a shop.
My local brick and mortar store is less than five minutes away. Why the hell do I have to replace it with an even more expensive alternative store that increases the waiting time by a factor of 216?
It's almost never 5 minutes though, is it? You have to get there, park if you are using a car, possibly pay for parking, depending on the location, go look for the things that you want all over the store, possibly not find some of them, wait in line which could be quite long, get to the car, drive back. All this time will add up.

Instead, I can do some of that shopping on my computer or phone, then quickly reference it again or even set up auto deliveries. A lot of times it'll be cheaper too because I can comparison shop.

For me, it's about convenience and saving time and money. It won't be the same for everyone, of course. The location where you live will dictate whether this shopping experience is similar to yours or not.

Lol Amazon would disagree and are laughing their way to the bank.
Amazon's retail branch is supported by AWS' profit, so no.
>18 hours is a pretty stupid selling point IMO. You either need something immediately or you can wait. Rarely do I need anything 18 hours from now.

Stupid or not, hard to argue with Amazon's income sheet. Obviously most people disagree. I don't disagree fwiw.

18 hours is a fantastic selling point for me. I am willing to wait a couple of days for something that I bought. Beyond that, I'd rather just go out and buy it.
Imo it’s less about the speed than the predictability.

I routinely pick the “next Monday and we’ll give you two bucks digital credit or whatever” option because I assume it’ll make the shipping a little more efficient or make some factory grunt’s life easier, and I’ll still pick Amazon over other vendors because when they say Monday, they mean Monday.

I’m always able to track the shipment, it’s always predictable, I never have to wonder. It’s a less tangible feature but far more valuable.

> make some factory grunt’s life easier,

No. At best it will reduce the number of factory grunts working. Amazon has whole departments dedicates to making factory grunts life as hard as possible. "Ease" == less profit.

A next day thing can save a trip to the shops, and more importantly one less thing on the todo list. You don’t need to remember to buy it.

2+ days is a world away from tomorrow. If it is that it needs to wait until the next shopping trip.

For “now” I would just have to go to the shops. Although Uber could deliver it from a petrol station for three times the price if desperate and lazy.

I have got embarrassing small orders on uber before :)

getting stuff that fast is very stupid 98% of the time. people may like it and want it and sing its praises, but its mostly stupid. and i think stupid things generally tend to die out. that is all to say that maybe that edge that amazon has is not that important.
It's not stupid.

Unnecessary most of the time but it becomes an expected processing and delivery standard, which makes the experience much more predictable for consumers.

Very few can really compete effectively with Amazon on this front.

Source: Used to run an e-commerce company that shipped up to 2 million packages annually. Once we optimised shipping and processing, customer service inquiries and complaints dropped dramatically, and customer trust / sentiment skyrocketed.

My understanding is that in certain regions Amazon offers the option to consolidate orders to be delivered on a specific day. This is actually impressive as it's much harder to do at scale than you'd imagine.

> Source: Used to run an e-commerce company that shipped up to 2 million packages annually. Once we optimised shipping and processing, customer service inquiries and complaints dropped dramatically, and customer trust / sentiment skyrocketed.

I used to work at company that shipped ~30k packages a day. I’d say 90% of customer complaints were about the delivery delays, and only 10% about the rest. It was really hard to optimize because we had 1M products and were using just-in-time logistics with very little inventory. This is a specific market that Amazon hasn’t really entered yet, but when they’ll do they’ll crush everyone.

Agreed. Every logistics partner I ever dealt with was another layer that you did not have full control of, and each had their problems.

Amazon's in-house logistics gets cheaper with scale. Waiting for the day Amazon launches their offerings to C2C and B2C delivery to directly compete with UPS and Fedex.

Amazon's in-house logistics, plus their ability to co-mingle this entire layer will be hard beat.

The advantage of a great logistics network is predictability.

If I order from Etsy, I will drop $100 on a product and shipping. But when will I get it? I don’t know. Will it even arrive? Who knows?

With Amazon I know what I order is coming this week. That’s why I buy from them and no one else. It doesn’t matter that half their website is styled like it’s 2003 and I’m probably getting a counterfeit product.

Bingo. Predictability and consistency is actually hard to execute and scale.

I can order an iPad from Best Buy or Apple, but most of the time I'm never quite sure when it might arrive. Amazon, I know it should arrive tonight or tomorrow.

I tend to avoid buying many brands on Amazon because of supply chain integrity risks, but their execution is consistent and predictable. I can't say that about many retailers.

how is it not kind of stupid to prioritize getting something asap over being genuine?
The growth potential and the customer satisfaction.

The sad reality is that a large majority of people don't actually use products they buy. They want the satisfaction of getting a new "quality" product and imagine it gives them status.

Even if it’s stupid, the sad reality is that most people want things as fast as possible and will always gravitate towards it.
https://bol.com in the Netherlands has delivery within a few hours (by bicycle) for some cities and select products. I got in this way an inflatable mattress (old one was punctured, so I needed one by the evening for my guests) and a few other electronic devices or household items.
Bol.com gives me hope that Amazon competitors can survive by excelling in their local market.
I’m pretty happy to live in world where it’s difficult to build a business where you move trucks around cities to deliver a single tube of toothpaste to someone who ordered it the day before. Yes, it’s hard to do this as fast as Amazon does. But should we really go that way, anyway?
>But should we really go that way, anyway?

Yes.

It is more efficient from an energy, carbon, land usage, and labor perspective.

The bluish-grey van that delivered my toothpaste had several hundred other deliveries on it, and the warehouse it came from stocks the products of hundreds of stores (if not more).

How do you think a tube of toothpaste gets to "Ye Olde Mum and Pop's Auntie Emma's Down Home Crunchy Granola Authentic and Real Indie Small Business"? Trucks.

> It is more efficient from an energy, carbon, land usage, and labor perspective

That's very doubtful. Normally you'd get toothpaste along with a bunch of other items. The convenience of delivery means you no longer purchase in batches. Batches is more efficient in every sense.

Maybe the mom and pop's supply chain could be shorter and more efficient, but the OP was talking about whether we should be going down the path of immediate delivery of small orders.

Not to mention the endless packaging these deliveries arrive in.
> It is more efficient from an energy, carbon, land usage, and labor perspective.

It would be if they saved up all orders from a week, and then send it all to you at the end of the week in a single delivery.

> How do you think a tube of toothpaste gets to "Ye Olde Mum and Pop's Auntie Emma's Down Home Crunchy Granola Authentic and Real Indie Small Business"? Trucks.

With one truck every two weeks that deliver toothpastes as boxes of 1000s. That’s one truck for all the customers that will go in that shop over two weeks.

Compare that to 2-3 trucks to directly deliver all these people one package per toothpaste. The only way to lower the delivery times is to increase the number of trucks.

Think of a tree where leaves are customers and the root is the producer. Each other node is an intermediary. In the worst case, if all customers go by foot in one shop that gets direct deliveries from the producer, you use only one truck (producer->shop). If all N customers are delivered by the producer, in the worst case, you use N trucks (producer->customer).

> Their fleet of trucks and aircraft is not.

A little while ago I drove past a giant blue pyramid dedicated to the grand and wise Jeff Bezos where I can only imagine The Great God of Online Commerce conducts his human sacrifice rituals on unwitting union organizers. Pretty sure they are currently keeping the management indoctrination ceremonies low key being Labor Day weekend and all that.

And people thought the Long Beach shipping container height restrictions were lifted over practical concerns…

This seems like a reseller's dream. If you're lucky enough to find an untapped resource on Etsy, Shopify, eBay, etc and you think you can market it better and flip it for a profit - create your own stores, route the orders through OpenShip and have the lesser-known seller fulfill them for you.

I didn't dig in, but in that above scenario, does the "supplier" dropship directly to my buyer or does it come to me and I reship it?

It goes directly to your buyer. Once you start getting a lot of orders, you can private label, order in bulk, and ship it yourself by just changing the channel. You can become the supplier people dropship from.
On your deployment page[0], it says you can deploy the entire thing to Vercel or Netlify and pass in the postgres connection string to the frontend directly. Am I understanding this correctly? Is the connection string for the database readable from the front end?

[0]https://docs.openship.org/deployment

It uses Next.js API routes as the backend which is all server-side.
I don’t think you should compare it to Amazon. What makes Amazon so popular isn’t the that their store front / reseller portal / interface is great.

What makes people buy from Amazon is the speed in which you get your product and their customer service.

Since this is an open source Amazon I’m curious to know how you are building out your product recommendations and suggestions for users?
My experience is that Amazon.com has never once recommended or suggested anything sane to me, beyond that it loves to "recommend" the items that I just bought. It's worse than the YT recommendation algo, in that way. If flushing the Amazon browse history wasn't such a monster PITA, I'd do it daily
You’re solving the wrong problem, For building Amazon you need capital not tech so much.