Shop data becomes shipping data
Delivery address, order items, sales channel, and package information are transferred into a shipping-ready data record. Your team does not need to re-enter existing information.
Connect your ikas shop to Paket International and combine order data, carrier selection, label creation and shipment status in a seamless shipping process.
The connection uses existing shop data instead of building parallel data silos. This creates a reliable process for national and cross-border orders.
Delivery address, order items, sales channel, and package information are transferred into a shipping-ready data record. Your team does not need to re-enter existing information.
The selection can be based on destination region, package dimensions, costs, transit time, and desired service. This allows shipping rules to be applied consistently to many orders.
Fulfillment, package status, tracking number, and tracking link can be assigned to the corresponding order package. The shop and shipping department maintain the same information.
When orders are transferred manually from the shop, media breaks occur precisely where speed and data quality are particularly important.
The connection with our central shipping platform It creates a seamless transition between ikas, carrier processes, and international shipping. Individual workflows can also be configured via our Shipping API depict.
The range of functions will be tailored to your order structure, shipping countries, package types and existing systems.
Orders relevant to shipping can be transferred to further processing based on suitable criteria.
Article data and package information remain uniquely assigned within the order model.
Available carriers, services, prices and transit times are determined based on the specific shipment data.
The shipping label is generated from the existing order, address and package information.
For shipments to third countries, the value of goods, origin, customs tariff number and invoice data can be processed.
Tracking number, tracking link, carrier and package status can be reassigned to the order in ikas.
The ikas Admin API maps orders, packages, and fulfillment as structured objects. This logic enables deeper, more deeply integrated shipping automation.
The connection is authorized via a private app created in ikas. Required permissions can be specifically limited using scopes.
Tracking data is not only stored generally with the order, but can also be assigned to the appropriate package or fulfillment.
Depending on the integration design, events can be sent to a defined endpoint. This eliminates the need to actively query for every change.
The process combines authorization, order acceptance, shipping decision and feedback without unnecessary system changes.
The required API permissions are defined in the ikas dashboard, and access data for the secure connection is generated.
The integration reads the order, recipient, location and package information necessary for shipping.
Paket International evaluates available carriers and services based on the specific shipment parameters.
Labels and available invoice, shipping and export documents are created from the existing data.
Tracking information and package status are assigned to the corresponding order package in ikas.
The connection follows the technical model of ikas and is only equipped with the permissions that are actually needed for your shipping process.
ikas uses the OAuth client credentials flow for private apps. The client ID and client secret are exchanged for a time-limited bearer access token. The enabled ordering and fulfillment functions can then be used via the GraphQL Admin API.
read_orders Required. Write operations such as fulfillment or status updates require appropriate write permissions. The specific scope will be defined before implementation.
Integration is particularly relevant where order volumes, international relationships, or multiple internal systems make manual processes confusing.
For brands that want to consistently manage customer experience and shipping status even after checkout.
For retailers who regularly process export-relevant orders to third countries in addition to EU shipments.
For companies that want to combine ikas, merchandise management, warehousing and shipping into a single workflow.
For service providers who handle and ship ikas orders in a structured manner on behalf of various brands.
Link the ikas connection with the solutions that are relevant to your specific shipping and export process.
The final range of functions depends on your approved API scopes, the order logic used, and the desired shipping processes.
The connection is established via a private app. It provides the client ID and client secret, from which a bearer access token is generated via the OAuth client credentials flow.
Depending on the process, order details, delivery address, line items, sales channel, and package and fulfillment information are used. For shipments to third countries, product and customs data are also included.
The query and filter logic is defined in the integration concept. This allows the process to be limited to the orders relevant to your shipping operations.
ikas displays order packages and associated fulfillment information in a structured manner. This allows tracking data to be assigned to the correct package instead of just to the order in general.
Write updates are possible with the necessary API permissions. Which status changes are used will be determined according to your process.
Depending on the configured workflow, tracking number, tracking link, carrier or cargo information and package status can be processed, among other things.
Depending on the shipping case and destination country, Paket International can prepare commercial or pro forma invoices as well as other available shipping and export documents.
Yes. The shipping solution can be integrated into a system landscape consisting of ikas, merchandise management, warehouse and other applications via API or middleware.
Webhooks can send events to a defined endpoint. Whether they are used in a specific sending process depends on the required events and the integration design.
Key factors include required scopes, order and package structure, carrier rules, shipping countries, customs requirements, and existing ERP or WMS connections.
We review the private app, required scopes, order structure, carrier rules and international shipping requirements, and develop a suitable technical implementation based on this.