Field name | Description | Values |
---|---|---|
Fulfillment Rule Set Name (Required) | The name of the rule set. This name is displayed in the table on the Fulfillment Rules page. | String |
Description (optional) | A description of the rule set. It’s best practice to include a detailed description describing the purpose of the rule set for anyone viewing the rule set. If this is a cloned rule set with minor differences, describe the differences between each rule set. | String |
Field name | Description | Values |
---|---|---|
Entity | Entity is used to determine the attribute schema used to fulfill the condition. For Order Level Rule Groups, the Order schema is set as the default. For Item Level Rule Groups, the Item schema is set as the default. The default values can’t be changed. | Order, Item |
Attribute | The dropdown for attribute is populated based on the Order or Item attribute type. | Default values for Order are type , subtype , orderId , channelId , and referenceId . The default values for Item are attributes , type , backOrdered , lineId , itemId , sku . Additional values are available based on your Order or Item schema. For example, shippingInfo.address.city, price.itemUnitPrice. |
Operator | A list of supported expressions. Each expression can be used to filter in different ways. Only supported expressions are displayed for an attribute. | • Equals • Doesn’t equal • Contains • Doesn’t contain • Less Than • Less Than or Equal To • Greater Than • Greater Than or Equal To |
Value | The value of an attribute. For example, an online order can have the attribute type with a value equal to STH (Ship to home). This value can also be SDD (Same day delivery). Multiple values are supported. | String |
DC 975
location. Additionally, you can use this method for item level rules to assign fulfillment locations for particular SKUs. For example, you can provide a SKU that starts with 1122 and set this SKUs specific fulfillment location.Field name | Description | Value |
---|---|---|
Location Numbers | Used to configure the distribution location number. | String |
Allows Partial Fulfillment | Set this value to Yes if you want to allow the order to be partially filled if one or more of the SKU’s aren’t available at a particular location. For example, if an order had 5 table lamps and 1 chair but you did not have the chair available, the 5 table lamps are shipped and the chair is ignored. Setting this value to No cancels the order if it can’t be fully fulfilled. | Yes/No |
Included Location Types | A dropdown containing all the available configured inventory networks. This option is only available for the Location Prioritization action type. All the locations that are selected will be checked for inventory availability based on the additional geo locations, split shipment, and exclude fields selected. | Value is based on your available fulfillment locations. All configured locations are listed. For example: StoreDropshipDC |
Geolocation | Enable this field if you want to fulfill shipments based on the customers shipping location. If this field is set to No, Initial Boundary, Increment Size, and Maximum Boundary aren’t used. | Yes/No |
Initial Boundary | The initial circumference boundary when determining geo-location. For example, if the value 100 is provided, fabric will look to see if any Included Location Types can fulfill the order within 100 miles of the shipping location. | Number |
Increment Size | Incremental Boundary In Miles is the number of miles you want to add every time search is performed. This means if the Initial Boundary was unable to fulfill an order, the incremental circumference is increased by the number specified here. For example, we can set this value set to 50. If no stores were in the first 100 miles entered in Initial Boundary, the search boundary is increased to 100-150, then 150-200, until it reaches the Maximum Boundary value. | Number |
Maximum Boundary | The maximum search radius. Once the Increment Size reaches this number and the order can’t be fulfilled, the order is canceled. | Number |
Inventory Balancing | The Inventory Balancing dropdown has two values, Distance and InventoryAvailability. Selecting Distance means the order fulfillment is completed by the nearest store with the items in stock. Selecting InventoryAvailability, means fabric looks at each of the eligible stores within your boundary and chooses the store with the most inventory. For example, if a store had 1 item remaining and another store had 5 of the same item within the search boundary, the order fulfillment would default to the store with more inventory. | DistanceInventoryAvailability |
Order Level Split Shipments | Setting this value to Yes enables orders to be fulfilled through multiple stores if the SKU’s or items aren’t available at a single location. Setting this value to No means that fabric must find a location that has every item for an order at a single fulfillment location. If fabric is unable to find all the items in the order at a single location, the entire order is canceled. | Yes/No |
Item Level Split Shipments | Set this value to Yes if you want to look between locations to meet the item quantity request of an order. For example, if an order for 20 of the same office chair came in, and a location only had 15 available, the remaining 5 chairs would be sourced from another location. With this set to No, the remaining quantity of chairs are canceled and only the 15 at the first location are allocated. | Yes/No |
Maximum Splits allowed per order | The maximum number of locations that a split order can be fulfilled from. | Number |
Item exclusions | Allows you to create an additional condition based on an item attribute. For example, if an item is less than $10, you can create a condition to ship it from a retail store near the customer to save on shipping costs. | Yes/No |
Order
attribute are the attribute types STH
(ship to home) and SDD
(same day delivery). The rules that are created must automatically send an order to a specific location based on the shipping type selected during checkout.
The following examples outline how to create a rule set for each requirement. Although the conditions and requirements are separate examples in this document, note that all of the following examples make up a single Fulfillment Rule Set and that only one rule set can be active at any given time.
All of the examples below build upon one another.
Order
. This can’t be changed.type
.Equals
.STH
as the value.
STH
. Note that in your instance, ship to home may not be equal to the value STH
. For example, the value could be Ship_To_Home
. It’s suggested that you check your Order
schema to determine what values are allowed/expected.STH
orders to the DC
fulfillment warehouse.
STH
orders.
STH
orders need to be fulfilled in DC
.STH
use case. For more information on each of these fields, visit the Action fields table. The following list is an example of what the default values look like:
No
.No
.No
.Yes
.3
.No
.STH
is selected during checkout. However, in order to create a same day delivery SSD
condition, an additional rule is needed.
type
.Equals
.SDD
as the value.
SDD
(same day delivery). Note that in your instance, same day delivery may not be equal to the value SDD
. For example, the value could be expedite
or same_day_delivery
. It’s suggested that you check your Order
schema to determine what value is expected.DC
and retail locations Store
.
Yes
.
STH
, SDD
requires that we take into consideration where the items are located in relation to the shipping location. This is because we want to fulfill the order as quickly as possible and ship from the closest location to the customer.100
.100
.300
.Yes
.Yes
.Yes
.3
.No
.STH
orders to a DC
fulfillment location. Same day delivery SDD
orders are fulfilled based on geographical location and can be shipped from retail stores or the DC
fulfillment location.
Yes
.
Item
.price.itemUnitPrice
.Less Than or Equal To
.5
.
Yes
, fabric looks at the next action in a rule that has been specified.Items under 5$
.price.itemUnitPrice
.Less Than or Equal To
.5
.Store
.
Yes
.
200
.100
.400
.Distance
.
No
.
No
.No
.No
.
3
.No
.STH
orders to a DC
fulfillment location. Same day delivery SDD
orders are fulfilled based on geographical location and can be shipped from retail stores or the DC
fulfillment location.
In this example, an additional action is added to backfill orders with no inventory. If an order can’t be fulfilled, the remaining items are sent to a dropship location to be fulfilled at a later time.
DC
from the previous example. A new action must be created under it.Dropship
, store
, and DC
.
Yes
.
Yes
. However, this can complicate shipping logistics making it so certain orders might have multiple shipping locations for different SKUs. Check with your team to determine what settings should be enabled based on your individual needs.