A third-party-billed order (Terms set to TPBILL) sent through the API can fail with a billing or account error and return no label when the profile's rate-shop business rules have no criterion that matches the Terms field. Add a Terms criterion (for example Terms equals TPBILL) to the profile's rate-shop rules so those orders are handled and a label comes back.

Problem

An order sent through the API with Terms set to TPBILL (third-party billing) returns a billing or account error and no label, while another order billed to the same account processes fine. Because the response has no label, the host or WMS never gets one and the shipment is not finished.

Cause

The profile's rate-shop business rules had no criterion matching the Terms field, so third-party-billed (TPBILL) orders did not match any rule and were not rate-shopped. That produced a billing or account error and no label. Adding a Terms criterion so the rules match third-party-billed orders fixes it.

Fix

  1. Open the profile's rate-shop business rules (the Default profile rules the integration uses).
  2. Add a criterion on the Terms (Shipment Terms) field that matches the billing type, for example Terms equals TPBILL for third-party billing.
  3. Apply the same Terms criterion to every rate-shop rule on the profile that should handle third-party-billed orders.
  4. Reprocess the affected order and confirm a label comes back in the API response.

What you should see

A third-party-billed (TPBILL) order sent through the API returns a label, the billing or account error stops for those orders, and orders billed to the same account keep processing normally.

Related articles

  • Set up a profile for third-party (TPBILL) billing
  • Third-party billing rule does not fire because a UDF is empty
  • Prepaid shipment flips to Bill Consignee (invalid account number)