Summary: When an order imports with a Ship Via or carrier-service code Shipstore cannot map (for example FedEx|HDS), loading it shows an error that it cannot set the service and asks you to set it by hand. Add an After Shipment Loads rule that sets the Service (and the Residential flag when needed) for that code.
Problem
Orders from an outside order source carry a Ship Via or carrier-service code (for example FedEx|HDS) that Shipstore does not map to a service. When the order loads, you see a message that the system cannot set the service for that Ship Via code, and it asks you to set the service manually.
Cause
The incoming Ship Via code has no matching Shipstore service, so the service is left blank at load and the order cannot go on until you pick one. A business rule can map the code to a service automatically.
Fix
- Open Business Rules for the affected profile.
- Add a rule on the After Shipment Loads event.
- Set the criteria to match the incoming Ship Via code (for example, Ship Via is FedEx|HDS).
- Set the actions to choose the correct Service (for example, FedEx Home Delivery), and for a residential service set the Residential flag to Active.
- Add a separate rule for each other incoming code you need to map (for example, the Ground code).
- Load a test order that carries the code and check that the service sets on its own.
What you should see
A test order with that code loads with the Service set and no manual prompt. The Residential flag is Active where the service needs it, and the label shows the mapped service.
Related articles
- PreRate error: service "not set up on profile"
- Set up a profile for third-party (TPBILL) billing