Extensible Order Routing allows an Admin user to select which custom product, location, customer, Order and Inventory attributes can be filtered for in Order Routing. This provides the power and flexibility to set up order routing rules best suited to your unique business needs and determine the most optimum locations to fulfill the orders from.Extensibility is available for all clients whose implementations include Order Management. OMS-Only implementations without a catalog can only reference customer, order, and location attributes. Contact Kibo Support to have this feature enabled for you.
The following sections describe example scenarios in which extensible order routing may be useful with custom product, location, order, Inventory or customer attributes. Note that this is only used with physical items (not digital or services).
Using order routing to route products to a certain set of locations based on custom product attributes that you have defined may be useful in scenarios such as:
Products that need warm weather packaging, based on a true/false attribute called “Perishable”
Products that need two people to lift the package, based on a true/false attribute called “Two Person Lift Required”
Products of a particular brand, based on a text attribute with options for “Brand”
Using order routing to route products to a certain set of locations based on custom location attributes that you have defined may be useful in scenarios such as:
Not routing shipments to an area with a weather event, based on a true/false attribute called “Weather Events”
Not routing shipments to locations where the capacity is less than 50%, based on a number attribute called “Capacity”
Routing shipments to a location with the lowest cost of fulfillment, based on a number attribute called “Cost to Fulfill”
Routing shipments to warehouses with a two-person forklift, based on a “Lifts” string attribute with options for one, two, or six person forklifts
Using order routing to route products to a certain set of locations based on custom order attributes that you have defined may be useful in scenarios such as:
Routing orders with a BOPIS pickup time of 2:00 PM, based on a text attribute called “Pickup Time”
Using order routing to route products to a certain set of locations based on custom customer attributes that you have defined may be useful in scenarios such as:
Routing shipments specially for Platinum customers, based on a text attribute called “tier” with options of “Platinum,” “Gold,” or “Silver”
Using order routing to route products to a certain set of locations based on custom inventory attributes that you have defined may be useful in scenarios such as:
Avoiding locations with negative inventory for critical items, based on a true/false attribute called “Negative Inventory Flag”
Prioritizing locations trying to clear specific SKU inventory, based on a true/false attribute called “Do Not Replenish”
Routing based on seasonal inventory availability, based on a text attribute called “Seasonal Availability” with options for “Spring,” “Summer,” “Fall,” or “Winter”
Using order routing to route products to a certain set of locations based on custom B2Battributes that you have defined may be useful in scenarios such as:
Define customers as “Small Business,” “Mid-Market,” or “Large Account” based on annual purchase volume. Small businesses might route to a general fulfillment pool, while Large Accounts get priority processing or dedicated warehouse space for their frequent orders.
Company offers different service levels (Standard, Premium, Enterprise) defined as a custom B2B attribute. Enterprise customers require fulfillment from specific locations with white-glove service capabilities.
You can also route shipments based on a combination of attributes from the above topics. For instance, you could reference both product and location attributes in the following scenario:
Perishable candy being routed to locations that offer insulated packaging, based on the true/false “Perishable” product attribute and the true/false “Insulated Packaging”
You must make the attribute available to Order Routing in the attribute configurations in order to use the attribute in routing filter logic. For more information about creating and configuring attributes in general, see the following documentation:
In the settings of each attribute type, locate and toggle on the Available as Order Routing Filter and click Save. The below example shows the option for a product attribute.Attributes must include the “Property” type to be used in order routing. You can select more than one attribute type, such as Property and Extra. Make sure that the attribute is not set to “Admin Only” in the display group.This example shows the option for a location attribute:The example below shows the option for an order attribute.This example shows the option for a customer attribute:This example shows the option for a Inventory attributeThis example shows the option for a B2B attribute
Once enabled, you will be able to select the attribute in routing filters. The Order Routing UI has been overhauled in August 2025 with an updated look and feel, as well as some functional changes. This new UI is now available to be enabled in your sandboxes. Contact Kibo Support to opt in and begin using it. All sandbox tenants will receive the new UI on September 3, unless you have specified to opt out by notifying Kibo Support. The UI will also be available for production tenants on September 3. Coordinate with Kibo to migrate your production tenants at any point between September and end of January 2026.Expand the below sections to attribute filter details for the appropriate UI version.
If you have not yet upgraded to the new Order Routing UI, then you are using the Classic UI. When configuring a filter, you will be able to define logic based on that attribute by selecting the filter type “Custom Value.”These sections can be expanded to display the out-of-the-box attributes as well as your custom attributes for each topic:The possible logic conditions will change depending on the data type of the attribute you selected. For logic conditions that support multiple values, such “or” and “any of,” you will be able to select multiple values from the dropdown. For logic conditions that support only single conditions, like “equals” or “not equals,” you will only be able to select one value.If you select a list filter type, it will support the “in” or “not in” logic conditions. For example, if your filter attribute was Material then you could use “in” to compare it against the Iron, Steel, and Aluminum custom values. If the item matches any one of those values, it will attempt assignment.
In the new UI, be aware that filters are defined within scenarios and cannot be shared across multiple scenarios. When configuring a filter, you will be able to define logic based on that attribute by selecting the filter type “Custom Value.”The possible logic conditions will change depending on the data type of the attribute you selected. For logic conditions that support multiple values, such “or” and “any of,” you will be able to select multiple values from the dropdown. For logic conditions that support only single conditions, like “equals” or “not equals,” you will only be able to select one value.If you select a list filter type, it will support the “in” or “not in” logic conditions. For example, if your filter attribute was Material then you could use “in” to compare it against the Iron, Steel, and Aluminum custom values. If the item matches any one of those values, it will attempt assignment.
