Carrier Integration in Turkey: Aras, Yurtiçi, MNG, PTT

Carrier integration means an order from a marketplace or your own store flows into your ERP and fulfilment process with the carrier already assigned, and the tracking number is reported back to the marketplace automatically. Aras, Yurtiçi, MNG and PTT Kargo are the four domestic carriers a multi-channel seller in Turkey works with most often. If you ship into Turkey from a local warehouse or through a Turkish partner, or you sell on Trendyol and Hepsiburada from a Turkish entity, these are the names on your labels. This article explains how to keep fulfilment in one routine when every channel has a different carrier rule.

Marketplace-contracted carrier or your own contract?

Most Turkish marketplaces offer sellers their own contracted carriers; some allow the seller's own contract for certain product groups or volume levels. The two models differ in more than price:

• Marketplace-contracted: the fee is set by the marketplace agreement and deducted from your payout; the label is usually generated from the marketplace panel or through the integration. Late dispatch is a performance metric the marketplace measures.
• Your own contract: you negotiate the rate, receive the invoice from the carrier and print the label from your own system. More flexibility, and the responsibility moves to you.

Which model applies on which channel, and the fees, are in each marketplace's current seller agreement; compare the general picture here with your own contract. What matters is that the carrier rule per channel lives in the integration: if Trendyol orders go with one carrier, own-store orders with another and heavy items with a third, that rule should be applied at order time, not remembered in the warehouse.

Aras, Yurtiçi, MNG and PTT: how to choose

All four deliver nationwide in Turkey; the differences show up in network density, delivery times, volumetric weight rules, branch and pickup-point options and integration maturity. Ask these questions when choosing:

• What are delivery times and failed-delivery rates in the provinces where you sell most?
• Which volumetric weight rule applies, and what does it produce for your actual packages?
• What is the same-day pickup cut-off; do orders after it slip to the next day?
• How is branch or pickup-point delivery priced against home delivery?
• What are the fees and the process for return shipments?
• Do tracking numbers and delivery confirmations reach your systems automatically?

We give no figures here; rates, transit times and volumetric rules change by carrier and by period, and the current terms are in the carrier's contract. Many sellers run two carriers at once, one for light, fast items and one for heavy or bulky goods. If the integration can define that split by channel and product attribute, two carriers are no harder than one.

Carrier choice is not a one-time decision. Review it yearly as your product mix changes and your regional balance shifts.

From order to delivery

A well-built carrier flow completes in five steps:

1. The order lands. A marketplace or store order reaches the integration with channel, product and address recorded.
2. A carrier is assigned. The rule defined by channel, item weight and delivery region picks the carrier.
3. The order is written to the ERP. With customer, line items, carrier and payment details. Invoicing and dispatch continue in your own ERP routine.
4. Label and tracking number are created. Via the marketplace for contracted carriers, via your own system for your own contract.
5. The tracking number is reported to the marketplace. The buyer sees the shipment and the marketplace counts the order as dispatched.

If any of the five is done by hand, it is repeated a hundred times on a hundred-order day. In Bulutegra the order is written to the ERP automatically with the carrier attached; invoicing and dispatch stay in the business's own routine and the integration carries the data. How the multi-channel order list works is covered in multi-channel order management.

The ERP side: invoicing and dispatch stay yours

Carrier integration does not replace your ERP's dispatch process; it feeds it. With Nebim V3, Logo, Mikro or SAP, when the order lands with the carrier attached, the pick list, delivery note and invoice are produced in your existing flow. The benefit is that accounting can track cost per carrier and, when a return comes in, the record shows which carrier shipped what. ERP details are in Nebim V3 marketplace integration and Logo, Mikro and SAP ERP integration.

Role separation matters in the warehouse: a user in the Warehouse role sees orders and dispatch but not prices or payouts. That keeps both errors and permissions simple.

Common problems

• Volumetric surprises: with no weight and dimensions on the product card, the carrier weighs the parcel and the invoice comes in higher than expected. Enter dimensions on the product card once.
• Missed cut-off: orders arriving after pickup time slip to the next day and the marketplace counts a delay. Make the cut-off visible in the order list.
• A silent channel: when a marketplace connection stops delivering data, orders pile up and the dispatch window closes. With channel monitoring continuously, silence raises an alert and a notification on your phone.
• Wrong carrier assignment: without a channel rule, the warehouse picks a carrier every time; errors follow.
• Return shipping: which carrier the return travels with, and who pays, should be defined in advance. See marketplace returns and the customer return portal.

Carrier setup checklist

1. Decide per channel whether the marketplace-contracted carrier or your own contract applies.
2. Make sure weight and package dimensions are on every product card.
3. Write the carrier assignment rule by channel, weight and region.
4. Ensure the carrier field in the ERP is filled with the order record; invoice and delivery note come out in your existing routine.
5. Manually verify on the first orders that the tracking number returns to the marketplace.
6. Note cut-off times per channel.
7. Define the return shipping rule.

How it works with Bulutegra

In Bulutegra, orders appear in one list separated by channel tabs and are written to the ERP automatically with customer, line items, carrier and payment details. Invoicing and dispatch stay in your own ERP routine. Channel monitoring runs continuously and a silent channel raises an alert. The Warehouse role lets the dispatch team see only their own work. For the full setup see integration setup in 4 steps, and for how the platform is built see Why Bulutegra?.

To see the carrier flow with your own channels, request a demo.