Can work proceeds with more than one carrier at the same time?

Yes, multi-carrier scenarios can be built within a project. However, which carriers get integrated is decided together during scope clarification; by default not every carrier is included, only the ones that fit the stated needs. Adding a new carrier later is evaluated as additional scope.

How is the desi (volumetric weight) calculation automated?

Once product or package dimensions are defined in the system, volumetric weight is calculated automatically and sent to the carrier with accurate data. This reduces the risk of mismatch between the label and the actual package, and simplifies any dispute that might otherwise arise with the carrier later.

How does the tracking number reach the customer?

The tracking number obtained from the carrier is synced to the business order source (e-commerce panel, ERP or custom panel). Customer notification is sent through the existing communication channels, with the content and frequency the company defines; Ayyıldızsoft builds the data flow, not the notification channel itself.

Are return processes included in scope?

Return / reverse logistics scenarios are included if requested within the project. Scenarios left out of scope are stated in writing during clarification, so expectations stay aligned later on, and Ayyıldızsoft can always add this scenario in a later phase if needed.

Does it work with our current ERP or e-commerce setup?

The integration is designed around the business order source, so it works with the business e-commerce site, marketplace panel or ERP system. How data flows between different systems is clarified at project kickoff, and each system's own constraints are planned around accordingly.

Is support available after setup?

After go-live, the business operations team gets a short training and support is provided for topics within scope. New needs that arise outside that scope are evaluated as a separate project or additional scope, following the same transparent process.

Cargo Integration

Cargo Integrations connect the orders coming from the business e-commerce site or ERP system to carrier companies, bringing label creation, volumetric weight (desi) calculation, tracking number sync and status updates into one flow. Scope is clarified together which carrier gets integrated, then build a setup that reduces manual work for the business operations team.

Addressed need

As order volume grows, running cargo processes by hand stops being sustainable. Labels get typed one by one, volumetric weight calculations vary per package, tracking numbers get entered manually, and "where is my order" questions cannot be answered instantly. Return requests make it hard to match the right carrier record to the right order, and the mess grows further for businesses selling through multiple channels at once.

This does not only slow down the operations team's daily work; shipping delays and incorrect tracking information also weaken the customer experience. During seasonal peaks (campaign periods, pre-holiday rushes) a manual process becomes even more fragile; a single mistake in printing a label can escalate into a cancelled order or a shipment sent to the wrong address. Cargo Integrations simplify this flow by building an automated bridge between the business order source and the carrier, reducing error-prone manual steps.

Delivered scope

Ayyıldızsoft builds an end-to-end integration from the company’s order source (e-commerce panel, ERP or custom software) to the carrier the company selects. Ownership of the integration and panel access stay with the company; Ayyıldızsoft builds, tests and rolls out the flow for the company team to use. The delivered scope can be summarized as follows:

Automatic label and barcode generation after order confirmation
Volumetric weight (desi) calculation and accurate shipping cost data reflected in the system
Automatic tracking number generation synced back to the company’s order source and the relevant screens
Real-time reflection of carrier status updates (in transit, out for delivery, delivered)
Correct matching of return / reverse logistics records to the original order
A simple, clear view for operations staff to use day to day

Who is it for?

This integration fits teams with regular daily or weekly order volume who sell through multiple channels and are tired of tracking cargo manually. It is especially relevant for businesses selling through marketplaces and their own e-commerce site together, where label and tracking work grows along with shipment count. Teams shipping from multiple warehouses or branches, or who want to shorten the time between order confirmation and label printing, also benefit.

If customer support answers "where is my order" questions one by one every day, or if finding the right order during a return request means opening several screens at once, that is a typical sign the integration would help.

Who is it not for?

Businesses limited to a few orders a month, those already running cargo smoothly from a single panel, or those who have not yet reached the order volume that justifies an integration may not need this as a priority. In that case, a manual process can still be practical, and Ayyıldızsoft recommends revisiting the topic once the business order volume grows. Similarly, if the business order source has not been settled yet or keeps changing, stabilizing that first should come before a cargo integration.

Scope

At project kickoff kickoff jointly clarifies which carriers, which order sources and which scenarios (shipment, return, multi-package) are in scope. This clarification prevents unexpected "can Ayyıldızsoft also add this" requests later in the project; both sides know from the start what was agreed. Scope usually takes shape around these points:

Carrier(s) to integrate: selected from Yurtiçi Kargo, Aras Kargo, MNG Kargo, Sürat Kargo and PTT Kargo based on the project
Order source: e-commerce site, marketplace panel, ERP or custom software
Design of the label, barcode and tracking number flow
Which screens show status updates and at what frequency
Whether return / reverse logistics scenarios are in scope

The carriers listed above are an example pool; not all of them are integrated by default on every project. Which carriers are included is decided together during scope clarification and confirmed in writing.

Points of attention

Because a cargo integration depends on order data flowing correctly, close attention is paid to a few points during setup:

Order, address and product data reaching the carrier without errors
Visible warnings instead of a silent stop when data is missing or malformed
Tracking and status data staying consistent across different screens instead of drifting apart
The integration continuing to work independently of the carrier's own panel updates

Integrations

A cargo integration rarely works alone; it is usually built together with the order source and sometimes with production or inventory processes. The areas Ayyıldızsoft most often work on alongside it are:

Connecting orders coming from E-Commerce Website to the automated cargo flow
Keeping inventory, order and shipping data in one shared flow with ERP Systems
Making completed production batches shipment-ready with Production Tracking Software

Scope can extend beyond these three areas too; if the business needs an integration with a virtual POS or a custom panel, Ayyıldızsoft evaluates that within the project as well.

Implementation steps

Analyzing the current order source and cargo process
Jointly clarifying which carrier(s) and scenarios to integrate
Setting up the label, desi calculation and tracking number flow
End-to-end verification with test orders
Go-live and a short training for the operations team
Post-launch support and scope expansion if needed

How long these steps take depends on how many carriers and which scenarios are in scope; a single carrier with a standard shipping flow can move quickly, while adding multi-carrier and return scenarios can stretch the testing phase a bit further. Decisions are shared a concrete output after every step: a scope document once analysis is clarified, a test report after setup, and a short usage note for the business operations team after go-live. This way the business always know where the process stands.

A cargo integration can start as part of the business e-commerce or ERP project, or as a standalone project. Reaching out via the contact page is enough to clarify what fits the stated needs; Ayyıldızsoft listens to the business current order source and cargo process, then prepare a scope proposal tailored to the business.

Cargo barcode tests in Konya

In cargo integration, order numbers are matched to barcodes before live labels. Tests run at the Konya office or the business warehouse by appointment.

Which carriers’ APIs the business use is chosen with the business order panel. Ayyıldızsoft does not open district branches.