Customs Data in the Label Process: International Shipping from weclapp
The moment at the packing table that decides the international shipment
A shipment to the UK, Switzerland or the USA needs more than a label. Depending on the destination country, service and shipment contents, it needs customs data such as goods description, value, origin and customs tariff number. If required details are missing or don't match the shipping documents, the parcel can get stuck at customs until someone follows up. For us at wals.pro, this is the point where international shipping from the ERP has to prove itself: not with the hundredth domestic parcel, but with the one shipment that crosses a border.
With Fulfillment 4 weclapp, we integrate customs processing into the label process. With the customs function enabled, the app takes item data from weclapp for supported non-EU single-parcel shipments and transmits it to the respective carrier API. Available carrier or app customs documents can then be output via a configured document printer.
Why this is more than a form
Missing or incorrect customs data can lead to queries, delays and rework. The more destination countries an assortment reaches, the more important a consistent data basis becomes. That is why, for us, customs processing belongs in the same operational process as the label and not in a detached after-the-fact data entry.
Which data is used in the label process
The basis is your maintained weclapp item and order data, including goods description, goods value, origin and, where required, customs tariff number. In the respectively supported carrier process, the connection checks the required details and aborts on incomplete mandatory data before an incomplete customs transmission takes place.
DHL Paket and DHL Express
For supported non-EU single-parcel shipments, the DHL Paket connection can take the customs details from weclapp into the API order. If the carrier API provides a customs document, it can be output in the label process via the configured document printer. DHL Express also receives the customs details for correspondingly configured non-EU shipments. Which documents are returned is determined by the respective carrier API and the booked service.
FedEx
For correspondingly configured FedEx shipments outside the EU, the connection transmits the customs details from weclapp. Which trade documents are available in the carrier process depends on configuration, service and carrier response. For configured dangerous goods shipments, the stored emergency contact can additionally be transmitted.
Österreichische Post
For supported non-EU single-parcel shipments, the connection to Österreichische Post transmits the required customs positions from the maintained weclapp data. For dangerous goods, the current connection is limited to limited quantities; non-LQ shipments are blocked before processing.
Kühne+Nagel and Shipcloud
With Kühne+Nagel, a commercial invoice provided in the fulfillment process can be passed to the Road Booking. For items flagged as dangerous goods, the connection takes over, among other things, UN number and packing group. Via Shipcloud, customs data can likewise be transmitted for supported non-EU single-parcel shipments. Which carrier documents are available depends on the respective Shipcloud and carrier configuration.
- 🔹 Customs data from maintained weclapp item and order data
- 🔹 Transmission for supported non-EU single-parcel shipments with the customs function enabled
- 🔹 Output of available carrier or app customs documents via a configured document printer
- ✅ Writing tracking and parcel data back in the supported completion flows
How the process works in practice
At the packing table, the flow stays familiar: the shipment is processed in the configured packing process, the label is requested from the carrier, and the connection checks whether customs data is required for the destination country. For a supported non-EU single-parcel shipment, it pulls the required details from weclapp and transmits them to the carrier API. If the carrier delivers a separate customs document or the app provides a document intended for this process, it can be output via the configured document printer. Tracking and parcel data are then written back to weclapp in the supported completion flow.
Multi-parcel customs shipments do not fall under the automatic single-parcel processing described here; their flow has to be clarified carrier by carrier.
Honest prerequisites are part of it
The customs function must be enabled, the shipment must fall into a supported non-EU single-parcel process, and the required item master data must be complete. Which documents the carrier actually generates additionally depends on API, contract and service. Dangerous goods can be shipped via Österreichische Post exclusively as limited quantities; the connection blocks non-LQ shipments. Fulfillment 4 weclapp offers more than 14 shipping connections, including direct carrier APIs, shipping platforms and other shipping processes. Which combination fits assortment, destination countries and customs requirements remains a deliberate carrier decision.
My position
International shipping from an ERP works well when customs and shipping data come from the same maintained source. That is why, for me, customs transmission belongs in the packing and label process: carrier-specific, traceable and with clear prerequisites.
Do you already ship internationally from weclapp, or is the first step across the border still ahead of you? You'll find the available shipping connections in the overview of shipping carriers for weclapp. If you want to talk through your international shipping concretely, book a no-obligation intro call. We'll look at your destination countries, master data and carriers together.