Back to

Throttling Strategy: Orders Per Window


To prevent too many orders from coming in at once, a store can set a maximum amount of orders that they can accept per 15 minute time slot. With this strategy, each store can set their own maximum number of orders to accept in a 15 minute period. 

An additional feature of this strategy is the ability to leverage our channel management functionality to limit the number of orders that come in from a Rails marketplace provider in a 15 minute period. For example, if you want to limit a specific provider to only send X orders every 15 minutes, you can do so using channel management. Note: If marketplaces are not able to get orders through to a store, they may deactivate the location on their system. We suggest reaching out to your marketplace partner(s) to ask how they handle throttled orders before proceeding. 


In the above screenshot, you can see how a Dashboard user can set a maximum number of orders per window and have the option to enable advanced channel limits. If this setting is set to Yes, a user will have the ability to individually limit the number of orders that come through their direct digital interfaces and Rails Marketplace partners. 

For example, a brand which accepts orders from Mobile Apps, Desktop, Mobile Site (regardless of the front-end UI/UX provider) would have a single throttling limit that will affect all orders incoming from these branded assets. They can then further enforce limits by putting a maximum on the number of orders that each Rails Marketplace can place in a 15-minute time slot. The number of orders for each individual provider and the direct brand channel must equal the number of orders per window. This section will only appear if the store is enabled for Rails. 

What's the customer experience like? 

ASAP Orders: Let's say a store only accepts 10 orders every 15-minute time slot and the 1:00 - 1:15 pm time slot has 10 orders for pickup during that time. If a customer attempts to place an order at 12:48 pm with 16 minutes of make time for ASAP, which would normally result in a 1:04 pm pickup, a message would appear when the customer attempts to proceed to checkout saying "{StoreName} is experiencing high order volume and cannot immediately start your order." Once the customer sees the message, they can select a later time and attempt to to checkout again. 

Later Orders: If a customer is placing an order for lunch tomorrow but their desired time slot of 1:00 pm is full, they will see a message saying "{StoreName} is experiencing high order volume and cannot prepare your order for {DesiredTimeSlot}."  Once the customer sees the message, they can then select a different time slot and attempt to proceed to checkout again. 

Both the messages outlined above are configurable. If you'd like to adjust the ASAP or Later message, please reach out to your CSM and we'll be happy to adjust. 

How do I enable this throttling strategy?

If you're ready to move forward with Orders Per Window, reach out to your CSM to enable it at the channel level. All throttling strategies need to be set at the brand/channel level, meaning that every store within a brand must share the same throttling strategy. They do not, however, all need to have throttling enabled as you may only want to throttle at some stores and not at others.

Once the channel level strategy is set, your CSM will ensure the throttling settings are visible in the Dashboard for a particular store (or for all stores). Once that is enabled, you will be able to access a store's Order Throttling settings by going to Settings --> Store Settings --> Select Store --> Order Throttling with Channel Management. 

Not sure if this is the right throttling strategy for your brand? Visit our Throttling Strategies Overview article to read about the other strategies we offer. 


Didn't find what you need?

Submit a request to our Help Team and someone will
get back to you shortly.

Submit a request

Copyright © 2020 Olo. All rights are reserved.