Custom MKG integration
Appfront builds integrations with MKG, the ERP package for the manufacturing industry. MKG has an API that lets other software exchange data in real time. We use it to connect MKG to your own systems: orders from your webshop or customer portal, parts and drawings from CAD, data from machines and the shop floor back into production orders, and figures into your own dashboard.
What is an MKG integration?
MKG is an ERP package for the manufacturing industry, widely used by metalworking companies, suppliers and machine builders. It covers costing, sales, purchasing, production and planning, among other things. MKG has an API that lets other software request and supply data in a question-and-answer model, without passing files back and forth. That makes integrations possible that work in real time.
Without an integration, an order from the webshop or customer portal arrives by email and is retyped. Parts exist in CAD and again in MKG, with the risk that the revision differs. The shop floor reports hours and quantities on paper or in a separate system, and post-calculation falls behind. And management wants to see how production is going, which someone pulls out of exports.
We build custom because the integration has to fit your factory: which webshop or portal you use, how drawings and parts are managed, which machines can supply data, and which figures you want to see. Which data the MKG API offers for your setup we will review in the first step, together with you and, where needed, with MKG.
Orders without retyping
Orders from your webshop or customer portal as sales orders in MKG, with the correct parts and customer details.
CAD and the shop floor
Parts and drawings from CAD into MKG, and hours and quantities from the shop floor back to the production orders.
Production in your dashboard
Orders, lead times and capacity utilisation from MKG into your own dashboard.
How we build your MKG integration
We start with your systems: which ones you use alongside MKG, where orders and parts come from, and where retyping happens today.
Your webshop, portal, CAD, machines and dashboard, and which data needs to flow in which direction.
Connecting the MKG API to your systems, for orders, parts, production and stock.
Testing with real orders and production orders, error monitoring, and a log per message.
Phased go-live, and maintenance when MKG or your systems are updated.
What an MKG integration actually does
The components below come up in almost every MKG integration. Which ones you need depends on your factory.
Sales orders
Orders from webshop or portal as sales orders in MKG.
Parts and CAD
Parts and drawings with revision from CAD or PDM.
Production orders
Production orders and operations to workstations and machines.
Shop floor reporting
Hours and quantities from the shop floor back to MKG.
Stock and lead time
Stock levels and lead times to customers in your portal.
Dashboard
Orders, lead times and capacity utilisation in your dashboard.
Who we build MKG integrations for
The integration is intended for manufacturers who use MKG alongside their own systems.
Metalworking companies
Many orders with their own drawings. Parts and CAD are the core.
Subcontractors
Orders from regular customers via a portal. The order flow matters most.
Machine builders
Projects with many components. Shop floor reporting is what is needed.
Companies with a webshop
Standard products sold online. Orders without retyping are the core.
Technology and integrations
This page is about integrations with MKG. For the manufacturing industry in general there is our page on software for the manufacturing industry, for the shop floor our page on a MES system, and for metalworking companies our page on software for metalworking. You can read about our way of working under custom software development.
Why Appfront for your MKG integration?
An order that gets retyped can end up with the wrong revision, and you only discover the error on the shop floor. That is what we build around: orders and parts from a single source, shop floor reporting, and figures without exports.
No duplicate entry
Orders and parts are entered once.
Correct revision
Drawing and part come from the same source.
Post-calculation on time
Hours and quantities are in MKG the same day.
Security and privacy in an MKG integration
The integration processes customer data, orders, drawings and prices, along with confidential business information. API access credentials are stored encrypted and used only by the integration, with only the permissions it needs.
The integration runs in a European data centre or in your own environment, with encrypted storage, daily back-ups and a log of every message.
Frequently asked questions about an MKG integration
Questions manufacturing companies ask before getting started.
MKG is an ERP package for the manufacturing industry, covering costing, sales, purchasing, production and planning, among other things. It is widely used by metalworking companies, suppliers and machine builders. The package runs in the cloud or on your own servers, and in addition to standard functions it leaves room for integrations with other software.
Yes. The MKG API allows other software to retrieve and supply data in real time, without sending files back and forth. In the first step we look at which data is available for your setup and what MKG requires in advance.
Yes. An order from the webshop or customer portal becomes a sales order in MKG, with the correct items, customer and delivery. Orders that cannot be processed automatically are held for review, with the reason stated.
Yes. Items with their drawing number and revision come from CAD or PDM into MKG, so production planning and the shop floor work from the same revision as the designer. A new revision is passed on, and production orders still based on the old one are flagged.
Yes, through a dedicated app, a terminal or machine data. Hours, quantities and scrap are recorded against the production order, so that the actual costing is correct the same day.
The integration reports the problem and records what went wrong. The message is retried or set aside for review. An overview shows which messages have been processed, which are waiting and which need attention.
For manufacturers with their own webshop, portal, CAD environment, machines or dashboard alongside MKG, where data is currently re-typed. For packages that already have a standard integration, that is often sufficient.
MKG and your factory working from the same data?
Tell us which systems you use alongside MKG, where orders and items come from, and where data is currently re-typed. We'll show you what the integration would look like.