ShipBob - Invalid ShippingOption in request
Orders fail to load from CartRover into ShipBob with the following alert:
Error sending orders to ShipBob
Order XXYYZZ ShipBob said: Http Status: 200. Invalid ShippingOption in request
ShipBob requires that you map all your cart's ship methods to the official ShipBob codes before orders can send through. To do so, follow these directions:
- For each of your carts in CartRover, go to it and click Edit Setup.
- Towards the bottom set the Reject Unmapped Shipping Codes option to Enabled. Click OK to save.
- This will ensure you are notified ASAP if this issue ever occurs again.
- Click the Ship Methods tab.
- For each cart, select the cart, in the list, select the desired ShipBob method on the right side. When finished, click Save.
Dropshipping Orders with ShipBob
ShipBob requires unique handling for dropship orders, compared to eCommerce. Each cart or order source will need to be configured to pass the required information. Specifically this needs to include the Carrier Registration ID, Dropshipping Retailer ...
Setting Up ShipBob
Required Parameters ShipBob Login Credentials Step-by-Step Guide Navigate in CartRover to your Merchant Settings. Select Grant Us API Access. This will open a new browser window asking you to log in to your ShipBob account. After logging in to your ...
VeraCore - Invalid Freight Code/Description
Problem Orders are failing to load into VeraCore with an error similar to the one listed below: Error sending orders to WMS Order XXXXXXXXXXX: Error: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> ...
Invalid carrier specified - Magento
Problem Could not upload tracking information to Magento because "Invalid carrier specified." This is caused when you ship orders using a carrier not defined in Magento. Solution Option 1: Add the missing carrier To solve the issue you need to add ...
Invalid api path - Magento
Problem CartRover displays the following error message when connecting to Magento: Invalid api path Solution This error is most commonly caused by improperly adding custom endpoints to the Magento API, which breaks/blocks the standard API endpoints. ...