Reserve Inventory - Allocation quantity reserves that quantity for the exclusive use by that customer (but does not limit the quantity that customer can purchase).
​
​

Limit Purchase - Allocation quantity establishes an upper limit of how many of the product the customer can purchase (but does not reserve that same quantity for the exclusive use by that customer).
​
​

Limit Purchase Quantity and Reserve Inventory - Allocation quantity will establish an upper limit of how many of the product the customer can purchase as well as reserves that same quantity for the exclusive use by that customer.
​
​

Reserve Inventory Depleting - Allocation quantity reserves that quantity for the exclusive use by that customer (but does not limit the quantity that customer can purchase) and decreases the allocated amount as the customer purchases the product.

Max Purchase QTY Per Invoice - This allocation type will limit the amount of product that can be on a single invoice to a maximum. This allocation will not deplete and can be set across locations, chains and any other related allocation fields to help prevent a single customer from eating up all the inventory.

Unrestricted - Allows the customer to purchase the product, used in conjunction allocation type Not Authorized to provide overrides to more finely filtered allocations. For example, if you wanted to restrict a certain product to only On-Premise accounts, you would then add an allocation of type Not Authorized for Off Premise customers. If you then want to allow a specific liquor store to purchase that same product, you could then add an allocation of type Unrestricted for that one customer. As this second allocation is filtered more granularly than the first, the Unrestricted overrides the Not Authorized for that one customer.
​
​

Not Authorized - Prevents the customer from purchasing the product. The customer is able to view and retun the product, but sales of this product are not authorized.

Used to block orders by all external sources (850 PO, dsdlink, ETC.) Internal Employees can still sell this product to retailers, but retailers are not able to order the product on their own.
​
​

This can be used with any allocation type above, and will offer the functionality of the allocation type selected with the limitation of only allowing internal users to use the allocation.
​
​

Allocations by sales rep will determine the customers that are assigned to the sales rep to enable this behavior, but does not only allow the sales rep to place orders. All internal users are able to place orders for the customers that qualify for this allocation.

*Location - Select the location that will be affected
​
​

*Product - Select the product that the allocation will be for.
​
​

*Allocation Type - determines the Customers impacted by the Allocation and the expected behavior on product Inventory.
​
​

*Start date - When the allocation starts **This is the date that will determine eligibility for the allocation. This refers to the Time Entered for the Invoice, not the Invoice date. Salesmen/customers can NOT invoice the product until this date.
​
​

*Units Allocated - Number of units in the allocation
​
​

On-Premise - Select if the product is available to on-premise accounts.
​
​

Customer Type - Select the type of customers that this product is available to under this allocation.
​
​

Salesman User ID - If the allocation is for a salesman, select the user ID from the Drop down menu. ***This will allow customers that have this salesman assigned to them to purchase this item. ***It is not for the salesmen to use on any customer they want.
​
​

Chain - If the allocation is going to be set up for a chain put the chain in this field.
​
​

Customer - If the allocation is going to be set up for a customer put the customer in this field.
​
​

End Date - The end date of the allocation. After this date, any units that are still allocated will be put back into available inventory.

In most cases, there is no need to 'layer' Allocation set filters on Customer, Chain, Salesmen, Customer Type, or to On/Off Premise.
​Example: If the Allocation is created for a certain Customer, the Salesperson and Premise are already set for that customer and adding the Salesman or On Premise conditions only complicates the logic required to process the Allocation.
​
​

As a best practice, Allocations Start Date should be set to a future date.
​
​

Allocations can stack to better create exclusions or align with business rules. The priority to determine what allocation is assigned is as follows: