Beta Testing Guide

Status: User Guide

Beta Testing Guide

Useful beta feedback does not need to be polished. It needs to be specific enough that someone can understand your setup, your goal, and where the experience helped or failed.

What Useful Feedback Looks Like

Good feedback often sounds like:

• "I got it running."
• "I opened it but didn't know what to do next."
• "I tried to set up inventory and got stuck at ___."
• "This would fit my shop because ___."
• "This would not fit my shop because ___."
• "I'm trying Docker/Synology/NAS."

What To Include

Please describe:

• your shop or workflow type
• your install method
• what you want BUS Core to help with
• where you got stuck
• what would make it actually useful for you

Especially Helpful Signals

• You got BUS Core running and can say what felt easy.
• You got it running but did not know the next step.
• A real workflow matched your shop.
• A real workflow clearly did not match your shop.
• Setup worked on Windows, Docker, or Synology, and you can describe the path.

Where To Send Feedback

• Use Bug Reports for broken behavior.
• Use Feature Requests for workflow gaps or missing capabilities.
• If you are not sure which one applies, include your context anyway. Early operator feedback is still useful.