Blue Dart Shipping FAQs – Multi Carrier Shipping Label App for Shopify
-
Configure Blue Dart rates, labels, and tracking using Shopify
Once you have correctly added the Bluedart account settings in the PluginHive app, including updating the Tracking license key and enabling the production key, your integration is ready to use. You can start shipping with Bluedart through the app immediately. If you use any preferred service for label generation, you should provide the name of that service along with the Product Type and Sub Product Type. This information will allow updating the automation rules accordingly, ensuring smooth label generation and processing.
Yes. If you only want to generate shipping labels, request pickups, and share tracking information for BlueDart shipments, you do not need to register the app or enable the Shopify ‘Carrier Calculated Shipping’ feature. This option does not impact your ability to manage BlueDart shipments through the app, only the ability to show live calculated shipping rates at checkout.
Yes, PluginHive supports configuring multiple courier services including Delhivery and Blue Dart within the same app environment. You can set up both express and surface shipping services as required. During the configuration call or through the app dashboard, you can add and manage accounts for multiple couriers. Make sure you obtain and enter the correct API credentials from each courier provider separately. Once configured, you will be able to generate shipping labels and manage shipments from both services seamlessly. If you need help with adding or switching between courier accounts, PluginHive support is available to guide you.
No, PluginHive cannot support generating return labels with COD for BlueDart shipments either programmatically (API) or through the app because BlueDart’s service does not offer COD options for reverse pickups. Return labels must be created as prepaid shipments to comply with BlueDart’s capabilities.
No, the PluginHive API cannot generate return labels with COD for BlueDart shipments, because BlueDart’s reverse or return shipments do not support COD or ToPay services. All return shipments must be created as prepaid, regardless of whether the original order was COD or prepaid.
To activate the Dart Plus service by Blue Dart as the default shipping service in the PluginHive app, follow these steps: 1. Navigate to **App Settings** in your PluginHive dashboard. 2. Go to **Automation** > **Setup**. 3. Find and edit the **Auto Rule for Blue Dart** automation rule. 4. In the **Action Details** section, remove the ‘ALL’ option from the list of services. 5. Add only the **Dart Plus** service to the rule. 6. Save the changes by clicking **Update the Rule**. 7. After updating, click on the **Re-Run Automation** button to apply the changes to all newly imported orders. This configuration will ensure that all future orders imported into the app will default to Blue Dart – Dart Plus service.
To add and connect your BlueDart account in the PluginHive app, follow these steps: 1. Install the PluginHive Multi Carrier Shipping Label App from the Shopify App Store, if not already installed. 2. Gather your BlueDart account credentials, including: – Customer Code – Origin Service Area Code – Service Center Code (if applicable) – Login ID – Shipping License Key – Tracking License Key 3. Enter these details accurately in the carriers section of the PluginHive app under BlueDart account settings. 4. Upon saving these details, the app will attempt to connect with BlueDart and verify the credentials for successful integration. If you encounter any issues or need assistance with setup, you can schedule a personalized support call with PluginHive by booking an appointment through their provided scheduling link. This allows them to guide you through the setup and confirm successful integration.
To add Blue Dart order tracking on your website, you need to use two different PluginHive apps depending on your needs: 1. **PH Multi Carrier Shipping Label app:** This app is suitable for generating shipping labels, requesting pickups, fulfilling orders, and internal tracking. However, it does not provide customer-facing shipment tracking on your website. 2. **Shopify Shipment Tracking and Notify app:** This app enables your customers to track their shipments directly on your website, providing a customer-friendly tracking interface. If your goal is to allow customers to track Blue Dart shipments on your storefront, this is the recommended solution.
To confirm and update BlueDart License Keys: 1. Contact your BlueDart account representative to obtain valid Production License Keys and Login ID. 2. Test these keys by making sample API requests to the BlueDart endpoint to verify their validity. 3. Update the License Keys and Login ID in your PluginHive BlueDart account settings. 4. Upon updating, the PluginHive app should accept the credentials and switch from Test to Production mode for live rates and label generation. 5. If errors persist, share the request-response logs with PluginHive and BlueDart support for further diagnosis.
Once the Tracking License Key is configured, follow these steps to confirm: 1. Log in to your store’s PluginHive plugin dashboard or shipping settings. 2. Locate the Blue Dart carrier configuration section. 3. Check that the Tracking License Key and API version fields are properly populated with the provided license key (e.g., g51gromqznnkjtkgjghm8kpktrttliqo) and version number (such as 1.3). 4. Conduct a test shipping label or shipment tracking request to ensure that tracking data is fetched without errors. 5. If no errors occur and tracking details are received correctly, the license key is properly set up. If you continue to face issues, contact PluginHive support again with specific error descriptions and logs for further assistance.
To confirm the COD payment option on the shipping label: 1. Verify the order in your system (e.g., order #11017 as a test case). 2. Generate the shipping label through the PluginHive system integrated with BlueDart and Gokwik. 3. Check the generated label’s payment option field; it should explicitly state “COD” if the order is Cash on Delivery. 4. If the label incorrectly shows “Pre-paid,” cancel the label and create a new one after ensuring the correct payment method is selected. 5. Confirm that the system or PluginHive solution includes recent enhancements that support Gokwik COD compatibility for the courier. 6. Enable any new UI features if applicable for the store to facilitate correct label generation. This process ensures that the shipping label accurately reflects the COD payment method as per the latest enhancements.
To confirm the COD payment option on the shipping label: 1. Verify the order in your system (e.g., order #11017 as a test case). 2. Generate the shipping label through the PluginHive system integrated with BlueDart and Gokwik. 3. Check the generated label’s payment option field; it should explicitly state “COD” if the order is Cash on Delivery. 4. If the label incorrectly shows “Pre-paid,” cancel the label and create a new one after ensuring the correct payment method is selected. 5. Confirm that the system or PluginHive solution includes recent enhancements that support Gokwik COD compatibility for the courier. 6. Enable any new UI features if applicable for the store to facilitate correct label generation. This process ensures that the shipping label accurately reflects the COD payment method as per the latest enhancements.
Creating a Blue Dart account must be done directly through Blue Dart. PluginHive cannot create the account on your behalf. You can refer to Blue Dart’s official guides or support resources to understand the signup process. Once you have created the account, you will receive the required details (Customer Code, Login ID, etc.) that you need to input into the PluginHive shipping app to start shipping. If you require guidance during the signup process, PluginHive support can assist you with instructions but cannot perform the account creation for you.
Since BlueDart does not support COD for return shipments, you have two alternatives: 1. **Create a prepaid return label manually via BlueDart portal:** Generate the return shipment as a prepaid shipment directly from the BlueDart web portal. This means no payment will be collected from the customer upon pickup or delivery of the return. 2. **Generate a prepaid reverse pickup via API using PluginHive:** You can generate a reverse pickup as a prepaid shipment by setting the following parameters in your API request: – `IsReversePickup` = true – `IsTopayPickup` = false (to ensure it is prepaid, not COD) This effectively treats the return shipment as prepaid, despite the original order being COD.
To download an existing BlueDart shipping label using the AWB number (e.g., 20877275720), follow these steps: 1. Log in to your BlueDart or integrated shipping portal where your shipments are managed. 2. Navigate to the shipment or waybill tracking section. 3. Enter the AWB number ( 20877275720. in the search or tracking field. 4. Once you locate the shipment, look for options to download or reprint the shipping label. 5. Download the label in PDF or desired format for printing or record-keeping. If your system integrates PluginHive with BlueDart, and the label was generated through PluginHive, you may also find the label within the PluginHive dashboard under the respective order details. Locate order #132618, and download the existing shipping label from there to avoid duplicate generation attempts.
BlueDart does not provide its own international shipping services. Instead, BlueDart has partnered with DHL Express for international shipments. Therefore, you cannot generate labels for international orders directly through the BlueDart service in the app. To enable international shipping, you need to: 1. Obtain a separate DHL Express account for your international shipments. 2. Integrate your DHL Express account within the PluginHive app. This setup allows you to process international orders using DHL Express while using BlueDart for domestic shipments.
To display weight and package dimensions on BlueDart shipping labels, you need to use the Box Packing Method in the PluginHive app. This method allows you to define how products are packed into boxes, including specifying package dimensions and weight, which then reflects on the shipping labels. Follow these steps: 1. Access the PluginHive Shopify Multi-Carrier Shipping Label app in your store’s admin panel. 2. Navigate to the packing methods settings. 3. Select and configure the Box Packing Method according to your packaging requirements. 4. Ensure you enter accurate weight and dimension details for each box type used. 5. Generate a label using BlueDart courier after this setup; the label will then include the size and weight information. For detailed instructions, refer to the PluginHive knowledge base article on packing methods here: https://www.pluginhive.com/knowledge-base/packing-methods-shopify-multi-carrier-shipping-label-app/#box-packing-method Additionally, you can watch a step-by-step video tutorial here: https://www.youtube.com/watch?v=Cdt2hqF6wRU If you encounter any issues during setup, you can contact support for further assistance.
To facilitate resolution of scanning issues by coordinating with Blue Dart representatives, follow these steps: 1. Obtain direct contact details of the relevant Blue Dart personnel, such as branch IT heads or account representatives, including email addresses and phone numbers. 2. Share these contact details promptly with PluginHive support to enable direct outreach and collaborative troubleshooting. 3. Provide detailed information about the issue, including order numbers, affected shipments, and descriptions of the scanning delays or failures. 4. Use multiple communication channels (phone and email) to increase the likelihood of reaching the right person. 5. Encourage the Blue Dart representative and PluginHive support to communicate directly for faster issue diagnosis and resolution. 6. Maintain consistent follow-up until the scanning problem is fully resolved to minimize shipment delays. This coordinated communication approach ensures PluginHive support and Blue Dart personnel work together efficiently to address label scanning problems.
1. For carriers like BlueDart, ensure you have provided active Production Account credentials in the app (not test accounts). 2. Enable the Production Key option within the carrier settings. 3. Provide valid Tracking License Keys as required to authenticate live label creation. 4. Contact your carrier’s account representative to obtain production account details if necessary. 5. Share those credentials with PluginHive support to complete configuration for live label generation.
To generate BlueDart return labels successfully in the app: 1. Ensure your BlueDart account has API permissions enabled for return labels by confirming with your BlueDart Account Representative. 2. Use the return label parameters as suggested by BlueDart, including setting the shipment to “Topay” mode with the following request properties: – ProductCode: “D” – ProductType: 2 – IsToPayCustomer: true – IsReversePickup: false – RegisterPickup: true 3. When creating a return label in the app, select either the Apex or Express service options, as these have been tested to work with the adjusted settings. 4. If labels still fail, share the detailed API request and response logs with PluginHive support for further diagnosis.
Currently, the Shopify order number is printed under the Invoice Number field on BlueDart labels. The Reference field shows a CCRCRDREF number returned by BlueDart after label generation, which is unique for each shipment. There is an enhancement underway to pass the Shopify Order Display ID as the Reference ID for BlueDart shipments so that the Reference field will reflect the Shopify order number. Once this feature is enabled, ensure the “Include Order Number in the label” option is enabled in your PluginHive app settings. Then new labels will show the order display ID in the Reference field. Note, however, that the Reference ID must be unique per shipment to avoid label regeneration failures, so a unique suffix might be appended and merchants should consider only the first 4 characters of the reference ID when matching orders.
To obtain the zone mapping with pincode-wise classification for Zones A, B, and C, please request the detailed zone mapping sheet directly from the BlueDart representative or sales contact. This sheet is necessary for accurate shipment cost calculation based on delivery locations. Contact details provided by BlueDart or your PluginHive account manager can facilitate this.
To integrate BlueDart and Delhivery carriers with the PluginHive app, follow these steps: 1. Install the PluginHive app from the Shopify App Store and ensure your subscription is active. 2. Open the app dashboard and navigate to the “Carriers” or “Shipping Services” section. 3. Select BlueDart and Delhivery from the list of supported carriers. 4. Add your BlueDart and Delhivery account credentials or API keys as requested to link your carrier accounts. 5. Configure shipping rules, rates, and preferences according to your business needs within the app. 6. Save the settings and test by creating a sample shipment to confirm the carriers are integrated correctly. If you require assistance with setup, you can schedule a free Zoom onboarding call through the app to get guided support.
To integrate BlueDart automation using the PluginHive app on your Shopify store, follow these steps: 1. Install the PluginHive Multi Carrier Shipping Label App from the Shopify App Store. 2. Obtain your BlueDart account API credentials from BlueDart (details needed include API key and other authentication information provided by BlueDart). 3. Add your BlueDart account details into the PluginHive app settings under the carriers section. 4. Once the account is added, you can automate the generation of BlueDart waybills for your Shopify orders through the app. If you need personalized help with setup, you can schedule a Zoom call with PluginHive support after adding your BlueDart account details.
To obtain your Blue Dart API keys, you need to contact your Blue Dart account manager directly. They will provide the necessary API credentials via email. Once you receive the API keys, if you require assistance with configuring the API within PluginHive, you can reach out to PluginHive support for help with the integration and setup.
In the PluginHive app, go to **App Settings** > **Carrier Settings** > **BlueDart** > **Other Details**. There you will find an option labeled **”Request Pickup along with Label Generation”**. This option is enabled by default, which triggers a pickup request for every label generated, causing multiple pickup requests for bulk label generation. To resolve this, disable the **”Request Pickup along with Label Generation”** option. Once disabled, pickup requests will no longer be sent automatically for each label, allowing you to manage pickup requests separately as per your preference.
You can prioritize Blue Dart over Delhivery by setting up automation rules within the PluginHive app as follows: 1. Navigate to the App Menu > Settings > Automation. 2. Click on “Set Up” to create a new automation rule. 3. Create a rule for Blue Dart: – Under Action Details, select “SET Carrier Service” and choose Blue Dart. – Save the rule. 4. Create a rule for Delhivery: – Under Action Details, select “ADD Carrier Service” and choose Delhivery. – Save the rule. With these rules, Blue Dart will be the default carrier. For any order where Blue Dart is not serviceable, manually select the order, click on “Change Carrier Service,” choose Delhivery, and then generate the shipping label.
To remove duplicate entries in the PluginHive app: 1. Log into your Shopify store and open the PluginHive Shipping app. 2. Navigate to the app settings section where BlueDart account details are configured. 3. Look for repeated entries of the BlueDart account and shipping address. 4. Confirm if the details are identical. If yes, delete one of the duplicate account entries or addresses to avoid conflicts. 5. Save your changes and try generating the shipping label again. If you are unsure or require assistance, provide permission to PluginHive support to access and remove duplicates on your behalf.
When using multiple Blue Dart accounts (old and new) in PluginHive and frequently switching between them, it is important to verify the following for smooth label generation: 1. Confirm which Blue Dart account you want to use for shipping each order. 2. Identify the specific Blue Dart service (e.g., Apex service) linked to that account. 3. Obtain the exact Product Type and Sub Product Type for the chosen service from Blue Dart. 4. Share the Request Response XMLs and generated labels with the Blue Dart support team to verify shipment data accuracy. 5. Ensure the correct Blue Dart API endpoint URL is used depending on whether you are in test mode or production mode (e.g., use the production URL https://apigateway.bluedart.com/in/transportation/waybill/v1/GenerateWayBill in production). 6. Avoid generating labels in test mode if you intend to use production services, as this can lead to incorrect or missing records on Blue Dart’s portal. Following these steps can help clarify issues arising from account switching and ensure synchronization with Blue Dart’s system.
To switch to an older Blue Dart account in the PluginHive app and reprocess orders, follow these steps: 1. Open the PluginHive app and navigate to the shipping integration settings. 2. Locate the Blue Dart account configurations where multiple accounts may be added. 3. Select or enter the credentials of the older Blue Dart account you wish to activate. These credentials typically include: – Customer Code – Origin Service Area Code – Login ID – Shipping License Key 4. Save the changes to update the shipping integration settings to this older account. 5. Go to the order management section of the app and identify orders that need to be reprocessed under the newly activated older account. 6. Use the reprocessing feature in the app to regenerate shipment labels and tracking details for these orders, ensuring the new account settings are applied. 7. Confirm that the updated shipments are correctly linked by verifying their status and tracking information within the app. This procedure allows seamless transition between multiple Blue Dart accounts while maintaining accurate shipment processing. For detailed guidance, refer to available video tutorials by PluginHive or contact support for a live walkthrough.
To update flat shipping rates for zip codes that are not serviced by Amazon and BlueDart in PluginHive, you should configure flat shipping rates based on weight ranges or fixed amounts within the PluginHive app. This setup allows you to accept orders for unsupported postal codes and fulfill shipping manually or through alternate carriers. The general steps are: 1. Access the PluginHive dashboard and navigate to the shipping settings for your store. 2. Locate the flat rate or shipping rules configuration section. 3. Define flat shipping rates based on weight slabs or cart value as per your business needs. 4. Specify the postal codes or regions where these flat rates should apply, especially targeting those that Amazon and BlueDart do not cover. 5. Save the configuration to enable flat rate shipping for unsupported areas. If needed, PluginHive support can assist you with this setup via a scheduled session to ensure your flat rates and shipping rules are correctly configured for your store’s requirements. *Note: Since direct step-by-step setup assistance is often provided via support calls or appointments, booking a session with PluginHive support is recommended for personalized guidance.*
To ensure that the barcodes on your Blue Dart labels scan correctly, verify the following: 1. Print labels using compatible thermal label printers or high-resolution printers recommended for barcode printing. 2. Use approved label stock that is clean, with no wrinkles, smudges, or damage that could interfere with scanning. 3. Confirm print density and contrast are sufficient; the barcode should appear dark and crisp against a light background. 4. Avoid scaling or resizing labels during printing, as this can distort barcode dimensions and affect scanner readability. 5. Test-scan labels with standard barcode scanners before affixing them to parcels to catch issues proactively. 6. Refrain from covering, folding, or placing labels over package seams or edges that may crease or damage the barcode. Maintaining high-quality label printing and handling standards minimizes scanning errors during Blue Dart pickups.
PluginHive support can assist by directly contacting BlueDart using either your provided BlueDart Account Representative’s contact details or PluginHive’s own BlueDart contacts. To enable this: 1. Share your BlueDart Account Representative’s contact details with PluginHive support. 2. If you do not have these details, inform PluginHive so they can use their internal contacts to inquire about your wallet status and shipment issues. 3. PluginHive support will then follow up with BlueDart to identify and resolve any wallet balance or account-related roadblocks affecting label generation. 4. Maintaining open communication and providing timely responses helps PluginHive facilitate faster resolution. This collaborative approach can help address technical blocks in label printing related to wallet balance discrepancies or API issues.
To activate and configure the BlueDart tracking license key in the PluginHive app, follow these steps: 1. Add your BlueDart account details in the PluginHive app settings under carriers. 2. Provide the valid BlueDart Tracking License Key (e.g., plogktqtqgplgmeozhtfh1eruhkjg4ri) to the PluginHive support team or update it yourself in the app if the option is available. 3. PluginHive support will verify and configure the tracking license key in your app. 4. Once updated, you will receive confirmation that the Tracking API key has been added and activated. 5. If any assistance is required during configuration, you can schedule a call or screen share session with PluginHive support using the booking link provided by the team. This process ensures that tracking functionality is properly activated for your BlueDart shipments within the PluginHive app.
To activate and configure the BlueDart tracking license key in the PluginHive app, follow these steps: 1. Add your BlueDart account details in the PluginHive app settings under carriers. 2. Provide the valid BlueDart Tracking License Key (e.g., plogktqtqgplgmeozhtfh1eruhkjg4ri) to the PluginHive support team or update it yourself in the app if the option is available. 3. PluginHive support will verify and configure the tracking license key in your app. 4. Once updated, you will receive confirmation that the Tracking API key has been added and activated. 5. If any assistance is required during configuration, you can schedule a call or screen share session with PluginHive support using the booking link provided by the team. This process ensures that tracking functionality is properly activated for your BlueDart shipments within the PluginHive app.
To find your BlueDart tracking license key: 1. Contact your BlueDart Account Manager and request the tracking license key for your account. They are the authorized point of contact for such credentials. 2. Once you receive the tracking license key, log in to the PluginHive app. 3. Navigate to the BlueDart carrier account settings section. 4. Enter the received tracking license key in the designated field and save the changes. After adding the key, the app will begin fetching and updating tracking data. If you already have the license key, add it directly as above to activate delivery status updates.
To set up and onboard PluginHive services with BlueDart integration, follow these steps: 1. Contact the BlueDart team directly and request the Product Codes for the specific services you intend to use with PluginHive. 2. Once you receive the Product Codes from BlueDart, share these details with the PluginHive support or your account manager. 3. The PluginHive team will then proceed with configuring and integrating the BlueDart services as per the provided Product Codes. This approach ensures that the correct service products are integrated properly and your shipping setup functions as expected.
To start shipping with Blue Dart through the PluginHive app, you need to add your Blue Dart account by entering specific details into the app. These details include: 1. Customer Code 2. Login ID 3. Origin Service Area Code 4. Shipping Licence Key 5. Tracking Licence Key You must obtain these details from your Blue Dart Account Representative. If you don’t have them, contact your Blue Dart representative directly. Additionally, PluginHive offers a free onboarding call via Zoom to help set up and configure the app according to your needs. You can request this onboarding session by responding to PluginHive support or booking a slot through the provided scheduling link.
To start shipping with Blue Dart using the PH Multi Carrier Shipping Label app, you must first have an active Blue Dart account. Follow these steps: 1. Create an account directly with Blue Dart by contacting them or filling their account registration form. 2. After account creation, Blue Dart will assign you an Account Representative. 3. Obtain the following details from your Blue Dart Account Representative: – Login ID – Customer Code – Origin Service Area Code – Shipping Licence Key – Tracking Licence Key 4. Add these details to the PH Multi Carrier Shipping Label app to integrate Blue Dart as a shipping carrier. Without a Blue Dart account and these credentials, you cannot enable Blue Dart shipping in the app.
To enable multi-package shipment support in PluginHive automation rules when using Blue Dart services: 1. Open the PluginHive app and go to the menu. 2. Navigate to Settings > Automation Setup. 3. Find and select the automation rule linked to Blue Dart Apex. 4. Click “Edit Rule.” 5. In the Action Details section, locate the service selection dropdown. 6. Change the selected service from “Apex” (or a single service) to “All.” 7. Save the changes. 8. Rerun the automation process so the updated rules apply to existing and new orders. This adjustment allows the app to select any Blue Dart shipping service that supports multiple packages per order. Keep in mind that this might increase shipping costs and change service selections automatically.
PluginHive facilitates resolution of Blue Dart label scanning issues through the following precise steps: 1. The customer shares the Blue Dart point of contact and details of the problematic labels. 2. PluginHive support reaches out directly to Blue Dart IT contacts, providing sample labels and associated XML data for the concerned orders. 3. Both teams collaborate by exchanging technical details and feedback to identify any discrepancies in barcode formats or label generation processes. 4. PluginHive keeps the customer updated on the investigation progress and confirms when the scanning issue is resolved. 5. Upon resolution confirmation from Blue Dart, PluginHive relays the update back to the customer to resume regular shipping activities with confidence. This direct cooperation ensures efficient troubleshooting and timely resolution of scanning-related problems with Blue Dart labels generated via PluginHive.
After subscribing to the PluginHive app, a designated support representative works closely with the customer to onboard them with integrated shipping services such as BlueDart and DHL. This involves configuring the shipping settings, helping set up the necessary accounts, and ensuring the shipping workflows are tailored to the customer’s needs. The onboarding can be scheduled or delayed as per the customer’s convenience, for example, starting after holiday seasons. The support executive also assists with any app-related queries during this phase to ensure smooth usage.
The label generation workflow involves: 1. Setting automation rules to assign shipping services based on priority and service availability (e.g., Blue Dart first, Delhivery second). 2. For orders where the primary carrier (Blue Dart) is not serviceable, manually switching to the secondary carrier (Delhivery) through the “Change Carrier Service” option. 3. Generating labels accordingly, noting that each carrier may have specific service names which you should confirm with the carrier and configure in PluginHive. 4. Monitoring label details including payment types (Prepaid or COD), and raising issues to PluginHive support if discrepancies appear.
BlueDart requires that each Reference ID be unique for every shipment. If the Reference ID is duplicated on labels: – Label regeneration or return label generation will fail. To maintain uniqueness while using the Shopify order number as reference, the system appends additional unique characters at the end of the order number. When reconciling orders, merchants should consider only the initial characters (e.g., first 4. of the Reference ID to identify the corresponding order. This ensures smooth label processing and accurate identification of shipments.
When shipment issues such as delays or damages occur, ensure clear communication by: 1. Contacting the carrier directly to clarify the issue and obtain detailed information. 2. Documenting all conversations and updates from the carrier for reference. 3. Keeping both your internal teams and the carrier informed to coordinate follow-up actions. 4. If needed, escalate the issue through formal communication channels, such as raising a security investigation or claim with the carrier. 5. Sharing carrier feedback with your customers or stakeholders promptly to maintain transparency.
To avoid errors or invalid shipments when using Blue Dart integration in PluginHive, follow these steps to confirm and switch between Test Mode and Production Mode: 1. Open the Blue Dart account settings within your PluginHive dashboard. 2. Check the current environment mode setting—Test Mode is typically used for integration testing and does not generate valid shipping labels for real orders. 3. When ready to process live shipments, switch the mode to Production Mode by toggling the appropriate setting in the account configuration. 4. After switching to Production Mode, use the correct API endpoint URL associated with production to generate labels (for example, https://apigateway.bluedart.com/in/transportation/waybill/v1/GenerateWayBill). 5. Regenerate shipping labels post-switch and verify on Blue Dart’s portal that tracking details are correctly registered. This ensures that shipments are processed against live Blue Dart accounts without test data conflicts or URL misconfigurations.
The issue was resolved by obtaining and using the correct License Keys and Login ID from BlueDart. The initially provided License Keys were incorrect or mismatched. After BlueDart shared the correct keys: 1. PluginHive updated the credentials in the app. 2. The BlueDart account was successfully added in Production mode. 3. Live rates and labels could be generated without errors. For assistance or onboarding support in setting up the app after credential updates, users can schedule a Zoom call with PluginHive support.
If BlueDart confirms your credentials are for the live API but the app still shows test mode, follow these steps: 1. Double-check that you have toggled on the “Production Key” option in the PluginHive app for BlueDart integration. 2. Share your BlueDart account representative’s contact details with PluginHive support so they can verify the account and credentials directly with BlueDart. 3. PluginHive and BlueDart teams will coordinate to identify any discrepancies or errors causing the credentials to work only in test mode. 4. Once resolved, production mode will be activated in the app, allowing live rate calculation and label generation.
Once the BlueDart tracking license key is provided and added to the PluginHive app, the support team or you can initiate a retracking process for orders: 1. The app will begin re-checking the fulfillment and delivery statuses using the valid tracking license key. 2. This retracking process may take some time to complete for all fulfilled orders. 3. Already updated orders will start reflecting the ‘Delivered’ status in Shopify immediately (as verified for some orders). 4. Please periodically check your Shopify orders for updated statuses. If you face any issues after adding the key, reach out to PluginHive support to verify and troubleshoot further.
Automatic label generation depends on accurate shipping information and enabled services in the app. For future orders to auto-generate labels for postal code 411004, ensure the following steps: 1. Verify that the shipping address in Shopify, including postal code, is accurate and matches the actual delivery location, as the app relies on this data. 2. Confirm that the BlueDart services enabled in the app cover the specific postal code area where shipments will be made. If services like BlueDart Apex or Domestic Priority are not available for that postal code, orders remain in the initial status and won’t auto-generate labels. 3. If a BlueDart service used in manual label generation via the Blue Dart dashboard differs from enabled services, add or enable that service for the order within the app to support auto-generation. No changes are typically required in the Blue Dart dashboard itself, but the app’s service configuration must align with the services used for shipments to enable automation. Regularly review and update enabled services in the app as needed.
Once you have active accounts with BlueDart and FedEx for domestic and international shipments, you can connect these accounts to PluginHive’s platform. We offer the “PH Multi Carrier Shipping Label” app for Shopify, which integrates multiple carrier APIs into one solution. After connecting your carrier accounts within this app, it automates order processing tasks such as: 1. Fetching live shipping rates at checkout. 2. Generating shipping labels for your orders. 3. Requesting carrier pickups automatically. 4. Tracking shipments through carrier systems. This integration centralizes your shipping workflows and reduces manual effort by coordinating pickups and label generation through the PluginHive app.
Yes, PluginHive supports integration with Blue Dart and Delhivery for shipping. To set up your store with these carriers, you can schedule an onboarding call with the PluginHive support team for step-by-step assistance. The support team provides an appointment link where you can book a convenient time slot for the setup session. During this call, they will guide you through connecting your account, configuring shipping settings, and handling any questions related to your Indian store’s integration with Blue Dart and Delhivery.
No. Currently, the enhanced Packaging UI with features like product price editing and advanced order filtering is exclusively available for the BlueDart carrier. Other carriers do not support this UI enhancement at this time.
No, as of now, the new Packaging UI is only enabled for the Bluedart carrier. Other carriers do not currently support this UI enhancement.
Currently, the PluginHive app does not support bulk export of manifests filtered by specific shipping services. Manifests can only be printed separately. However, if you fulfill multiple orders at once and click the print option, a combined manifest of all those fulfilled orders will be generated on a single sheet. Filtering manifests by courier service and exporting them in bulk is not available at this time.
Currently, no official public example or Request-Response XML has been shared by BlueDart demonstrating return label generation with COD because this scenario is unsupported by BlueDart. Return labels must be generated as prepaid shipments, and PluginHive can assist you with parameter configuration for such requests. For detailed API requests, set `IsReversePickup = true` and `IsTopayPickup = false`. If you need sample API request-response data, please contact PluginHive support or your BlueDart representative.
The additional digits appearing after the initial part of your Order Number on labels generated via PluginHive are typically due to automated reference number formatting or carrier requirements integrated within the PluginHive system. To address and potentially rectify this issue: 1. Verify the reference number mapping configuration in your PluginHive dashboard: – Log in to the PluginHive dashboard. – Navigate to the carrier settings or order mapping section. – Check how the “Reference Number” or “Order Identifier” field is mapped. Ensure it is set to use your exact internal Order Number without additional concatenated digits. 2. If the system appends extra digits by default (due to carrier or PluginHive formatting rules), contact PluginHive support to check if the reference number formatting can be customized or disabled for your Blue Dart integration. 3. Confirm with the carrier (Blue Dart) if the additional digits are mandatory for their label generation process. If so, the label format might be restricted by their requirements, limiting customization. 4. After making any changes, generate a test label through the PluginHive platform to verify that the label now displays the Order Number as desired. 5. If immediate configuration changes are not available, consider creating labels directly through the Blue Dart portal for orders requiring exact Order Number display until a resolution is implemented. By reviewing and adjusting the reference number mapping settings or coordinating with PluginHive support, you can minimize or eliminate undesirable additional digits on your shipment labels.
BlueDart’s Apex and Express services are recommended for generating return labels within the PluginHive app. These service options have been verified to work correctly with the required request parameters when generating returns, especially in cases needing “Topay” shipment mode. Attempt using these services if you face issues with default or other service options when generating return labels.
Below is an example of the request and response data used for troubleshooting: Request Payload Example: “`json { “pinCode”: “456010”, “profile”: { “Api_type”: “S”, “LicenceKey”: “your-shipping-api-licence-key”, “LoginID”: “your-login-id” } } “` Response Example with Error: – Status: 400 Bad Request – Error: ‘UserDoesNotExists’ – The response includes multiple null or zero value fields indicating failure to recognize the user/credentials. Providing these logs to BlueDart helps them check why the API is rejecting the credentials and resolves the problem.
To create a prepaid reverse pickup with PluginHive API for BlueDart, ensure you include these parameters in your shipment creation request: – `IsReversePickup`: Set this to `true` to indicate this is a return shipment. – `IsTopayPickup`: Set this to `false` so the shipment is treated as prepaid (no COD to be collected). Using these settings, the system treats the return as a prepaid shipment and successfully generates the return label.
The BlueDart Air Etail rates and charges are as follows: – **Zones**: A, B, C (zone mapping needs to be confirmed separately with pincode-wise classification). – **First 500 grams**: – Zone A: ₹88 – Zone B: ₹95 – Zone C: ₹101 – **Additional 500 grams**: – Zone A: ₹88 – Zone B: ₹95 – Zone C: ₹101 – **COD Charges**: 3% of declared invoice value or ₹60, whichever is higher. – **FOV Insurance (Owner’s Risk)**: 0.20% of declared invoice value or minimum ₹ 100. – **Fuel Surcharge (FS%)**: 61% for April 2024 (calculated as per sliding mechanism). – **Currency Adjustment Factor (CAF)**: 16% based on average exchange rate (USD/Euro-INR 78.5), and for each 1 INR increase in base exchange rates, base percent increases by 0.5%. – **Reverse Logistics Charges**: ₹100 (Closed) or ₹150 (Open/QC based RVP). – **TDD (Time Definite Delivery) Optional Charge**: ₹ 150. **Example of COD shipment calculation (Clothing, 500g to Delhi, Invoice Value ₹25,000, Zone A):** – Basic Freight: ₹88 – COD Charges: Higher of 3% of ₹25,000 (₹ 750. or ₹60 → ₹750 – Fuel Surcharge: 61% on freight – CAF: 16% on freight – Total (without GST): ₹1,565 **Example of non-COD shipment calculation (Same shipment as above):** – Basic Freight: ₹88 – No COD charges applied – Fuel Surcharge: 61% on freight – CAF: 16% on freight – Total (without GST): ₹165 Note: The calculation excludes GST and assumes Air Etail mode.
To configure tracking license keys for carriers like BlueDart, follow these steps: 1. Confirm and cross-check your Area Code associated with your shipments. 2. Obtain the Tracking License Key from the respective carrier (e.g., BlueDart) by contacting their support or via your carrier account portal. 3. Share the obtained Tracking License Key with PluginHive support or your account manager. 4. PluginHive will add the Tracking License Key to your account backend to enable tracking integration. This setup ensures that shipment tracking works smoothly within the PluginHive platform.
To reprocess orders in the PluginHive app while switching to an older Blue Dart account, follow these steps: 1. Access the order management section in the PluginHive app where your shipments are listed. 2. Identify the orders that need to be reprocessed under the new or older Blue Dart account credentials. 3. Update the shipping integration settings by entering the credentials of your older Blue Dart account, including the Customer Code, Origin Service Area Code, Login ID, and Shipping License Key associated with that account. 4. Use the order reprocessing feature within the app to resend or regenerate shipment labels and tracking information using the updated account details. 5. Verify that the orders have been successfully reprocessed and are linked to the correct Blue Dart account by checking the shipment status and tracking details in the app. If further assistance is needed, watch the video tutorial shared by PluginHive support or contact their team for a live walkthrough of the process.
To set up BlueDart integration in the PluginHive app, you need to obtain the following API credentials from BlueDart: 1. API key or token provided by BlueDart for authentication. 2. Endpoint URLs for BlueDart API services (such as rate calculation, shipment creation, and tracking updates) if applicable. 3. Additional parameters such as account number, client code, or any other authentication details BlueDart provides. These credentials must be entered into the PluginHive app to enable automated waybill generation and order processing using BlueDart services. If you require exact details, please refer to BlueDart’s developer portal or support team for the correct API information. Once obtained, you can input these credentials into the app to complete the integration setup.
To activate the BlueDart shipping integration code and start the formalities, you need to provide the following company information: 1. Company GST number 2. Company PAN number Submit these details to your BlueDart Business Development team contact or PluginHive representative to complete the activation process.
The “UserDoesNotExists” error with a 400 Bad Request status generally means the credentials submitted are not recognized by BlueDart’s production API. This can occur due to: – Incorrect or mismatched Login ID or License Key. – Using credentials that belong to a different BlueDart account or environment. – Account details not fully activated or synced on BlueDart’s side. To resolve this: 1. Verify the exact Login ID and License Keys with your BlueDart account representative. 2. Ensure PluginHive is using the correct API endpoint: https://apigateway.bluedart.com/in/transportation/finder/v1/GetServicesforPincode 3. Provide the request and response logs (including the pin code and profile used) to BlueDart support for troubleshooting. 4. Coordinate with PluginHive and BlueDart teams to get corrected credentials or system updates needed.
This error indicates that a shipping label (waybill) has already been generated for the specified order using the given Credit Reference Number. BlueDart prevents duplicate waybill creation for the same order or reference, so attempts to create a new label for the same shipment will fail with this message. Essentially, the label associated with the waybill number 20877275720 already exists in the system for that order.
The Reference number on BlueDart labels is a unique identifier called the CCRCRDREF number generated by BlueDart after label creation. The first five digits of this reference number correspond to the Shopify order number. For example, if the reference number is 9352214055410, the Shopify order number is “93522”. You can use this to map remittance data references back to your Shopify orders for reconciliation purposes.
The common error message encountered when attempting to generate a COD return label for BlueDart is: **”ToPay COD Facility is disabled”** This message indicates the BlueDart account or service does not support COD payments for return (reverse) shipments.
To facilitate efficient troubleshooting with Blue Dart and PluginHive support, provide the following: 1. Copies of generated shipping labels that are exhibiting issues. 2. The Request and Response XML files from the Blue Dart API calls related to those shipments. 3. Details of the Blue Dart account used (including customer codes and service types like Apex). 4. The exact URL/endpoint used for generating labels to confirm environment (test vs production) and API correctness. 5. Any error messages received from PluginHive or Blue Dart portals (e.g., “Record Not Found”). 6. Contact details of your Blue Dart representative, if coordination between PluginHive and Blue Dart teams is required. Providing complete and accurate information allows both PluginHive and Blue Dart support teams to verify configurations, trace consignments, and resolve integration issues promptly.
The API endpoint for BlueDart integration is: https://apigateway.bluedart.com/in/transportation/finder/v1/GetServicesforPincode Use this endpoint to fetch shipping services and rates based on pin codes. Ensure that the request profile includes the correct Api_type, LicenceKey, and LoginID parameters for your BlueDart account.
After resolving a label generation issue, follow these communication best practices: 1. Confirm with the support team that the label has been successfully generated for the affected order(s). 2. Inform the merchant promptly via email or messaging that the issue is resolved and ships can proceed. 3. Request the merchant to test label generation with new orders to ensure ongoing stability. 4. Await confirmation from the merchant before formally closing the support ticket. 5. Provide courteous closure messages, assuring support availability for future queries. This ensures transparency, confirmation, and customer satisfaction post-resolution.
Blue Dart Apex service in PluginHive has these key limitations: 1. It supports only single-package shipments per order. Orders split into multiple packages using the new PluginHive UI will not process correctly with Apex. 2. Orders requiring multiple shipping labels (one per package) cannot be generated using Blue Dart Apex. 3. Certain postal codes may not be covered by Blue Dart Apex, which can prevent orders from advancing to the processing stage. 4. To ship multi-package orders, you must use a different Blue Dart service or carrier that supports multiple packages per shipment. Understanding these limitations helps ensure correct service selection and smooth order processing within PluginHive.
PluginHive offers a new Packaging UI for BlueDart shipments with the following features: 1. “Edit Package” option allowing direct adjustment of Product Price before label creation to account for COD changes. 2. Advanced order search and filtering capabilities for efficient order management. 3. Quick Action buttons to speed up workflow processes. 4. OPEN tab showing orders pending label generation, and Fulfilled tab showing processed orders with labels created. 5. Ability to toggle visibility of columns like Product Names, Weight, and Dimensions for clearer views. 6. A “Today’s Label” button to filter orders with labels created on the current day, assisting daily tracking. These features streamline shipment preparation, label creation, and order monitoring within the PluginHive dashboard.
PluginHive has enabled a new Packaging UI specifically for the Bluedart carrier to enhance order processing and package editing. Key features include: 1. Ability to adjust Product Price directly using the “Edit Package” feature before label creation. 2. Advanced order searching and filtering options to quickly locate orders. 3. Quick Action buttons for faster workflow management. 4. OPEN tab showing all orders pending label creation. 5. Fulfilled tab showing orders that have been processed and labels created. 6. Options to enable or disable viewing Product Names, Weight, and Dimensions columns for clarity. 7. “Today’s Label” button to filter orders with labels created on a particular day, aiding daily tracking. These features streamline shipment preparation, label creation, and daily order tracking within the PluginHive dashboard.
Despite BlueDart representatives stating all services are enabled, the system limitations prevent COD return label generation. The recommended approach is: – Treat returns as prepaid shipments. – Generate return labels manually via BlueDart portal as prepaid, or – Use PluginHive API and set return label request parameters to prepaid (IsTopayPickup = false). This bypasses system errors and aligns with BlueDart’s operational constraints.
In cases where bulk label creation fails initially but succeeds upon retry—except for a single order—you should take the following steps: 1. Verify that no labels were created outside the PluginHive app or accessed through the BlueDart portal by thoroughly checking both systems. 2. Confirm with your team that no external label generation occurred outside your current shipping solution. 3. Allow some time (for example, holding shipment until the next day) before retrying the label generation process. 4. Investigate the specific order for which the label generates failure separately, including checking error messages and referencing support if needed. 5. If needed, escalate to PluginHive support with the order number and relevant details so they can assist in fixing any reference ID or system errors affecting label generation. This careful approach prevents unnecessary duplicate labels and facilitates focused resolution for problematic orders.
To identify which BlueDart account your PluginHive app is using: 1. Check the customer code used within the PluginHive app when generating BlueDart shipping labels. 2. Compare this customer code with details from your BlueDart accounts. 3. Confirm with your BlueDart Account Manager which account corresponds to that customer code. Once identified, obtain the corresponding tracking license key from that account and add it into the app to enable status updates.
If API errors prevent enabling BlueDart production mode: 1. Verify you have the correct and active Production API credentials (Login ID and License Keys) from BlueDart. 2. Confirm you are using the correct API endpoint as per BlueDart’s documentation. 3. Obtain request and response logs from PluginHive support to share with your BlueDart representative. 4. Work with both PluginHive and BlueDart support teams for resolving user existence, authentication, or configuration errors indicated in API responses. 5. If needed, schedule an onboarding call with PluginHive support for step-by-step assistance in configuration and troubleshooting.
If you have applied for a Blue Dart account and have not received a reply: 1. Follow up directly with the Blue Dart team or your nearest Blue Dart office to check the status of your account application. 2. Confirm the estimated timeline for account creation and assigned Account Representative details. 3. Once your account is approved, ensure you receive the necessary credentials (Login ID, Customer Code, Origin Service Area Code, Shipping Licence Key, and Tracking Licence Key). 4. Use these credentials to complete the Blue Dart add-account process within the PH Multi Carrier Shipping Label app. Until your Blue Dart account is active and the required details are available, you will not be able to start shipping via Blue Dart in the app.
For live assistance with BlueDart integration and PluginHive app setup, you should: 1. Schedule a personalized support call using the appointment booking link provided by PluginHive. This ensures that a dedicated support analyst is available to assist you. 2. During the scheduled call, have your BlueDart account credentials ready for verification and demonstration. 3. Use the call to clarify any doubts about automation, waybill generation, or app configuration related to BlueDart services. Note that PluginHive requires scheduled appointments for live support calls to manage availability and provide focused assistance. Contacting support outside pre-scheduled slots may result in delays or inability to connect immediately.
If the Reference ID enhancement was rolled back due to issues, PluginHive will prioritize fixing and re-releasing the feature. Meanwhile: – The existing functionality (Invoice Number shows Shopify order number, Reference shows unique BlueDart ID) remains unchanged. – For COD reconciliation, you can continue to use the exported order reports from the app. – Await further communication from PluginHive about the re-release timeline. – Understand that the Reference ID must be unique per shipment; hence, any new implementation will ensure uniqueness possibly by appending additional characters.
To enable an effective investigation into barcode scanning failures on Blue Dart labels generated through PluginHive, provide the following information: 1. Examples of order numbers for the shipments whose labels fail to scan. 2. Copies or screenshots of the problematic labels, highlighting the barcode area. (Note: Mentioning this does not create an FAQ entry.) 3. Details about your printing setup, including printer model, label type, and print quality settings. 4. Any communication or feedback received from the Blue Dart pickup personnel or account representative regarding the scanning failure. 5. Your store URL and details of your PluginHive plan to assist the support team in verifying your account settings. Providing comprehensive details helps PluginHive support swiftly identify potential causes related to label generation, printing, or carrier API integration.
To troubleshoot connection issues between BlueDart and the PluginHive app: 1. Verify all BlueDart credentials (Customer Code, Service Area Code, Service Center Code, Login ID, Shipping License Key, Tracking License Key) are correct and have no typos. 2. Confirm that your BlueDart account is active and that API access is enabled by BlueDart. 3. Ensure the internet connection and Shopify store permissions allow external API communication. 4. Re-enter credentials carefully in the PluginHive app carrier settings and save changes. 5. If connection fails, gather error messages or logs and provide them to PluginHive support along with the account details. 6. Schedule a support appointment with PluginHive for direct troubleshooting and resolution assistance. Following these steps systematically helps identify and fix common configuration or connectivity errors.
To escalate and troubleshoot return label failures: 1. Confirm your BlueDart account supports return label generation and clarify COD or prepaid policies with your account rep. 2. Provide PluginHive support with your BlueDart account representative’s contact for direct liaison. 3. Share details of the errors encountered, including API request-response logs if possible. 4. Attempt generating prepaid return labels manually to verify BlueDart portal behavior. 5. Follow PluginHive’s guidance on parameters for reverse pickups in API calls. This structured approach helps resolve any configuration or integration issues effectively.
When an order stays in “Initial” status due to unavailable services, follow these steps: 1. Verify the postal code in the shipping address is correct and matches the actual delivery location used in Shopify orders. 2. Check the list of Blue Dart services enabled in the app and confirm whether they cover the order’s postal code. 3. If enabled services do not cover the order’s postal code, manually assign a Blue Dart service within the app that is supported for that postal code. 4. Generate the shipment label manually using the assigned service in the app. 5. For future shipments, consider enabling additional Blue Dart services in the app that service the postal code to enable automatic label generation. This process ensures orders with unsupported postal codes are still fulfilled while keeping the app’s service settings aligned with your shipping requirements.
If Blue Dart refuses parcel pickups due to unscannable labels, take the following actions: 1. Temporarily halt shipping of affected parcels until the issue is resolved to avoid rejected pickups. 2. Contact your Blue Dart Account Representative immediately to report the scanning problem and seek guidance. 3. Reach out to PluginHive support with detailed information about the affected shipments and labels. 4. Collaborate between Blue Dart and PluginHive teams to confirm whether the issue lies with label generation, carrier API, or label printing quality. 5. Implement corrective measures advised by PluginHive or Blue Dart, such as regenerating labels, adjusting printing parameters, or updating integration settings. 6. Once resolved, conduct test scans with Blue Dart personnel before resuming normal shipment processing. This approach ensures swift resolution and prevents shipment delays due to barcode scanning failures.
Follow these steps: 1. Contact your BlueDart Account Representative and request the activation of Return Label generation API permissions for your account. 2. Provide the representative with the RequestResponse XML showing the return label generation failure so they understand the permission issue. 3. After confirmation that permissions are granted, attempt to generate the return label again via the PluginHive app. 4. If you encounter any other errors, escalate the issue back to PluginHive support with updated details.
If you experience errors related to the BlueDart API, you should contact your BlueDart account manager and share the XML request and response generated by the API to help diagnose the issue. Additionally, you can keep PluginHive support in the loop by CCing [email protected] on your communication for further assistance.
To successfully connect BlueDart with the PluginHive app, the following credentials are required: 1. Customer Code – issued by BlueDart to identify your account. 2. Origin Service Area Code – the location code from where shipments originate. 3. Service Center Code – if applicable, used for service-specific routing. 4. Login ID – your BlueDart system user login identification. 5. Shipping License Key – authorizes shipment creation via API. 6. Tracking License Key – authorizes tracking data retrieval via API. Ensure all keys and codes are current and accurately entered; incorrect details will prevent integration. If any information is missing or unclear, contact BlueDart support for exact credentials before entering them into the PluginHive app.
This error typically indicates an issue on the carrier’s end rather than with the PluginHive system. Since another BlueDart user recently faced a similar problem, it suggests a temporary disruption or internal server error from BlueDart’s service. Steps to address this situation: 1. Retry generating the label after some time, as such carrier issues are often resolved by the carrier’s technical team. 2. Ensure your order and shipment details are correctly entered before retrying. 3. If the error persists over an extended period, contact BlueDart support directly to confirm if there is an ongoing issue on their side. 4. Monitor your PluginHive dashboard for any further error messages or updates. 5. If you continue experiencing issues despite these steps, reach out to PluginHive support with relevant order details for further assistance. In the reported case, no user action was ultimately needed as the carrier resolved the issue internally.
This error typically occurs because your BlueDart account does not have COD (Cash on Delivery) shipment permissions enabled. To resolve this issue: 1. Verify that your BlueDart account supports COD shipments by checking with your BlueDart Account Representative. 2. If COD is currently not enabled in your account, request your representative to enable COD shipment functionality for your account. 3. Ensure that your BlueDart account details and “Shipping From” address are correctly updated in the PluginHive app. 4. After your account is updated to allow COD shipments, try placing the order again. If needed, you can share the Request Response XMLs of the failed order with your BlueDart representative, as these contain detailed information about the failure.
This error typically occurs due to a technical synchronization issue between the PH MultiCarrier Shipping Label app and the Bluedart carrier integration. To resolve it, PluginHive support can manually reprocess the affected orders in the system to refresh the wallet balance status. After they have reprocessed the orders, you should attempt generating the shipping labels again. If the problem persists, contact PluginHive support with the affected order details for further investigation.
The issue occurs because BlueDart does not support Cash on Delivery (COD) facility for return shipments or reverse pickups. Your BlueDart account is configured to accept COD payments only for forward shipments and not for return labels. Consequently, when you attempt to generate a return label with “ToPay COD” option, the system returns an error stating that the “ToPay COD Facility is disabled.” Therefore, COD return pickups cannot be processed through PluginHive or BlueDart’s API as COD; returns must be handled differently.
This error is returned from the BlueDart API and indicates an issue related to your BlueDart account or pickup registration for the specified area/customer code. To resolve it: 1. Verify and ensure that the BlueDart account details and shipping address configured in the app are not duplicated. If duplicates exist, remove one set of duplicate entries from the app settings. 2. Share the shipment request and response details (XML payload) from PluginHive with your BlueDart account manager, explaining the error message. 3. Work with your BlueDart account manager to confirm your account status and area registrations are correct and active. 4. You can CC [email protected] in your communications with BlueDart so PluginHive support can assist if necessary. 5. Address any dues or account activation issues with BlueDart promptly to restore label generation functionality.
The PluginHive app requires the Shopify ‘Carrier Calculated Shipping’ feature to be enabled on your store in order to register the app and display carrier-calculated shipping rates at checkout. However, BlueDart does not provide calculated shipping rates via their APIs, so even if the Shopify feature is enabled, you cannot use the app to show BlueDart calculated rates at checkout. You can still use the app with BlueDart to generate shipping labels, request pickups, and share tracking details without enabling this feature or registering the app for calculated rates.
The error “This Customer Cannot Send COD Shipment” indicates that the BlueDart API is rejecting the creation of COD (Cash on Delivery) labels for your orders. This usually occurs when your BlueDart account’s COD shipping privileges have been revoked or altered. To resolve this issue: 1. Verify if your BlueDart account still has active COD shipping privileges by contacting your BlueDart Account representative directly. 2. Share the label failure XML files generated by PluginHive for the affected orders with your BlueDart representative. These files contain detailed error information that can assist them in diagnosing the issue. 3. Confirm with BlueDart if any recent changes have been made to your account settings or if there are restrictions on sending COD shipments. 4. Once your COD privileges are reinstated or confirmed active, retry generating the labels through PluginHive. 5. If the issue persists, provide PluginHive support with any updates or additional error details received from BlueDart for further assistance. Taking these steps will help identify if the problem originates from account restrictions at BlueDart’s end and enable you to restore label generation for COD shipments.
Shipments are not auto-generated because the BlueDart services enabled in the app (BlueDart Apex and Domestic Priority) are not available for the specific order’s shipping details. For order GAR66081, these services are disabled in the app because the postal code or service used does not match the enabled options. To auto-generate shipments, the order must be assigned a BlueDart service that is enabled and available for its postal code within the app. If a different BlueDart service is used manually on the Blue Dart portal, you need to update the order in the app to use that same service to enable automatic label generation.
If Blue Dart representatives are unable to scan parcel labels generated via PluginHive, causing manual processing or refusal to collect shipments, follow these steps to diagnose and resolve the issue: 1. Verify if the problem affects all labels or specific orders. Since it occurs for every parcel over multiple days, the issue may be systemic. 2. Contact your Blue Dart Account Representative to confirm if there have been any changes or issues on their end related to barcode scanning or label formats, as labels are generated via the official carrier API. 3. Check for recent updates or changes in your PluginHive integration settings that might have impacted label generation. 4. Request your PluginHive support team to investigate the label generation logs and validate if the barcodes conform to Blue Dart’s scanning standards. 5. Share specific order numbers or sample labels with both PluginHive support and your Blue Dart representative to assist in troubleshooting. 6. Ensure your label printing method maintains the barcode quality—using correct label stock, print resolution, and printer calibration—to avoid scanning problems. 7. Collaborate with both parties (PluginHive and Blue Dart) until the exact cause is identified and resolved. By coordinating with PluginHive support and your Blue Dart representative, you can promptly pinpoint and fix issues causing barcode scan failures.
Shipping labels may not be generated if the selected courier service is temporarily unavailable. In this case, the labels for your orders were not generated due to service unavailability from Bluedart. To resolve this: 1. Confirm with your client whether they can allow alternative courier services besides Bluedart (such as Dart Plus or others). 2. If an alternate service is allowed, update the shipping service settings accordingly in PluginHive. 3. If the client insists on using only Bluedart, you will need to wait until the service is restored before label generation can proceed. 4. Once confirmed, contact PluginHive support for further assistance or to resume label generation. This approach helps manage shipment flow when a courier service experiences downtime.
This error occurs because your BlueDart account may not have the necessary API permissions enabled for generating return labels, or the return label request parameters are not configured correctly. To resolve this: 1. Contact your BlueDart Account Representative and request them to enable Return Label generation API permissions for your account. 2. Share the RequestResponse XML of the return label failure with the BlueDart rep to help them identify the issue. 3. Based on BlueDart’s feedback, adjust the shipment mode in the return label request to “Topay” mode instead of prepaid by updating the request with these parameters: – ProductCode: “D” – ProductType: 2 – IsToPayCustomer: true – IsReversePickup: false – RegisterPickup: true 4. Try generating a return label again using the PluginHive app with the updated parameters. 5. If the problem persists, try generating the return label using alternative BlueDart services like Express or Apex, as these services have been confirmed to work with the updated request format.
The “Record Not Found” error for tracking numbers on Blue Dart’s portal can occur due to the following reasons and should be addressed as follows: 1. Verify if the PluginHive app was set to Test Mode when generating the labels—labels generated in test mode will not appear in Blue Dart’s live system. Switch to Production Mode before generating actual shipping labels. 2. Confirm that the correct Blue Dart service, Product Type, and Sub Product Type associated with your account are accurately configured. 3. Use the correct Blue Dart API URL that corresponds to your environment: Production Mode requires the production API URL (e.g., https://apigateway.bluedart.com/in/transportation/waybill/v1/GenerateWayBill). 4. After updating these configurations, regenerate the labels and check if the tracking information is now available on Blue Dart’s portal. 5. If the issue persists, share the generated labels and Request Response XML files with Blue Dart support for deeper investigation to ensure that the consignments are properly recorded in their system.
BlueDart does not provide live shipping rates via an API that PluginHive can integrate with. This limitation is due to BlueDart’s service and not an issue with the PluginHive app.
The discrepancy in the courier shown on the AfterShip tracking URL could be due to incorrect or incomplete integration settings between your store and the courier services. It is recommended to check your store’s integration configurations thoroughly. If you notice any mismatch, you may need to update the courier information used for generating tracking URLs. Additionally, verifying courier mapping settings in your shipping or tracking app can help ensure the correct courier is displayed to customers.
BlueDart appears as a test account because the Production Key is not enabled in the app settings for the BlueDart integration. To activate live rates and generate live labels, you must: 1. Ensure the Production Key option is enabled in your BlueDart account settings within the PluginHive app. 2. Confirm that you are using the correct Production API credentials provided by BlueDart. Test credentials will only allow test mode access. 3. After updating these settings, try processing your orders again. If the issue persists, verify the credentials with your BlueDart representative or PluginHive support.
This error indicates an issue on the Bluedart account side related to the pickup registration for your specified area customer code. To resolve this: 1. Verify if any recent changes were made to your Bluedart account settings or pickup area codes. 2. Contact your Bluedart Account Representative to check if your account is properly configured for pickup registration in the concerned area. 3. Share the Request and Response XML files of the failed order with your Bluedart representative to help them diagnose the issue accurately. 4. After confirming and correcting any account or area code configurations with Bluedart, retry generating the shipping label in PluginHive. This issue is not caused by PluginHive but by your Bluedart account setup, so coordination with your carrier is essential.
The “insufficient wallet balance” error can occur because the PluginHive app does not receive live shipping rates from BlueDart’s API. Instead, it uses the total order value as a proxy for the shipping cost during label generation. Therefore, if your order value is higher than your wallet balance, the app may show this error even if your actual wallet balance is sufficient for the shipping cost. To resolve this: 1. Confirm your BlueDart wallet balance and transaction status directly with BlueDart support or your BlueDart Account Representative. 2. Provide PluginHive support with your BlueDart account contact information so they can coordinate and verify wallet status on your behalf. 3. If needed, share the PluginHive-provided Request Response XMLs related to the order with BlueDart to clarify the actual debited amounts per shipment. 4. Wait for wallet balance updates to reflect fully on BlueDart’s system, as there can be a delay. By following these steps, you ensure accurate wallet balance verification and avoid label generation failures due to perceived insufficient funds.
This error occurs because your BlueDart account is configured for Cash on Delivery (COD) payments only for forward shipments and not enabled for COD payments on return shipments. In order to generate return shipping labels with COD payment via PluginHive, your BlueDart account must be specifically enabled to accept COD for return shipments. Since payment type changes after order fulfillment are not supported in the app, return labels with COD that are not pre-enabled in your account will fail. The recommended workaround is to create the return shipment label directly via the BlueDart website where you can specify payment terms.
The issue where shipping labels display the payment type as “false? Collection Amount:” instead of showing whether it is prepaid or COD has been identified by PluginHive’s technical team. It occurs despite using Razorpay for prepaid payments and Shopify COD for cash-on-delivery. PluginHive is actively working on fixing this bug, and the development team has prioritized it. They are generating test labels and troubleshooting with your permission and will update you once the fix is deployed.
The “Authentication Failed” error when adding the Blue Dart Tracking License Key usually occurs due to incorrect or missing authentication details in the API request XMLs. To resolve this: 1. Verify that you are using the correct Blue Dart account credentials and license key exactly as provided. 2. Ensure that the API request XML includes all required authentication fields in the correct format. 3. Obtain the XML request and response logs displaying the authentication failure from your system. 4. Share these XMLs with PluginHive or Blue Dart support for detailed analysis, as they can pinpoint the exact cause of authentication failure. 5. PluginHive support can then apply necessary fixes or update configurations on the backend. In the reported case, PluginHive support has already configured the Tracking License Key from their end. Please verify in your store’s settings to confirm it is working; if the issue persists, provide the XML error logs for further troubleshooting.
The label generation failure for BlueDart shipments was caused by an issue with the Reference ID used in the label creation process. The PluginHive technical team identified and fixed this Reference ID problem, which was preventing labels from being generated successfully. After the fix was implemented, labels for affected orders, such as order 11805, were generated successfully. To resolve similar issues: 1. Avoid creating shipping labels outside the PluginHive app during investigation periods to prevent conflicts. 2. Verify that there are no existing active Tracking IDs for affected orders before retrying label generation. 3. Once PluginHive confirms the fix has been applied, test label generation for new orders and confirm successful processing.
The scanning issue with Blue Dart parcel labels generated by PluginHive, reported in the prior week, appears to have been resolved. Previously, labels were not scanning for Blue Dart pickup teams, causing delays or refusal of parcel pickups. PluginHive coordinated closely with the Blue Dart IT Operations team by sharing label samples and XML data for detailed investigation. After collaboration and verification, the Blue Dart team confirmed that the scanning problem no longer exists as of the latest status update. Customers experiencing similar issues should engage with PluginHive support and provide affected order details so that PluginHive can liaise directly with Blue Dart to diagnose and address label generation or scanning issues promptly.
Looking for more details or ready to get started?
Visit the app page to explore features and pricing.