Companies implementing industrial label printing often ask the same question:
Should labels be printed from the ERP or from the MES?
It sounds like a simple architectural decision. In reality, it reflects a misunderstanding of how modern manufacturing systems should work together.
Enterprise Resource Planning (ERP) systems and Manufacturing Execution Systems (MES) manage different parts of the manufacturing process. Each system owns different business events, different data and different responsibilities.
Trying to choose one system as the single source for every label often leads to unnecessary complexity, duplicated business logic and difficult-to-maintain integrations.
A more scalable approach allows each system to trigger labels for the events it owns while a centralized printing workflow determines how every label is validated, generated, routed and tracked.
A typical ERP and MES label-printing scenario
Imagine a manufacturer producing industrial equipment.
The ERP creates the production order, reserves inventory and manages customer-specific requirements. The MES controls the production line, records completed operations and verifies quality inspections.
Later, the finished product is packed and shipped.
Three labels are printed during that process:
- a product-identification label,
- a pallet label,
- and a shipping label.
Should all three originate from the ERP?
Should they all originate from the MES?
Or should each system trigger different labels according to its own responsibility?
The answer depends on the business event—not on which system happens to be available.
Key takeaway
ERP and MES should not compete for label printing. Each system should trigger labels for the events it owns, while a centralized printing workflow controls how labels are validated, generated, routed and tracked.
Why this comparison matters
Many organizations begin their label-printing journey by connecting whichever system is easiest to integrate.
If production is already connected to an MES, the MES may gradually become responsible for every label. If the ERP already communicates with warehouse operations, the ERP may become the default source for every print request.
Neither approach is inherently wrong.
The problem appears when one system starts taking responsibility for business events that actually belong to the other.
Examples include:
- shipping labels generated from production events,
- product labels generated from sales-order logic,
- printer routing embedded inside ERP transactions,
- template selection embedded inside manufacturing applications,
- and equivalent business rules maintained independently in both systems.
Over time, this creates duplicated logic, unclear ownership and integrations that become increasingly difficult to change.
A better architecture assigns responsibility according to the business event itself rather than according to technical convenience.
What is the ERP responsible for?
An ERP system manages the commercial, administrative and logistical side of manufacturing.
It knows what the organization plans to produce, purchase, store and deliver. It maintains business master data, customer information, inventory records and order-management processes.
For label printing, the ERP is typically the authoritative source for events such as:
- customer shipments,
- delivery processing,
- inventory movements,
- purchase receipts,
- warehouse operations,
- customer-specific labeling requirements,
- and business or compliance documentation.
These events originate from business transactions rather than from physical production activities.
For example, the ERP may know that a completed pallet has been assigned to a specific delivery, customer and destination. That business context can determine whether the pallet requires a customer-specific label, an SSCC logistics label or additional shipping documentation.
As explained in our guide to ERP label printing, the ERP should communicate trusted business information while allowing the printing workflow to determine how the resulting labels are validated, created and delivered.
ERP provides business context
The ERP usually provides information such as:
- sales and production orders,
- customer and supplier information,
- product and material master data,
- inventory and warehouse locations,
- delivery destinations,
- packaging requirements,
- and commercial or regulatory attributes.
This information is essential for labels connected to planning, logistics, inventory and customer fulfillment.
What is the MES responsible for?
A Manufacturing Execution System focuses on what is happening on the production floor.
Rather than managing customer orders or inventory planning, the MES records and controls real-time manufacturing activities.
Typical MES events include:
- completed production operations,
- quality approvals,
- machine and equipment events,
- work-order progress,
- product serialization,
- batch completion,
- container completion,
- and pallet completion.
These events describe what has actually occurred during manufacturing.
For example, the MES may know that a specific serial number has completed its final assembly operation and passed the required quality inspection at a particular work center. That event can trigger a product-identification label at the exact point where it becomes operationally valid.
As discussed in MES label printing, the MES should communicate production events while the printing workflow manages templates, validation, printer routing and traceability.
MES provides execution context
The MES usually provides information such as:
- work orders and operations,
- production lines and work centers,
- machine and equipment identities,
- operators and shifts,
- lot and serial numbers,
- production quantities,
- quality status,
- and event timestamps.
This information is essential for labels connected to real-time production, quality control and traceability.
ERP responsibilities vs. MES responsibilities
The clearest way to understand the difference is to compare the business context owned by the ERP with the execution context owned by the MES.
| ERP responsibility | MES responsibility |
|---|---|
| Manage customer orders and business transactions | Manage production execution and shop-floor activities |
| Plan production and material availability | Monitor real-time production progress |
| Manage inventory and warehouse operations | Manage work centers, machines and operators |
| Provide customer and logistics information | Provide production and quality information |
| Trigger shipping and logistics labels | Trigger production and product-identification labels |
| Manage commercial master data | Manage manufacturing execution data |
| Record business transactions | Record production events and traceability |
| Provide business context | Provide execution context |
This comparison illustrates why choosing a single system for every label is usually the wrong question.
The better question is:
Which business event should trigger this label?
Once that question has been answered, selecting the appropriate source system becomes much simpler.
When should the ERP trigger label printing?
The ERP should trigger labels whenever the event originates from a commercial, logistical or administrative business process.
In these situations, the ERP is the authoritative source because it owns the information required to determine what should be printed.
Typical ERP-driven label scenarios include:
- customer shipment labels,
- SSCC logistics labels,
- warehouse and inventory labels,
- purchase-receipt labels,
- customer-specific compliance labels,
- export and delivery documentation,
- finished-goods inventory identification.
For example, an ERP may determine that a shipment for a particular customer requires a unique pallet label, additional compliance markings or customer-specific barcode formats. Those decisions are based on commercial information rather than production activities.
In these cases, the ERP should communicate the business event to the printing workflow instead of attempting to generate printer-specific output itself.
Typical ERP trigger
Customer shipment released for Delivery 84726. Generate the required logistics labels for the shipment.
The printing workflow can then determine which approved template should be used, which printer should receive the job and how the completed print should be recorded.
When should the MES trigger label printing?
The MES should trigger labels whenever the event originates from manufacturing execution.
Unlike the ERP, the MES knows what has actually happened on the production floor.
Typical MES-driven label scenarios include:
- product-identification labels,
- product serialization,
- quality-approved products,
- completed production operations,
- batch completion,
- container completion,
- pallet completion on the production line.
These labels depend on manufacturing events rather than commercial transactions.
For example, a product label should normally not be printed simply because a production order exists. It should be printed because the required production operation has actually been completed and approved.
Typical MES trigger
Production order 47118 completed final assembly and passed quality inspection. Print the approved product-identification label.
Again, the printing workflow remains responsible for validation, template selection, printer routing and complete traceability.
When should both systems trigger label printing?
Many manufacturing environments require both ERP and MES to trigger labels—but for different reasons.
This is often the most scalable architecture because each system communicates the business events it owns while the printing workflow provides a single, centralized printing service.
A typical production flow might look like this:
- The ERP creates the production order.
- The MES executes manufacturing.
- The MES triggers product-identification labels.
- The ERP later triggers shipping and logistics labels.
- Both systems receive relevant print status and traceability information from the centralized printing workflow.
Neither system needs to understand printer languages, template versions or printer routing. Those responsibilities remain centralized and consistent across the entire manufacturing environment.
Recommended architecture
The most maintainable architecture separates business systems from printing execution. ERP and MES both communicate trusted business events, while a centralized printing workflow decides how every label should be validated, generated, routed and tracked.
This architecture avoids duplicated business logic, simplifies future integrations and allows printers, templates and routing rules to evolve independently from ERP and MES implementations.
This model combines the strengths of both systems without forcing either of them to manage responsibilities outside its intended domain.
Practical manufacturing examples
Different labels originate from different business events.
| Label | Recommended trigger | Reason |
|---|---|---|
| Product label | MES | Triggered by completed production and quality approval. |
| Pallet label | MES or ERP | Depends on whether the pallet represents production completion or shipment preparation. |
| Shipping label | ERP | Triggered by logistics and customer-delivery processes. |
These examples demonstrate that the correct trigger depends on the business event—not on the system that happens to be easiest to integrate.
Common mistakes when choosing ERP or MES for label printing
Many labeling projects become unnecessarily complicated because organizations focus on selecting a single system instead of assigning responsibilities correctly.
The following architectural mistakes are among the most common.
1. Making the ERP responsible for every label
An ERP system is excellent at managing business transactions, but it usually lacks real-time visibility into production events.
If product labels depend on machine completion, quality approval or serialization, forcing the ERP to manage those events often introduces unnecessary integrations and delays.
2. Making the MES responsible for shipping labels
Manufacturing Execution Systems typically do not own customer deliveries, logistics planning or transportation processes.
Generating shipping labels directly from the MES frequently results in duplicated customer logic that already exists inside the ERP.
3. Embedding printing logic inside business systems
Printer selection, template management and printer-language generation should not be implemented inside ERP or MES applications.
Those responsibilities belong to the centralized printing workflow, where they can be maintained consistently for every production line and business process.
4. Maintaining duplicate label templates
Creating separate template libraries inside ERP, MES and printer software quickly becomes difficult to maintain.
A centralized template repository ensures that approved label designs are reused regardless of which business system initiated the print request.
5. Ignoring print traceability
Simply sending print jobs to industrial printers is rarely sufficient.
Modern manufacturing environments also require confirmation that labels were successfully generated, routed and printed so ERP and MES can maintain accurate operational records.
Decision matrix
The following matrix provides a practical guideline for deciding which system should normally trigger different types of labels.
| Business event | Recommended trigger |
|---|---|
| Production order released | ERP |
| Machine operation completed | MES |
| Quality inspection approved | MES |
| Product serialization | MES |
| Pallet completed in production | MES |
| Inventory receipt | ERP |
| Customer shipment released | ERP |
| Warehouse movement | ERP |
| Customer-specific logistics label | ERP |
Implementation checklist
When designing an industrial label-printing architecture, use the following checklist as a starting point.
- Define which business events belong to the ERP.
- Define which production events belong to the MES.
- Keep printer communication outside both systems.
- Use a centralized workflow engine for validation and routing.
- Maintain a single repository of approved label templates.
- Implement print status and traceability feedback.
- Avoid duplicating business rules across multiple applications.
- Allow ERP and MES to evolve independently from the printing platform.
In practice
Choosing between ERP and MES for label printing is rarely about selecting one system over the other.
Modern manufacturing environments rely on both systems because they represent different parts of the manufacturing lifecycle.
The ERP communicates business events. The MES communicates production events. A centralized printing workflow transforms those events into validated, approved and fully traceable labels.
This separation of responsibilities simplifies integrations, reduces maintenance effort and creates a scalable architecture that can support future production lines, printers and enterprise applications without redesigning the labeling process.
Related resources
- Manufacturing Label Printing
- Production Label Printing Software
- ERP Label Printing
- MES Label Printing
Ready to modernize your label-printing architecture?
Tagpresto Cloud helps manufacturers connect ERP, MES and other enterprise systems to a centralized industrial label-printing platform without embedding printer-specific logic inside business applications.
By separating business events from print execution, organizations can standardize templates, automate printer routing and improve traceability across the entire manufacturing process.
Frequently asked questions
Should ERP or MES print labels?
Neither system should be responsible for every label. Each should trigger labels for the business events it owns while a centralized printing workflow manages execution.
Can ERP and MES trigger the same printing platform?
Yes. This is considered the preferred architecture because both systems can submit trusted business events while sharing templates, printer routing and traceability.
Which system should manage product serialization?
In most manufacturing environments, serialization is closely connected to production execution and is therefore typically managed by the MES.
What if our company does not use an MES?
The ERP can still trigger many label-printing events. However, production-related events may require integrations with manufacturing equipment, operators or other shop-floor systems.
Why use a centralized printing workflow?
A centralized workflow keeps validation, template management, printer routing and traceability outside ERP and MES, making the overall solution easier to maintain, expand and standardize.
