VeraCore - Invalid Freight Code/Description

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. ---> System.Exception: Invalid Freight Code/Description: UPSN_FC
at ProMail.OMS.Orders.WSOrderSaver.validatePMObject(PMObject obj, String name, String value)
at ProMail.OMS.Orders.WSOrderSaver.validate()
at ProMail.OMS.Orders.WSOrderSaver.Save(Order order)
at ProMail.Objects.Updates.Updater`1.Update(Boolean process, Boolean commit)
at ProMail.WebServices.OMS.Order.AddOrder(Order order)
--- End of inner exception stack trace ---

Solution

VeraCore error messages can be difficult to read. We have bolded the important portion of it above.

This error is thrown by the VeraCore system when they don't recognize the ship method code on an order.
Clicking "View Order" from the alert takes you to the order in question. From there or in the alert you can see the shipping method causing the issue. In the example above it is: UPSN_FC.
There are two options:
  1. Add the code into VeraCore so they will accept the order
  2. Map the code in the Ship Methods tab of Extensiv Integration Manager to convert it to a valid VeraCore ship code.
    1. Learn more about ship method mapping

Make sure the Code field matches with VeraCore, not the description. The screenshot below highlights which field in VeraCore shows the Shipping Code that needs to match with the code in Integration Manager:


    • Related Articles

    • Setting Up VeraCore

      Integration Specs: Supported functions: Order Send Inventory Sync Pickup Multi-Warehouse Support Shipment Confirmation Pickup - Detailed Warning: Due to a limitation in Veracore, orders split due to a backorder in VeraCore will only report the first ...

    • VeraCore - Multi package orders not reporting tracking properly

      Problem Orders which ship in multiple boxes are not properly reporting both package tracking numbers and shipment cost back to the Order Source. Solution There are two causes for this: Ensure that your shopping cart or marketplace actually supports ...

    • Invalid api path - Magento

      Problem Extensiv Integration Manager 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 ...

    • Invalid response from WooCommerce

      Problem You are receiving the following error message in Extensiv Integration Manager: Invalid response from WooCommerce. Integration Manager only uses the native functionality built into WooCommerce without modifying it in any way. Integration ...

    • 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 ...