Crossing system boundaries
Magento owns the order and shipment context. The logistics provider expects correctly structured shipment information and valid API communication.
// Case study 01 · Official Planzer integration / Magento 2
The work begins after checkout.
A shipment is more than a button in the shop. Planzer Connect is the official Magento 2 integration for Planzer logistics, bringing shipment creation, API communication and label processing into one operational workflow.
Discuss a similar integrationMagento 2Planzer APISwiss logisticsVermonta Studio
01 / Context
Two systems. One process.
The moment a customer places an order, a different part of commerce begins. Someone has to prepare a shipment, create the right label and pass reliable information to the logistics provider.
Without a direct connection, shipment data may need to be repeated across systems. A good integration does not merely transfer data. It fits into the workflow people already know.
Planzer is a family-owned transport and logistics company from Switzerland, founded in 1936. Its services include parcel delivery, freight transport and warehousing in Switzerland and beyond. Planzer Connect is the official Magento 2 integration for Planzer logistics, developed by Vermonta Studio. This case study looks at the engineering decisions behind that connection.
02 / The challenge
The difficult parts are in the details.
Order data, fulfilment actions and carrier requirements do not always line up neatly. The integration has to handle practical exceptions without disrupting the store operator's work.
Respecting exceptions
Not every order line or shipping method should be sent to the carrier. Partial shipments make that distinction particularly important.
Keeping operations simple
The integration must remain manageable across store views, environments and day-to-day shipping tasks, without unnecessary manual work.
03 / The approach
Make the connection part of Magento.
The design centres on the shipment the operator already creates. Planzer communication belongs within that workflow, rather than in a second, separate interface.
STEP 01
Magento order & shipment
The existing checkout remains untouched. Shipment creation provides the context for the integration.
STEP 02
API request & label
Relevant shipment details are sent through the Planzer connection and the shipping label is generated in the Magento workflow.
STEP 03
Fulfilment continues
Warehouse or back office staff work with the label and shipment information, without repeating the data entry in another portal.
04 / Engineering decisions
Small decisions. Lasting consequences.
Behind the apparently simple shipment action are deliberate choices about security, configuration and the less obvious cases.
Test and live environments
Separate API environments support careful setup. The configured authentication token is encrypted in Magento's database.
Precise exclusion rules
Shipping methods and products can be excluded. With partial shipments, the logic considers the items in that shipment rather than blindly applying rules to the entire order.
Bulk labels and options
Mass printing can combine selected shipment labels into one PDF. Extended shipping options can be selected where supported by the carrier.
The real world is the benchmark.
The goal is not a complicated dashboard. It is a reliable connection between order processing and dispatch, designed for the people who run the business.
05 / What this work demonstrates
Integration is a form of craftsmanship.
This project demonstrates a practical approach to commerce engineering: understand the operational context, make external systems work together, and address exceptions before they become everyday problems.
The result is a Magento extension designed to bring Planzer shipment processing into existing administrative routines. It includes label generation, flexible configuration, multilingual store-view settings and shipping controls.
Let's make the systems work together.
Logistics, ERP, shipping or another specialist API: the best integration begins with understanding your existing process.
Discuss your requirementsPlanzer is a trademark of its respective owner. This article describes the independently developed Magento integration by Vermonta Studio.