ups-banner-bg
ph_img_faq_page_image

DHL Paket Shipping FAQs – Multi Carrier Shipping Label App for Shopify

    Everything you need to know about DHL Paket shipping with Shopify

Questions in this section:

Does DHL Paket API support street numbers that include letters (e.g., “6A”) and how is this handled in the PluginHive app?

DHL Paket API technically restricts the streetNumber field to numeric values only, which is a limitation of the DHL Paket API itself, not the PluginHive app. While the DHL website portal allows labels with street numbers including letters (e.g., “6A”), the API rejects letters in the streetNumber field. To accommodate this, PluginHive has enhanced the app to correctly map German address formats that include street numbers with letters, slashes, hyphens, and ranges by parsing and separating components where possible. However, the literal alphabetic characters in the streetNumber field are handled differently or may be omitted due to API constraints. If you encounter mismatches, it is recommended to also test label creation directly on the DHL portal and share shipping labels with PluginHive support for further investigation.

How can I add minimum and maximum weight and measurements for DHL Paket in the PluginHive app to create checkout rules based on size and weight?

You can create rules for rates on checkout using the Order Weight criteria within the PluginHive app. However, it is currently not possible to create checkout rate rules based on package measurements. To manage rates by weight: 1. Navigate to the Rules or Automation section of the app. 2. Set conditions based on the total order weight to apply specific shipping rates. 3. Unfortunately, dimensions or package size-based rules are not supported at this time. For further customization or specific carrier requirements, it is recommended to discuss these details during a support call with PluginHive.

How can I reprocess existing orders to generate labels after resolving a DHL Paket API failure in PluginHive?

To reprocess existing orders after the DHL Paket API issue is resolved in PluginHive: 1. Select the affected order(s) in the app. 2. Go to the **Advanced** menu and change the order status to **Initial**. 3. Confirm the order status has changed to **Initial**. 4. Select the order again, then choose **Prepare Shipment** to regenerate the shipping label. This process restarts the shipment workflow allowing label generation with the updated API integration.

How can I resolve the issue when I am unable to create a shipping label for an order, even after switching between DHL Paket and DHL Stycke services?

To resolve the issue of not being able to create a shipping label for an order, ensure that the order status is set to “Processing” and that a valid shipping service is assigned. For example, set the order status to Processing and assign the appropriate DHL service (such as DHL Paket). Once these settings are applied, attempt to generate the label again. This approach will typically enable label creation while preventing errors related to status or service mismatches.

How can merchants give permission for PluginHive to generate test labels using their DHL Paket credentials?

Merchants can provide explicit written permission (via email or support ticket) authorizing PluginHive to use their DHL Paket account credentials to generate test shipping labels. The process includes: – PluginHive creates test shipments and labels using merchant credentials. – Test labels are immediately cancelled after creation to avoid any charges or shipments. – Feedback is shared on whether the test reproduced the reported issues. This permission helps diagnose integration issues without interrupting live shipments.

How do I generate DHL Paket shipping labels after the PluginHive app was updated with the new DHL Paket REST API integration?

After the PluginHive app was enhanced with the DHL Paket REST API integration, you can generate DHL Paket labels through the app normally. For any existing orders that failed to generate labels, follow these steps to reprocess and generate labels: 1. Select the existing order in the app. 2. Navigate to the **Advanced** option and change the order status to **Initial**. 3. Once the order is in the **Initial** status, select the order again. 4. Click **Prepare Shipment** to generate the label. New orders imported into the app should generate labels without any issues.

How does PluginHive address the issue when DHL Paket API does not support passing company name on shipping labels?

Initially, DHL Paket API did not support sending company name fields or the app did not pass them correctly, preventing company names from showing on labels. PluginHive enhanced its app to include company name fields both for Shipper and Recipient addresses. This update required testing with merchant credentials and DHL confirmation. Merchants were advised to temporarily add the company name in other address fields to bypass the limitation. Following testing and internal fixes, PluginHive released the feature allowing company names to be displayed on DHL Paket labels as per the new app update.

How should notification sections be handled in the DHL Paket API request to avoid errors?

According to DHL Paket API support recommendations and PluginHive experience: – Remove empty or unused Notification sections from the API request, such as empty recipient email address tags. – If notification or communication details are needed, provide them fully and correctly as per DHL’s sample format. For example: “`xml “` – Avoid sending empty notifications which can cause request rejections or errors. Review your app or integration settings to ensure notifications are configured properly in requests.

How should the street name and street number be formatted in the DHL Paket API request to avoid label failures?

Based on DHL API feedback, the correct way to format address fields is: – The streetName field should contain only the street name without the house number (e.g., “Gewerbering”) – The streetNumber field should contain only the numeric house number (e.g., “3”) For example: “` “` Do not include the house number in the streetName field (e.g., avoid “Gewerbering 3”). This formatting ensures the DHL API recognizes the address without errors like “specified street cannot be found.” If the shipping address contains only a street name with no number, use “0” in the streetNumber field as a placeholder, since house numbers are mandatory.

How to differentiate between DHL Paket International and Warenpost International services within PluginHive when both appear similarly?

Differentiation can be done by: 1. Checking the service codes or descriptions assigned to each carrier service within the app’s configuration, as these uniquely identify the service backend. 2. Using distinctive naming conventions in your app’s service setup (e.g., “DHL Paket Intl” vs. “Warenpost Intl”) if the app interface allows editing service labels. 3. Consulting PluginHive support to understand if the app supports custom labels or other metadata to distinguish services clearly on the customer-facing side. 4. Mapping specific shipping zones and manual rates explicitly to each service to avoid overlap or confusion in the selection process. 5. Reviewing your DHL account services to confirm which service corresponds to which shipping option in the app.

How to troubleshoot and resolve a “login failed” error when generating DHL Paket labels in PluginHive?

The “login failed” error typically indicates issues with your DHL Paket account connection. To fix this: 1. Confirm that the DHL Paket services are activated/enabled on your DHL account—contact DHL support if uncertain. 2. Double-check the account credentials, API keys, or access details entered into the PluginHive app for accuracy and completeness. 3. Ensure there are no trailing spaces or typos in any account information input fields within the app. 4. If you recently updated your DHL account credentials, synchronize those changes with PluginHive promptly. 5. Attempt to log in directly on the DHL portal to confirm credentials are valid and active. 6. Clear plugin cache or disconnect and reconnect the DHL account within PluginHive to reset authentication. 7. Contact PluginHive support if the problem persists after these steps, and provide a detailed error message and account information for further diagnosis.

How was the DHL Paket label generation issue resolved in the PluginHive app?

The PluginHive team enhanced the DHL Paket API integration by moving from the existing API to the new DHL Paket REST API. The resolution steps were: 1. Developed and tested the enhanced DHL Paket REST API integration within the app. 2. Released an app update including this new API integration. 3. Instructed the user to reprocess existing orders in the app to update their status and generate new labels by selecting the order, clicking More Options, and choosing Reprocess Orders. 4. Confirmed that new orders imported post-update should generate labels without difficulty. This resolved the DHL Paket label generation failures.

What are the acceptable formats for German street addresses in the DHL Paket API integration, and how does the PluginHive app handle these?

The PluginHive app currently supports and correctly maps the following German address formats: 1. Numeric only (e.g., “103”) 2. Numeric with letter suffix (e.g., “12a”, “45b”, “103c”) 3. Numeric with slash (e.g., “12/1”, “45/2”, “103/3”) 4. Numeric with hyphen range (e.g., “12-16”, “45-49”, “103-105”) Addresses should be formatted so that the street name does not include the street number. The number should be passed separately in the streetNumber field. This ensures the DHL Paket API accepts the address. PluginHive is continuously working on enhancements to further improve address parsing and mapping based on DHL API limitations.

What are the key considerations when shipping with DHL Paket through PluginHive?

When using DHL Paket as your carrier via PluginHive, keep these points in mind: 1. Shipments must originate from Germany only; other countries like China are not supported for DHL Paket. 2. The “Ship From” address registered in the app must correspond exactly to the address linked to your DHL Paket account. 3. Valid DHL Paket login credentials are mandatory for integration and label generation workflows. 4. Ensure your DHL Paket account has access to the specific shipping services you intend to use, as lack of service permissions may cause API errors. 5. Confirm postal code and address formats conform to DHL Paket requirements to avoid shipment errors. 6. For significant order volumes, ensure all orders have been properly reprocessed after any address or credential changes.

What are the steps to troubleshoot label generation issues specifically with DHL Paket in PluginHive before the API was fixed?

When experiencing DHL Paket label generation failures in the PluginHive app before the API fix: 1. Recognize that this is caused by DHL Paket API failures on the carrier’s end. 2. Generate DHL labels externally outside of the app to avoid delays. 3. Wait for PluginHive updates confirming the API issue resolution and app enhancement. 4. Once the PluginHive app is updated with the new DHL REST API, follow the reprocessing steps to handle existing orders.

What is the proper handling of shipping addresses without a house number in the DHL Paket API?

DHL Paket API requires the house number to be a mandatory field in the request. If an address legitimately does not have a house number, the correct approach is: – Use “0” (zero) as a placeholder in the streetNumber field to satisfy the mandatory requirement. – Do not leave the streetNumber field blank or reuse the street name as the number, as this causes API validation failures. For example: “`xml “` This ensures the address passes validation and the shipment is processed correctly.

What should be checked if DHL Paket labels are refused with errors about ‘Postal Code not valid’ or ‘Shipping Confirmation service not available’ after recent PluginHive updates?

When encountering postal code validation errors or disabled confirmation services: – Verify the postal code entered in Shopify matches the official postal code format accepted by DHL API. Correct any typos. – Confirm the shipment date in the request is valid and current. – Remove deprecated or unsupported service options such as ‘Shipping Confirmation’ and switch to DHL-recommended services like ‘Paketankündigung’. – Check if any recent app updates changed the way these fields are populated and roll back temporarily if needed to isolate the cause. – Collaborate with PluginHive support to review API request/response logs to identify exact rejection causes. – Once corrections are made, reprocess orders and generate new labels. These steps help resolve common validation-based label refusals after updates.

What should be done if the DHL Paket API returns a “specified street cannot be found” error when generating labels via PluginHive?

This error usually indicates an invalid or incorrectly formatted street address in the API request. To resolve it: 1. Verify the street name and number are properly split, with the street name excluding the house number, and the house number sent as a separate field. 2. Remove the house number from the streetName and ensure it is set correctly in the streetNumber field. 3. If the address has no house number, set streetNumber to “0” to meet API requirements. 4. Cross-check the address format against DHL API specifications and sample working addresses. 5. Test label creation directly on the DHL business portal to compare accepted address formatting. 6. Share sample failed labels and API request/response logs with PluginHive support for further analysis. Following these steps can prevent the “street cannot be found” error.

What should I do if my DHL Paket credentials are incorrect and causing shipping label generation failures in PluginHive?

If your DHL Paket credentials are invalid or not working properly, follow these steps: 1. Verify the username and password you have entered in the PluginHive app are correct by attempting to log in directly to the DHL Paket website. 2. If you cannot log in with your current credentials, contact DHL Paket support or your account manager to recover or reset your login details. 3. Once you have the correct credentials, update them immediately in the PluginHive app settings. 4. After updating credentials, attempt to generate shipping labels again. 5. If you encounter API error messages related to postal code formats or access to specific shipping services, inform DHL Paket support to check your account’s configured services and restrictions. 6. You may also provide your DHL Paket account manager’s contact details to PluginHive support so they can liaise with DHL Paket on your behalf if necessary.

What should I do while DHL Paket API is down or experiencing issues for label generation?

While DHL Paket API is down or experiencing issues, follow these steps: 1. Generate DHL labels directly from the DHL website or DHL’s official app. 2. Avoid generating DHL labels using the PluginHive app until the API issue is fixed to prevent failures. 3. Coordinate with PluginHive support and DHL support; share any error messages or label attempts for faster diagnosis. 4. Keep orders queued and ready in the app but avoid label requests until you receive a confirmation that the API is restored. 5. Once PluginHive announces resolution (like an app update or API switch), reprocess the existing orders to generate labels successfully.

What should merchants do if they experience intermittent label generation failures with DHL Paket on certain days after PluginHive updates?

If label generation fails intermittently: 1. Note the specific dates and times when failures occur. 2. Check if there were any PluginHive app updates or DHL API changes around those periods. 3. Share videos or screenshots showing label generation attempts with PluginHive support for diagnostics. 4. Provide authorization to PluginHive to generate test labels on your store, allowing them to replicate the issue. 5. Confirm your shipping addresses are accurate and consistent across orders. 6. If PluginHive identifies address or service-related errors, apply recommended corrections accordingly. 7. Monitor label generation behavior after fixes, informing PluginHive immediately if problems continue. Prompt reporting and cooperation enable PluginHive to work with DHL to stabilize the service and minimize downtime.

What troubleshooting steps should be followed when encounters “Label Failed” errors in PluginHive for DHL Paket shipments after recent app updates?

If label generation fails after recent updates, follow these steps: 1. Confirm the Shopify shipping address fields are correctly formatted as per DHL API requirements (street name and number separated, no company name missing). 2. Check if the orders generating errors were processed before or after the update — reprocessing the order might be needed after updates. 3. Provide PluginHive support with specific failed order numbers and, if possible, screenshots or error logs shown in the app. 4. Grant PluginHive permission to generate test labels on your store to replicate the issues. 5. Review the exact API error messages and determine if errors relate to invalid addresses, unsupported services, or validation failures. 6. Allow PluginHive to liaise with DHL support to clarify API constraints or required request changes. 7. Continue testing label generations for valid orders and update your app version if a fix is released. Following these steps allows PluginHive to isolate the cause and fix DHL label failures efficiently.

Why am I unable to generate DHL Paket shipping labels using the PluginHive app, and what can I do in the meantime?

The inability to generate DHL Paket labels is due to failures in the DHL Paket API. As a temporary workaround, you should generate DHL labels outside the PluginHive app until the issue is resolved. The PluginHive team is in contact with DHL to fix the API failure and will update you once resolved.

Why are DHL Paket labels failing to generate in the app while DHL’s own app generates them successfully?

DHL Paket labels failing in the app while working in the DHL app usually indicates an issue with the DHL Paket API integration in the PluginHive app. In this case, the API was returning an “NA” error without XML details, starting suddenly from one day. The recommended course of action is: 1. Verify no account changes have been made that might affect label generation. 2. Attempt label generation directly from the DHL website or DHL’s own app to confirm if the issue is app-specific. 3. Contact DHL Paket support or your DHL account manager to check the status of your account and API access. 4. Meanwhile, it is advised to generate DHL labels outside of the PluginHive app until the app developers resolve the issue. 5. PluginHive will coordinate with DHL and provide updates once the integration is fixed.

Why are DHL Paket shipping labels generated via the PluginHive app sometimes failing suddenly, despite valid addresses?

Label failures can be caused by several issues: – Invalid or improperly formatted shipping address fields that do not comply with DHL API requirements (especially street name and number separation). – Temporary outages or changes on the DHL API side affecting label generation. – Use of outdated app versions or labels generated before the latest address mapping enhancements. – Metadata or service options in the request that DHL API rejects, e.g., invalid shipment confirmation options. If you experience label failures for multiple orders: 1. Verify the address fields for correctness. 2. Update to the latest PluginHive app version which includes recent fixes. 3. Confirm API error messages provided by PluginHive support to pinpoint the root cause. 4. Share order details and failure screenshots with support for troubleshooting. In the reported case, PluginHive investigated with DHL API developers and adjusted request structures accordingly to handle these issues.

Why are two entries for “DHL Paket International” showing up when selecting service carriers after adding shipping zones and manual rates in the PluginHive Multi-Carrier app?

This happens because both “DHL Paket International” and “Warenpost International” (for EU and international shipments) appear with very similar or identical service names, causing confusion in selection. To resolve this: 1. Review the service names configured in the app under your carrier settings to ensure each service is clearly and distinctly named. 2. If the app does not allow customizing service names directly, use different shipping service codes or labels to differentiate “Warenpost International” from “DHL Paket International.” 3. Verify the shipping zones and rates are correctly mapped to the intended service to prevent overlap. 4. If the confusion persists, schedule a support session with PluginHive to clarify service setup. Properly distinguishing services ensures you can select the correct service and apply the correct rates at checkout.

Why does the company name not show on DHL Paket shipping labels when entered as part of the delivery address in Shopify, and how can this be resolved?

Initially, the PluginHive app did not pass the company name field to the DHL Paket API, causing it to be missing on shipping labels. PluginHive has enhanced the app to include both the Shipper and Recipient company name on the DHL Paket labels. However, this update required testing with merchant credentials before going live. Merchants can temporarily workaround this by adding the company name either in the Person Name field or the Address field in Shopify to ensure it appears on labels. If the company name is missing on DHL labels despite being entered correctly, ensure the order has been reprocessed after the update. Also, for orders shipped via other carriers (e.g., UPS), the changes will not apply for DHL labels.

Looking for more details or ready to get started?
Visit the app page to explore features and pricing.

Shopify Multi Carrier Shipping Label App