Summary
Auto Carrier Selection decides which carrier reference a shipment should be booked with, so you do not have to set a carrier on every shipment before booking. A set of routing rules you define is evaluated against the shipment’s data, and the matching carrier reference is assigned to the shipment, ready for booking.Who it’s for
Logistics and operations teams that ship with several carriers and choose between them by destination, weight, service level or similar criteria. It removes the need to decide the carrier in your own systems before a shipment reaches Perform.AI, and it keeps complex routing logic in one place.Key benefits
- No carrier reference needed up front. Create the shipment without a carrier and the rules assign one.
- Rules use the data you already send. Conditions are built from existing shipment fields and your configured carrier list.
- Complex logic stays readable. Multiple rules with AND and OR conditions are ordered by priority, so the first matching rule wins when several apply.
- Every outcome is visible. Each shipment is tagged with the routing result, and the tags are filters in Booking Overview.
- Re-run on demand. After rules change, the Auto Assign Carrier action re-evaluates selected shipments.
How it works
Rules
A routing rule combines one or more conditions on shipment data fields, joined with AND or OR, and produces one outcome: the carrier reference to book with. Carrier references come from the carriers configured in Settings > Carriers. You can define several rules; they are ordered, and the order decides which rule applies when a shipment satisfies more than one. Rules can compare the carriers available for a shipment on cost and delivery speed, and a fallback can take over when a carrier is delayed.When rules run
Rules are evaluated when a shipment is created. You can also trigger them manually with Auto Assign Carrier in Booking Overview or on a shipment’s detail page, for example after the rules were changed. Manual re-runs do not apply to shipments that are already Booked or Shipped.Outcomes and tags
The tags are available as filters in Booking Overview.
Override
By default, routing only fills in a missing carrier reference. If you enable the override function, the routing result replaces a carrier reference you uploaded with the shipment. Decide this when you define the rules.Set up in the portal
There is no self-service rule editor. Rules are set up on your account by Perform.AI:- Contact your Customer Success team to start the routing rule setup.
- Fill in the routing rule template with your conditions, their order and the carrier reference each rule should produce, and state whether the override function should be enabled.
- Confirm the rules in a review with Customer Success; they are then enabled for your account.
- To re-run the rules on existing shipments, go to Logistics > Booking Overview, select the shipments and choose Auto Assign Carrier, or use the same action on a shipment’s detail page.
Use via API and MCP
Create the shipment with Create a Shipment without acarrier_reference; routing assigns one. Then call Create a Booking (POST /v5/booking/) with the shipment_id or shipment_uuid and omit carrier_reference, so the booking uses the carrier the rules assigned. If the shipment carries the routing_noresult tag, pass a carrier_reference in the booking request instead.
FAQ
Can I edit the rules myself in the portal?
Not currently. Rules are configured on your account by Perform.AI from the template you fill in. Contact your Customer Success team to change them.What happens when no rule matches a shipment?
The shipment is taggedrouting_noresult and stays without a carrier reference from routing. Filter Booking Overview by that tag and assign a carrier manually, or book it with an explicit carrier reference.
Will routing change a carrier I already set on the shipment?
Only if the override function is enabled for your account. Without it, routing fills in missing carrier references and leaves existing ones unchanged. When it does replace one, the shipment is taggedrouting_<carrier_reference>_replaced.