Summary: A profile-switch or third-party billing rule keyed on Customer Name may not fire when it uses a regex match. When the customer name comes in as one steady value, change the match to "is" (an exact match) so the rule fires reliably.
Problem
A business rule keyed on the incoming Customer Name (used to switch profiles and default third-party billing) did not fire, so the shipment did not default to the third-party account and carrier you expected.
Cause
The rule used a regex match on the Customer Name. When the name arrives as one steady value, a regex match is fragile and did not match reliably, so the rule did not fire. On top of that, an extra carrier option was available, which let orders take a carrier the billing rule was not built for.
Fix
- Open the profile-switch or billing rule and look at the Customer Name criteria.
- Change the match from regex to is (an exact match) on the steady customer name value.
- Check that the customer name arrives exactly the same each time. If it comes in more than one way, add each version.
- Limit the carrier on the profile or rule so orders use the carrier the billing rule is built for.
- Add the field defaults the rule should set (account number, carrier, service) so third-party billing fills in.
- Reload the shipping screen and run a test order.
What you should see
A test order for that customer switches to the correct profile and defaults third-party billing to the right account and carrier, and the rule fires the same way every time.
Related articles
- Profile switch rule errors when the new profile has no integration
- Prepaid shipment flips to Bill Consignee (invalid account number)