What a Bill of Materials does in day to day production
A Bill of Materials, or BOM, is the master list that shows exactly what goes into a finished item. It records each component, sub-assembly, quantity, unit of measure and revision so production, purchasing and stores all work from the same version. In practical terms, that means fewer mistakes on the floor, fewer urgent calls to suppliers and less scrap when a job is built from the wrong list.
For South African SMEs, this matters whether you are assembling electrical panels in Midrand, producing food packaging in Durban or building fitted products in Cape Town. When stock is tight and lead times move, a proper BOM helps you plan what to buy, what to issue and what to reserve for each work order. It also helps with cost control because each item can carry its current price, usage rule and approved substitute if one is allowed.
Bizmatics supports BOM structures that are simple enough for small teams yet detailed enough for multi-step manufacturing. You can keep one level or many, depending on how your products are made, and you can link the BOM to inventory, purchasing, shop-floor issue and reporting. That gives managers a proper view of material consumption instead of relying on spreadsheets that get out of date fast.
BOM structures, sizes and options that suit different operations
Not every business needs the same BOM setup. Some need a flat list for a single finished item, while others need nested structures for sub-assemblies and variants. Bizmatics can support a range of setups so you can match the system to your real production process rather than changing your process to suit the software.
Common options include standard BOMs for repeat items, variant BOMs for size or specification changes, and revision controlled BOMs for products that change over time. If your business makes items in different pack sizes, lengths or material grades, the list can reflect those differences clearly. This is useful for manufacturers in Gauteng and the Western Cape where one product often has multiple customer specific versions.
- Flat BOMs for simple assembly or kitting work
- Multi level BOMs for sub-assemblies and parent items
- Revision based BOMs for controlled changes over time
- Variant BOMs for different sizes, colours or material grades
- Phantom or reference items where a grouping is needed without stock holding
Typical fields include item code, description, quantity per build, unit of measure, scrap allowance, issue method and approved substitute notes. You can also store minimum batch quantities, routing links and revision dates where needed. That keeps the BOM useful for procurement and production control not just as a static list.
Where the BOM fits across purchasing, stores and production
A good BOM is not only for the production office. It should feed purchasing, receiving, inventory and dispatch so each part of the process sees the same approved requirement. When a work order is created, the BOM can drive material reservations, pick lists and purchase requests, which cuts down on manual rekeying and missing lines.
This is especially helpful when operations run across more than one site or branch. A business with teams in Johannesburg, Pretoria, Durban or Gqeberha may need central control over what gets used, while allowing local stores to issue stock against the correct revision. That helps when branch teams are dealing with lead times, supplier differences or local stock shortages.
For SMEs, the biggest gain is visibility. Managers can see expected usage against actual issue, then compare that against scrap, rework or approved substitutions. It becomes easier to spot where material is being lost, where a line is over issuing and where a supplier spec has changed without anyone updating the list.
- Purchase planning based on required quantities and lead times
- Stores issue linked to approved BOM usage
- Work order picking and kitting for production teams
- Costing and margin checks using current component values
- Traceability when customers ask which revision was built
Setup, integration and power requirements for a clean rollout
Implementing BOM control is mainly about getting the data right from the start. We map how your products are built, define the hierarchy, agree the naming rules and align units of measure so the records are consistent. If your team currently works from old spreadsheets, we can help clean the list before it is loaded into the system.
The software itself does not need any special power or gas supply. It runs on standard business IT infrastructure with a stable internet connection and suitable user devices. For sites that are affected by load-shedding, a UPS, backup power or controlled shutdown process is sensible so users do not lose unsaved work. If you operate from a factory, office or store room with patchy connectivity, we can plan the setup around that reality.
BOMs can also be linked with your other systems where needed, such as inventory, purchasing, finance or production tracking. That means a change in one place can flow through to the rest of the business, instead of being copied by hand. It saves time and reduces errors, especially when teams are spread between Centurion, the East Rand and coastal operations where staff may not all work from the same office each day.
Care, version control and ongoing servicing
A BOM needs regular attention if it is going to stay useful. Component prices move, substitutes change and product designs get updated. If revisions are not controlled, the team may keep using an old list and the result is wrong quantities, wrong costing or stock being issued for the wrong build. That is why revision discipline matters as much as the original setup.
We recommend that one person or small team owns approval of BOM changes. That person checks the impact on stock codes, quantities, costing and linked work orders before release. If your operation works with QA checks or customer approvals, those rules can be added too. It keeps the list practical and stops every department from making untracked changes.
Support can include periodic reviews, change handling, user retraining and upgrade planning. For growing SMEs, that support is often more valuable than a once off setup because the business changes as volumes grow. A BOM that worked for a ten person workshop may need tighter revision rules once you are producing across multiple shifts or supplying larger contracts.
What to check before you order BOM software support
Before you commit, it helps to define exactly how your products are built and who needs to use the BOM. A well planned setup will save time later and avoid rework. If the business has many variants, multiple branches or a mix of make to stock and make to order jobs, say so upfront. Those details affect the structure and the approval rules.
- How many finished items and sub-assemblies need to be controlled
- Whether revisions must be locked and approved before release
- Which unit measures you use, such as each, metres, litres or kg
- Whether substitutions are allowed and under what conditions
- What reports you need for costing, issuing and stock checks
- Which teams need access, from procurement to production and stores
It is also worth checking how the BOM will be maintained after go-live. If your team wants training, change support or a support retainer, plan that in early. A good BOM process should fit your actual workflow, not force extra admin onto people who are already busy. With the right structure, your component lists stay tidy and your production control stays dependable.
Key facts
| Core function | Structured component lists with revision control and usage rules |
|---|---|
| Typical users | Manufacturing, assembly, kitting and job-based production teams |
| BOM types supported | Flat, multi level, variant and revision controlled structures |
| Key fields | Item code, description, quantity, unit, scrap allowance and substitutes |
| Integration | Inventory, purchasing, production, costing and reporting |
| Implementation note | Suitable for SMEs operating from one site or multiple branches across South Africa |
