Order data is transferred in a controlled manner.
Orders ready for shipment can be selected based on defined status, store, and process rules. This ensures that only relevant orders are processed for shipping.
Connect Magento Open Source or Adobe Commerce with Paket International and integrate carrier selection, label creation, shipping documents and tracking into your existing order, warehouse and fulfillment architecture.
Magento and Adobe Commerce are often operated with ERP, PIM, WMS, multiple store views, and custom modules. Therefore, the shipping integration must complement existing data flows, not bypass them.
Orders ready for shipment can be selected based on defined status, store, and process rules. This ensures that only relevant orders are processed for shipping.
With multi-source inventory, the source, reserved quantity, and shipped items can be included in the shipment creation.
Labels, tracking information, and shipped quantities are linked to the Commerce shipment. This ensures that the operational status remains consistent in the shop backend.
Individual attributes, multiple warehouse sources, partial shipments, third-party modules and custom order statuses make Magento projects powerful – but also demanding for standardized shipping solutions.
International Package connects the central shipping platform with your existing commerce logic. Individual data flows, mapping rules, and feedback can be configured via our Shipping API depict.
The implementation will be tailored to your Commerce version, modules, store views, warehouse structure, carrier rules, and international shipping scenarios.
Only orders that meet the agreed shipping criteria will be selected for further processing.
Project-specific additional fields can be included in the mapping and shipping decision.
Package dimensions, weight, destination country, price and transit time form the basis for service selection.
Shipping labels, invoices and available export documents are created from the existing order and merchandise data.
Shipped items and quantities are correctly assigned to the order, even in the case of multiple packages or partial quantities.
Carrier, title and tracking number can be stored with the respective shipment and made visible to customers.
A robust integration must respect the internal commerce logic. An order, a physical shipment, and an inventory transaction are not technically the same thing.
The order contains items, addresses, payment status, and other business data. However, it is not yet a physically confirmed shipment.
Only the shipment record documents which items and quantities were actually sent. Tracking information therefore belongs with this item.
In multi-source setups, shipment creation must work together with the correct source selection and inventory posting.
The process follows the commerce logic and supplements it with carrier selection, label creation, export and tracking.
REST access, roles, and required resources are securely granted to the connected application.
Status, positions, addresses, store view and project-specific attributes are checked.
Warehouse source, package data and carrier rules are all factored into the operational shipping decision.
The shipping label is created and the actual quantities shipped are recorded as shipments.
Carrier and tracking number are assigned to the shipment and are available to Commerce and the customer account.
Adobe Commerce provides REST and GraphQL web APIs. The REST interface is particularly relevant for backend processes such as order, invoice, and shipment management.
Adobe documents the complete order lifecycle via REST, including orders, invoices, and shipments. For shipment creation, Adobe recommends the order-based Ship endpoint, depending on the use case; for multi-source inventory, source and quantities are also taken into account.
The connection is particularly relevant for retailers with complex fulfillment structures, international shipments, or a high degree of customization of the commerce platform.
For companies with high order volumes, individual modules and clearly defined fulfillment processes.
For shops with multiple storage sources, distributed inventories, and complex source selection.
For retailers who need to map EU and third-country shipments, including shipping and export documents.
For companies where commerce, inventory management, warehousing and shipping platforms need to work synchronously.
Combine Magento connectivity with solutions for carriers, export, tracking, and individual system integration.
The specific scope depends on the Commerce edition, version, installed modules, warehouse structure, and desired shipping processes.
Generally, yes. Both platforms provide commerce web APIs. However, available endpoints and features may differ depending on the edition, operating model, and version.
Shipping-relevant orders can be retrieved via the REST API using defined search and status criteria. Project-specific fields can be mapped as needed.
The order represents the commercial transaction. The shipment documents which items and quantities were actually shipped and contains the associated tracking information.
Yes. Shipments can contain subsets of an order. This allows for the differentiated representation of items that are not fully available or multiple shipping packages.
Yes. With appropriate setups, storage sources, available quantities, and source selection can be included in shipment creation.
Tracking information can be added to each shipment. Adobe Commerce also makes this data available in the customer account and order history.
Yes. Adobe Commerce allows additional statuses within existing order states. Which statuses trigger or block the shipping process is defined in the integration concept.
The specific commerce instance is technically analyzed. Relevant extensions and additional fields can be included in mapping, filtering, and feedback.
Yes. Depending on the shipping situation, commercial or pro forma invoices as well as other available export documents can be prepared from order, product and customs data.
Before going live, order selection, shipment creation, source booking, labeling, and tracking are tested in a test environment. The integration should be revalidated after any Commerce updates.
We examine the edition, version, REST endpoints, order status, multi-source inventory, custom modules and international shipping requirements, and develop a robust solution based on this information.