Start with the job the code must do
Before you choose font size, position or content, decide what the code must achieve on the line. Is it for traceability, batch control, expiry dates, product IDs, or a simple logo mark? A code that is easy to read on the factory floor is not always the best code for a retail shelf, so the purpose matters first.
For South African production sites, the practical brief should also include line speed, material type, surface finish and the conditions the item will face after marking. Glass bottles moving through a bottling plant in Boksburg will behave differently to a clear plastic component packed for export from Kempton Park. If the code has to survive moisture, cold rooms or daily cleaning, design for that from the start.
- Define the code purpose in one sentence.
- List the material, thickness and surface finish.
- Note the expected handling, packing and storage conditions.
- Confirm whether the code is human readable, machine readable, or both.
Choose a layout that fits the product and the line
A good code uses the available area without crowding the product. On small containers, curved glass, or narrow plastic housings, the temptation is to pack in too much information. That usually slows production and makes the mark harder to scan or read. Keep the code clean, and place it where operators and scanners can reach it easily.
When planning the layout, think about orientation as well. A code placed too close to a mould line, edge or label panel can distort during marking or disappear in handling. In Jet Park and Boksburg, many factories work in compact spaces, so it helps to map the code position against conveyors, clamps and transfer points before installation.
- Allow enough blank space around the code.
- Avoid placing marks on seams, curves and high wear edges.
- Check that the code stays visible after filling, capping or packing.
- Keep the layout consistent across batches to reduce operator error.
Make the code readable at a glance and under scan
Readability is about more than size. Contrast, character spacing and mark quality all matter. On glass, the mark must be crisp enough to read in bright plant lighting and on a busy packing line. On plastics, the surface can vary from gloss to matte, and that changes how the mark appears. If the product is handled in low light or during load-shedding with backup lighting, clarity matters even more.
Set your standards before full production. Test the code under the same conditions the customer will use, including dust, glare and movement. If your team works across Alberton, Germiston and Midrand sites, use the same acceptance check every time so the code quality stays consistent. A short, clean code often performs better than a long one with too many details.
- Use short text where possible.
- Test readability from normal viewing distance.
- Check scan performance on every material variation.
- Review the mark under factory lighting, not only in the office.
Build a code that can survive real production conditions
Permanent marking only helps if the code remains legible after cleaning, stacking, transport and retail handling. For glass and plastics, that means thinking about abrasion, moisture and chemical exposure. A code that looks fine after marking can still fail later if the design is too small or too shallow. In coastal areas, humidity can also affect packaging and storage, so the mark should hold up without extra protection.
Use the material and end use to guide the design. A returnable bottle, a medical plastic part and a cosmetic container all need different settings. If a code will be exposed to municipal washing processes, cold chain storage or frequent touch points, specify the worst case first. That way the finished mark remains practical, not just neat on day one.
- Test for abrasion and wiping resistance.
- Check moisture and humidity exposure.
- Consider chemical contact during cleaning.
- Confirm that the mark stays readable after packing and transport.
Set up the production process before you go live
A workable code design is only one part of the job. The setup needs the right fixtures, software settings, operator instructions and quality checks. If the product changes often, a clear setup sheet saves time and cuts mistakes. This is especially useful on lines with mixed batches, short runs, or frequent changeovers between customers in Pretoria, Benoni and the East Rand.
For new projects, sample testing should happen before final sign-off. That gives time to adjust content, spacing and mark depth without slowing the line later. If you are integrating the marking into an existing process, plan the sequence carefully so the code is applied at the correct stage and does not get damaged before packing.
- Prepare a setup sheet for each product or SKU.
- Confirm the code position, size and orientation.
- Train operators on start-up checks and fault finding.
- Keep approved samples at the line for easy comparison.
Keep the code standard simple enough for daily use
The best code design guide is one that the whole team can follow. Standardise the common parts, then allow only the fields that must change. That reduces errors and keeps production moving. A practical standard should show what is fixed, what changes, and who approves the final version. It should also cover maintenance intervals, spare parts and software backups so the line does not stall when a problem comes up.
For South African operations, that is important during busy periods, public holidays and power interruptions. If the line stops, the code process needs to return to normal quickly once power is back. A simple checklist helps your team get back on track without guessing. Keep it short enough to use under pressure, but detailed enough to catch the common mistakes.
- Use one approved template per product family.
- Record all changes and the reason for them.
- Schedule preventive maintenance before peak production.
- Review the code standard after any line change or customer complaint.
