A mold can be sitting in the correct storage rack and still be unfit for the next order. Mold Management Software helps answer the questions that a rack label cannot: how much has this tool run, what needs attention, and who has cleared it for production?
Those answers matter when a customer wants a delivery date. The press may be available, the resin may be in stock, and the production team may be ready. But if the required mold is overdue for service, the order needs another plan.
For an IT head or business owner, the starting point is quite practical. The toolroom and production planner need to agree on the condition of the same physical tool. A reliable mold record gives them a place to do that.
What Mold Management Software needs to tell your team
Picture a planner checking tomorrow’s switchgear component order. The system lists two molds against the part number. One is ready; the other has a damaged insert and is waiting for a repair supplier.
That distinction should be visible before the planner assigns a press. If someone has to call the toolroom to find it out, the software record is missing information that affects the schedule.
Build each mold record around the questions people ask during a shift.
| Question | Record needed | Why it matters |
| Which tool is this? | Permanent mold ID, part reference and drawing revision | Similar tools need separate histories |
| Where is it now? | Press, rack, plant or repair supplier | The planner can locate the tool |
| Can we use it? | Status, hold reason and release approval | A repaired tool may still await a trial |
| How much has it run? | Lifetime shots and service baselines | Maintenance can follow actual usage |
| What happened last time? | Fault, affected cavity, work done and trial result | Technicians can investigate repeat problems |
| Who owns it? | Customer or company ownership and agreed responsibilities | Repairs may need customer approval |
Give the mold a durable identification tag that opens this record. A barcode or QR code can make that easier. However, scanning the tag only identifies the tool; it does not establish that the tool is ready to run.
Mold Management Software should show readiness separately from location. “Back from the supplier” and “approved for production” describe different stages. Keeping those stages clear can prevent an avoidable setup on the wrong tool.
Count shots before you calculate mold usage
A shot is not the same as a finished part. In a conventional injection molding cycle, an eight-cavity tool can make eight parts from one shot. That assumes every cavity is active and every part is acceptable.
Suppose one cavity closes halfway through a run. The mold continues cycling, but its output per shot falls. Meanwhile, startup shots and rejected parts add usage without adding saleable stock.
For that reason, dividing good output by the original cavity count gives an incomplete picture. Use a verified counter reading or cycle source for the mold’s usage history. Keep output and reject quantities alongside it for production analysis.
Select a counting method your plant can maintain
There are several ways to bring shot data into Mold Management Software. Each has a practical limitation worth checking during the trial.
- A counter fitted to the mold travels with the tool. Check whether it counts mold movements or actual injection cycles.
- A machine connection can supply controller readings. The system still needs to know which mold occupied the press during each run.
- A sensor and gateway may offer a route on compatible older equipment. Confirm the signal against actual cycles before using it for maintenance.
- Manual opening and closing readings can work initially. Assign someone to review missing entries and unusual changes.
Progressive Components’ CVe monitoring tools provide an example of monitoring linked to tool history. When reviewing any device, ask what happens during a dry cycle, a setup movement or a counter reset. These details decide how useful the reading will be.
Also, ask what happens when the network goes down. A connection that silently loses readings can leave a believable but incomplete total. Retain the source reading and timestamp so the team can reconcile gaps later.
Preserve the lifetime total after maintenance
Cleaning a mold does not erase the cycles it has already completed. Your system needs a lifetime total and a separate baseline for each service task. Technicians update the relevant baseline when they finish and approve that task.
Here is a simple example. A mold has accumulated 420,000 shots, and its last approved vent-cleaning service was at 392,000. It has therefore run 28,000 shots since that service.
If the team repairs an ejector component today, that repair should not reset the vent-cleaning baseline. Otherwise, an unrelated job could postpone a service that remains due.
Plan maintenance around the next production run
An overdue alert tells the team that a limit has passed. A more useful planning check asks whether the next order will push the mold past that limit. Mold Management Software needs enough order and usage data to support this check.
Take a hypothetical tool with a plant-approved service interval of 50,000 shots. It has run 44,000 shots since that service, leaving an allowance of 6,000. The next order needs 56,000 good parts from eight active cavities.
At perfect yield, the order requires at least 7,000 shots. Startup losses and rejects may increase the requirement. The planner should therefore review the maintenance slot before releasing the order.
The numbers here illustrate the calculation; 50,000 shots is not a recommended interval. The toolmaker and maintenance team should agree on the actual limits. Resin, tool design, operating conditions and previous faults all belong in that discussion.
Give different tasks their own due points
A mold may need several kinds of attention. Some tasks follow usage; others relate to storage time or a condition found during inspection. Combining everything into one maintenance date hides those differences.
Keep cleaning, inspection and component work separate where the maintenance plan requires it. A rarely used mold may need a storage check before it returns to production, even with a low shot count. Likewise, a fault found during a run may require attention before the next scheduled service.
Recurring flash, for example, deserves an investigation. The cause might involve the tool, the material or the process settings. Recording the finding does not establish the cause, so the service entry should also capture what the team checked.
Progressive’s activity-report documentation places maintenance events alongside cycle counts. That is a useful model for reviewing how a tool behaved before and after work.
Use the history to judge mold life
Management may want a dashboard that shows exactly how many shots remain before a mold fails. A shot total alone cannot provide that certainty. It describes usage, while the tool’s condition still needs inspection and engineering judgment.
In Mold Management Software, keep the planned life target separate from actual shots and inspection findings. Record the basis of that target and who approved it. Then review it as the team collects evidence from the tool.
The history can still support a good investment decision. Perhaps a mold has had three repairs to the same area within a short period. The repair invoices look manageable, but every incident also interrupts a customer order.
Review the repair spend together with lost production time, quality losses and upcoming demand. Also, check the lead time for a rebuild or replacement. A tool needed for future orders may warrant action well before it reaches its original life target.
Track replacement inserts without losing the parent history
Replacing an insert gives that component a new service history. It does not make the whole mold new. Keep the replacement linked to the parent tool, with its installation date and reading.
This becomes especially useful when one cavity needs repeated attention. The team can see whether faults follow the same component or continue after replacement. Meanwhile, management retains an honest view of the mold’s total usage and repair cost.
Make the service record useful for the next technician
“Mold serviced” leaves too much unanswered. Was it cleaned, repaired or adjusted? Did someone investigate the problem reported during the previous shift?
A better entry identifies the mold, counter reading and affected cavity or component. It describes the work completed, parts used and observations made. Photographs and measurements help when they explain a defect or document a change.
For example, an entry stating “cavity 3 insert repaired; trial parts accepted” gives the next technician something to investigate. Link it to the relevant drawing revision and trial result. Also, retain the technician’s name and the person who approved the release.
Mold Management Software should make it easy to record that information at the time of service. If technicians must complete a lengthy form after their shift, entries may become late or incomplete. Start with the details needed for a handover and add fields only when they serve a clear purpose.
For customer-owned tooling, include repair approvals and agreed responsibilities. A customer report can then show the work performed on that customer’s mold without exposing other customers’ records.
Where Manufacturing ERP and Odoo fit
The toolroom may only need a maintenance application at first. The wider business has another need: mold status must reach the people promising deliveries. That is where a connection with Manufacturing ERP can help.
Consider a mold put on hold during production. The planner needs that status against the affected orders, while purchasing may need to source a replacement component. If each team keeps a separate record, they can make decisions from different information.
A connected setup can link the mold with production orders, service requests and relevant costs. However, those links need clear rules. For example, will a hold prevent scheduling, or will it simply display a warning that a planner can overlook?
For a broader view of this workflow, see Apagen’s ERP for injection molding manufacturers. Tooling requirements should form part of the production scope from the start.
Using Odoo for manufacturing as the foundation
Odoo for manufacturing can provide a foundation for production and equipment-maintenance workflows. Its Maintenance documentation describes preventive and corrective requests for equipment and work centers.
That does not mean a standard installation covers every mold requirement. Automatic shot capture, separate usage thresholds and lifetime counters may need extensions or integrations. Mold reservation, press compatibility and customer ownership also need validation in the proposed setup.
Before approving an Odoo scope, ask for a demonstration using one of your molds and a real order scenario. Confirm the version, edition and hosting arrangement, because these affect the available features and extension options. The proposal should identify what comes as standard and what the partner will configure or develop.
A practical software evaluation for IT and management
Use a small group of your own tools to evaluate Mold Management Software. Include one that moves between presses, one with recurring repairs and a customer-owned mold. These expose different gaps in the workflow.
During the demonstration, ask the supplier to perform the following tasks:
- Move a mold to another press without losing its usage history.
- Correct a counter reset while preserving the original reading and reason.
- Check an upcoming order against the remaining service allowance.
- Record a repair and keep the mold on hold until the required release checks finish.
- Export the mold history and attachments in a usable form.
- Show who can change readings, approve work and view customer records.
Then test the process during normal shifts. Can operators capture readings without leaving several entries until the end of the day? Can the planner tell whether a tool is available without making a phone call?
Budget for more than the software subscription. Tags, counters, gateways, data cleanup, integration and training can all add work. Apagen’s injection molding ERP implementation cost guide can help frame the wider implementation discussion.
Judge the pilot against the problem that justified it. That might be missing shot records, repeat tooling failures or orders delayed by an unavailable mold. Once the records hold up during everyday use, expand the process to more tools.
FAQs about Mold Management Software
Can we track mold shots on older presses without a reliable network connection?
You can begin with checked opening and closing readings from a suitable counter. For automatic capture, review the controller outputs or a compatible sensor and gateway. Test what the signal actually counts, then check how readings survive a lost connection. A mixed approach can be sensible when some presses support automation and others do not.
Should we maintain a mold after a fixed number of shots or after a fixed number of days?
Match the interval to the service task. Shot limits can guide work linked to use, while dates help manage inspections during storage. Start with the toolmaker’s guidance and review it against your own findings. Mold Management Software should let the team maintain separate rules, rather than force every task onto one schedule.
How do we prevent the shot history from becoming inaccurate when a mold moves between plants?
Use the same permanent mold ID at every location. Record the transfer, opening and closing readings, and the press used for each run. If a counter resets, keep an approved adjustment with the original reading and explanation. This gives the receiving plant a continuous history instead of another total that starts at zero.
Can we manage mold maintenance within our existing Odoo system?
Check the gap in your existing setup first. Odoo supports equipment-maintenance requests, but your shot counters, maintenance limits and planning rules may need additional work. Ask your partner to demonstrate those requirements in your version. A separate application may suit specialist toolroom needs, provided its status and data reach the ERP when required.
Can software tell us exactly when a mold will need replacement?
It can help identify a tool that needs review, but a shot total cannot establish an exact failure date. Compare usage with the approved target, inspection findings, repair frequency and future order demand. Include rebuild or replacement lead time in the decision. Engineering must assess the physical tool before management commits to continued operation or replacement.
How can we show a customer that we maintained their mold properly?
Keep dated service entries linked to the mold ID and counter reading. Include work details, parts, photographs where useful, and the required approvals or trial results. Also, record the responsibilities agreed with the customer. A customer-specific report from Mold Management Software can present that history while limiting access to that customer’s information.
When should we replace our Excel mold records with dedicated software?
Excel may remain adequate when the team keeps a modest set of records current. Reconsider it when people disagree over readings, miss service work or schedule tools that are unavailable. Test whether software fixes those specific problems and how much effort the new process takes. If Manufacturing ERP integration is necessary, include that cost in the comparison.
Put a reliable mold record into daily use
The first useful result from Mold Management Software is a planner and technician working from the same up-to-date history. From there, the plant can schedule service around actual usage and review tooling costs with better evidence. Accurate records give those decisions a firmer basis.
If your shot counts, repairs and tooling status sit in separate sheets, Apagen can help review how they should connect. We can identify the configuration, development and integrations an Odoo-based workflow would require. Discuss your injection molding ERP requirements with Apagen and start with the tools causing the most disruption.