ups-banner-bg
ph_img_faq_page_image

CouriersPlease Shipping FAQs – Multi Carrier Shipping Label App for Shopify

    FAQs covering CouriersPlease shipping configuration and troubleshooting

Questions in this section:

After enabling the Authority To Leave option in PluginHive for Couriers Please, how can I verify it works as intended?

After toggling the Authority To Leave option in the app: 1. Place a new order that requires courier labeling. 2. Generate the shipping label for that order via PluginHive. 3. Confirm from the label or carrier confirmation whether ATL is applied or disabled as per your setting. 4. Contact PluginHive support if the label does not reflect your configuration for further assistance.

Can I book orders exceeding 10 boxes with CouriersPlease through PluginHive in the future?

Currently, PluginHive’s integration with CouriersPlease enforces the carrier’s API limit of up to 10 packages per order for rate requests and bookings. Booking orders with more than 10 packages is not supported through PluginHive at this time. For such orders, booking directly via CouriersPlease remains necessary. For up-to-date information or potential enhancements, contacting PluginHive support is advised.

Can I enter fractional weights (e.g., 7.8 kg) when requesting quote rates in PluginHive for Couriers Please, or do I need to use whole numbers?

Based on observed behavior and testing, Couriers Please API and PluginHive currently require weight input as whole numbers for accurate rate calculation. Entering fractional weights (e.g., 7.8 kg) may cause incorrect rate responses or surcharges only, instead of correct freight charges. It is recommended to round up the weight to the nearest whole number (e.g., 8 kg) before submitting the quote request. This practice ensures the API returns valid and expected rate quotes.

Can I see an example of a JSON request for creating a shipping label with Couriers Please?

Yes, an example JSON payload includes detailed shipment information such as: – Item dimensions and weight – Special instructions – Rate card ID – Pickup and destination contact details (names, company, email, address, phone) – Reference number – isATL (Authority To Leave) boolean flag Example snippet: “`json { “items”: [ {“length”:10,”width”:10,”height”:10,”physicalWeight”:2,”quantity”:1} ], “specialInstruction”: “[email protected]”, “termsAccepted”: true, “dangerousGoods”: false, “rateCardId”: “TD3”, “pickupFirstName”: “Couriers”, “pickupLastName”: “Please”, “pickupEmail”: “[email protected]”, “pickupAddress1”: “Unit 2, 5 Test Street”, “…”: “…”, “isATL”: false } “` Note: This is for reference; PluginHive is working towards JSON integration but currently prioritizes XML fixes.

Can I select multiple Couriers Please shipping services individually to exclude the “Multiple Items” service and control service display at checkout?

Yes, you need to individually select which Couriers Please services to show: 1. Navigate to the Rate Automation rules section of the PluginHive app. 2. Instead of enabling all Courier Please services at once, manually enable only the specific services desired to appear at checkout. 3. Exclude undesired services like “Multiple Items” by deselecting them. 4. The app currently does not support selecting multiple services simultaneously via bulk checkbox; selection is per service but you can enable multiple services one-by-one. 5. This granularity helps prevent confusing or inaccurate options from showing and allows customizing shipping options based on your business needs. 6. Maintain clear automation rules reflecting the exact shipping services per shipping class or criteria you defined.

Can the “isATL” (Authority To Leave) parameter be configured for Couriers Please shipping label requests in PluginHive?

Originally, PluginHive was passing “isATL” as true by default following carrier team’s recommendation, causing labels to be created with Authority To Leave enabled. They acknowledged customer requests to set this to false (disabling ATL) for signature-required shipments. PluginHive has: – Released an update for Couriers Please to reflect these changes. – Introduced an option in the app settings to enable or disable the Authority To Leave (ATL) service on labels. You can now configure the ATL option from the PluginHive app settings page to true or false according to your requirements.

Can the PH MultiCarrier Shipping Label app show shipping rates from multiple carriers, such as Couriers Please and MyPost Business, simultaneously at Shopify checkout?

Yes, the PH MultiCarrier Shipping Label app can display shipping rates simultaneously from multiple carriers at checkout. For example, you can show both Couriers Please and MyPost Business rates together, allowing customers to select their preferred carrier and shipping option during checkout once the ‘Carrier Calculated Shipping’ feature is enabled on your Shopify store.

Did PluginHive make changes that could affect Couriers Please rate calculations when a TDKG rate issue was resolved?

No changes were made by PluginHive that affected the Couriers Please rate calculations. The resolution of the TDKG rate issue was due to external factors, likely on the Couriers Please API or system side. Users are advised to monitor transactions closely for any recurrence and report if problems return.

Has the Couriers Please “250 Gram Parcel (TD250)” service been added to PluginHive, and how can I use it?

Yes, PluginHive has enhanced the app to include the Couriers Please “250gm Parcel” service. You can now use it to show rates at checkout and generate shipping labels for your orders. Please test this service and inform the PluginHive team if you encounter any issues. For support or assistance, you may schedule a Zoom call with PluginHive.

How can I confirm that the Couriers Please L11 service is correctly functioning and showing accurate shipping rates in PluginHive?

To confirm proper functioning of the L11 service: 1. Ensure your PluginHive app is updated to the latest version with L11 service mapping included. 2. Check your shipping automation rules to confirm the L11 service is selectable and included. 3. Perform test transactions using products and shipping addresses where L11 service should be available. 4. Verify that L11 appears in the checkout shipping options with dynamic rates rather than flat or missing rates. 5. Examine transaction summaries and compare shipping rates with the courier-provided rates for accuracy. 6. If discrepancies or missing services occur, report immediately to PluginHive support for further assistance and confirmation. Following these steps will confirm that the L11 service is fully integrated and providing reliable, real-time shipping quotes as intended.

How can I confirm that the Couriers Please L11 service is now correctly mapped in PluginHive and available for use?

The service mapping for all Couriers Please services, including the L11 service, has been completed and integrated into PluginHive. To confirm and use the L11 service: 1. Update your PluginHive app to the latest version where the inclusion of L11 and other new courier services is available. 2. Check your shipping settings or perform a test checkout to see if the L11 service appears as a shipping option. 3. Verify that dynamic shipping rates are being calculated for L11 instead of falling back to flat rates or showing “undefined.” 4. If you encounter any issues or the service does not appear, contact PluginHive support for further assistance. This confirms that you can now utilize the L11 service with accurate, mapped shipping rates within your store.

How can I ensure PluginHive support can effectively troubleshoot multi-package rate failures with CouriersPlease TCKG?

To help PluginHive support diagnose issues related to CouriersPlease TCKG multi-package shipments, provide the following: 1. Transaction request IDs where rate failures occurred (examples such as “2a61f8aa1fbe2292d03d58be0ce9c65f”). 2. Specific examples of multi-package shipments triggering errors, including products, quantities, and package weights. 3. Collaborator access to your Shopify store granted to the PluginHive support team’s designated email, enabling them to review your app configurations and logs. 4. Any courier communication or official documentation explaining the carrier’s rate calculation policies and requirements. 5. Timely responses to follow-up questions posed by support for faster resolution. Supplying this detailed information facilitates thorough investigation and more precise troubleshooting outcomes.

How can I ensure that the Couriers Please L11 service is correctly mapped in PluginHive to replace the deprecated L22 service and provide dynamic shipping quotes?

To have the new Couriers Please L11 service correctly mapped in PluginHive as a replacement for the deprecated L22 service and receive dynamic shipping quotes instead of flat rates, follow these steps: 1. Confirm with PluginHive support that the L11 service is the intended replacement for L22 in your courier agreement. 2. Inform PluginHive support that flat rate shipping is not feasible due to variation in package sizes and that dynamic shipping quotes are required. 3. PluginHive’s development team will prioritize implementing the L11 service mapping to enable dynamic quotes. 4. Wait for PluginHive to release the update, which is typically announced and deployed by end of day (EOD) as per communication. 5. Once notified, update your PluginHive app to the latest version to activate the new L11 service with dynamic shipping rate calculations. This process ensures accurate, real-time shipping rates based on package dimensions and weight, avoiding reliance on flat rate approximations.

How can I ensure that the Couriers Please L11 service replaces the old L22 service in PluginHive to show accurate shipping rates?

To have the new L11 service from Couriers Please properly reflected in PluginHive in place of the deprecated L22 service, you need to: 1. Report the change to PluginHive support, specifying that the L22 service has been replaced by L11 in your courier agreement. 2. PluginHive will verify with their development team to map the L11 service code correctly within the system. 3. Upon completion, PluginHive will include this mapping in an upcoming app update. 4. After receiving notification, update your PluginHive app to the latest version to have L11 service appear correctly during checkout. In the meantime, you can use custom flat rates as a temporary solution until the official mapping is complete.

How can I ensure that the shipping prices shown to customers match the actual prices charged by Couriers Please to avoid financial discrepancies?

To better align the shipping prices displayed at checkout with the actual charges from Couriers Please: 1. Review and update your shipping rate automation rules to ensure the services and pricing structures match those offered by Couriers Please. 2. Verify that only valid courier services supported by Couriers Please are selected in your rules (e.g., replace any outdated or unsupported service names such as “General L22” with currently supported services like “Road Express”). 3. Confirm that custom handling fees (e.g., a flat $5 fee) are correctly applied in your automation rules. This can be done at **App Settings → Shipping Rates → Rate Automation**. 4. Run test transactions and compare fees from the app with rates obtained directly from Couriers Please to validate accuracy. Regularly auditing and updating the automation rules reduces the risk of undercharging and unexpected costs on your monthly invoice.

How can I process shipments and book orders using the PluginHive app for Couriers Please and Australia Post after generating labels?

To process orders and book shipments through the PluginHive app: 1. Generate the shipping label in the app for the order. 2. After label generation, fulfill the order in your platform (e.g., Shopify). 3. Confirm the shipment booking within the app if required. Be careful not to cancel shipments accidentally in the app, as canceling will void the booking and require manual reprocessing. 4. Refer to the detailed setup and usage guide here: https://www.pluginhive.com/knowledge-base/setting-up-shopify-multi-carrier-shipping-label-app/ 5. Follow the instructions for each carrier’s booking process, as they may differ slightly. 6. If you encounter issues where booking is not reflected or the shipment cannot be processed after label generation, check for product and order data correctness (e.g., dimensions, addresses). 7. Contact support if bookings fail persistently, providing order details for investigation. Proper adherence to these steps ensures successful label printing and shipment booking within the app.

How can I report and escalate the Couriers Please API certificate validation issue to PluginHive support?

When contacting PluginHive support for this issue: – Share detailed error logs showing the “unable to verify the first certificate” message and the associated API endpoint URL. – Provide your store details (store URL, carrier setup, and subscription plan) and specific transaction request IDs where errors occurred. – Share any correspondence and contact emails you have with Couriers Please technical support to enable PluginHive to liaise directly with them. – Request PluginHive to follow up with Couriers Please on your behalf regarding API SSL issues and keep you informed of progress and resolution.

How can I resolve or work around the issue of CouriersPlease shipping rates not showing for orders with more than 10 boxes in PluginHive?

To address this: 1. Confirm the total number of packages in your order. If it exceeds 10, consider splitting the order into smaller shipments with 10 or fewer boxes each for rate retrieval and booking in PluginHive. 2. Alternatively, contact PluginHive support to discuss your shipping needs. They may investigate carrier API capabilities or explore possible solutions to handle larger orders. 3. If immediate rate visibility or booking for large orders is critical and cannot be split, you may need to continue booking such orders directly on the CouriersPlease website until the integration can support higher package limits. 4. For further assistance, schedule a call with PluginHive support using their booking link to explore personalized solutions and clarify limitations.

How can I resolve the issue of missing or incorrect Couriers Please TCKG service name in the shipping rates shown to customers?

The Plugin Hive team needs to update the app to include the new TCKG services in their Courier Please service list. Once included, these services will be properly named and displayed at checkout. In this case, Plugin Hive added the “TCKG – Road Express” service to the app, enabling it to appear correctly in checkout rates. After the app update, you should test the checkout using a VPN with an Australian IP to confirm the TCKG service is shown properly.

How can I test and confirm that the new Couriers Please TCKG service is available and displaying correctly to customers using the Plugin Hive app?

1. Use a VPN to simulate browsing from within Australia to ensure location-specific shipping rates are fetched accurately. 2. Perform a test checkout on your store with a valid Australian shipping address. 3. Review the available shipping services displayed at checkout. 4. Confirm that the “TCKG – Road Express” or other relevant Couriers Please services appear properly with their correct service names and rates. If the service is still missing or incorrectly displayed after these steps, reach out to Plugin Hive support for further assistance.

How can I test the newly added Couriers Please “250gm Parcel” service or Authority To Leave toggle in PluginHive?

To test new features: 1. Place a test order in your store that uses the Couriers Please carrier. 2. In PluginHive app, check if “250gm Parcel” service appears in the shipping options or rates. 3. Generate shipping labels for this test order. 4. If testing ATL functionality, enable or disable the setting accordingly before label generation. 5. Verify labels reflect the selected service and ATL status. 6. Report any discrepancies or issues to PluginHive support for assistance.

How can I troubleshoot incorrect quote rates for the “Items Over 5 Kgs / TDKG” rate when using Couriers Please API in PluginHive?

To troubleshoot incorrect quote rates for the “Items Over 5 Kgs / TDKG” rate with Couriers Please API: 1. Verify the exact weight value sent in the API request. The API may handle fractional weights differently; try inputting the weight as a whole number (e.g., 8 kg instead of 7.8 kg). 2. Enable the “signature option” on the Couriers Please website and observe if the rates returned by the API change or appear correctly. 3. Test the quote with standalone rate automation to isolate the problem from other rate calculations. 4. Monitor the API responses for specific RateCardCode and RateCardDescription values to verify if surcharges or expected freight charges are included. 5. Contact Couriers Please API support to confirm if there are any ongoing issues or changes affecting the TDKG rate. 6. After any changes, continue testing multiple transactions to confirm if the issue resolves or reoccurs. 7. If issues persist despite correct input, plugin support can assist further with logs and settings.

How do I activate my myEzySend account and provide the necessary Couriers Please credentials to complete the setup?

To activate your myEzySend account and complete the setup with Couriers Please, follow these steps: 1. You need to obtain your Couriers Please Account credentials, specifically your Account Number and API Key (Token). 2. Contact your Couriers Please Account Representative or their support team to request these credentials. 3. Once you receive your Account Number and API Key from Couriers Please, inform the PluginHive support team. 4. PluginHive can then assist you further, including offering a Zoom session to help you complete the app setup using the credentials. Ensure you have these details ready, as the app requires them to integrate with Couriers Please and fully activate your account.

How do I enable or disable Authority To Leave (ATL) for Couriers Please shipments in PluginHive?

PluginHive has added an “Authority To Leave” toggle in the app settings for Couriers Please carrier. To configure it: 1. Open PluginHive app settings. 2. Locate the Couriers Please carrier settings. 3. Find the “Authority To Leave” option. 4. Enable to allow ATL or disable for signature-required delivery. 5. Save changes. For older orders without “isATL” passed, the shipment is considered as signature required by default. For new orders, the isATL flag will be set based on your configuration.

How do I properly configure Label Automation Rules for CouriersPlease to avoid rate failures?

For Label Automation Rules related to CouriersPlease, follow these steps to avoid rate failure issues: 1. Understand that there may be multiple similar services (e.g., three different “1Kg parcel” services). 2. Add all relevant service variants in your automation rule rather than enabling just one service. If only one service is selected and that particular service code is not returned by the carrier’s API, no label rate or shipping option will appear. 3. Update the automation rule by selecting all the applicable CouriersPlease services to increase the chances of valid rates and labels being returned. 4. Save your automation rule configuration. 5. Verify by placing a test order that the appropriate labels and rates are generated successfully.

How does PluginHive handle communication and issue resolution between customers and Couriers Please?

PluginHive acts as an intermediary by: – Escalating technical issues and error messages to Couriers Please support team. – Maintaining email communication threads including customer and carrier support. – Sharing diagnostic XML/JSON payloads and error logs. – Requesting input from Couriers Please development. – Asking customers to share or follow up with Couriers Please contacts directly to hasten resolution. This collaborative approach helps resolve integration issues efficiently.

How does PluginHive handle multi-package shipments with CouriersPlease TCKG regarding rate requests, and why can’t separate rate requests be submitted for each package?

PluginHive sends a single rate request per transaction to the carrier, whether the shipment contains one or multiple packages. This is the standard process for obtaining shipping rates and aligns with carrier portals and API usage across nearly all carriers. Creating separate rate requests for multiple packages in a single transaction is not feasible or supported by CourierPlease’s carrier API or PluginHive’s app. Shipments with multiple packages are treated as a single entity with one combined shipping cost, and individual packages within that shipment receive their own labels but without separate pricing or rate requests. Thus, splitting one order into multiple shipments—each with its own shipping cost and label through automated separate rate requests—is not supported by PluginHive or most native Shopify apps due to technical API limitations and potential fulfillment complications.

How should I configure the automation rule for Couriers Please services if I am unsure which specific services apply to my account?

If you are unsure which specific Couriers Please services apply, you can set the offered services in your automation rule to “ALL.” This configuration attempts to include all available services returned by the Courier Please API. However, note that some newly added or unsupported services may not display proper names unless the app’s service list is updated by Plugin Hive to include them. Regularly check for app updates or announcements related to supported services to ensure full compatibility.

How should I handle multi-package shipments with CouriersPlease TCKG to get successful shipping rates using PluginHive?

To obtain successful multi-package rates for CouriersPlease TCKG using PluginHive, follow these steps: 1. Submit separate rate requests for each individual package rather than sending one combined request with all packages. 2. Ensure each package’s weight is within the 25 kg limit set by TCKG. 3. Aggregate or sum the individual rates returned from each separate request within your store or app. 4. Display the total combined shipping cost to the customer at checkout reflecting the sum of individual package rates. This approach aligns with CouriersPlease’s expected API usage and prevents rate failures caused by exceeding weight limits in a single combined request.

How to ensure PluginHive generates labels successfully when using CouriersPlease shipping services?

To ensure labels generate correctly: 1. Navigate to PluginHive’s automation rules for CouriersPlease labels. 2. Include all relevant services (including all variants of the same named parcel service) in your rule, rather than a single service. 3. Do not remove the PluginHive app from your Shopify shipping profile, even if you are not displaying carrier rates at checkout. 4. Confirm your label automation rule is saved and active. 5. Place a new test order and attempt label generation. 6. Monitor XML responses from the carrier in case adjustments to service selection are needed. 7. If label creation still fails, review logs or contact support with detailed information about the automation rule settings and carrier responses.

I can book an order with more than 12 boxes directly on the CouriersPlease website, so why can’t I do the same through PluginHive?

Although you can book large orders directly via the CouriersPlease website without issue, the PluginHive integration relies on the carrier’s API, which enforces a strict package quantity limit (currently 10 boxes per order). This discrepancy happens because direct bookings may bypass certain API restrictions or handle data differently. PluginHive’s system must adhere to these API limits, which can prevent booking or rate retrieval for orders exceeding the allowed package count through the PluginHive platform.

I have installed the Couriers Please app on my Shopify site, but it is not showing next to my orders. How do I correctly set it up so that orders show with a courier service assigned?

To set up Couriers Please and have your orders show with the courier service assigned, follow these steps: 1. Navigate to the PluginHive app settings in your Shopify admin. 2. Go to **App Settings -> Automation -> Setup**. 3. Check for any existing automation rules based on price or other criteria. 4. Disable duplicate or conflicting automation rules to avoid conflicts. 5. Enable all relevant courier services within the active automation rule to cover your shipping options. 6. After these changes, your orders should show a “Processing” status with the courier service assigned accordingly. 7. Verify in the orders section that each order is linked with the respective courier service.

If I manually add tracking information in Shopify for Aramex or Couriers Please shipments, why are delivery status updates not received or displayed?

Manual upload of tracking numbers in Shopify does not trigger delivery status updates because those live status updates come from the carrier API integration present in the PluginHive app. Only tracking numbers pushed and synced via the app’s integrated API connection will provide ongoing delivery status updates from the carrier.

Is PluginHive planning to support JSON API requests for Couriers Please instead of XML?

PluginHive recognizes the value of supporting JSON API requests due to current issues with XML processing on the carrier side. However, implementation of JSON requests represents major development work and is planned for the future. For now, PluginHive focuses on resolving XML-related issues to provide quicker fixes.

Is the Authority To Leave (ATL) option currently available in PluginHive for Couriers Please, and how can I enable it?

Yes, PluginHive has introduced the Authority To Leave option. You can enable or disable it directly from the PluginHive app settings for Couriers Please. This feature allows you to control whether your shipments require a signature or allow drop-off without signature.

Is there a workaround for the Couriers Please API issue with XML requests failing while JSON requests work?

Yes, Couriers Please reported issues processing XML requests, whereas JSON requests are functioning properly. However, PluginHive currently does not fully support JSON API requests and considers this a substantial development effort. Meanwhile, PluginHive is working on fixing the XML API issues to provide a quicker resolution. They will update the app accordingly and notify when available.

What alternatives exist if I want to ship orders over 25 kg with CouriersPlease TCKG using PluginHive, given the single-request limitation?

Since automated multi-package rate requests exceeding 25 kg aren’t supported, consider these alternatives: 1. **Restrict Order Weight at Checkout:** Configure Shopify’s checkout or shipping settings to prevent orders over 25 kg. Customers placing orders exceeding this weight will not see a shipping rate. Include a clear message advising them to either place multiple separate orders or contact support for manual assistance. 2. **Manual Separate Orders:** Advise customers to create two or more separate orders below the 25 kg threshold to ensure successful rate calculation. 3. **Manual Label Creation for Heavy Orders:** For orders over 25 kg, generate a shipping label inside PluginHive for a 25 kg portion using TCKG rates. Handle the remaining weight by manually creating additional shipments and labels directly through the carrier’s portal outside the app. 4. **Adjust Checkout Shipping Rates:** For weights exceeding 25 kg, plan alternative shipping options or flat rates for checkout, since TCKG rates won’t be available for these orders. These manual or semi-manual workarounds maintain compliance with carrier API limitations and avoid automation conflicts.

What are the necessary steps to integrate and configure the PH MultiCarrier Shipping Label app to show exact shipping rates from MyPost Business and Couriers Please on Shopify checkout, including adjusting costs based on package size?

To integrate and configure the app for exact shipping rates and variable costs based on package size, follow these steps: 1. Ensure your Shopify store has the ‘Carrier Calculated Shipping’ feature enabled (usually requires Shopify Plan with yearly billing). Contact Shopify support to confirm or activate this. 2. Install and set up the PH MultiCarrier Shipping Label app in your store. 3. Configure your shipping carriers (MyPost Business and Couriers Please) within the app by inputting necessary account details and rate rules. 4. Set package size and weight parameters in the app to allow dynamic cost adjustments based on the package dimensions or weight. 5. Test the checkout rates to confirm the app displays the accurate carrier-calculated shipping costs dynamically according to delivery region and package specifications. 6. If you encounter any difficulties during setup, you can request a Zoom call with PluginHive support for personalized assistance.

What can I do if I want live assistance from PluginHive to resolve multi-package shipping rate issues with CouriersPlease?

To receive real-time support from PluginHive for multi-package rate or other complex setup issues: 1. Use the appointment scheduling link provided by PluginHive support or reply directly via email/message requesting a call. 2. Specify your preferred date, time, and time zone for the meeting. 3. Join the scheduled session via the Zoom link or phone call provided. 4. During the call, discuss your issues and get hands-on troubleshooting and guidance from the PluginHive technical team. Scheduling live support calls helps clarify issues more quickly and ensures personalized assistance for your integration setup.

What does the error “unable to verify the first certificate” mean when trying to get rates from CouriersPlease API, and how can it be resolved?

The error “unable to verify the first certificate” indicates that the SSL/TLS certificate chain presented by the CouriersPlease API endpoint (https://api.couriersplease.com.au) could not be verified by the client making the request. This usually means there is an issue with the server’s SSL certificate configuration, such as a missing intermediate certificate or an invalid certificate. To resolve this issue: 1. Verify the API endpoint’s SSL certificate chain externally using tools like SSL Labs’ SSL Test (https://www.ssllabs.com/ssltest/) to identify any certificate chain problems. 2. Contact CouriersPlease technical support or their API provider team to inform them of the certificate verification failure and request that they fix the server certificate configuration if needed. 3. On the client side, ensure your system has up-to-date root CA certificates. This can be done by updating your operating system’s CA bundle or your programming environment’s trusted CA store. 4. As a temporary workaround (not recommended for production), you may configure your API request client to ignore SSL certificate validation errors, but doing so exposes security risks. 5. Once CouriersPlease fixes their certificate chain, retry the API request to confirm the issue is resolved. If you continue to face errors after these steps, provide detailed error logs and environment specifications to CouriersPlease support for further investigation.

What happens if the isATL field is missing in shipping label requests to Couriers Please?

If the isATL field is missing in a label request (common for older orders imported previously), Couriers Please treats the shipment as signature required delivery by default (i.e., ATL disabled). For all new orders processed using the updated PluginHive app, isATL will be explicitly set to true or false based on your app configuration.

What is the current status of the investigation regarding multi-package TCKG rate failures with CouriersPlease?

PluginHive has contacted the CouriersPlease team for clarification about multi-package TCKG rate failures and is actively following up for updates. No response has been received from CouriersPlease yet, and the support team will inform you immediately once they have further information. Meanwhile, it is recommended to implement the separate request approach for individual packages to mitigate the problem.

What should I do if I experience a sudden change or disruption in Couriers Please rate responses through PluginHive?

If you encounter sudden changes or disruptions: 1. Verify your input parameters such as weight, dimensions, and destination details. 2. Test with both fractional and whole number weights to identify input sensitivity. 3. Reconfirm any optional parameters or features enabled on the carrier website. 4. Contact Couriers Please support to check for API issues or downtime. 5. Report your findings along with API request and response samples to PluginHive support for troubleshooting. 6. Monitor transactional quotes over several times to ensure the issue is stable or resolved.

What should I do if I want to keep flat shipping rates at checkout but the CouriersPlease API returns “There are no valid services available”?

If you choose to keep flat rates at checkout instead of showing carrier rates, but still need to generate labels via PluginHive, make sure: 1. Even though rates are disabled in your Shopify checkout settings, the PluginHive app’s automation rules for CouriersPlease should be configured correctly to fetch available services for labels. 2. Avoid disabling or removing the app rates from your shipping profile entirely because that can cause the API to return no services. 3. Configure all relevant services in the Label Automation rules in the app, so label creation works properly when fulfilling orders, independent of checkout rates. 4. Test by creating labels manually or via automated sync to ensure labels can be generated without checkout rate display. If the issue persists, review the XML responses (carrier replies) to check which services are returned and adjust automation rules accordingly.

What should I do if PluginHive is unable to generate labels or get shipping quotes from Couriers Please, and shows data validation or XML errors?

When facing label creation errors like “Error converting value {null} to type ‘System.Boolean'” or data validation errors: 1. Forward detailed error responses and order numbers to PluginHive support. 2. PluginHive will escalate the issue to Couriers Please developers for investigation. 3. Coordinate with Couriers Please support (e.g. [email protected]), sharing error details and requests for updates. 4. Track communication between both teams until a fix is applied on the carrier’s API.

What should I do if the Couriers Please API issue persists and PluginHive has not yet provided a resolution?

You should: 1. Follow up directly with Couriers Please support, using the provided contact ([email protected] or other contacts shared). 2. Share PluginHive’s case details and error messages with Couriers Please to expedite investigation. 3. Keep PluginHive support informed about any updates or responses from Couriers Please. 4. Continue collaboration between PluginHive and Couriers Please teams until the issue is resolved.

What steps can I take to resolve the Couriers Please rate quoting and label creation errors in PluginHive?

To troubleshoot and resolve this issue, follow these steps: 1. Confirm with Couriers Please support whether there are known issues or changes to their API SSL certificate or endpoints (this has been initiated with [email protected] and their technical team). 2. Provide PluginHive with your Couriers Please contact details so they can directly coordinate with Couriers Please technical support to resolve SSL or API issues. 3. Verify your store’s “from” address and credentials for Couriers Please are correctly configured in PluginHive, ensuring no duplicate or incorrect entries. 4. Wait for PluginHive’s development or support team to confirm that the SSL certificate chain on Couriers Please’s API endpoint is updated correctly and recognized by PluginHive’s system. 5. Retest the rates and label generation after confirmation that the certificate-related issue is resolved on Couriers Please’s side.

What steps has Plugin Hive taken to address the Couriers Please TCKG service naming issue in the app?

Plugin Hive reviewed the issue where the TCKG service was missing from the app service list, then enhanced the app by adding the “TCKG – Road Express” service to the Courier Please carrier profile. This update allows the app to recognize and display this service name properly during real-time rate fetching and customer checkout.

What steps should I take if I notice a discrepancy between rates or booking capabilities on the CouriersPlease website versus PluginHive?

To troubleshoot discrepancies: 1. Verify the order details (number of packages, weight, dimensions) are identical in both PluginHive and directly on CouriersPlease’s website. 2. Check the courier’s API limitations, including maximum package count, which may differ from the website’s direct booking system. 3. Document examples of orders that show this discrepancy, including screenshots if possible. 4. Contact PluginHive support with order details to escalate the issue. They may perform a detailed comparison to understand the root cause and inform you of current functionality limitations or possible workarounds.

What steps should I take if I notice rate calculation issues with Couriers Please “TDKG” service in PluginHive?

Follow these steps to address rate calculation issues for the TDKG service: 1. Isolate the problem using standalone rate automation or a test environment to ensure other rates are unaffected. 2. Double-check the API request payload, especially weight, dimensions, and locations, to ensure accuracy. 3. Enable any optional features on the carrier website, such as signature requirements, as these may influence rates. 4. Perform tests by adjusting weights, using whole numbers to see if quotes improve. 5. Contact Couriers Please support to verify if their API is functioning correctly or if there are reported issues. 6. Keep PluginHive support informed with sample requests and responses to assist with deeper analysis. 7. Continue monitoring the issue after any fixes, retesting multiple shipments to ensure stability.

What support is available if I still face issues after the ATL option is configured correctly for Couriers Please in PluginHive?

If issues persist after configuring ATL: – Provide specific order numbers with problems to PluginHive support. – Share any error messages or discrepancies observed. – PluginHive can then engage Couriers Please support for deeper troubleshooting. – Scheduling support calls or sending debug information can assist faster resolutions. PluginHive customer support remains available for ongoing help.

When performing a mock purchase as a customer, I only see the “express” shipping option for Couriers Please, but I expect to see other options based on my settings and free shipping over $40. Why is this happening?

The reason you only see the “express” shipping option at checkout is that Shopify is currently showing rates based on its default shipping profile, not dynamically fetching rates via the Couriers Please app. To display real-time rates from Couriers Please at checkout, you need to: 1. Upgrade your Shopify store plan to the Shopify plan or any higher-tier plan that supports carrier-calculated shipping. 2. Contact Shopify support to have the **Carrier Calculated Shipping** feature enabled on your store. This feature allows third-party apps like PluginHive Couriers Please to display real-time courier rates during checkout. 3. Once enabled, the checkout will dynamically display all available Courier Please shipping options, respecting your shipping rules including free shipping thresholds. Until these steps are completed, checkout will continue to show only the shipping options defined in Shopify’s native shipping profiles.

Why am I encountering the “UNIDENTIFIED_ERROR” when trying to get shipping rates or create labels with Couriers Please in PluginHive?

The “UNIDENTIFIED_ERROR” usually indicates an issue on the Couriers Please API side. In this case, the PluginHive team confirmed they needed to contact Couriers Please for clarification and resolution. You should share any relevant error messages, such as Request Id or error XML, and coordinates communication with Couriers Please support. PluginHive has reached out to Couriers Please and suggests that you follow up with them as well to expedite the resolution.

Why am I getting a 500 Error generating a CouriersPlease shipping label via the PluginHive app, even though the label appears successfully on the CouriersPlease backend?

The 500 Error during label generation with CouriersPlease in the PluginHive app is due to an ‘UNIDENTIFIED_ERROR’ occurring internally when processing the order in the app, while the CouriersPlease backend processes the label correctly. This issue can happen if orders are manually fulfilled within the app, preventing the app from properly retrying or regenerating labels. To troubleshoot: 1. Confirm if the order was manually fulfilled in the PluginHive app. Manual fulfillment blocks automated label retries. 2. Compare XML data of failed and successful label generation attempts; if no differences are evident, the issue likely relates to order processing status or app connection rather than data errors. 3. Try processing new orders entirely through the PluginHive app without manual fulfillment to see if label generation succeeds. 4. Share any label files generated on the CouriersPlease dashboard with support for additional analysis. 5. If issues persist, contact PluginHive support with order details for deeper investigation.

Why am I getting an error message “Error converting value {null} to type ‘System.Boolean'” when generating a label with Couriers Please, and how can this be resolved?

This error typically occurs because the shipment request is missing the mandatory `

Why am I not seeing shipping rates from CouriersPlease for orders with more than 12 boxes when using PluginHive?

CouriersPlease imposes a restriction on the maximum number of packages/boxes per order when rates are requested via their API integration with PluginHive. Specifically, the carrier limits the total package quantity to 10 or fewer. If your order exceeds this threshold (for example, 14 boxes), PluginHive will not receive shipping rates from CouriersPlease for that order due to this quantity limit set by the carrier’s API. This limitation explains why rates do not appear for large orders through PluginHive.

Why am I receiving a 500 error with the “Unidentified Error” code when requesting Couriers Please rates and creating labels via PluginHive?

The 500 error with the “Unidentified Error” message typically indicates a server-side or API-level issue when PluginHive tries to fetch rates or create labels from Couriers Please. A common cause is an SSL certificate verification failure on the API endpoint during the rate request. Specifically, PluginHive logs show an error “unable to verify the first certificate” for the URL https://api.couriersplease.com.au/v2/domestic/quote. This means PluginHive’s system cannot properly verify Couriers Please’s API SSL certificate, causing the rate request and label creation to fail with a 500 error.

Why am I unable to add the Couriers Please L11 service to my rate automation rules in PluginHive, and how can this be resolved?

If the L11 service does not appear in your rate automation rules, it is likely due to improper configuration or incomplete mapping of the service within PluginHive. To resolve this: 1. Verify that your PluginHive app is updated to the latest version where L11 service mapping has been included. 2. Confirm that your rate automation rules are properly configured—incorrect rule setup can prevent new services from showing. 3. Clear your website cache and test in an incognito browser window to avoid cached data interference. 4. If L11 still does not appear, report the issue to PluginHive support with complete details and screenshots, if possible. In the referenced case, PluginHive support identified misconfiguration in automation rules and corrected them, enabling rates to show at checkout. However, the L11 service specifically may require a further investigation by the development team to ensure it is mapped correctly and available for selection in automation rules.

Why are CouriersPlease shipping rates not showing in my Shopify checkout and how can I fix it?

The likely cause is that the shipping rates from the CouriersPlease app are disabled in your Shopify shipping settings, or the automation rules in the PluginHive app are configured to enable only specific services whose rates are not available. To resolve this: 1. Go to your Shopify Admin > Settings > Shipping and Delivery > Shipping Profile. 2. Ensure you have added the shipping rates from the PluginHive app in your Shipping Profile by clicking “Add Rate” and selecting the app rates. This allows rates to be fetched dynamically at checkout. 3. In the PluginHive app, review the Rate Automation rules for CouriersPlease. If only one service (for example, a 1Kg parcel service) is enabled, and that service code is not returned by the carrier’s API for certain orders, no rates will appear. 4. Enable all relevant services in the automation rule to ensure fallback services are available. This has been shown to fix the “There are no valid services available” error. 5. Save the changes. Then, test with a new order to confirm that the rates appear correctly at checkout.

Why are shipping fees for Couriers Please not being generated or shown at checkout even though the service is enabled and the rate is provided in the XML response?

Shipping fees for Couriers Please may not be generated or shown at checkout due to incomplete or missing mapping of certain services within the PluginHive system. For example, the Couriers Please Road Express service will not appear if it is not fully configured or mapped on the platform. In this case: 1. Verify that the service is enabled in the rate automation rules. 2. Confirm that the shipping rate is returned correctly in the response XML. 3. Check whether the specific Couriers Please services you want to use are fully integrated and mapped in PluginHive. 4. Certain services like TSKG are not yet mapped and will only be available after specific system updates. If you encounter missing services or shipping methods, contact PluginHive support to confirm service mapping status and any necessary configuration steps to enable them fully.

Why are TCKG rates failing for multi-package shipments when using the PluginHive Multi Carrier Shipping Label App with CouriersPlease in Australia?

The TCKG service has a maximum weight limit of 25 kg per package. When creating multi-package shipments, the PluginHive app currently sends a single rates request containing all package details combined. However, CouriersPlease checks the total combined weight in that single request rather than individual package weights, causing the rates request to fail if the combined weight exceeds 25 kg. The failure happens because the total weight exceeds TCKG’s maximum allowed weight, even though each individual package meets the limit.

Why does editing package sizes before generating a shipping label cause an error, specifically when changing the dimensions to 20x20x20 cm for order #s30180 using CouriersPlease service?

The issue occurs because the current shipping integration with CouriersPlease via PluginHive does not support manual editing and updating of package dimensions once the order is in the shipping label generation process. This limitation is specific to the CouriersPlease carrier service. To work around this: 1. Verify if the package dimensions are correctly set in the original order before starting the label generation process. 2. Ensure that the package size is within the allowed dimension limits set by CouriersPlease to avoid validation errors. 3. If package dimensions must be changed after the label generation initiation, cancel or delete the current label and re-enter the updated package size before generating a new label. 4. For persistent issues, review the PluginHive settings related to CouriersPlease integration or contact support for assistance, providing the order number and exact error details. Note: Currently, direct manual editing of package sizes during the label creation step is not supported for orders shipped via CouriersPlease using PluginHive.

Why does my label creation fail with an error about converting value {null} to type ‘System.Boolean’ in the Couriers Please API?

This error indicates that a required boolean field is missing or improperly formatted in the API request payload sent to Couriers Please. Likely causes include: – Missing values in fields expected to be true/false. – Passing null or empty values where boolean is required. To resolve: 1. PluginHive is working with Couriers Please to identify and correct the required fields. 2. Share order details and error messages with PluginHive support. 3. Await updates to PluginHive app reflecting correct handling of these fields.

Why does the app split shipping types and show “Road Express” instead of my provider “CouriersPlease”?

“Road Express” is a specific shipping service offered by CouriersPlease. When the app detects shipments using the Road Express service, it labels them accordingly to reflect the exact service used. This means that even though your general provider is CouriersPlease, the app distinguishes between different service levels or options they offer, such as Road Express, for accurate tracking and management.

Why does the TCKG service rate fail to show for multi-package shipments when shipping with CouriersPlease via PluginHive?

The TCKG service has a maximum weight limit of 25 kg per package. When multiple packages are shipped (for example, 11 quantities of a 2.5 kg product split into two packages), PluginHive currently sends a single rate request containing all packages combined. However, CouriersPlease evaluates the total combined weight instead of individual package weights, causing the rate request to fail if the total weight exceeds 25 kg, even if each individual package is within the limit. This weight aggregation conflicts with CouriersPlease’s requirement for separate requests per package.

Why is the Couriers Please TCKG service not displaying correctly in Plugin Hive Multi Carrier Shipping Label and showing the automation rule title instead of the service name?

The Couriers Please TCKG service is a new service not yet listed in the app’s predefined Courier Please service list. Because the app lacks this service name mapping, the automation rule title is shown instead of the actual service name at checkout. The rate information is correctly received from the Couriers Please API, but without a matching service name in the app, the system defaults to displaying the rule name as the service name.

Why might the PluginHive app not select the lowest shipping rate from multiple rates returned by a carrier like Couriers Please?

Some carriers, including Couriers Please, may return multiple shipping rate options in the API response. The PluginHive app selects the appropriate rates based on configured shipping methods and pricing logic; it may not always choose the lowest rate if: 1. Your shipping methods or services configured in the app prioritize specific service levels over cost (e.g., express vs economy). 2. The app filters rates based on rules or minimum service standards defined in your account settings. 3. If you want the app to display the lowest rate among all returned rates, review the shipping method configurations and ensure that all available services are enabled and that no filters exclude lower-cost options. 4. Contact PluginHive support if you require assistance adjusting settings for rate selection behavior.

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

Shopify Multi Carrier Shipping Label App