What does this integration do?
The MNG Kargo integration opens a shipment record the moment an order is confirmed and writes the tracking information onto the Shopify order. Shipping charge rules and region-based pricing are managed on the store side. Because the brand has moved under DHL eCommerce Türkiye, the integration is built according to which API version your account is registered on.
The data it synchronises
Shipment record and barcode
Tracking number transfer
Status updates
Region-based shipping rules
Bulk operation support
Return shipments
How the data flows
01
Account and API version are identified
Because the brand moved under DHL eCommerce, accounts can be registered on different API versions. We start the setup by confirming which version yours is on.
02
The order becomes a shipment
A shipment record is opened for the confirmed order; recipient, address and volumetric weight are written into the carrier's system.
03
The barcode is generated
Labels are produced individually or in bulk, and placed into the warehouse flow according to daily volume.
04
Tracking information is written to the order
The tracking number is written onto the Shopify order and the customer notification is triggered.
05
Status and returns flow
Delivery statuses are read back; on return shipments, who generates the label follows the flow you have defined.
What we watch for in this integration
Which API version your account is on directly changes the scope of the setup; the old and new versions do not expose the same fields under the same names
If you use region-based pricing, the shipping rules on the Shopify side are rewritten to match that breakdown
If volumetric weight is not fed from product data, there will be a constant gap between shipment cost and the shipping charge collected
When your corporate agreement terms change, the pricing setup on the integration side has to be updated too
The setup process
01
Data and permission analysis
We decide which data flows in which direction, which system is the master, and what API permissions are required.
02
Mapping table
Product, variant, category, warehouse and account fields are mapped between the two systems, one by one.
03
Development and testing
The integration is built on a development store; order, return and error scenarios are tested with real data.
04
Going live
It is released through a controlled switchover, watched closely for the first few days, with the error queue monitored.
05
Monitoring and maintenance
Logging, error alerting and API version updates continue under the maintenance retainer.
What we need from you before we start
MNG / DHL eCommerce customer number and API credentials
Which API version the account is registered on
Your negotiated price list and region breakdown
The state of product weight and dimension data