Australia Post Checkout or API Error Messages – Shopify Australia Post Shipping App with Rates, Labels & Tracking FAQs
-
Identify and fix API or checkout errors for smooth Shopify shipping
Questions in this section:
- What should I do if I encounter an error or failed attempt when booking a shipment with PluginHive’s AU Post integration? (screenshot)
- What should I do if I see the error “Role with this name already exists” when trying to grant collaborator access in Shopify?
- What should I do if my product CSV import is failing when updating product dimensions?
- What steps must I complete before obtaining access to the Australia Post production environment?
- Why am I getting a "bad request" error at checkout saying there is nothing in the cart, even though I have added a product?
- Why do I get error code 413 when importing a CSV file with updated weights and dimensions for products?
What should I do if I encounter an error or failed attempt when booking a shipment with PluginHive’s AU Post integration? (screenshot)
If you face errors or a failed shipment booking process: 1. Reach out to PluginHive support along with a screenshot of the error and Approve the Shopify store collaborator request sent to your store’s email address by PluginHive. 2. Inform PluginHive support once the request is approved. 3. PluginHive support will investigate your store’s setup and assist in resolving the order processing issue.
What should I do if I see the error “Role with this name already exists” when trying to grant collaborator access in Shopify?
If you encounter the "Role with this name already exists" error while sending a collaborator request, try these steps: 1. Check your Shopify Collaborator Requests section to confirm if there is a pending invite for the same collaborator email. If so, cancel or respond to the pending request. 2. Once the pending request is cancelled, contact PluginHive support so that they can raise a fresh request for Collaborator Access for your store.
What should I do if my product CSV import is failing when updating product dimensions?
If your product CSV import is failing, review the CSV file for formatting errors or missing information, especially in the dimension fields. You can also share the updated CSV file with PluginHive support to help identify and resolve any issues from their end. This ensures your product data is correctly imported and the shipping calculations work as intended.
What steps must I complete before obtaining access to the Australia Post production environment?
Before being granted access to the production environment, you must: 1. Complete and submit the “Lodgement Integration Validation” document. 2. Provide a PDF of all label types for the services you use (e.g., Express, Standard, single and multi-article shipments, ATL, international, On Demand). 3. Submit a PDF Order Summary (your paper manifest). 4. Supply all API payloads (Requests/Responses) in JSON format. 5. Describe your workflow process. 6. Detail your error handling process. All required documents and information should be submitted via the Lodgement Support form: https://auspost.com.au/lodgement-techsupport. The initial review process typically takes up to 5 business days.
Why am I getting a "bad request" error at checkout saying there is nothing in the cart, even though I have added a product?
A "bad request" error indicating an empty cart can occur if the product cannot be successfully added to the cart due to frontend or backend issues. Please contact PluginHive support for more clarification.
Why do I get error code 413 when importing a CSV file with updated weights and dimensions for products?
Error code 413 can occur if the imported CSV file differs in structure from the original export. Ensure that after exporting the CSV from the app, you do not remove any rows or columns. To avoid this error, follow these steps: 1. Export a new CSV file from the app. 2. Do not delete any rows or columns in the exported file. 3. Only update data in the required columns as needed. 4. Save the file in csv format without altering its structure. 5. Try importing the unchanged file with just the updated data. This process helps ensure compatibility and prevents import errors such as code 413.
Looking for more details or ready to start using the plugin?
Visit the product page to explore all features and pricing.