# NO BOT PROTECTION

## INFORMATION

There is quite a-lot that goes into botting restocks with no BP. Firstly you will want to understand how botting these restocks works and you also need to identify if your bot is even capable of botting said restocks as there are only a handful of bots that are capable. So if your bot does not have the right restock flow system there is literally no point running these restocks as you will have a huge disadvantage.&#x20;

## BOT RESTOCK FLOW

As we just mentioned there are only a hand full of bots that have what we will call the "submit" method. If you your bot has this method, when you start tasks it will add the item to cart despite it being OOS, fill in all your shipping, billing and payment information then it will attempt to submit the order / payment every x seconds, x is determined by your delays. Bots that do not have this method will, when started, attempt to add the item to cart. If the item is out of stock it will not be able to add to cart so it will just try again and again determined by your retry delay.&#x20;

So now lets say you have Bot #1 that uses the submit method and Bot #2 that does not monitoring for a restock of item x. Item X restocks and Bot #2 the one without the submit method adds to cart, adds shipping information, adds billing informa-.... oh wait, Bot #1 with the submit method already did all of that when they started the tasks and submitted the order long before Bot #2 was even able to finish adding all the profile details. That is why this method is so superior and if you have a bot that does not use this method, your chances of hitting a restock are extremely slim.

However this all depends if someone is running for Item X already with the submit method. Lets say a very random item restocks that not many people know is profitable and you quick task it from the monitors, you might be able to cop because no one was running submit restocks on it. So it kind of depends what item it is. Chances are if its profitable and or has dropped recently. There will be many people running hundreds of tasks using the submit method so chances of you copping without are low.

### BOTS WITH SUBMIT METHOD

As far as we know there are only a select few bots that use this method and they are listed below. However its likely many others use this method, we are just unaware of them as of now. We will try to update this guide if we find any other bots that utilise this Shopify restock method.

* **Nebula**
* **Balko**
* Prism
* Cyber
* \+ Others

We have highlighted Nebula and Balko as they are the kings of Shopify restocks and their method, although its the same submit method as the other 2, theirs seems to be more consistent.

So, as we have said if you do not have these bots you are unlikely to hit restocks that are commonly occurring. Lets say Item Y restocks and you see it in the #shopify-filtered channel, as we said you may be able to cop if you quick task and you are fast enough however, any restocks after that will be nearly impossible to hit for Item Y as people would have noticed it restocked then setup hundreds of tasks submitting orders every second until it restocks again. It all just depends on what type of restock it is.&#x20;

If its for example, restocks after an initial drop, you wont hit unless you have a bot that supports said method. But if its a random restock for a random item, you might hit the first but any after that you likely wont.&#x20;

If you want to find out if your bot has this method, find a Shopify site with an out of stock item and setup tasks with a fake profile (just incase said item actually restocks whilst your testing) using your bots restock / fast mode. Watch your task status and if it just goes straight to "waiting for restock" or something similar such as "monitoring" then your bot does not have this method. If the task submits your shipping, billing and payment information, then either sits on "waiting for restock" / a similar status or attempts to submit the payment / order over and over again, then it has the correct method.&#x20;

## MORE INFORMATION

So you have a bot with the submit method, if you setup correctly you should be able to hit restocks hard. Not many people fully understand how to utilise this method to its fullest potential. Before we go on we are going to quickly explain this method a bit more.

Every task you make is going to attempt to submit the order every x seconds. x is your delay. Let's say you have a delay of 1000ms. That task is going to attempt to submit the order every second. As restocks are extremely competitive you have to break everything down to milliseconds. In an ideal world you would want 1 task submitting an order every millisecond, so yes, you ideally want to be running 1000+ tasks on 1000ms delays however you cant run 1000ms delays or your proxies will eventually get rate limited (429) you need to be running at-least 2222ms. We will get to task count later but that should give you a general idea of how it works.&#x20;

The more tasks you are running the more times you're going to be submitting the order. So lets say we are working in a 10 millisecond window the more tasks your running the more times your going to be submitting orders in that time frame, lets item x restocks on the 7th millisecond and you have a task cycling to submit an order on the 8th millisecond, your likely going to hit because you attempted to submit the order just a millisecond later. However we are getting way too deep into this, you don't really need to understand the minute details you just need to sort of understand how it works.

We are not going to go any further into the explanation we will just get started on the setup. There are multiple times when you will want to be running restocks and the main one is after BP goes down after an initial drop. Lets take Kith for example, the initial drop for item x is at 10am EST. Once the item drops its likely going to restock a-lot after its dropped however BP is still on so you will not be able to run your fast / restock task modes, only safe / preload will work otherwise your tasks will get picked up by BP. Bot protection usually goes down around 15-30 minutes after the release. This is when you will want to start your tasks. The ideal setup would be your normal initial setup for the initial drop. Then once the drop is finished you will want to prepare tasks for when BP goes down so you can run for restocks.&#x20;

As soon as you see BP is down in #shopify-antibot-password start those tasks. Next we will talk about how to actually setup these tasks. Again, before we get started we just want to mention more about task count. As we know the more tasks your running the more times your going to be submitting an order in a given time frame, however this is only for each size, for the sake of explanation lets say your running for an item with 500 sizes, your 500 tasks on 1 task per size using the recommended 3333ms delays, your only going to have 1 task submitting an order for each size every 3333ms which is a long time so your probably not going to hit. The aim of the game is to run as many tasks as possible for **each size.**

## **SETUP**

### Variants

You will want to be using variants for this, you can get these by typing `-shopify productURL` in any channel, however all the variants we recommend you run will be posted in #us-restocks after all profitable Shopify releases. Copy the full variant list, or if you only want to go for a select few sizes just copy the corresponding variants. Next go to your bot and paste these variants in the keyword section or if your bot has a specific section for variants, post them there. Next set your task mode to fast or restock depending on your bot. Next select as many profiles as you desire, the more the better and create your tasks. Ideally you will want to be running as many tasks as you possibly can and this will lead us onto proxies.

### Proxies

So ideally, you will want to be running restocks for as long as you can, and even in some cases you will want to be running for restocks on certain items 24/7. So this is where ISP's will be best. But as ISP's are extremely expensive and you will want to be running upwards of 1000+ tasks so this is where resis come into play. Basically any and all ISP or Resi will work so you wont need the best of the best. There are a hand full of ISP providers that will sell ISP's for incredibly cheap that will only work on Shopify no BP and other sites with little to no proxy filtering. These would be ideal especially for long term restock running. However residential will also do the trick and allow for easy scaling. These are better for short and sweet restocks.

With residential you will want to identify the best time to use them which is most of the time, for items that are constantly restocking or items that are restocking after an initial release. As we know the more tasks your running the better, so put thousands upon thousands of resi IP's into a proxy list, we suggest 10,000 just to be safe, and use that proxy group to make hundreds if not thousands of tasks for item x that is restocking. Depending on your bot data usage for submit order restocks is next to nothing, for reference we ran 1000 restock for over 5 hours and used just under 1GB. Usage is extremely minimal meaning you should not be afraid to run thousands of tasks using resis for restocks. But again, this is not exactly ideal if you plan to run restocks for item x 24/7.&#x20;

### Delays

We recommend you run 2222ms delays for short and sweet restocks, 3333ms delays for kind of long term restocks and 5555ms for 24/7 restocks. Try to base your task count around this, remember the more tasks submitting order per second the better.

### Stagger Start Time

This is a very important step for maximising your chances, its no use starting 1000 tasks at the exact same time on the same delay. Lets say you start 1000 tasks at the exact same time on 5000ms delay, every 5 seconds all your tasks are going to submit the order, if a restock happens 2 seconds after the last order submit attempt your tasks are going to have to wait another 3 seconds before they attempt submit the order again, and in that time frame that restock likely went OOS. Remember most restocks after often 1 stock at a time. So the aim of the game here is to stagger start your tasks. \
\
Start 1 task at a time and depending on how many tasks you run try to start tasks around 0.1 seconds after each other. However don't read into it too much as some proxies will be a few ms slower than others so they are naturally going to eventually spread them selves apart. Another good technique if your bot supports it is to run different delays for a chunk of tasks. Let's say you're running 1000 tasks and you started them all at random staggered times. It's suggested you, for example run 250/1000 tasks on perhaps 3216ms then another 250 on 4318ms then another 250 on 2341ms and so on.... random delays above 2222ms works well.&#x20;

### Captchas

As there will be no BP you will not need to solve checkpoint captchas however, sometimes sites will leave checkout captcha on meaning every task will have to solve a checkout captcha. The good news is you will only have to solve 1 captcha per task every 10 or so minutes so in that 10 minute time frame you can still run for restocks. It's not ideal to run for restocks on an item that still has a checkout captcha enabled but this just means the competition will be less and it might be easier to cop, It's just more of a hassle. If your bot supports third party captcha solvers you can have a third party captcha solve all these captchas for you.

## CONCLUSION

You now know how to run for restocks. Just to recap:

* Try to run as many tasks as you can, in the thousands if possible.
* ISP's are ideal but resis are good for scaling up task count
* Be consistent, and don't give up.&#x20;
* Remember you are up against thousands of others for literally 1 stock at a time, the more task your running the better chances you have of submitting an order as soon as that 1 stock loads, before anyone else's tasks.
* Use variants
* Run as many tasks per size as possible
* Identify which sizes are commonly restocking and target those if you are not hitting.
* Ensure your bot supports the proper restock method or you wont have a chance at hitting restocks unless its a random restock for a random item

### &#x20;
