Orders and items without retyping Machines and shop floor linked to the ERP Figures from MKG in your dashboard

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, items and drawings from CAD, data from machines and the shop floor back to the production orders, and figures to 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. Among other things, it handles costing, sales, purchasing, production and planning. MKG has an API that lets other software request and supply data in a request-and-response model, without sending 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. Items 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 lags behind. And management wants to see how production is going, which someone has to pull together from exports.

We build custom because the integration has to fit your factory: which webshop or portal you use, how drawings and items are managed, which machines can supply data, and which figures you want to see. We look at which data the MKG API offers for your setup in the first step, together with you and, where needed, with MKG.

Orders without retyping

Orders from your webshop or customer portal as a sales order in MKG, with the right items and customer details.

CAD and shop floor

Items and drawings from CAD to MKG, and hours and quantities from the shop floor back to the production orders.

Production in your dashboard

Orders, lead time and utilisation from MKG to your own dashboard.

How we build your MKG integration

We start with your systems: which ones you use alongside MKG, where orders and items come from, and where data is currently retyped.

1
Mapping systems and flows

Your webshop, portal, CAD, machines and dashboard, and which data needs to flow in which direction.

2
Building the integration

The MKG API connected to your systems, for orders, items, production and stock.

3
Testing and monitoring

Testing with real orders and production orders, error monitoring, and a log for every message.

4
Go-live and maintenance

Step-by-step go-live, and maintenance when MKG or your systems are updated.

What an MKG integration actually does

The components below appear in almost every MKG integration. Which ones you need depends on your factory.

Sales orders

Orders from your web shop or portal as sales orders in MKG.

Items and CAD

Items 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 for customers in your portal.

Dashboard

Orders, lead time and capacity utilisation in your dashboard.

Who we build an MKG integration for

The integration is designed for manufacturers that use MKG alongside their own systems.

Metal companies

Many orders with their own drawings. Items and CAD are the core.

Subcontractors

Orders from regular customers via a portal. The order flow matters most.

Machine builders

Projects with many components. What you need is reporting back from the shop floor.

Companies with a web shop

Standard products sold online. Orders without retyping are the core.

Technology and integrations

This page is about MKG integrations. For manufacturing in general, see our page on software for the manufacturing industry; for the shop floor, our page on an MES system; and for metal companies, our page on software for metalworking. You can read about our approach on building custom software.

MKG API Sales orders Items and revisions CAD and PDM Production orders Shop floor reporting Stock Web shop and portal Dashboard Log per message

Why Appfront for your MKG integration?

An order that gets retyped can end up with the wrong revision, and you only notice that mistake on the shop floor. That's what we build on: orders and items from a single source, reporting back from the shop floor, and figures without exports.

No double entry

Orders and items are entered once.

The right revision

Drawing and item come from the same source.

Post-calculation on time

Hours and quantities are in MKG the same day.

Security and privacy with an MKG integration

The integration processes customer, order, drawing and price data, which is confidential business information. API 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 backups and a log of every message.

Frequently asked questions about an MKG integration

Questions manufacturers ask before getting started.

MKG is an ERP package for the manufacturing industry, covering estimating, sales, purchasing, production and planning, among other things. It is widely used by metal companies, suppliers and machine builders. The package runs in the cloud or on your own servers and, alongside its standard functions, offers room for integrations with other software.

Yes. With the MKG API, other software can 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 web shop or customer portal becomes a sales order in MKG, with the right items, customer and delivery. Orders that cannot be processed automatically are held for review, with the reason.

Yes. Items with drawing number and revision come from CAD or PDM into MKG, so that work preparation and the shop floor work with the same revision as the draughtsperson. A new revision is passed on, and production orders still on the old one stand out.

Yes, via a custom app, a terminal or machine data. Hours, quantities and rejects are booked to the production order, so the post-calculation is correct the same day.

The integration reports the error and records what went wrong. The message is retried or queued for review. An overview shows which messages have been processed, which are waiting and which need attention.

For manufacturers with their own web shop, portal, CAD environment, machines or dashboard alongside MKG, where data is currently retyped. If a standard integration already exists for your package, that is often enough.

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 retyped. We'll show you what the integration would look like.

Edit content