[sophacles]

Neat! Im curious - were you in tech before becoming a baker at all, or did you pick up the programming skills to help your baking career?

I ask because I'm always interested in hearing how non-programmers end up programming. I've long held the opinion that we (tech that is) should try to make things more programmable by users (e.g. game scripting, excel, the "citizen developer" world of sharepoint), etc and like to hear how non-tech folks use programming to solve problems.

[mcaravey]

Oh, I do software by trade. The bakery is because it started as a family business that I helped get off the ground. My background is in B2B payments and construction software. Even though the bakery doesn’t make as much money as software, there’s a whole other world of experience to be gained by running a blue collar business that runs 20 hours a day, 7 days a week. Very very different that a software shop.

But to your point, most ERP planning software for bakeries sucks badly, like really badly. One of the prominent ones you can purchase today runs off a JET database from the 90s, with the “cloud” version just being Citrix access to a VM. but they all seem to universally require you to print out paper every day for every shift, so a ton of people just fall back on Excel (using bakers math) to pan production, daily. My software runs on an iPad that is kept at each station for kind of shift, and it spits out packing sheets and invoices from Quickbooks, and integrates with our delivery route planner. It would be a full time job to be calculating everything from mix quantities to how to pack the final product, without mistakes, 7 days a week.

There definitely needs to be better tools for the lay-person though. None of my staff can make changes to our custom software, but also it is basically impossible to recreate it with low/no-code tools. Hence Excel…

[esperent]

I'm in a basically identical situation to you, except it's my partner's cafe-bakery and I'm probably a few years behind you.

I've chosen to use Odoo rather than roll my own. It's highly customizable and open source. I'm self hosting it and I've written a couple of small plugins so far. I'm finding it pretty hackable. It's built from comfortably boring tech (Python + PostgreSQL backend, Bootstrap + JS frontend). Not perfect by any means (for example there's an annoying split between the paid and free versions, although there are plugins to extend the free version to do nearly everything the paid one can, at least for my needs), but from what I can see it's way ahead of most other similar offerings and there's a big community of developers behind it and tutorials for nearly everything.

It's a decent ERP for a restaurant. I will need to build some bakery specific stuff on top but it's already reducing our workload a lot. Previously my partner was doing the low tech excel sheets and paper receipts method and we're gonna do a slow transition to Odoo over the next 6 months or so.

Besides that, we are trialling Rocket.Chat for Slack style messaging and Outline wiki (Notion clone minus database views) for knowledge management, both free and self hosted.

Odoo is somewhat technical to learn, unavoidably (as with any ERP software). But it's been a good test of the other two to see whether non-technical baking staff can use them. Some of them are very non-technical, internet = Facebook level.

Besides a few teething problems, so far so good. It's a learning experience for me, for sure. I'm staying out of the kitchen mostly but I am studying the coffee side of the business which is lovely change of pace from coding.

[radanskoric]

I’m always super interested to hear about industries seemingly “neglected” by software. There are so many software product opportunities off the beaten path.

Would you mind sharing the name of that 90s software?

What makes it impossible to recreate with low/no-code tools? It sounds like a relatively standard interface over some calculations which sounds like it should fit.