125 Jars of Chili Crunch in 24 Hours: The Messy Reality of Physical Side Projects

I spend way too much time watching people deploy SaaS apps on r/sideproject. We love arguing about Hetzner versus DigitalOcean or whether we should rebuild our landing pages in Astro 4.0. But every once in a while, a post stops me dead in my tracks.

Someone just shipped 125 jars of chili crunch with their husband in the first 24 hours of launching.

That is a physical product. In the physical world, you cannot just spin up a new containerized instance when you get a traffic spike on Hacker News. You run out of glass jars. You run out of labels. Your printer jams.

I tried selling physical merch for a software project two years ago. It was an absolute nightmare. Dealing with SKU variants, calculating shipping zones, and trying to figure out if a 4x6 thermal label printer works with a 2019 MacBook Pro will make you yearn for a simple TypeScript migration error.

So when I see a food side project hit 125 orders out the gate, I immediately look at the underlying stack and the operational reality of what they just pulled off.

The sauce that broke the link-in-bio #

Let’s talk about the backend. I guarantee they didn’t use a complex multi-tenant architecture.

If you are launching a physical food product, BigCommerce is overkill for most people, and WooCommerce will absolutely bleed you dry on plugin subscriptions unless you are deeply familiar with PHP. They almost certainly used Shopify Basic. At $39 a month, it handles the tax logic and the label integration.

But here is the fatal flaw of instant demand: inventory sync.

If you read the original comments on the r/sideproject thread, someone asked why they capped the initial batch. The creator mentioned they literally only had 125 jars physically bottled and labeled in their kitchen. When you sell out in 24 hours, the gating factor isn’t server RAM or database locks. It is the fact that you physically cannot boil enough oil to crush more chili flakes before midnight.

I haven’t tested their exact logistics on a food scale, but I have tested the Shopify + ShipStation integration on a burst of 100 orders. It works flawlessly right up until you realize you need a specific USPSRegionalRateBoxA and you only bought a pack of B boxes from Uline.

The reality of fulfillment math #

Let’s break down the economics of a launch day like this.

Assume retail price is $15 a jar. 125 jars is $1,875 in gross revenue. That sounds amazing for 24 hours of side-hustle work.

Now subtract the COGS. The jars, the labels, the chili flakes, the oil, the shipping boxes. If they are netting $5 a jar, they are doing incredibly well. That is $625 in actual gross profit.

Then subtract the cost of customer acquisition. If they ran even $10 a day on Meta ads to drive that traffic, or spent hours crafting the perfect TikTok video that got 10,000 views, the hourly pay rate drops fast. The community is genuinely split on whether physical goods are worth the hassle precisely because of this math.

You can build a SaaS with zero marginal cost. Food? Every new customer represents a trip to the wholesale store to lug around 40-pound bags of bulk spices.

Scale cautiously, pack lightly #

There is a specific kind of burnout that happens when your side project demands you stand on your feet for six hours straight taping boxes. It is different from sitting in a dark room debugging a React hook.

A burst of 125 orders is a dream scenario, but it hides a brutal operational overhead. You start asking yourself if a Pirate Ship integration is saving you enough time to justify eating cold pizza at 2 AM.

I love seeing indie hackers break out of the purely digital mold. Making something tangible that people will actually eat is a profound feeling. The unit economics are genuinely terrifying compared to having zero marginal cost on board. But I respect the hustle. Now they just need to figure out how to not get crushed by their own success before the next batch.