Delivery Service Integration for E-commerce: How It Actually Works

In the modern world of e-commerce, integrating with delivery services is not just a convenience, but a critical element for successful operational activities. This process involves connecting your trading platform, CRM, or ERP system to the application programming interface (API) of logistics operators. Such a connection allows for the automation of numerous routine tasks, from calculating costs and selecting branches to creating waybills (TTN) and tracking package statuses. As a result, your online store can operate more efficiently, minimizing manual data entry and reducing the likelihood of errors.

For the Ukrainian e-commerce market, the main integration partners are Nova Poshta, Ukrposhta, and Meest. If your business targets the international market, it's essential to consider connecting with global giants like DHL, UPS, or FedEx. In this material, ShockWave Trade experts will thoroughly analyze the principles of integration, optimal connection methods, and key aspects to consider before implementation.

Key Advantages of Logistics Automation

Delivery service integration transforms the operational processes of an online store, providing a number of significant benefits:

• Optimized Order Process: Customers can choose a convenient delivery method (courier, branch, parcel locker) directly on the website.
• Accurate Cost Calculation: Delivery costs and estimated times are automatically calculated based on order parameters (weight, dimensions, destination).
• Document Creation Automation: Managers generate waybills, labels, and accompanying documents without manual data entry, significantly accelerating order processing.
• Status Synchronization: Shipment statuses are updated in the store's system in real-time, providing customers with current information.
• Flexibility in Carrier Selection: The ability to work simultaneously with multiple logistics partners, both Ukrainian and international.

How Integration Works: From Routine to Automation

Essentially, integration creates a continuous channel for data exchange between your system and the logistics partner's system, most often via API. This process helps avoid manual data transfer, which is not only labor-intensive but also prone to errors. Without integration, managers spend hours copying customer data, creating waybills in the carrier's cabinet, tracking statuses, and informing buyers, which becomes inefficient as sales volumes grow.

After successful integration, all order data (contents, address, weight, payment) is automatically transmitted to the carrier. The developer's task is to correctly map this data to the API requirements and anticipate possible non-standard situations, such as address changes or partial returns. Our analysts emphasize: the key is to identify the primary source of truth for order information (CRM, ERP, CMS); this system should be the foundation for creating shipments.

Processes Subject to Automation

Which specific logistics processes can be optimized through integration?

Selecting a Delivery Method on the Checkout Page

Customers see an up-to-date list of available branches, parcel lockers, or address delivery options. Interactive search with suggestions minimizes address entry errors and improves user experience.

Calculating Cost and Estimated Times

The store's system transmits the necessary parameters to the carrier, receiving accurate rates and times in return. It's important to inform the user about possible minor adjustments to the final amount.

Automatic Creation of Waybills (TTN)

Recipient and order data are already available, so the manager only needs to confirm TTN creation. Batch processing and automatic printing are possible.

Printing Labels and Accompanying Documentation

For domestic shipments, this mostly includes shipping labels; for international ones, invoices, customs declarations, content descriptions, etc. Integration ensures all necessary documents are generated.

Synchronization of Shipment Statuses

Despite the variety of statuses among different carriers, they can be normalized to a single business logic (e.g., "TTN Created," "In Transit," "Received"). This simplifies reporting and further automation.

Notifying Customers About Status

After a shipment is created, the system automatically sends the customer the TTN number and status updates via convenient communication channels (email, SMS, messengers).

Analytics and Control of Logistics Processes

Centralized storage of status and cost data allows for analyzing logistics effectiveness, identifying problematic areas, and making informed management decisions.

Overview of Integration Capabilities with Major Carriers

Each logistics operator has its integration specifics:

Nova Poshta / Nova Post

• Target Scenarios: Sales within Ukraine, international delivery via Nova Post Europe, delivery to branches, parcel lockers, courier.
• What's Integrated: Directories of settlements and pickup points, shipment creation, calculation, label printing, tracking, returns, and rerouting.
• Important Aspects: Correct handling of weight and dimension parameters, caching directories for faster operation, controlling data relevance.

Ukrposhta

• Target Scenarios: Delivery within Ukraine and international postal shipments.
• What's Integrated: Address classifier, search for branches and indices, shipment creation, labels, tracking, international documents.
• Important Aspects: Full integration requires access tokens and official cooperation. International shipments demand more mandatory fields.

Meest

• Target Scenarios: Domestic and cross-border delivery, e-commerce.
• What's Integrated: Selection of service points, shipment creation and processing, documentation, statuses, and tracking.
• Important Aspects: Functionality and API access may vary depending on the specific Meest product and country.

DHL Express

• Target Scenarios: Urgent international delivery, export orders, global logistics.
• What's Integrated: Checking available services, rates, estimated time, shipment creation, courier pickup request, labels, tracking, customs data.
• Important Aspects: An active business account is required. Special attention to addresses, product descriptions, HS codes, currencies, and customs documents.

Always check the current official documentation of carriers (Nova Poshta, Ukrposhta, Meest, DHL), as API capabilities are constantly updated.

Order Journey: How Integration Works Step-by-Step

1. Cart Formation: Customer adds items; the system records contents, total, estimated weight, and dimensions.
2. Delivery Parameter Selection: Customer chooses country and locality; the system displays available services and methods.
3. Rate Retrieval: An API request to the carrier provides available pickup points or delivery costs.
4. Order Saving: Selected delivery options are integrated into the order data.
5. Manager Data Verification: If needed, the manager clarifies shipment details.
6. Shipment Creation: The system automatically generates the TTN, label, and other service information via API.
7. TTN Linking: The TTN number becomes available to the customer, manager, and other connected systems.
8. Status Updates: Status changes are tracked and synchronized.
9. Automated Reactions: For example, after an order is received, the deal closes; upon refusal, a return scenario is initiated.

The most complex stage is data reconciliation among different systems. Discrepancies in storing phone numbers, addresses, or payment statuses can lead to errors, even if the API works correctly.

Integration Methods: From Ready-Made Solutions to Custom Development

1. Ready-Made Plugins or Modules

Ideally suited for standard platforms (WooCommerce, OpenCart) with typical business processes. Ensure fast launch and lower budget. However, they may have limited functionality and developer dependency. For WordPress, there are separate connection guides.

2. Integration via CRM

Optimal when all orders are processed in a CRM. The TTN is created there, and the number and status are returned to the website. If standard CRM solutions don't meet needs, consider custom CRM module development.

3. Integration via ERP or WMS

For large stores with complex logistics chains, multiple warehouses, and wholesale sales, ERP or WMS is the primary data source. Shipment creation is initiated after order fulfillment. We offer comprehensive ERP integration services.

4. Direct API Integration

Required for custom CMS, marketplaces, B2B portals, or when maximum control over processes is needed. Provides full flexibility in implementing unique logic. The choice between a ready-made solution and custom development significantly impacts integration capabilities. More details can be found in analytical materials.

5. Middleware — Intermediate Integration Layer

When orders come from various sources (website, marketplaces, mobile apps) and shipments are made from multiple warehouses, Middleware helps centralize and normalize data, acting as a single point of interaction with carrier APIs.

Step-by-Step Plan for Connecting Delivery Services

1. Describe the Real Delivery Process: Clearly define who creates shipments and when, where data is stored, how returns and cash-on-delivery are handled.
2. Select Services and Scenarios: Choose carriers and determine which delivery methods will be available to customers (filtering by geography, weight, order amount).
3. Obtain API Access: Get the necessary keys and tokens for each carrier. Ensure their secure storage.
4. Prepare the Data Map: Map your system's fields to the carrier's API fields (full name, address, weight, declared value, etc.).
5. Configure Checkout: Ensure a fast, clear, and fault-tolerant order process. Cache branch lists, optimize search.
6. Implement Manager's Cabinet: Create functionality for creating, modifying, deleting TTNs, printing labels, and tracking requests.
7. Normalize Statuses: Create a single internal table for mapping shipment statuses across all carriers.
8. Thorough Testing: Test all possible scenarios, including problematic ones (incorrect data, API timeouts, returns).
9. Launch Monitoring: After launch, monitor errors, API response times, and status discrepancies. Regular monitoring ensures stable integration performance even after updates.

Specifics of Integration with Key Ukrainian Carriers

Integration with Nova Poshta

The basic scenario includes displaying branches/parcel lockers, saving the customer's choice, and creating an express waybill. Extended integration can include cost calculation, address delivery, label printing, registers, and automatic status updates. It's crucial to correctly handle product weight and dimension parameters and cache branch directories.

Integration with Ukrposhta

Ukrposhta's API allows working with domestic and international shipments, address classifier, branch search, and tracking. For international delivery, special attention should be paid to the country, full Latin address, and customs information. It's recommended to develop a unified delivery selection component if working with multiple carriers.

Integration with Meest

Used for domestic and cross-border logistics. Before development, it's necessary to clarify the specific Meest service the business uses and the features of international shipments, as technical scenarios can vary significantly.

International Delivery Services: DHL and Others

Integration with international operators like DHL is more complex due to customs rules, product descriptions, HS codes, currencies, taxes, and restrictions. MyDHL API provides capabilities for checking services, calculating rates, creating shipments, ordering couriers, and tracking. It's important to consider international checkout specifics:

• Country selection at the beginning of the process.
• Validation of postal code and address structure.
• Separate fields for regions/states.
• Latin spelling of name and address.
• Warnings about customs duties.
• Restrictions for certain products.

As market analysts emphasize, international delivery integration should ideally be planned at the design stage, rather than added at the last minute, which significantly simplifies subsequent operation.

Technical Requirements for Reliable Integration

• Server-side Key Storage: API keys and tokens must be stored on a secure server, never exposed in HTML.
• Directory Caching: Cities, branches, and parcel lockers should be synchronized on a schedule to speed up checkout.
• Queues for Background Operations: Mass actions (TTN creation, status updates) are performed via queues, increasing fault tolerance.
• Idempotency: Repeated requests should not create duplicate waybills.
• Logging: Detailed logging of requests and errors accelerates problem diagnosis.
• Fallback Scenario: The system must allow order completion even if the carrier's API is temporarily unavailable.

Common Mistakes to Avoid

Among the most frequent integration problems:

• Excessive Logic in Checkout: Every API request slows down the process.
• Lack of a Unified Status Model: Complicates analytics and automation.
• Premature TTN Creation: Generates unnecessary waybills for unpaid orders.
• Missing Weight/Dimensions in Catalog: Leads to inaccurate calculations.
• API Keys in Browser: Creates security risks.
• Ignoring API Changes: Requires regular maintenance and updates.
• Absence of a Return Scenario: No less important than the shipment scenario.

Cost and Timeline of Integration: Influencing Factors

The complexity and cost of integration vary greatly. These factors include:

• Website platform and existing code quality.
• Number of delivery services and depth of integration.
• Need for rate calculation, document creation.
• Integration with CRM, ERP, WMS, marketplaces.
• Complexity of logic (multiple warehouses, international addresses, currencies).
• Need for user interface refinement.
• Availability of technical specifications, test environment, and support requirements.

We always recommend starting with an audit and defining the minimum viable functionality. Often, there's no need to implement all API capabilities at once; it's more rational to launch incrementally, expanding functionality as the business grows.

The approach of one of the leading companies in the market involves viewing delivery as part of the entire sales system, which is extremely effective for stores with complex architectures.

Our integration process includes:

1. Audit of Current Architecture: Assessment of CMS, code, databases, CRM, ERP.
2. Description of Business Scenarios: Detailing business needs regarding delivery services, TTN processing, statuses, returns.
3. Integration Design: Choosing the optimal solution — ready-made module, direct API integration, or middleware.
4. Development and Testing: Implementation and verification of all scenarios.
5. Phased Launch: Connecting functionality in parts, if necessary.
6. Documentation Transfer: Providing complete instructions for clients.
7. Post-Release Support: Monitoring and prompt response to changes.

Integration can be implemented in both new and existing projects. For a comprehensive launch, we recommend the e-commerce platform development service. For existing resources, a code audit is suitable.

Checklist Before Starting Integration

• All delivery services, countries, and methods are defined.
• It is clear which system is the main source of order data.
• Business accounts, contracts, API keys, or tokens have been obtained.
• Products include weight, dimensions, and other necessary logistics parameters.
• Rules for cash-on-delivery, free shipping, and insurance are described.
• The moment of TTN creation has been agreed upon.
• Internal order statuses and their mapping to carrier statuses are defined.
• Returns, refusals, rerouting, and re-shipments are anticipated.
• A test environment or a safe testing plan is in place.
• Logs, monitoring, and a person responsible for support are configured.

Frequently Asked Questions About Delivery Service Integration

What is delivery service integration for online stores?

It's an automatic data exchange between a store (CRM/ERP) and a carrier's system via API or a ready-made module. It automates delivery selection, TTN creation, document printing, and status retrieval without manual input.

How to connect Nova Poshta to an online store?

You need to obtain API access, integrate via a module or develop a direct connection, configure sender data, branch selection, package parameters, TTN creation, and status synchronization. Testing is conducted after setup.

Can Nova Poshta, Ukrposhta, and Meest be connected simultaneously?

Yes. Customers can be shown multiple services, filtered by criteria (city, weight, amount). For effective analytics and automation, it's advisable to normalize statuses from different carriers into a single model.

Can delivery integration be added to an existing website?

Yes, but it requires a preliminary audit of the CMS, platform version, existing modules, and code quality. For simple stores, a plugin might suffice; for complex ones, custom API integration is needed.

What's better: a ready-made plugin or custom integration?

A ready-made plugin suits standard processes and fast launch. Custom integration is preferable for complex business models with multiple warehouses, CRM/ERP, unique rules, or international logistics.

Is a CRM mandatory for delivery integration?

No. Integration is possible directly with the website. A CRM becomes necessary when managers actively process orders, interact with customers, and track statuses through it.

How does delivery cost calculation work?

The website sends the carrier the route, weight, dimensions, and service type. The API returns the available rate or estimated price. The final cost may vary slightly after actual measurement.

How to connect DHL and other international delivery services?

You need to sign a contract or create a business account, obtain API access, configure international addresses, product descriptions, weight, currency, and customs documents. For DHL Express, an active business account is required.

What happens if a delivery service API is temporarily down?

Reliable integration should include a fallback scenario: caching directories, saving customer choices, re-executing operations, or escalating to a manager. The error should be logged and clearly communicated to the user.

What determines the cost of integration?

The platform, code quality, number of carriers, depth of automation, integration with other systems, complexity of logic (international shipments, multiple warehouses), and support requirements. An accurate estimate is only possible after a detailed audit.