Module Setup Guide

Set up the B-good Module in Odoo 18 and run the demo flow

B-good is a product of Kitswys Pty Ltd. This guide explains how the ZIP is delivered, how to install the module in Odoo 18, and what to check on the first run. If the ZIP is hosted in Google Drive, it should use a direct-download link so users never land on a Drive preview page.

What This Module Is

B-good is a B-BBEE preferential procurement control center for Odoo 18. It turns supplier compliance, recognised spend, and scorecard movement into one operational workflow.

This module includes the dashboard, supplier profiles, evidence tracking, spend batches, spend lines, evidence packs, printable outputs, and a guided demo dataset.

Installation Steps

1. Download the ZIP

Use the download button above to fetch the full module package. If you move the ZIP to Google Drive later, replace the link with a direct-download URL so the browser downloads the file immediately.

b-good-main.zip

2. Extract the module folder

Unzip the archive on your machine or server and keep the module folder intact. Odoo expects the folder to contain the manifest, Python code, XML views, and demo data.

unzip b-good-main.zip

3. Add it to your addons path

Place the extracted folder in a directory that your Odoo server already scans for custom modules, then confirm that directory is listed in the Odoo configuration.

4. Restart Odoo and update the Apps list

Restart the Odoo service, enable developer mode if needed, then click Update Apps List and search for B-good.

5. Install and validate

Install the module, open the B-good menu, and confirm the active company, measurement period, and rule set. Make sure the dashboard loads without missing-menu or missing-view errors.

6. Run the demo flow

Open supplier profiles, review certificates, inspect spend batches, and recalculate the scorecard so the first run is visibly useful.

What The ZIP Should Contain

One Odoo module folder with a manifest, models, views, security rules, and any demo data you want users to see on first open.

Optional release docs such as a readme, changelog, or setup notes if you want the package to be self-explanatory outside the website.

Odoo 18 compatibility and any Python dependencies needed for exports or reporting should be included in the package notes.

Tip: load the demo data if you want the first run to open with sample supplier records, spend batches, and scorecard movement already visible.

First-Run Checks

Open B-good.
Confirm the dashboard loads and the navigation is visible.
Open supplier profiles and make sure certificate fields are readable.
Inspect spend batches and spend lines for sample or live data.
Recalculate the scorecard.
Generate an evidence pack.
Use the documentation tab for product guidance.

Download Module ZIP See architecture

What To Show In A Demo

These are the screens that tell the story fastest and prove the product is real and usable:

Primary Screens

Dashboard
Supplier Profiles
Certificates and Affidavits
Spend Batches
Spend Lines
Scorecard Assessments
Evidence Packs
Documentation

Packaging Checklist

Keep the ZIP naming consistent across the site and the downloaded file.

Make sure the module folder name matches the addon import path you expect users to place in Odoo.

Include demo data only if the first-run experience should be pre-populated.

If you host the ZIP in Google Drive, swap every download link to the direct file URL, not the Drive preview URL.

Troubleshooting

Download opens Google Drive instead of the file: use the direct-download URL. The file should be downloaded by the browser, not opened in a Drive page.

Odoo cannot find the module: confirm the addon path in the Odoo config and restart the service after extraction.

Module does not appear in Apps: enable developer mode, refresh the Apps list, and check that the folder name matches the addon module name.

Demo data does not load: verify the XML/demo files are included in the ZIP and that the module is installed on a database that allows demo content.