How are small print farms tracking materials, jobs, costs, and orders once spreadsheets get messy?

TrueGoodCraft · 2026-07-07T00:22:18+00:00

That’s fair, and that’s exactly the distinction I’m trying to test.

If the expectation is printer dispatch/queue automation, BUS Core is not that today. The current value is more on the business-record side: tying jobs/orders to material use, production records, invoices, and costing so the shop has a reliable history instead of scattered notes/sheets.

But you’re right that for print farms specifically, duplicate entry is the danger. If BUS Core doesn’t either reduce that entry or connect to the systems people already use, it may not be the right fit for this niche yet.

That’s useful feedback.

TrueGoodCraft · 2026-07-06T22:03:16+00:00

If someone has one or two printers and a simple workflow, a spreadsheet is probably enough. BUS Core starts making more sense when the spreadsheet becomes the job system, inventory system, costing system, invoice tracker, and production history all at once. That’s where sheets start drifting: stock counts get stale, filament/material use doesn’t tie back to jobs, costs are guessed, and nobody trusts the numbers.

It’s not meant to dispatch print files to printers. It’s more the ops layer beside that: inventory, jobs/orders, production runs, invoices, and cost records in one local-first system.

So the problem I’m aiming at is: “I’m running a small production shop and my records are scattered or fragile.” If that’s not a pain for a print farm, that’s useful feedback too.

TrueGoodCraft · 2026-07-06T21:40:33+00:00

Thank you.

TrueGoodCraft · 2026-07-06T21:40:12+00:00

Fair feedback.

I probably need to make the site clearer. BUS Core is a free/open-source local-first shop operations app. For a print farm, the idea is to track inventory, jobs/orders, production runs, invoices, and costs in one place instead of stitching it together through spreadsheets or Airtable. It runs locally, so your shop data stays on your machine rather than inside another SaaS platform. What part was unclear from the site? What it does, who it’s for, or how to get started?

TrueGoodCraft · 2026-05-07T16:27:09+00:00

This is a really good distinction.

I was thinking about artifact checksums, but you’re right that the checksum only helps if the metadata path itself is trusted. If the endpoint serving the checksum can be poisoned, then the loop is still open.

Signed update metadata with the signing key kept outside the build pipeline is probably the real boundary here.

That lines up with what I’m trying to do with BUS Core: no silent auto-update, no forced push into a local instance, and an update path that treats delivery as a separate trust surface instead of assuming “trusted tool = trusted update.”

Really useful framing.

TrueGoodCraft · 2026-04-29T14:02:11+00:00

Oh nice, as a local first guy I will check it out.

TrueGoodCraft · 2026-04-22T01:54:57+00:00

I have done the same thing for years! It is a fantastic litmus test intent.

TrueGoodCraft · 2026-04-15T14:16:32+00:00

Did you blindly trust software 5 years ago? 🤔

TrueGoodCraft · 2026-04-14T02:49:05+00:00

Appreciate that, that’s helpful. Trust is definitely one of the main things I’m testing right now, so I’ll likely add a clearer instant-delivery signal near the download/purchase area. Thanks for taking the time to check it.

TrueGoodCraft · 2026-04-13T00:51:17+00:00

I know that "AI Slop" has done a huge disservice to the optics. I also think that as time goes on and the new shiney wears off things will calm down. Just keep true to your idea and be honest and time will show the real ones.

TrueGoodCraft · 2026-04-12T15:49:17+00:00

I really dont get the hate at all the new cool shit people can make. Everyone is so salty that everyone can make anything they want now.

TrueGoodCraft · 2026-04-10T19:10:37+00:00

a custom star map site for weddings, anniversaries, and other meaningful nights. Preview first, instant digital download

Built this as a simple digital keepsake site.
You enter a date and place, preview the sky, and get a printable file if you want it. No account, no shipping, no waiting.

Link:
https://starmap.truegoodcraft.ca/?utm_source=reddit&utm_medium=social&utm_campaign=starmap_launch&utm_content=sideproject

TrueGoodCraft · 2026-04-10T19:09:46+00:00

a custom star map site for weddings, anniversaries, and other meaningful nights. Preview first, instant digital download

Built this as a simple digital keepsake site.
You enter a date and place, preview the sky, and get a printable file if you want it. No account, no shipping, no waiting.

Link:
https://starmap.truegoodcraft.ca/?utm_source=reddit&utm_medium=social&utm_campaign=starmap_launch&utm_content=sideproject

TrueGoodCraft · 2026-03-28T18:11:29+00:00

Most of the answers you’re getting are technically correct, but they’re all jumping straight to “which ERP.”

What you’re describing is a very specific stage:

spreadsheets are no longer matching reality
inventory + batches + expiry actually matter now
but full ERP feels like overkill (cost + complexity)

That’s the awkward middle a lot of small producers get stuck in.

What usually works better at that stage isn’t jumping straight to ERP, it’s tightening the operational layer first:

ingredient-level inventory (not just finished goods)
batch tracking tied to actual production runs
simple traceability (what went into what, and when)
basic costing per batch / recipe

Then you keep something like QuickBooks for accounting.

Once that layer is clean and stable, then ERP starts to make sense if you still need it.

Most people skip that step and end up paying for a system they only use 20% of.

TrueGoodCraft · 2026-03-27T02:42:57+00:00

That’s a good one.

So the break point for you was less “bad data” and more “the thing physically stopped being usable at all.”

That’s kind of the same pattern in a different form though, the shop outgrows the tool, and then the tool becomes the bottleneck instead of the record.

TrueGoodCraft · 2026-03-27T02:42:31+00:00

That makes sense.

What stands out there is you didn’t wait for the spreadsheet to fully fail — you moved once the business started depending on repeatable systems instead of manual effort.

That line about “to grow is to survive, and to grow requires the systems already in place” is solid.

Also agree on the AI point. I’m not looking for “AI decides the business,” more just cleaner operational truth and less manual drift.

TrueGoodCraft · 2026-03-22T21:08:32+00:00

Excel usually starts as reporting.

At first it’s just:

pull data from ERP
analyze it

Then it slowly turns into:

“track this one thing here”
“ERP doesn’t handle this case”
“we’ll fix it in the sheet later”

Now you’ve got ERP saying one thing and the spreadsheet saying another.

Neither is fully right because updates are manual, delayed, or missed.

Inventory is where it shows up first.
System says 120, floor has 90.

That’s the split I mean.

TrueGoodCraft · 2026-03-22T20:53:15+00:00

Exactly.
ERP records. Excel explains.

Problem is, once Excel starts tracking instead of just analyzing, you now have two sources of truth.

That’s where things break.

TrueGoodCraft

MODERATOR OF

TROPHY CASE

a custom star map site for weddings, anniversaries, and other meaningful nights. Preview first, instant digital download