ERP, the order book
Orders, purchasing, inventory, costing and the ledger. Usually the oldest software here.
An ERP plans the work. An MES records what happened to it. We build the software and the data model in between, specified against the standards your buyer names. Our three named builds are in apparel manufacturing, linked below.
Tell us what you are building
Manufacturing software development means building the systems a plant runs on: ERP for the order book, MES for the shop floor, and the integration between them. The standards decide the shape. ISA-95 sets the model, OPC UA and MQTT Sparkplug move the machine data, and your buyer's audit decides what you must trace.
Our work
Read this before the rest of the page. None of the three is a shop floor rollout, a machine connection, an MES or a SCADA project, so none of it is plant floor experience. No outcome metric is published, because none was approved.
System types
Most plants run several, bought at different times from different vendors. The integration is the project.
Orders, purchasing, inventory, costing and the ledger. Usually the oldest software here.
Results tied to a lot, batch or serial, so a recall resolves to a list.
Packaged options
Most of it is bought. We do not resell or implement any of these; we build the custom parts and the integration.
An ERP suite with production planning and its own shop floor modules. If it is here, ask what is missing.
One cloud system carrying finance and the plant, so ask how far your process must bend.
A modular ERP and CRM family. Fewer modules leaves integration work you pay for.
Both are sold as manufacturer ERP, not general suites. The industry edition is the pitch: check what it assumes.
Failure modes
Six places an ERP to MES project goes wrong, most of them data model problems, not connector problems.
An ERP issues a works order, an MES reports operations, scrap and labour. Agree which owns the quantity first.
Metres against pieces against bundles against cartons. Two systems holding one stock in different units disagree forever.
A terminal loses the network and keeps recording. Queue locally, send with idempotency keys, handle duplicates.
Item, bill of material, routing and work centre each need one owner. That is what IEC 62264-1 settles.
An ERP thinks in shifts, a machine in seconds. Fix the aggregation level before sizing the database.
Older equipment speaks Modbus with no security model. TallyPrime is XML over ODBC on a desktop.
The decision
Three honest answers, and one saying hire somebody else.
Your process is near standard and you can change how you work. Build only what refuses to fit.
Package for finance, a build for the rest, one owner per data object. Most estates end up here.
If you want a packaged ERP or MES selected and rolled out, you want an implementation partner.
Our specialism
The same problems, with a data model no general ERP holds. The part our case studies cover.
Yield, marker, shrinkage, labour efficiency and rework, each with a named owner. One combined variance gives no action.
Cut order planning from the size curve, with lay and marker tied to it, so fabric costs per size.
Bundle tickets that survive every operation, with rejects captured at the operation.
Expected return computed from the cut order bill of materials at issue, plus ageing on goods outside.
Standards
Your buyer's specification will name these. Every row was read at the issuing body's own record, on webstore.iec.ch, iso.org, docs.oasis-open.org, sparkplug.eclipse.org, eur-lex.europa.eu or dhs.gov, and each row carries the date it was last read.
| Instrument | What it forces the software to do | When |
|---|---|---|
| IEC 62264-1, the IEC counterpart to ANSI/ISA-95 | Defines the enterprise model, the terminology and the information exchange between manufacturing control functions and other enterprise functions, at the interface between levels 3 and 4 of the Purdue Reference Model. It settles which system owns which master data. | IEC 62264-1:2013, Edition 2.0, published 22 May 2013 by IEC TC 65/SC 65E, replacing the 2003 first edition. Stability date 2028. Read 17 November 2026. |
| IEC 62541, OPC Unified Architecture | Expose and consume plant data through a service oriented, platform independent information model, with X.509 certificate authentication, session encryption and message signing. The information model is the deliverable, not the wire format. | Maintained by IEC TC 65/SC 65E. Part 1 was IEC TR 62541-1:2020, Edition 3, and the IEC record states it is replaced by IEC 62541-1:2025. Read 13 November 2026. |
| MQTT 5.0, with Eclipse Sparkplug 3.0 on top | MQTT is the publish-subscribe transport, used on the floor because it survives an intermittent link where request-response does not. Sparkplug adds the topic and payload convention that lets sources and subscribers interoperate without a connector per device. | MQTT 5.0 became an OASIS Standard on 7 March 2019, and OASIS notes v3.1.1 is also ISO/IEC 20922:2016. Sparkplug 3.0 is current from the Eclipse Sparkplug Working Group, which publishes no release date for it. Read 17 November 2026. |
| ISO 13381-1, prognostics | Requirements for developing and applying prognosis processes, so you can work out which data and behaviours accurate prognosis needs. It is the specification behind the claim that predictive maintenance works. | ISO 13381-1:2025, Edition 3, published September 2025 by ISO as Condition monitoring and diagnostics of machine systems, Prognostics, Part 1. Read 13 November 2026. |
| IEC 62443-2-1, industrial security | Specifies asset owner security program policy and procedure requirements for an industrial automation and control system in operation, which turns a plant security conversation into documented controls. | IEC 62443-2-1:2024, Edition 2.0, International Standard, 189 pages, published 7 August 2024 by IEC TC 65. Stability date 2026. Read 17 November 2026. |
| Regulation (EU) 2024/1781, the ESPR | Introduces the digital product passport. Article 13(5) creates a unique registration identifier, and Article 15 requires whoever releases a covered product for free circulation to give it to customs, checked against a registry through EU CSW-CERTEX. Supplier, lot and certificate identity become first class fields on stock. | Done at Brussels on 13 June 2024, in force twenty days after publication in the Official Journal. The customs provisions apply only once the registry and the interconnection are operational, so no fixed customs date exists to quote. Read 17 November 2026. |
| The UFLPA Entity List, US Homeland Security | Screening it needs supplier identity held deep enough to reach the tier that made the input: a data model decision, not a report added later. Garment manufacturers are named on the list. | Published by the US Department of Homeland Security under Section 2(d)(2)(B)(i), with additions announced by the FLETF Chair. Of the 210 effective dates on the list we read on 14 November 2026, the earliest is 21 June 2022 and the latest is 29 October 2026, with 52 of them effective during 2026. This list grows, so screen against it on a schedule rather than once. |
We hold none of these as a certification. Not IEC 62443, not ISO/IEC 27001, not SOC 2, and we have never connected a PLC or deployed an MES. We read your buyer's specification, build what it demands, and hand you the evidence pack. Where finished goods go next is a logistics and distribution problem.
Transparency
None of the three top ranked pages on this keyword publishes an hour figure, checked 14 November 2026. Here are the drivers and the hours for the apparel scope we have delivered. A plant floor or MES scope is a different build with no number here.
Worked example
1,400 hours
Seven modules, each inside its range
Typical timeline
12 to 20 weeks
To a slice the floor uses, not one passing UAT
Realistic band
1,000 to 1,900
Hours, across the scopes we see
| Driver | Hours |
|---|---|
| Whether the three level model already existsRetrofitting three levels into a system built on one item master means re-costing history, not adding a column. | Highest impact |
| Number of job work stages and vendors | High |
| Whether the floor is tracked at bundle level | High |
| Fabric complexity, dyelot, shade and remnants | High |
| Integration count, and whether Tally is one | Medium |
| Export document formats per buyer | Medium |
| Historic data migration and unit consistency | Variable |
| Module | Hours |
|---|---|
| Style, colourway and variant model | 120 to 260 |
| Costing, BOM and the five variances | 220 to 460 |
| Cut order, lay, marker and bundle identity | 220 to 460 |
| Job work challans and reconciliation | 200 to 420 |
| Fabric store, dyelot, shade and remnants | 160 to 340 |
| Valuation, GST and export documents | 180 to 400 |
| Reporting, admin and integrations | 160 to 360 |
Delivery
Four phases, named by the artifact each produces.
Phase 01
Every unit the business uses, metres against pieces against bundles, and the level each system speaks at.
Phase 02
The cost sheet structure, five variance definitions with owners, consumption per size and the valuation method, agreed before any code.
Phase 03
One real order carried from cost sheet through marker, bundle and job work to valuation, beside the live process.
Phase 04
Runbooks, the valuation method and its edge cases written down, source and credentials in your accounts.
Six categories: ERP for the order book, MES for the shop floor record, WMS for material movement, PLM for the product record, quality and traceability, and maintenance with condition monitoring. Most is bought: SAP S/4HANA, Oracle NetSuite, Microsoft Dynamics 365, Epicor Kinetic, Infor CloudSuite Industrial. What gets built is the integration.
An ERP plans and an MES records. The ERP holds the order, the cost and the ledger, and issues a works order. The MES holds what was made, on which line, by whom, with how much scrap. Confuse them and two systems both own the production quantity, which is the commonest failure here.
IEC 62264-1, the IEC counterpart to ANSI/ISA-95. Edition 2.0 was published on 22 May 2013 by IEC TC 65/SC 65E, replacing the 2003 first edition. It defines the enterprise model, the terminology and the exchange between manufacturing control functions and other enterprise functions, at the interface between levels 3 and 4 of the Purdue Reference Model, so it settles which system owns which master data.
They solve different problems. IEC 62541, OPC UA, gives an information model with certificate based authentication and message signing, so a consumer knows what a value means. MQTT 5.0, an OASIS Standard since 7 March 2019, is transport that survives an intermittent link, and Eclipse Sparkplug 3.0 adds the convention MQTT lacks. Many plants run OPC UA inside, MQTT with Sparkplug outbound.
Configure a package if your process is close to standard and you can change how you work. Build if your process is the product, or if no package holds your data model, which is the apparel case. Most estates are both: package for finance, a build for the rest, one owning system per object.
Regulation (EU) 2024/1781, the ESPR, done at Brussels on 13 June 2024, introduces it. Article 13(5) creates a unique registration identifier, and Article 15 requires whoever releases a covered product for free circulation to give it to customs, checked against a registry through EU CSW-CERTEX. In software that means supplier, lot and certificate identity as first class fields on stock. Customs timing follows the registry going live, so no fixed date can be quoted.
Twelve to twenty weeks to a slice the floor actually uses, which is not the same milestone as passing user acceptance. The worked example above is 1,400 hours across seven modules, and real scopes land between 1,000 and 1,900.
Three steps, each with a time.
Bring a works order, a cost sheet and the last reconciliation you argued about.
At no charge. One page on the level your systems speak at, where units stop agreeing, and an hour band.
Mostly at the line. Output is the unit and level inventory, the costing specification and a costed plan.
Two to three weeks on the floor produces the unit and level inventory, the costing specification and a costed plan.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
The stack behind both garment builds
Where the item model lives
Sensor and gateway work
Finished goods leaving the plant
Where finished goods get sold
What a line costs
What an MES does that an ERP cannot
Build or buy, with both numbers
Why generic ERP misfits apparel
ERP and MES integration, and the apparel detail this page summarises.