Which Shipping Connection Fits Your weclapp Setup? A Guide by Use Case

"Which shipping connection actually fits us?" This question comes up when a weclapp setup grows: new countries are added, parcels are joined by pallets, or a dangerous goods item enters the assortment. The right answer is rarely "one carrier for everything", but "the right shipping route per shipment type, controlled centrally from one system". Fulfillment 4 weclapp offers more than 14 shipping connections, including direct carrier APIs, shipping platforms and other shipping processes. Through the integrated Shipcloud interface, additional carriers can be used depending on the booked portfolio and the configuration. So that you don't have to research each connection individually, I've sorted them here by five practical use cases.

Parcel shipping in Germany: the daily volume

For classic parcel shipping in Germany, DHL Paket, Deutsche Post, DPD and GLS are among the options. In the supported packing and completion flows, Fulfillment 4 weclapp creates labels and writes tracking data back into the weclapp shipment. Deutsche Post additionally covers Warenpost and letter products for small, light shipping. In the implemented process, GLS takes a minimum weight for very light parcels into account. DPD Paket runs either via the DPD Public Web Services or the DPD Cloud service. Important to know: the implemented dangerous goods flow is intended for the Public Web Services, not for the Cloud service.

International and customs: when the border thinks along

For shipments outside the EU, DHL Paket, DHL Express, FedEx, Österreichische Post and Shipcloud support the transfer of customs data from weclapp, depending on the carrier and configuration. The current automatic customs processing is intended for supported non-EU single-parcel shipments. Complete item master data and an activated customs function are prerequisites. Available carrier or app customs documents can then be output via a configured document printer. For correspondingly configured dangerous goods shipments, FedEx can additionally take over the stored emergency contact. For Österreichische Post, dangerous goods in the current connection is provided exclusively as limited quantities; non-LQ shipments are blocked.

Freight and general cargo: pallets instead of parcels

If you ship pallets, mesh boxes or consolidated freight, you can use Dachser, DB Schenker, Gebrüder Weiss or Kühne+Nagel. With Dachser, targo on-site, targo speed 12/10/8, targo fix and targo direct are among those available; tail lift and advance notification can be configured per shipping method, and existing recipient contact data is transferred. DB Schenker covers 23 package types, from pallet to crate to sack; the dimension sorting is configurable. Gebrüder Weiss transmits several packages as line items of one transport order and supports SSCC/GS1 as well as dangerous goods data in the intended process. Kühne+Nagel integrates Road Bookings, can transmit a commercial invoice provided in the fulfillment process and, for items flagged as dangerous goods, takes over, among other things, UN number and packing group.

Switzerland: its own rules, its own language

For the Swiss market, there are three specialized connections: DPD Schweiz, Schweizerische Post and Planzer. DPD Schweiz creates labels in German, French, Italian or English, as you choose. Schweizerische Post works with your franking license and supports Priority, Economy and configurable additional codes, including COLD. Which combination is actually available depends on the franking license, service mapping and permissible PRZL configuration. Planzer maps the weclapp shipping methods Paket and Palette to the services PAKET and TRAUFT respectively.

Special cases: when standard isn't enough

The Eurotranspharma connection integrates ETP service profiles for 15–25 °C and 2–8 °C and processes label and tracking data via the ETP API. The Track-POD connection retrieves shipping labels and tracking information for existing Track-POD orders and transfers them into the connected ERP process. This also lets special shipping flows be placed in the same operational context, without promising functions that lie outside the respective interface.

Customs, dangerous goods, multi-parcel: the capabilities at a glance

The functions differ by carrier and configuration. The most important patterns are:

• 🔹 Customs data can be transferred from weclapp to the carrier API for supported non-EU single-parcel shipments; available documents can be output in the label process.
• 🔹 DPD Public WS and Gebrüder Weiss each support their own dangerous goods and document processes; Kühne+Nagel takes over dangerous goods data of flagged items, FedEx a configured emergency contact and Österreichische Post limited quantities.
• 🔹 Multi-parcel shipments are processed carrier-specifically, depending on the connection with package IDs, SSCCs, tracking numbers or a shared booking reference.
• 🔹 The required dangerous goods and customs data come from maintained weclapp item and order data and are transferred in a way that fits the respective interface.

My position: combine instead of choosing

For me, the real strength is not the individual connection, but that you can use several shipping routes from the same weclapp packing process. A merchant with a German parcel business, occasional pallet shipping and a dangerous goods item may in practice need several carriers in parallel. For additional carriers, the integrated Shipcloud interface can be used, depending on your Shipcloud contract, the booked carrier portfolio and the configuration. This way you choose the shipping route that fits each shipment, without leaving the central ERP process.

Which connection fits your assortment?

Tell me which shipping types come together for you at the moment: parcel, pallet, dangerous goods or abroad. You'll find an overview on the landing page for shipping carriers for weclapp. If you want to talk through your setup concretely, book a no-obligation intro call.