# Welcome to PepperScripts documentation ![](/files/-Maiyajewq9n28y2vBSV) First of all: we are very happy to have you in our Pepper family! **Please take your time and read this guide carefully.** Many of your future questions can find an answer here. If there still is anything left you would like to ask, feel free to open a ticket in our Discord and a supporter will help you for sure. Are you ready? On to the [first steps](/getting-started/first-steps)! # Rules You can use these in real-life too! 1. Have respect for each other. Everyone started somewhere. 2. Do not spam any channel on our server. 3. You are not allowed to use any offending words / racist terms - this also goes for your nickname and avatar. 4. Do not post any adult / explicit / controversial graphics or messages in our Discord. 5. **Do not share your key / Discord account with anyone. Break this rule and your access will be revoked without warning.** 6. If there is any issue please make sure to use our ticket system. This is the best way to find a solution. 7. **All keys are non-rentable / non-unbindable / non-sellable.** 8. **Do not share anything to anyone besides your private success webhook. Do not take any screenshots, videos or other stuff from PepperScripts and share it with someone else. Doing so will result in you losing your key without warning!** # Dashboard You can access the Pepper dashboard anytime by using this link: In the dashboard you will find your Pepper key. # First steps Well.. what is the first step? It's time to start. Pick up a towel, a bottle of Gatorade and... get ready! First of all download the Pepper bundle specifically for Windows or macOS (you will find the links in our server - #updates) and unzip it in a folder where you want to place Pepper. You will only see #updates in our server if you got verified by staff members. For that, please fill your information into the billing link, that our bot (PepperScripts#0786) sent you. If the link expired, open a ticket and click on the "change data" button. This folder **can not** be changed later, so pick your desired folder carefully! \ If you need to change the folder afterwards Pepper might require a full re-setup. For an easier change, have a look at our [import / export function](/getting-started/options/import-export)! You should also exclude this folder from your Anti-Virus tool - as some tools cause trouble when running Pepper / the updater. Yes also Windows Defender (guide [here](https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26#ID0EBF=Windows_11)). Last but not least: the folder **has to be a local folder** - not a cloud-synced (GoogleDrive, OneDrive, MEGA, ...) folder! Next and most important step:\ Have your license key ready as you will need to copy & paste it into the updater on your first run. (Pasting something into the CLI/Updater on Windows only works by right clicking your mouse!) You can now run the updater in order to automatically download the latest version of Pepper. \ Windows users: run the updater **at least once as administrator**.\ MacOS users: run the updater once by right clicking on it, then click on Open. For the next times you can just double click it. This whitelist our updater from the master control checker. Now hop over to the extensions page of Chrome (yes please use Google Chrome as other chromium based browsers might cause issues) which you can access with the puzzle icon on the top right. Allow the developer mode on the top right of that page and click on Load Unpacked, where you select the "extension" folder, which was created by the updater. Start Pepper by clicking on the Pepper logo in your extension bar and it will ask you for your license key. Input it and login with your main Discord account (if we'll notice that you are using a burner Discord account we will immediately revoke your license without any warning - same goes for sharing Pepper with anyone). Remember that **everytime you change your ip** you'll need to re-login. This is needed for security reasons. This includes the use of proxies, VPN, mobile hotspots or just the overnight IP renewal of your provider. ### The settings.json This file will be automatically created by the updater on your first installation. It contains following options that we will explain now: 
{
"license": "YOUR PEPPER KEY",
"spawnLimit": 5,
"harvester": {
	"enabled": true,
	"bankSize": 2,
	"preferredSolver": "random",
	"capmonsterKey": "YOUR CAPMONSTER API KEY",
	"twocaptchaKey": "YOUR 2CAPTCHA API KEY"
	"capsolverKey": "YOUR CAPSOLVER API KEY"
	"aycdKey": "AYCD TOKEN:AYCD BOT API KEY"
	},
"paypal": {
	"username": "YOUR PAYPAL E-MAIL",
	"password": "YOUR PAYPAL PASSWORD",
	"country": "YOUR COUNTRY ISO CODE (like DE, IT...)"
	},
"webhook": "YOUR WEBHOOK",
"sites": {
	"nike": {
		"disableVideos": false,
		"disableImages": false,
		"browser": "chrome"
	},
	"amazon": {
		"disablePublicWebhooks": false,
		"restartTaskAfterCheckout": true
	}
},
"imap": {
	"host": "YOUR IMAP HOST (like gmail)",
	"port": 993,
	"username": "YOUR E-MAIL",
	"password": "YOUR E-MAIL PASSWORD"
	}
},
"cloneable": false
**License**: your Pepper license key **Spawn Limit**: defines how many Chrome instances will be spawned if they have a defined [mirror mode](/getting-started/shortcuts#start-mirror) shortcut. **Harvester**: defines the size of your captcha bank and which solvers will be used to fill the bank if you don't fill it manually. **PayPal**: your settings for PayPal sessions with CLI. Pretty self explanatory. **Webhook**: this is additional, for example if you want your Nike webhooks to go somewhere. Normally your specified webhook in the Pepper instance is used. **Sites**: * *Nike*\ Here you can specify: * if you want to disable videos or images. This can be pretty helpful for running residential proxies as this will limit data usage. Put "true" or "false" depending on what you want. * which browser to use "chrome", "edge" or "brave" are supported (of course these browser has to be installed on your machine. * *Amazon*\ Here you can specify: * if you want to keep your webhooks private with `disablePublicWebhooks` (enable it only if you doing FBA and you don't want to share your clips). Don't abuse it for normal or Pokemon items or your module will be disabled * `restartTaskAfterCheckout` self explanatory. **Imap**: This part is solely for imap. Pretty self explanatory. **Cloneable**: you decide if you want to automatically start a new instance as soon as CLI module is started. This is useful if you want to have always an instance ready to be launched via quicktasks. ### The updater This will be your best friend... after Pepper of course. You will not need to manually download every update. You simply run the updater and it will replace your old Pepper version with the newest one. Simple as that. **After that** go to `chrome://extension` inside your Chrome and press the small reload button as shown in the picture below. Repeat for each of your Chrome instances. **This step is very important -> do not forget it!** ![](/files/-Mk6yT0mm26VZV65ZTQ2) # Common issues Make sure you checked this section of the guide before we hit you with the evil :checkguide: emote in the chat...! ;-) Here you will find the most common issues while using Pepper - the solution we present helps in 99% of the cases. If you have followed the possible solution and it does not solve your problem: you belong to the unlucky 1% - please open a ticket! **Always ****make sure**** first that you are ****using the latest version of Pepper (+ refresh in Chrome)**** and that your ****Pepper instance is active**** (= does not need to be reset when you click on the icon).**\ \ Please use the search function of your browser to find a matching issue more easily. **Updater errors** *I get "challenge expired" or "bad request" error when running my updater / CLI.*\ Solution: Synchronize your pc time and try again. *"Request failed with status code 403"*\ Solution: Log into the [whop dashboard](https://whop.com/hub/) once in a while so your license is linked to their system. *"EPERM: operation not permitted, unlink 'C:\Users\\\[username]\\\[savedPlace]\\\[foldername]/pepper-cli.exe'"*\ Solution: Close the CLI while updating. **General errors** *Everytime you start Pepper you have to reset your key.*\ Solution: Your external (= Internet, not LAN) IP has changed. Usually your internet provider resets your IP every night automatically - you can't change that. Just add resetting Pepper every morning to your daily workflow! # Chrome Extension Access the Chrome extension options by right-clicking the PepperScripts icon in your extension bar. You can also enter the options by Accounts or Profiles inside the extension. {% content-ref url="/pages/-MfYMUP19mBEj8jwi7yT" %} [Settings](/getting-started/options/webhook) {% endcontent-ref %} {% content-ref url="/pages/-MfYLkSP89nqcN4lA3Fp" %} [Overview](/getting-started/options/dashboard) {% endcontent-ref %} {% content-ref url="/pages/-MfYLnx4zzB2zibtGdCI" %} [Store accounts](/getting-started/options/store-accounts) {% endcontent-ref %} {% content-ref url="/pages/-MfYLuTBJaJzwEGLxjK0" %} [Profiles](/getting-started/options/profiles) {% endcontent-ref %} {% content-ref url="/pages/V6nVeteWjWvDWbzV8FJ6" %} [Solvers](/getting-started/options/solvers) {% endcontent-ref %} {% content-ref url="/pages/a7MFCWohRQgVHmD7m8a3" %} [Logger](/getting-started/options/logger) {% endcontent-ref %} {% content-ref url="/pages/-MfYLxAV1hadS64uAq4Y" %} [History](/getting-started/options/history) {% endcontent-ref %} {% content-ref url="/pages/-Mg2EAB3flQei5MsOhhm" %} [Import / Export](/getting-started/options/import-export) {% endcontent-ref %} # Settings You can access the settings by clicking on your Discord avatar within Pepper. First of all, you can refresh the remote config. This is super useful if we change something in the backend and you need the newest version (e.g. a new shopify store). You can give your Pepper instance a custom name to identify it later more easily when using multiple-instances. One field below you can define your own Discord server webhook. This will allow you to send your checkouts to your own Discord server including checkout information and PayPal/3DS confirmation links. **Don't forget this!** As a little extra you can re-position the PepperScripts on-site popups to a location of your choice to prevent overlapping with other notifications or important buttons.
# Overview The main options page will show you the Dashboard which gives you a summary of all your money spend on each of our supported stores. The Dashboard is automatically synchronized accross all of your PepperScript instances! One click on the [History ](/getting-started/options/history)button will give you a more detailed overview about your purchases.
# Store accounts On this page you will save all your store accounts. Multiple accounts can be saved for each store. You select the shop, then give it a name before inputting the username (E-Mail in most cases) and Password.\ \ For data security reasons these accounts are not synchronized across your PepperScripts instances. **Please make use of the** [**Import / Export**](/getting-started/options/import-export) **feature and save the generated file somewhere on regular basis to never lose your accounts and profiles!**
# Profiles On this page you will save all your checkout profiles. You can save as many profiles as you want. For data security reasons these profiles are not synchronized across your PepperScripts instances. Please make use of the [Import / Export](/getting-started/options/import-export) feature.
Creating the profile is quite simple. Just follow the example values of each field and nothing will go wrong. Fields like "Second Address Line", "Company Name", "VAT Number" and "PEC or SDI code" are optional of course.
For your name and address options you can also fill **XXX** to have Pepper automatically jig your profile information with random letters for each checkout. Be aware, that using the auto-jig feature will store many new addresses for stores like LuisaViaRoma or Zalando. This is just a cosmetical issues and will not affect your account in any bad way. > **Please make sure that your profile name does not contain any special characters like: ä-ö-ü-ß... just use the regular alphabet + numbers from 0-9** Please see the example below: ![](/files/-Mk7-tISommco8J2lakR) # Solvers Define your 3rd party captcha solver keys Use this page to define your 3rd party captcha solver API keys - following services are available: * 2Captcha * CapMonster * CapSolver We also fully support the use of **AYCD Autosolve**! Read more about it here: [Captcha harvester](/getting-started/cli/captcha-harvester) # Logger As per the name, our event logger will log events created by running many services in the Pepper ecosystem. As of now both the [routines scheduler](/getting-started/cli/routines-scheduler) and our [captcha harvester](/getting-started/cli/captcha-harvester) are supported. You can easily monitor what is happening. Which service is doing what and when it happened. All good but.. where I can open the Logger? Well, it's easy: * Open Pepper * Click on your avatar * Choose Logger * You are done If you want to quickly access to our Logger, save the resulting URL as a bookmark. # History The History page will give you a detailed overview of your success. You can delete your test checkouts or checkouts you don't want to have in your history manually using this page. The History is automatically synchronized accross all of your PepperScript instances! You can also get your checkout links from here in any case.
# Import / Export In order to transfer all of your PepperScripts settings, store accounts and profiles to another PepperScripts instance you will need make use of the import / export feature. Simply click Export to create an encrypted file containing all your data. You can open this file with any text editor of your choice. Copy & paste the complete content of that file into the Import pop-up. # CLI Always make sure to run the CLI as ADMIN to avoid any possible errors! You can start multiple CLI instances.\ If you do it you will see that just one will be considered as **Master**, other ones will be considered as **Peer**. ### Master instances Are responsible of accepting quicktasks, serving our built-in harvesters and coordinating your browser instances with all utilities we always offered. If you need to mirror a link, bootstrap your chrome instances at once and do what you are used to do with our CLI just run it here. ### Peer instances Also considered as standalone ones, are simple instances that will run CLI modules.\ They are context isolated. They will not comunicated with any chrome extension running on your instances. Consider them like continers that can only run tasks. Nothing more. *** {% hint style="warning" %} On Windows, as soon as you open the CLI a popup appears by asking you if the app "driver.exe" can access your network: **please allow it** or CLI modules will not work! If you - by mistake - denied the network access please head to:\ \- Settings\ \- Privacy and Security \ \- Firewall\ \- Allow apps via firewall\ \- Scroll into the list and search for *driver.exe* and manage his permissions by allowing it to access your network {% endhint %} # Mirror product page Very simple: this function will open an URL of your choice in all connected instances! You can use the [mirror shortcut](/getting-started/shortcuts) for this or simply paste your desired URL and hit enter. Keep in mind - every instances is one more chance to cop. # Available sites For each of our supported sites, we offer different options for the CLI If you open the CLI, go under option 2 `Available sites` you will see some shops in there. Many are "just" helpers for the extension instances, for mirroring link, starting preloads and stuff like that. Others are real modules that can be ran directly via our CLI. You will find more details [here](broken://pages/YddPcboVBT0ChMNFFsqu). # Spawn Chrome instances Right after starting the CLI, you have the option to choose "Spawn Chrome Instances" as second available action. This will **automatically open every Chrome user** on your computer that has a [**shortcut for mirror mode defined**](/getting-started/shortcuts)**!** In your [settings.json](https://docs.pepperscripts.com/getting-started/cli/pages/-M_XOszXGomxz7135gcR#the-settings.json) file, you find a line called "Spawn Limit". Here you can define how many Chrome instances the CLI should **spawn as a maximum**. {% hint style="info" %} For example if you leave the default number of 10, the CLI will spawn 10 Chrome instances, even if you have a shortcut defined in 15 Chrome instances. However, if the limit is at 10 and you have a shortcut defined in only 5 instances, the CLI will only open 5 instances. {% endhint %} # Routines scheduler The routines scheduler could act as a solution for users that won't be available on their Computer for drop time. With the routines scheduler you can define a series of tasks that will be run automatically on your command / pre-defined time. Running the routines scheduler requires you to have correctly filled .csv file in your "tasks" folder, which you will find in your main PepperScripts folder. Please don't forget to give your instances a string value as name, even if you don't want to exclude/ include instances (we will talk more about that in a minute), such as "A" "peppermain" or whatever you desire. Do that by clicking on the pepper popup and select the settings page. We will use this example file to show you some of the already available functions: {% file src="/files/PpIlOTxneWDTz0T1nBTh" %} Routines scheduler example.csv {% endfile %} ``` SITE TIME ACTION VALUE INCLUDED INSTANCES EXCLUDED INSTANCES BROWSER 08:25:00 OPEN TAB https://www.zalando.de/ ZALANDO 08:25:20 START PRELOAD zalando BROWSER 08:34:55 OPEN TAB https://www.zalando.de/schuhe/?q=NI112O0P7-A11 PPR-QSP BROWSER 08:37:00 CLOSE TAB zalando ``` These are the lines included in the file - and what will happen is quite self-explainatory: At 8:25, Pepper will open the german Zalando homepage and start the preload 20s later. At 8:34:55, which is 5s before drop, Pepper will open up a product page only for the instance named `PPR-QSP` and let it run. If you haven't copped initial, it will start monitoring with the right settings. By 8:37 the tab will be closed If you look closely, you can see columns for INCLUDED INSTANCES and EXCLUDED INSTANCES - this refers the name of your instances, which you can set [here](/getting-started/options/webhook). If you leave those options empty, all connected instances will be effected. Following commands are available to you right now - feel free to experiment with them! Site: **BROWSER**\ Actions:\ \- OPEN TAB (needs an URL as value)\ \- CLOSE TAB (you can use a substring as value - see below for explanation)\ \- RELOAD TAB (you can use a substring as value - see below for explanation)\ \ Site: **ZALANDO**\ Actions:\ \- START PRELOAD\ \- CLEAR CART\ \- FORCE START\ \ Using a substring as value means that you can enter value like "zalando" and all tabs that have this word in their URL will be affected by the command. Everything that happens in the routines scheduler will be logged inside the [logger](/getting-started/options/logger). # Mass change size preferences Quickly change your size preferences in all opened instances! Open the desired site - and then you have these options: * Set a size: this means single sizes like 44 or size ranges like 42-44 * Type "clear" to remove whatever was set there # Captcha harvester Get your one-click Gmails ready - here comes the harvester! Some sites require a captcha to cart and/or checkout. The faster this captcha is processed, the more likely is a successful checkout. Pepper will already handle those captchas on-the-fly right now - but you can gain a huge advantage for scheduled drops when you pre-harvest those captchas right before the drop. Thats where our captcha harvester comes into play! ### Prerequisites You will need is a **MASTER** cli instance running. How you know that? Just see if inside your CLI. If you are running an [AIO module](broken://pages/YddPcboVBT0ChMNFFsqu) you must start a new CLI instance since running io modules will switch the current instance to **PEER**. ### Usage Make sure your Pepper setup is fully finished before starting with the harvester. Everything should be ready to run. Starting and using our captcha harvester is easiest now. You simply need to: 1\) Start Pepper CLI as Administrator. In this way all the things will be set up in the right way. If no issue will appear, you are good. 1.1) If prompted, allow Pepper CLI to access both local and public networks. 2\) Open Pepper chrome extension 3\) Click on your avatar and then click on "Logger" menu item 3.1) A message should be now available inside the Logger. Something like "Harvester ready at XXX". Mark and copy the URL that is shown and bookmark this page because that's all what you need for an easy access to our harvester. 4\) Select the store you want to harvest captchas for - doing so will immediately request the first captcha to harvest. 5\) Keep track of your harvested captchas inside the Logger as captchas are only valid for a certain amount of time. If you want to use a 3rd party solver, please set your CapSolver or AYCD key in the [`settings.json`](/getting-started/first-steps). Don't forget to change the `bankSize` to your likings/ instances! The harvester will always try to hold this specified amount of captcha tokens ready. All Pepper instances that are connected to the Pepper CLI will now make use of this captcha pool! No matter who opens the Logger, just all the banks are shared between all instances. **Please make sure to exclude the captcha harvester from your proxies by adding the URL to the exclusion list** (see [Multiple Instances](/getting-started/multiple-instances))**.** #### **Disable harvester auto-open** As said before, now the Harvester automatically opens itself when the Pepper CLI is launched. If you don't want that to happen, you can disable it by setting `enabled` property inside [`settings.json`](/getting-started/first-steps) file to `false`. This will prevent the harvester automatically starting. ## **AYCD Autosolve** We are the first extension to fully support AYCD Autosolve and have a partnership with AYCD. You can find more details about it and a discount code inside our server! In order to connect the captcha harvester with AYCD Autosolve you will have to edit the settings.json file inside your Pepper folder (same folder your updater is located). Following settings have to be edited: ``` "preferredSolver": "AYCD", "aycdKey": "AYCD_TOKEN:AYCD_BOT_APIKEY" ``` You will find your AYCD Access Token and the option to create a Bot API Key for Pepper inside of the AYCD dashboard (not in the application!). For more details about the access token and the bot API key - please refer to the guide of AYCD. Once you have edited your settings.json like shown above you should launch AYCD Autosolve first and make sure it has the status "Connected". After that you launch the PepperScripts Captcha Harvester and it will connect to the already running AYCD Autosolve instance. {% hint style="info" %} Note that AYCD Autosolve is the fastest and most versatile option to solve captchas with Pepper! {% endhint %} # Proxies The CLI will create a proxies folder by default if you open it. These proxies will be used to monitor productpages such as from [Shopify](/supported-sites/shopify) or [Skatedeluxe](/supported-sites/skatedeluxe). Thats why there are multiple folders, to seperate proxy usage from site to site.\ Do you want to monitor Skatedeluxe locally and Shopify with proxies? No problem! Fill the folders `.txt` files how you like. The CLI will not pick a random proxy for a request, it will go through the list 1 by 1. # Quicktasks Learn how to configure our quick-tasks and how can you launch them A quicktask URL is composed by two mandatory parameters: * a `source` parameter that identifies the product page url * a `pid` parameter that will be used for all your tasks and an optional parameter: * a `sizes` parameter that can be a specific size or a range. * an `offer` parameter - useful only for Amazon - that can be a specific product offer What you need to do in order to run a quick task is to **have a Master** instance running. \ Having only Peer instances running will not allow you to handle any quicktask. Quicktask task files are located inside `quicktask` folder and their names **have to match** the shop you are running for. So for example if you want to be ready and start quicktasks for Amazon and SVD just create `svd.csv`and `amazon.csv` task files. Just fill them with all the right informations. \ You can ignore the `PID` column since it will be overridden by the one scraped from quicktask url. A couple of our quicktask examples urls can be: * without specifying any size * [http://quicktasks.pepperscripts.com:13391/?pid=ji2735\&sizes=37-41\&source=https%3A%2F%2Fwww.sivasdescalzo.com%2Fit%2Fp%2Fsamba-og-leopard-w-ji2735](http://quicktasks.pepperscripts.com:13391/?pid=ji2735\&source=https%3A%2F%2Fwww.sivasdescalzo.com%2Fit%2Fp%2Fsamba-og-leopard-w-ji2735) if you want to run also for specific size range (37-41 in that case) * if you want to run a specific offer for an amazon product # PayPal ACO For our CLI modules like ProDirect App and Ugg, you can use our PayPal ACO feature in order to auto-pay PayPal links. In order to do it you just need to configure PayPal credentials inside our [`settings.json`](https://docs.pepperscripts.com/getting-started/cli/pages/-M_XOszXGomxz7135gcR#the-settings.json) file placed inside Pepper bundle folder. Once done you just need to create a PayPal session by navigating through our CLI under `Available sites` submenu. Start a PayPal session to cache your session that will be available until the session will be active. You will also see that the PayPal status inside your Master instance will switch from `Inactive` to `Active`. You should start a PayPal session before a drop.\ Our CLI will keep your session alive while you are running and immediately pay a checkout once available. {% hint style="info" %} Handling too many checkouts with `PP ACO` as payment method can be hard for your hardware. {% endhint %} # GUI Control your tasks. From everywhere. Every CLI module that can be run inside the CLI can be controlled via a fancy user interface. Since you still need to run your task file via CLI, the GUI is nor mandatory. Up to you if you want to use it or not. As soon as you start a task file via CLI you will see two interesting messages: one related to the local interface that usually is available [locally on port 8000](http://localhost:8000) (pay attention that this may vary if the port 8000 is already busy or not) and another message about... remote address! Yes, the cool thing is that you can keep an eye on what's going on.. directly on your phone or via any remote device. You just need to log into our [remote dashboard](https://tasks.pepperscripts.xyz) with your discord account and you will be able to see which instances are running and on which computer. {% hint style="info" %} You can set a shortcut on iPhone and see it similar to an App. 1. Open the Shortcuts App 2. Configure a new shortcut\ 2.1 Select "open URL" and paste into it\ 2.2 Click done 3. Click on it and tap "add to home screen" Hint: You can also rename it to something like "Pepper GUI" and give it a custom profile picture for better visibility. {% endhint %} You can also have a quick look for the item you are running for and how many tasks are present in the task file. Just click on an instance and you will jump directly into the tasks list. ### Known "issues" **I don't get the f\*king remote address, why?** We experienced this issue only with one user during our tests. We discovered that the issue is related to his internet provider, nothing we can do against it. **Even if I have just one task file running, the number I have in the url is not 0001 but something diff.** Is normal, busy numbers will be collected after some time, no worries about it. # Settings ### SMS Services configuration Under `sms` node into settings.json you can specify all providers keys. As of now **HeroSMS**, **SMSPool** and **5SIM** are supported. Please specify related keys by editing the following properties: * `herosmsKey` and put the key that you can find [here](https://hero-sms.com/profile/safety) * `smsPoolKey` and put the key that you can find [here](https://www.smspool.net/my/settings) * `fiveSimKey` and put the key that you can find [here](https://5sim.net/settings/security) {% hint style="info" %} Don't forget to run few tasks at once since as soon as you request a phone number for validating your accounts they holds your money, even if you will not receive the SMS code. Pepper will try to automatically ask for balance release as soon as possible but it cannot be done before a couple of mins. Again, run few tasks at once or your balance will be drained in a second. {% endhint %} # Multiple instances How to make the most out of Pepper + CLI with running multiples instances Unlike other extensions Pepper will allow you to run multiple Chrome instances - as many as you like - on one computer. ### Prerequisites You will need: * Pepper * Pepper CLI * [BP Proxy Switcher](https://chrome.google.com/webstore/detail/bp-proxy-switcher/bapeomcobggcdleohggighcjbeeglhbn) * Good proxies (we can't recommend you anything for this in the guide, as the sites change a lot constantly - pick your proxies based on your own experience or try asking others in the chat) ### Usage First of all make sure you setup all your Chrome users with a fully configured Pepper instance. This means: 1\) Create a new **Chrome Profile** (no guest) 2\) **Load Pepper** inside the new Profile from the **same folder** you used to setup your first Chrome instance 3\) [**Import**](/getting-started/options/import-export) Pepper Settings from your other Chrome instance and setup the **webhook** etc. 4\) Check if everything is working by doing some **test checkouts**! ### Autostart Chrome instances via CLI Check the [Spawn Chrome instances](/getting-started/cli/spawn-chrome-instances) guide. # Shortcuts Keeping things simple and fast Go to `chrome://extensions/shortcuts` in your Chrome and you will see something like this:
#### Start mirror With this shortcut you can have almost the same functionality as our CLI - but for shock drops. Start mirror and all other PepperScripts instances will open the same product as you are currently watching. You need to open the CLI in the `mirror product page` mode! #### Start quicktask This shortcut will cause Pepper to start your quicktasks for the [CLI modules](broken://pages/YddPcboVBT0ChMNFFsqu) on whatever link you have opened. You will still need to have the Quicktask task file filled. More about that [here](/getting-started/cli/quicktasks). #### Switch mode Most of the sites supported by Pepper have at least two working modes. In a situation when something goes wrong and you want to switch to the next mode, you normally have to open Pepper and manually change it before refreshing the page. By using the `Switch mode` shortcut you could easily switch to the next mode and the page will be automatically refreshed. #### Toggle modules switches With `Toggle modules switches` shortcut you can enable or disable all the Pepper modules at once. This is very useful for testing purposes. # Amazon You can run this module directly into our CLI You have 8 modes available: * (no value): normal drop or restock mode * `ADDRESS`: adds default address/payment method * `INVITATION`: let you to join their invitation only drop (you'll receive an email if chosen) * `INVITATION CHECK` : let you check if account that made entries with `INVITATION` have been selected to purchase the product * `MONITOR`: monitors a specific pid for (eventually) a specific size range * `MONITOR DISCORD`: monitors your discord channels and grab the ping you need * `AWAIT`: runner that waits once a MONITOR detects stock * `SESSION`: generates a session for an existing account * `MANUAL`: after login (if needed) will let you do your stuff manually (for example deleting orders and so on) * `SECRET`: :doughnut: (don't forget to backup your accounts.csv everytime you run it) * `ACCOUNT`: let you generate an account and automatically run SECRET for you (read more [here](#generating-account)) ### Tasks setup Setting up a single task is quite easy. You don't need to specify any information about shipping or about the payment method. You just need to fill the COUNTRY since it will be used for selecting the Amazon region you want to run for. {% hint style="info" %} **IMPORTANT NOTE** Your account has to have a default shipping address and a default payment method already set into your account. If you want to le pepper handle this just run ADDRESS mode.\ If you don't have all necessary info set into your csv everything will be reported. {% endhint %} | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | AMAZON as a value | | MODE | Empty or one as a reported above | | PID | ASIN or multiple ones comma separated when running MONITOR mode | | OFFER | Provide a specific offer id. Running with an OFFER is the fastest way to checkout | | QUANTITY | As many as you want, if a product is not available for the desired quantities, the minimum one will be used | | MAX QUANTITY | Usable only for MONITOR mode, defines how many the item should be checkout at most by a single task: that means that once an await reaches this number it will ignore further pings | | MAX PRICE |

When monitoring a product, might be that the item comes in-stock but with an higher price.

Type the maximum price you are willing to pay for the given product.

If the mode for this task is set to MONITOR, as per PID column, you can put multiple max prices comma separated.

Don't forget to respect the order!

| | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email | | PASSWORD | Account password | | FIRST NAME | | | LAST NAME | | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | A 2-letters country ISO Code (e.g. `GB` for UK) | | PHONE | | | PAYMENT | | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

Has te the exact filename, don't forget the extension name like .txt (e.g. amazon.isps.txt).

If empty amazon.txt will be used.

| | IMAP |

When you generate sessions, accounts or using SECRET mode, Amazon might send you a 6-digit OTP code to the given email address.
To let Pepper handle this for you, put here your IMAP connection settings in the following format: server:port:username:password

As example: imap.mail.me.com:993::my-app-password

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| ### Generating session If you are wondering how and if you need to generate a session for your account.. the answer is yes but almost every mode available covers your back. It really depends on your account status. If your account: * already has a default address/payment method just leave MODE column blank or run MONITOR/AWAIT, it is ready to go * doesn't have a default address/payment method just run ADDRESS mode, it will login and fill your account with the data taken from your csv * isn't in unknown state (you don't know if has address/payment method and you want to check manually) just run MANUAL or SESSION {% hint style="warning" %} Running SECRET mode is strongly recommended when running your accounts with Pepper {% endhint %} ### Generating account Generating an account might led you in a couple of scenarios: * you trigger Amazon blocks: they will requires you to solve a captcha and eventually ask you for going throught an SMS validation * not triggering anything: just otp via email and that's it What our ACCOUNT does is to bring you as much as possible to generate your accounts in the second scenario: just otp validation via email. **Catchall** will not pass for sure. Use a password that: * contains at least an uppercase letter * contains at least a lowercase letter * contains at least a number * min-length 8 If you need to force account generation and validation for an email you own you can enable in settings.json the option `validateAccountsWithPhoneNumberIfNeeded` by setting it to `true`. Other settings are easy to be filled. **Don't forget** to setup imap in settings.json if all OTP emails will arrive in your mastermail or specify specific imap connection string for the specific task into IMAP column. ### Example taskfile Here is an example task file: {% file src="/files/1l2uIpO6oH6Nvh0rFv5T" %} You can edit this file by using [Rons editor](https://www.ronsplace.ca/products/ronseditor). {% endfile %} In the example task we have 3 taks. One `MONITOR` task that is going to monitor three different products. One `AWAIT` tasks that, once prepared his session, will listen for a `MONITOR` input: as soon the MONITOR task detect an availability for the monitored items, this task will automatically start.\ \ One task with EMPTY mode but with a specific **OFFER**.\ This task will ignore what MONITOR task will provide during the time and will run as a standalone task.\ Since a specific OFFER has been given the task will check when the product related to the specific OFFER will come back in stock and will try to checkout. {% hint style="success" %} Doing a proper usage of MONITOR and AWAIT mode will **drastically** reduce your proxy data consumption and to keep your accs more safe.\ \ Using an EMPTY task with an **OFFER** will give you the highest chances to checkout the specific product but way more aggressive for your accounts. {% endhint %} ### Quicktasks You can read more [here](/getting-started/cli/quicktasks).\ The important thing you should know is that once started a quicktask for a region, this region will be overwritten into your task file: that means that if your `quicktasks/amazon.csv` file has some accounts (independently if MONITOR or EMPTY or AWAIT) filled with IT as a country and you start a quicktask for a product restocked on DE, all your tasks will automatically run on DE region. ### ASIN blacklist and MAX QUANTITY As mentioned, with MONITOR mode you can specify in CSV how many times an asin can be checkout (for the running region) at most by a single account. This is useful if an item is limited to a maximum quantity for a specific account. Further checkout will lead in a cancel. Once an ASIN is "blacklisted" (once the maximum quantities have been checked out), the couple ASIN-ACCOUNT will be saved into `blacklist.csv` where also the blacklist date is reported. If you want to let a specific account to run again for an asin just remove the entry from the csv and restart the AWAIT task. It will clear and read the updated blacklist again (if any). ### Mode "MONITOR DISCORD" and how to use it Configuration for this task is quite simple: * Inside the **MODE** column put `MONITOR DISCORD` * Inside the **PID** column put the filename you have previously created in discord folder * e.g. `ram_and_pokemon.csv`, read more on the content of this file [here](/supported-sites-cli/discord) * Inside the **COUNTRY** column you can put one or more countries comma separated * e.g. `IT, DE` for filtering all pings made on amazon.it and amazon.de * Indie the **WEBHOOK** column you can specify a different webhook where all catched pings will be forwarded and notified. This is optional. That's it. All grabbed pings will be forwarded to all AWAIT tasks as it happens with normal MONITOR tasks. ### FAQs * **Where is the generator?**\ We don't have it since seems like manually made accounts are better chances to not being clipped instead of the ones that are bot-generated. * **Too much modes, which one should I run?**\ We strongly recommend to run MONITOR-AWAIT tasks since it is the best way to run multiple accounts without destroying them with individual monitoring and actions made in background.\ If you know that an item is frequently restocking we also suggest you to run some tasks also with EMPTY mode with and without offer id. * **Wtf is an offer id and where I can find it?**\ An offer identifies uniquely a product with a specific price. For that reason you don't need to use MAX PRICE column when you going to run with an offer id. It's useless.\ You can find an offer id manually on site if you are good to do it or, simply, just watch your cookgroup, they will provide it for sure when their monitor pings. * **Why on monitors for a single product and the same price I have different offers?**\ Offer id changes everytime you refresh the page but under the hood the ASIN and price involved is still the same. You can always run an "old" offer id that has been pinged in the past. * **So.. in the end.. should I run with or without offer?**\ The answer is always the same: every mode is different and they uses different approaches.\ Event EMPTY mode with and without offer is actind differently.\ So.. Mix them and find the bast way for your setup! * **Should I run my accounts with SECRET mode?**\ We strongly support this. Don't forget to backup your `accounts.csv` after you run your accs with SECRET mode! * **My account got banned!**\ Unfortunately that's quite normal when you run the same info across different accounts.\ Try to avoid running the same CC or the same address on multiple accounts. This will trigger their anti-fraud automatically.\ What we recommend is to run accounts that doesn't matter if they get clipped.\ Just gen some, it takes few seconds and use the SECRET + ADDRESS mode to have everything ready. ### Common errors * **I'm getting errors while logging in.**\ There might be many reasons. First of all, as it improve your account stability, we strongly recommend to run SECRET mode, this will help a lot. * **I ran SECRET mode but still looping on login.**\ If you see the same error just rest your account for like 3-5 mins and try again. They tend to softly rate limit if they see too much login attempts. Is normal. * **My order has been canned**\ It happens. Unfortunately also that thing is quite normal.\ Automatic anti-fraud jump into canning orders when they see that too many accounts are sharing the same credit card and the same delivery address. The best solution is to use aged accounts and using unique address/recipients. They care about j1gs. That's the hardest part. Who has the best setup wins. # Aliexpress You can run this module directly into our CLI You have 6 modes available: * (no value): normal mode * `ADDRESS`: adds default address into your account * `MONITOR`: monitors a specific pid for (eventually) a specific sku / keywords * `AWAIT`: runner that waits once a MONITOR detects stock * `ACCOUNT`: generates an account * `ORDERS`: scrapes and save all account orders into orders.csv * `TEST`: lets you just to test the checkout flow (address included) without closing the checking out ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | ALIEXPRESS as a value | | MODE | Empty or one as a reported above | | PID |

Product identifier. If your task is an AWAIT one you can let this field empty for catching evert restock or you can specify one or multiple (comma separated) pid for catching specific pings.
MONITOR task can have just one pid.

| | SKU | Since every product can have multiple variants you can specify the sku if you know it in advance or just add some keywords like "whole set" or "single" to cart just specific items. | | QUANTITY | When used with ACCOUNT mode, this will be threshold that needs to be satisfied in order to let this task to be completed. | | CURRENCY | Optional. You can specify which currency you want to use. You can use USD, EUR or GBP | | DELAY |

In milliseconds (e.g. 3000 for 3 seconds delay)
When used with mode ACCOUNT this will be the delay between a generation attempt and the next one

| | EMAIL | Account email or @yourcatchall.com when generating new accounts with ACCOUNT mode (don't forget the @ in front of your catchall) | | PASSWORD | Account password | | FIRST NAME | | | LAST NAME | | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | A 2-letters country ISO Code (e.g. `GB` for UK) | | PHONE | | | PAYMENT | PP or PP ACO for PayPal without or with autopay. If you want to manually pay your order you can just use CC. You will not be charged at checkout time but you manually need to do it via account' orders page. | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

Has te the exact filename, don't forget the extension name like .txt (e.g. aliexpress.isps.txt).

If empty aliexpress.txt will be used.

| | IMAP |

When you generate accounts or sometimes even when logging in, Aliexpress might send you a 6-digit OTP code to the given email address.
To let Pepper handle this for you, put here your IMAP connection settings in the following format: server:port:username:password

As example: imap.mail.me.com:993::my-app-password

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| ### Generate new accounts This is the hardest part. They tend to ban easily. We suggest you to use a catchall and use residential proxies. As of now this is the only thing that works better. You can experience this high ban rate also trying to generate your accounts manually. ### Monitoring Even there, residentials are the way to monitor. You can try your ISPs or DCs but they will be banned quite easily. ### Example taskfile {% file src="/files/6lBb9lJEPkieNwMNnALm" %} # Dreamland You can run this module directly into our CLI Here are the modes currently available: * (no value): normal mode * `MONITOR`: monitors one or more specific pids * `AWAIT`: runner that waits once a MONITOR detects stock * `ACCOUNT`: generates an account {% hint style="warning" %} You need a CapSolver key set up into settings.json in order to run this module since for some hyped products a challenge must be solved {% endhint %} ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | DREAMLAND as a value | | MODE | Empty or one as a reported above | | PID | Product URL | | QUANTITY | Self explanatory | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email or @yourcatchall.com when generating new accounts with ACCOUNT mode (don't forget the @ in front of your catchall) | | PASSWORD | Account password | | FIRST NAME | RANDOM or specific name | | LAST NAME | RANDOM or specifics surname | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | BE or NL only | | PHONE | | | PAYMENT |

CC, BANCONTACT, IDEAL

For all payment methods you need to manually pay for your orders since payment is hold for some minutes.
Payment links will be saved into success.csv and into checkout webhook

| | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. dreamland.isps.txt).

You can also use a specific proxy connection string.

Prefer lists over single connection strings.

| | IMAP |

When you generate accounts, Dreamland sends you an account verification link to the given email address.
To let Pepper handle this for you, put here your IMAP connection settings in the following format: server:port:username:password

As example: imap.mail.me.com:993::my-app-password

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| # Dadi e Mattoncini You can run this module directly into our CLI Here are the modes currently available: * (no value): normal mode * `MONITOR`: monitors one or more specific pids * `AWAIT`: runner that waits once a MONITOR detects stock * `ACCOUNT`: generates an account {% hint style="warning" %} MONITOR mode can be ran for upcoming drops when product page is not even available by setting up lookup keywords. {% endhint %} ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | DADIEMATTONCINI as a value | | MODE | Empty or one as a reported above | | PID | Product URL or keywords like `prima luce -hero` (in that case you are looking up for products that have both "prima" and "luce" in title/url but doesn't have the word "hero" in it. | | QUANTITY | Self explanatory | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email or @yourcatchall.com when generating new accounts with ACCOUNT mode (don't forget the @ in front of your catchall) | | PASSWORD | Account password | | FIRST NAME | RANDOM or specific name | | LAST NAME | RANDOM or specifics surname | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | | | PHONE | | | PAYMENT | Forced as bank transfer, you need to pay the order you receive via email | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. dadiemattoncini.isps.txt).

You can also use a specific proxy connection string.

Prefer lists over single connection strings.

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| # Elbenwald You can run this module directly into our CLI Here are the modes currently available: * (no value): normal mode * `MONITOR DISCORD`: monitors your cookgroup pings and forward them to your awaiters * `MONITOR`: monitor a specific item * `AWAIT`: runner that waits once a MONITOR detects stock * `ACCOUNT`: generates an account {% hint style="warning" %} You need a CapSolver key set up into settings.json in order to run ACCOUNT mode and gen your accounts {% endhint %} ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | ELBENWALD as a value | | MODE | Empty or one as a reported above | | PID | Product URL | | QUANTITY | Self explanatory | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email or @yourcatchall.com when generating new accounts with ACCOUNT mode (don't forget the @ in front of your catchall) | | PASSWORD | Account password | | FIRST NAME | RANDOM or specific name | | LAST NAME | RANDOM or specifics surname | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | A two letter country code like IT, ES, FR | | PHONE | | | PAYMENT | CC, PP | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. dreamland.isps.txt).

You can also use a specific proxy connection string.

Prefer lists over single connection strings.

| | IMAP |

When you generate accounts, Dreamland sends you an account verification link to the given email address.
To let Pepper handle this for you, put here your IMAP connection settings in the following format: server:port:username:password

As example: imap.mail.me.com:993::my-app-password

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| # Fantasia Store You can run this module directly into our CLI For this module you have two modes available: * FAST * EMPTY (leave the cell empty) {% hint style="warning" %} This module is GUEST checkout only {% endhint %} ### Tasks setup Setting up a single task is quite easy. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | FANTASIA as a value | | MODE | Empty or FAST | | PID | Product ID if you already know it or keep it empty and fill it as soon as you get it. | | QUANTITY | As many as you want, if a product is not available for the desired quantities, the minimum one will be used | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Email or @catchall.com | | PASSWORD | | | FIRST NAME | | | LAST NAME | | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | A 2-letters ISO CODE (e.g. `MI` for Milan) | | COUNTRY | A 2-letters country ISO Code (e.g. `GB` for UK) | | PHONE | | | PAYMENT | BT (bank transfer) | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

Has te the exact filename, don't forget the extension name like .txt (e.g. fantasia.isps.txt).

If empty fantasia.txt will be used.

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| ### I don't know the pid in advance What should you do if you don't know the pid of the product that is going to be dropped? You can just leave the PID column empty. As soon as you start the tasks, they will setup them and then wait for your input. As soon as you know the pid just edit the CSV, save it and the tasks will immediately start to run for it. # FedericStore You can run this module directly into our CLI For this module you don't need to specify a mode. Just leave the `MODE` cell blank. The site might be hella slow, it happens everytime a restock or a preorder is available to be purchased.\ Don't give up and expect slow responses from their backend. {% hint style="warning" %} This module is GUEST checkout only {% endhint %} ### Tasks setup Setting up a single task is quite easy. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | FEDERICSTORE as a value | | MODE | Empty as reported above | | PID | Product URL | | QUANTITY | As many as you want, if a product is not available for the desired quantities, the minimum one will be used | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Email or @catchall.com | | PASSWORD | | | FIRST NAME | | | LAST NAME | | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | A 2-letters ISO CODE (e.g. `MI` for Milan) | | COUNTRY | A 2-letters country ISO Code (e.g. `GB` for UK) | | PHONE | | | PAYMENT | CC, PP or BT (bank transfer) | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

Has te the exact filename, don't forget the extension name like .txt (e.g. federicstore.isps.txt).

If empty federicstore.txt will be used.

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| ### Quicktasks You can read more [here](/getting-started/cli/quicktasks). # FootDistrict You can run this module directly into our CLI You have 7 modes available: * empty for running fcfs accounts * `RAFFLE` for entering a raffle (you need verified accounts) * `CHECKER` for checking raffle successes * `ACCOUNT`: allows you to generate new accounts * `ADDRESS`: sets a new address for an existing account * `RESET ADDRESS`: change delivery informations for an existing account * `VERIFY` : checks verification status and something more ### Tasks setup Here is a table that explains the meaning of every field and, if applicable, a default value. | COLUMN NAME | VALUE | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | FOOTDISTRICT as a value | | MODE | One as reported above | | PID | Raffle URL or product sku if running CHECKER mode | | SIZES | A specific size or a range like `44, 46-48` | | QUANTITY | Ignore this column, leave it empty | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email | | PASSWORD | Account password | | FIRST NAME | Recipient name | | LAST NAME | Recipient surname | | ADDRESS LINE 1 | Recipient first address line | | ADDRESS LINE 2 | Recipient second address line (optional) | | HOUSE NUMBER | Recipient house no. | | CITY | Recipient city | | ZIPCODE | Recipient zip code | | STATE | Recipient state that has to be picked from the [this list](https://pepperscripts.com/sites/footdistrict) | | COUNTRY | A 2-letters country ISO Code (e.g. `GB` for UK) | | PHONE | With country prefix like +44123456789 | | PAYMENT | `CC` | | CARD HOLDER | Your card holder | | CARD NUMBER | Card number | | EXP MONTH | Two digits (e.g `02` or `12`) | | EXP YEAR | Four digits (e.g. `2026)` | | CVV | Credit card CVV | | WEBHOOK | If empty the one set up in `settings.json` will be used | | ENTRY WEBHOOK | If present and filled it will send a webhook for all entries that have been made successfully | | START TIME |

Empty if you want to immediately start your task.

A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| | PROXY |

You can put a specific proxy or a proxy list.

In case you using a proxy list, it has to be the exact filename, don't forget the extension name like .txt (e.g. footdistrict.resi.txt).

If empty footdistrict.txt will be used.
You can also run without proxy by writing localhost

| {% hint style="warning" %} Be sure to use an unbanned proxy that **matches** the region where your account has been verified or you won't be able to enter any raffle . Prefer **good** residentials, not packet. When they don't like your proxy they don't get you to read available sizes and to enter the raffle. If that happens, wipe your session, change proxy and start the task again. {% endhint %} ### Example taskfile Here is an example task file: {% file src="/files/7HuO2QvJyukuea9n1chw" %} You can edit this file by using [Rons editor](https://www.ronsplace.ca/products/ronseditor). ### Generate tasks Now, you filled your CSV (e.g. called **footdistrict.csv**) and you are ready for entering a raffle. Everything is well configured. You can of course still manually edit your CSV and change PID, SIZES and START TIME (if needed) but there is something more. You can quickly edit all this infos directly via CLI by using our task generator (option 2 inside the FootDistrict submenu). Once started it will ask you which is the source task file to edit (you will choose **footdistrict.csv** as per the example). Right after it will show you all upcoming raffles with the related closing date. Once chosen it it will ask you the first "start time" and - if you specify an initial "start time" - the last "start time", pepper will generate all "start times" for other tasks according with the value you specified for start and end "start time" and the numbers of tasks you have. You can also specify the sizes or the size range you want to run for. Once finished a new file named **footdistrict-pid.csv** will be generated. The `pid` will be the one you decided to run for. Also the mode for the file will be automatically set as RAFFLE. {% hint style="info" %} Why "START TIME" is needed for a Raffle module? It is a good question but this will ensure you to not have all your entries made all in a short time frame. What we suggest is to spread your entries across hours or days even better. {% endhint %} ### Account creation If you want to let pepper create an account for your, you can setup your csv with the values you explained in general [tasks setup](#tasks-setup) section. Keep in mind that you still need to manually verify your account by yourself. ### Account verification You know that in order to enter super hyped drops you need to verify your account. Using this mode in conjiuction to the SMS service [you configured into settings.json](/getting-started/cli/settings) you can let Pepper to verify the accounts for you. In order to do this you need to specify the sms provider you want to use and the service you looking to use for receive your sms. An example of `footdistrict` node into settings.json can be the following one: ``` "footdistrict": { "scrapeInvoiceWhenCheckingOrders": false, "smsProvider": "smspool", "smsService": "any other", "smsMaxPrice": 1.5 } ``` `smsMaxPrice` is optional, if not specified it will take the first price available. When you use it with HeroSMS, `smsMaxPrice` property is used for picking the **exact** price, so be sure you double check the available prices on HeroSMS website before setting this value. #### Specific SMS Provider services For: * HeroSMS: you can use `footdistrict` if your region is available (check their site) or `any other` * SMSPool: just use `any other` since they don't have specific footdistrict service * 5SIM: just use `footdistrict` ### Change your delivery address FootDistrict allows you to change your delivery address only once every 3 months. Run `RESET ADDRESS` only if you already have an address and you want to change this informations. If address details can't be changed, the task will print the error. ### Scraping order invoices When running `CHECKER` mode and into your settings.json, under the node `sites.footdistrict` if the option `scrapeInvoiceWhenCheckingOrders` is set to true the cli will download the order invoice automatically. # Funko You can run this module directly into our CLI Here are the modes currently available: * (no value): normal mode * `RAFFLE` : for entering raffles * `MONITOR`: monitors one or more specific pids * `AWAIT`: runner that waits once a MONITOR detects stock * `AWAIT FAST`: like AWAIT mode but more aggressive * `ACCOUNT`: generates an account * `FAST`: like empty mode but... faster :-) {% hint style="warning" %} You need a CapSolver key set up into settings.json in order to run this module. {% endhint %} ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | FUNKO as a value | | MODE | Empty or one as a reported above | | PID |

Product identifier. If your task is an AWAIT one you can let this field empty for catching every restock or you can specify one or multiple (comma separated) pid for catching specific pings.

If you using RAFFLE and

  • you want to run a fan reward giveaway raffle, just put a keyword that matches the name of the product you want to enter
  • you want to run a free raffle with product page up just use the product pid


MONITOR task can have multiple comma separated pids

| | QUANTITY | Self explanatory | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | CAPTCHA |

If set to YES captcha will be user for add to cart. Most hyped drops have it enabled. Not needed for restocks.

Keep it empty if you don't want to use it.

| | EMAIL | Account email or @yourcatchall.com when generating new accounts with ACCOUNT mode (don't forget the @ in front of your catchall) | | PASSWORD | Account password | | FIRST NAME | RANDOM or specific name | | LAST NAME | RANDOM or specifics surname | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | A 2-letters country ISO Code (e.g. `GB` for UK) | | PHONE | | | PAYMENT |

PP or CC.

Use PayPal only for testing purposes.
Definitely run CC preferably with frictionless (non-3DS) credit cards.

| | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. funko.isps.txt).

You can also use a specific proxy connection string.

Prefer lists over single connection strings.

| | IMAP |

When you generate accounts or sometimes even when logging in, Funko sends you a 6-digit OTP code to the given email address.
To let Pepper handle this for you, put here your IMAP connection settings in the following format: server:port:username:password

As example: imap.mail.me.com:993::my-app-password

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| | ENTRY TIME |

Used in conjuction with FAST mode.
In case you are running for a drop just set it as the product drop time like 18:00:00

| ### How to run? Please use a mix of your proxies. On drop time they might rate limit or ban a lot of subnets. Definitely run a mix of: * MONITOR and AWAIT FAST tasks * FAST with ENTRY TIME set at the drop time Why mix both modes? Trust us and do it. ### Where is the captcha bank? Don't worry, there is an automatic built-in mechanism that will let you to don't think to manually run anything. Just be careful that running too much FAST modes (AWAIT FAST and FAST) might drain your CapSolver balance so... check your setup! ### Reward drops Some drops are for accounts that have at least a specific amount of reward points. When genning your accounts with ACCOUNT mode, Pepper will automatically join the reward program for you (if applicable for the running region) ### Example Here is a CSV you can use as a quick start to start configuring your setup. {% file src="/files/jF3sm0LtlA33pgfuQfia" %} # IPZS You can run this module directly into our CLI There is only one mode currently available * (no value): normal mode {% hint style="warning" %} You need a completely filled account for run this site. Be sure the Italian CF is correctly filled into your account. Delivery address is taken from account not via CSV. {% endhint %} ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | IPZS as a value | | MODE | Empty | | PID | Product identifier. If you don't have it ask in our server which product you want to run and it will be shared. | | QUANTITY | 1 | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email | | PASSWORD | Account password | | FIRST NAME | | | LAST NAME | | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | IT | | PHONE | | | PAYMENT | It doesn't matter, manual payment link will be sent to your webhook. | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. ipzs.isps.txt).

You can also use a specific proxy connection string.

Prefer lists over single connection strings.

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| | ENTRY TIME |

If there is a drop incoming and you know the time (usually at 11:00:00) just set it as the product drop time like 11:00:00.

The task will just login and wait for drop time.

| ### How to run? Please use unbanned proxies. When they bans proxies they just will not reply to any of your requests. You will see status all requests that will fail with status code (0). Don't run local on the same ip with more than a task. Start your tasks like a min before drop time and use ENTRY TIME. Disable `restartTaskAfterCheckout` if you want that a single task has to hit just once. If enabled the task will restart right after a checkout. ### Example Here is a CSV you can use as a quick start to start configuring your setup. {% file src="/files/sU0JEyDV2jckMhEiOBPa" %} # DFN San Marino You can run this module directly into our CLI There is only one mode currently available * (no value): normal mode {% hint style="warning" %} You need a completely filled account for run this site. Be sure all the infos is correctly filled into your account. Delivery address is taken from account not via CSV. {% endhint %} ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | DFN as a value | | MODE | Empty | | PID | Product identifier. If you don't have it ask in our server which product you want to run and it will be shared. | | QUANTITY | 1 | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email | | PASSWORD | Account password | | FIRST NAME | | | LAST NAME | | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | | | COUNTRY | Country ISO Code | | PHONE | | | PAYMENT | It doesn't matter, manual payment link will be sent to your webhook. | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. dfn.isps.txt).

You can also use a specific proxy connection string.

Prefer lists over single connection strings.

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| | ENTRY TIME |

If there is a drop incoming and you know the time (usually at 11:00:00) just set it as the product drop time like 11:00:00.

The task will just login and wait for drop time.

| ### How to run? Please use unbanned proxies. When they bans proxies they just will not reply to any of your requests. You will see status all requests that will fail with status code (0). Don't run local on the same ip with more than a task. Start your tasks like a min before drop time and use ENTRY TIME. Disable `restartTaskAfterCheckout` into settings.json if you want that a single task has to hit just once. If enabled the task will restart right after a checkout. ### Example Here is a CSV you can use as a quick start to start configuring your setup. {% file src="/files/FBOA6ihoLqjOm5wDkNTK" %} # EQL You can run this module directly into our CLI There is only one mode currently available * (no value): normal mode ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | EQL as a value | | MODE | Empty | | PID | Raffle URL | | QUANTITY | | | SIZE | Specific size or a range like 42-44 | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Specific email or your catchall (in @catchall.com format) | | PASSWORD | | | FIRST NAME | | | LAST NAME | | | ADDRESS LINE 1 | | | ADDRESS LINE 2 | | | HOUSE NUMBER | | | CITY | | | ZIPCODE | | | STATE | Be sure it is an allowed value. For example if you put MI instead of Milano it might not work. Just double check manually which values are available and fill it in this cell | | COUNTRY | Country ISO Code | | PHONE | | | PAYMENT | It doesn't matter, only CC checkout will be used | | CARD HOLDER | | | CARD NUMBER | | | EXP MONTH | | | EXP YEAR | | | CVV | | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. dfn.isps.txt).

You can also use a specific proxy connection string.

Prefer lists over single connection strings.

| | START TIME |

Empty if you want to manually start your task. A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| {% hint style="info" %} You can specify the amount of concurrent threads by editing the related value in settings.json {% endhint %} # ProDirect App You can run this module directly in our CLI Lately, very often, all hyped shoes are dropped only on ProDirect mobile app. After running Pepper CLI for the first time, the tasks folder will be created in your pepper folder. You will need this below. You have 5 modes available: * (no value): normal drop or restock mode * `FAST`: way more faster than normal mode, don't forget to run `SESSION` mode at least once in a time * `SESSION`: useful for generating accounts session and prepare your account for running `FAST` mode (run it everytime you change the account delivery address) * `ACCOUNT`: generates an account for the given username and password, don't forget to fill address too since it will be seeded into your account * `ADDRESS`: changes your default account delivery address to the one specified into the CSV * `ORDERS`: fetches all orders with the relative state for the given account ### Available payment methods We currently support three different payment methods: * `CC` for using a Credit card when checking out * `PP` for using PayPal when checking out * `PP ACO` for auto paying PayPal links (only available if an valid session is found, it falls back to normal PayPal checkout if ACO session is invalid or something goes wrong) ### Tasks setup Here is a table that explains the meaning of every field and, if applicable, a default value. | COLUMN NAME | VALUE | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | PRODIRECTAPP as a value | | MODE | Empty or one as a reported above | | PID | Product ID (e.g`1010175`) | | QUANTITY | Leave empty, unused on that site | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email or @catchall.com when generating accounts | | PASSWORD | Account password (min 8 characters, at least an uppercase char, a lowercase char, a number and a special char) | | FIRST NAME | Recipient name | | LAST NAME | Recipient surname | | ADDRESS LINE 1 | Recipient first address line | | ADDRESS LINE 2 | Recipient second address line (optional) | | HOUSE NUMBER | Recipient house no. | | CITY | Recipient city | | ZIPCODE | Recipient zip code | | STATE | Recipient state | | COUNTRY |

A 3-letters country ISO Code (e.g. GBR for UK)
You can check your country here

| | PHONE | With country prefix like +44123456789 | | PAYMENT | `PP`, `CC` or `PP ACO` | | COUPON | Usually `PRODIRECT10` | | CARD HOLDER | Match the real data, they are used to cancel | | CARD NUMBER | Card number | | EXP MONTH | Two digits (e.g `02` or `12`) | | EXP YEAR | Four digits (e.g. `2026)` | | CVV | Credit card CVV | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY LIST |

Has te the exact filename, don't forget the extension name like .txt (e.g. prodirect.resi.txt).

If empty prodirect.txt will be used.

| ### Accounts generator You can generate an account by using `ACCOUNT` as a mode and as `EMAIL` you can use: * specific email like `pds@pepperscripts.com` * your catchall like `@pepperscripts.com` (don't prefix it with RANDOM!) In case you are going to use your catchall, first name and last name will be used in order to generate a random email prefix. {% hint style="info" %} Basically every recipient component can be jigged with the XXX trick: put as many uppercase X (2 minimum) and they will be replaced with a random letter. If you want you can also jig your phone number. So using like +4476XXXXXX will generate something like +4476112234. {% endhint %} ### Example taskfile Here is an example task file: {% file src="/files/qVdFFbqRu3u1PSDxCqaM" %} You can edit this file by using [Rons editor](https://www.ronsplace.ca/products/ronseditor). # SNKRS (Raffle drops) You can run this module directly into our CLI You have the following modes available: * (no value): normal drop mode * `FAST` : definitely faster than empty one, you should normally use this for drops * `SHOCK DROP`: faster than empty mode useful to catch/run shock drops (you should be sure that a session for the given account is already available) * `CHECKER`: check the health of your account, if it is phone number validated and also your the score that nikes assign to your address * `EA`: check if you have an upcoming EA for this account * `MANUAL`: just logs into your account with the given proxy and halts, it is useful if you want to manually handle a recent order or do your stuff to set up your account manually * `SESSION`: generates a session for an existing account * `ADDRESS`: remove all existing saved addresses and payment methods and add new ones based on your csv * `VALIDATE`: validates your account via SMS if needed * `ACCOUNT` : generates a new account, fills the address, the payment and... validates your account via SMS :tada: ### Tasks setup Here is a table that explains the meaning of every field and, if applicable, a default value. | COLUMN NAME | VALUE | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | NIKE as a value | | MODE | Empty or one as a reported above | | PID | Product SKU like `HJ4303-400` | | QUANTITY | Ignore this column, leave it empty | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email (has to be a valid Nike account) | | PASSWORD | Account password | | FIRST NAME | Recipient name | | LAST NAME | Recipient surname | | ADDRESS LINE 1 | Recipient first address line | | ADDRESS LINE 2 | Recipient second address line (optional) | | HOUSE NUMBER | Recipient house no. | | CITY | Recipient city | | ZIPCODE | Recipient zip code | | STATE | Recipient state | | COUNTRY |

A 2-letters country ISO Code (e.g. GB for UK)
Only non-GS regions are allowed right now.

GS module is in roadmap

| | PHONE | With country prefix like +44123456789 | | PAYMENT | `CC` | | CARD HOLDER | Your card holder | | CARD NUMBER | Card number | | EXP MONTH | Two digits (e.g `02` or `12`) | | EXP YEAR | Four digits (e.g. `2026)` | | CVV | Credit card CVV | | WEBHOOK | If empty the one set up in `settings.json` will be used | | ENTRY WEBHOOK | If present and filled it will send a webhook for all entries that have been made successfully | | START TIME |

Empty if you want to manually start your task.

A specific time in the format hh:mm:ss like 08:50:00 to automatically start this task at the given time.

Don't worry if you recognize you put a wrong time in there. You can still manually force start it.

If you didn't put a specific time, don't forget to put MANUAL as a value if you want to avoid every task to immediately start as soon as your task file is started.

| | ENTRY TIME |

In the same format as per START TIME cell but this value refers to the specific time the entry for the draw has to be done.

You can use our wizard built into the CLI to easily generate it

You recognise you put a wrong entry time?
You can still manually click on the entry button and pepper will take care of it

| | PROXY |

You can put a specific proxy or a proxy list.

In case you using a proxy list, it has to be the exact filename, don't forget the extension name like .txt (e.g. nike.resi.txt).

If empty nike.txt will be used.
You can also run without proxy by writing localhost

| | IMAP |

When you generate sessions, Nike will sends you an 8-digit OTP code to the given email address. Put here your IMAP connection settings in the following format:
server:port:username:password

As example:
imap.mail.me.com:993::my-app-password

| ### Proxy checker We built our own proxy checker, not to check their speed but to check if your proxies are banned on specific steps during the entry flow. During our tests we identified a lot of blocks at entry step and at payment one. Put all of your proxies inside a txt and run the proxy checker.\ \ You will be able to check which is good to go and which it isn't. {% hint style="warning" %} Please don't overtest it. You are invoking some sensible endpoints. Don't let your proxies to be banned by yourself.\ \ Prefer **good** ISPs over resis. {% endhint %} ### Example taskfile Here is an example task file: {% file src="/files/0v9CXbtXQTMVkAXFvxDw" %} You can edit this file by using [Rons editor](https://www.ronsplace.ca/products/ronseditor). ### Generate tasks Now, you filled your CSV (e.g. called **nike.csv**) and you are ready for a drop. Everything is well configured. The day after another drop is coming. You can of course still manually edit your CSV and change PID, SIZES and ENTRY TIME (if the drop mode is different from the previous one) but there is something more. You can quickly edit all this infos directly via CLI by using our task generator (option 2 inside the Nike submenu). Once started it will ask you which is the source task file to edit (you will choose **nike.csv** as per the example). Right after it will show you all upcoming drops with the related drop date and time. Once chosen it it will recognise also which drop method will be used (if LEO and DAN) and will ask you the first entry time and the last entry time, pepper will generate all entry times for other tasks according with the value you specified for start and end entry time and the numbers of tasks you have. You can also specify the sizes or the size range you want to run for. Once finished a new file named **nike-pid.csv** will be generated. The `pid` will be the one you decided to run for. Also the mode for the file will be automatically set as empty. ### Account validation `VALIDATION` and `ACCOUNT` mode needs an sms provider set up in order to validate your account. Here is an example of configuration you should have in settings.json under nike node: ``` "nike": { .... "validateAccountsAfterCreation": false, "smsProvider": "smsactivate", "smsService": "nike", "smsRegion": "RO" } ``` All options should be self explanatory. Just little a note on the `smsRegion` : up to you which region you want to use. Don't forget to set up the sms provider key as explained [here](https://docs.pepperscripts.com/getting-started/cli/settings) ### Proxies, which ones? ISPs or DCs are always the best choice, in terms of speed and costs since you don't need to care about data usage. Be sure to ask your provider that you need to run them on Nike drops and be sure to run the built-in proxy checker in order to check if they are unbanned (for real) on all sensitive steps that will be involved during a drop. If you are going to run with Residentials you definitely should take care about data usage since you are billed per netwrok usage. Since Nike website is fully loaded with images and videos this will be a money drain while using residentials. If you want to save a lot of data you can edit your `settings.json` and edit the following part: ``` "sites": { "nike": { "disableVideos": false, "disableImages": false } } ``` You can just put what you want to disable to `true` instead of `false`. So for example imagine you want to disable only videos but you want to keep images you can just need to do as follows: ``` "sites": { "nike": { "disableVideos": true, "disableImages": false } } ``` # SVD You can run this module directly into our CLI You have 5 modes available: * (no value): normal drop or restock mode * `MONITOR`: monitors a specific pid for (eventually) a specific size range * `AWAIT`: runner that waits once a MONITOR detects stock * `ACCOUNT`: generates an account for the given username and password, don't forget to fill address too since it will be seeded into your account * `ADDRESS`: removes any existing address into your account and it seeds a new one taking informations from your csv * `SESSION`: generates a session for an existing account * `FAST`: especially useful in case of shock drop/restocks that aren't being monitored in advance (you should be sure that a session for the given account is already available) ### Available payment methods We currently support four different payment methods: * `CC` for using a Credit card when checking out * `PP` for using PayPal when checking out * `PP ACO` for auto paying PayPal links (only available if an valid session is found, it falls back to normal PayPal checkout if ACO session is invalid or something goes wrong) ### Tasks setup Here is a table that explains the meaning of every field and, if applicable, a default value. | COLUMN NAME | VALUE | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | SVD as a value | | MODE | Empty or one as a reported above | | PID | Product SKU or product link, both ar valid | | QUANTITY | Maximum 10 | | DELAY | In milliseconds (e.g. 3000 for 3 seconds delay) | | EMAIL | Account email or @catchall.com when generating accounts | | PASSWORD | Account password (min 8 characters, at least an uppercase char, a lowercase char, a number and a special char) | | FIRST NAME | Recipient name | | LAST NAME | Recipient surname | | ADDRESS LINE 1 | Recipient first address line | | ADDRESS LINE 2 | Recipient second address line (optional) | | HOUSE NUMBER | Recipient house no. | | CITY | Recipient city | | ZIPCODE | Recipient zip code | | STATE | Recipient state. It has to be one picked from [here](https://pepperscripts.com/sites/svd) | | COUNTRY | A 2-letters country ISO Code (e.g. `GB` for UK) | | PHONE | With country prefix like +44123456789 | | PAYMENT | `PP`, `CC` or `PP ACO` | | CARD HOLDER | Match the real data, they are used to cancel | | CARD NUMBER | Card number | | EXP MONTH | Two digits (e.g `02` or `12`) | | EXP YEAR | Four digits (e.g. `2026)` | | CVV | Credit card CVV | | WEBHOOK | If empty the one set up in `settings.json` will be used | | PROXY |

Has te the exact filename, don't forget the extension name like .txt (e.g. svd.resi.txt).

If empty svd.txt will be used.

| {% hint style="info" %} You **must** have a CapSolver key set up in your settings.json, a captcha is required in order to checkout on this site. {% endhint %} ### Accounts generator You can generate an account by using `ACCOUNT` as a mode and as `EMAIL` you can use: * specific email like `svd@pepperscripts.com` * your catchall like `@pepperscripts.com` (don't prefix it with RANDOM!) In case you are going to use your catchall, first name and last name will be used in order to generate a random email prefix. {% hint style="info" %} Basically every recipient component can be jigged with the XXX trick: put as many uppercase X (2 minimum) and they will be replaced with a random letter. If you want you can also jig your phone number. So using like +4476XXXXXX will generate something like +4476112234. {% endhint %} ### Example taskfile Here is an example task file: {% file src="/files/iesCmDdvDJ1aQrPMGYTg" %} In the example task we have 3 `MONITOR` tasks that are going to monitor three different products for the same size range `36-39`. Two `AWAIT` tasks that, once prepared their session for a faster checkout, will listen for a `MONITOR` input. \ The first one will accept ANY product, the second one will accept only monitors that detects stock for product `FQ8138-001`. Other restocks will be ignored. In the end two alone wolfs (the ones with `MODE` field empty) that will run independently from other tasks. {% hint style="info" %} Doing a proper usage of MONITOR and AWAIT mode will **drastically** reduce your proxy data consumption. {% endhint %} You can edit this file by using [Rons editor](https://www.ronsplace.ca/products/ronseditor). # Discord You can run this module directly into our CLI If you want to use your group' monitors at their best you can integrate their pings into your Pepper CLI. {% hint style="warning" %} This kind of task needs your personal Discord token. This token will not be shared/stored anywhere. {% endhint %} ### Tasks setup Setting up these kind of tasks is totally different from other modules but it is quite easy at the same time. First of all, all discord tasks has to be placed inside the `discord` directory places into `tasks` folder. Here is a table that explains the meaning of every field. | COLUMN NAME | VALUE | | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | DISCORD as a value | | SERVER |

Server identifier or name.

e.g. 646011490037530621 or pepperify

| | CHANNEL |

Channel identifiers or names, comma separated. You can also write \* if you don't want to restrict the monitoring to a specific channel.

e.g. 646011490037530621, 646011490037530622 or amazon, funko

| | INCLUSIVE KEYWORDS | Optional. Filter all products that contains certain keywords. Read more below. | | EXCLUSIVE KEYWORDS | Optional. Ingore all products that containes certain keywords. Read more below | | TOKEN | Your Discord token. Instructions on how to pick this token in this page. | | WEBHOOK | Where catched pings should head to (optional) | | BROWSER | Ingore this cell as of now. | {% file src="/files/tccMljkQqgmtYr4EZgXN" %} Example task file to be placed under "tasks/discord" folder {% endfile %} ### How to use keywords For both inclusive and exclusive keywords you can specify a "group" of keywords. Keywords can be entered as a list of alternatives, separated by commas. Commas behave like OR: if any listed keyword is present, the condition is satisfied. * Inclusive keywords: a product matches if it contains any of the listed keywords. * Exclusive keywords: a product is ignored if it contains any of the listed keywords. **Examples** * Inclusive: `ram ddr, pokemon trainer, pokemon allenatore` * Matches if the product contains `ram ddr` OR `pokemon trainer` OR `pokemon allenatore`. * Exclusive: `minitin`, `kingston` * Ignores the product if it contains `minitin` OR `kingston` . **Best practices** * Use commas to separate each keyword or phrase. * For multi‑word phrases, write the full phrase (e.g., pokemon trainer) as a single item. * Avoid duplicate items; the list is evaluated with OR. ### How to get my Discord token You can see how to get it quickly at [this video](https://www.youtube.com/watch?v=GUqSNoJ28aU). A quickiest way will be implemented directly in our extension. # Any site You can run this module directly into our CLI Might be you need a quick solution to run queued drops or just making your accounts manually for the sites we aren't supporting (yet). With this module you can just bootstrap as many browsers you want applying them proxy (from a list or a specific one). ### Tasks setup The table below shows how to setup your tasks. All blank fields are self-explained. | COLUMN NAME | VALUE | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SITE | ANY as a value | | URL | Just specify the url where you want to bootstrap your browser | | URL |

Product identifier. If your task is an AWAIT one you can let this field empty for catching every restock or you can specify one or multiple (comma separated) pid for catching specific pings.


MONITOR task can have multiple comma separated pids

| | START TIME |

Schedule when the browser should start. As a local time like 18:00:00.

MANUAL if you want to start this task manually or empty if you want to start this task automatically.

| | PROXY |

You can give a proxy list and - in that case - it has to be the exact filename, don't forget the extension name like .txt (e.g. isps.txt).

You can also use a specific proxy connection string.

| ### CSV Changes If you need to quickly change the current URL where your browsers are currently on, you can just edit your CSV and just save it. All the changes will be detected and immediately applied. ### Example Here is a CSV you can use a quick start to configure your tasks. {% file src="/files/mT3X6R7OxupcdetfqLer" %} # Solebox What will be reported here will be useful for all Demandware sites. ### Prerequisites You obviously need to have a Solebox account. You should also must have set up your **default shipping** and **billing address**. You could do that by visiting your [address book settings](https://www.solebox.com/en_DE/addresses). If you want to be faster during checkout also preselect your preferred payment method by visiting the [payment settings](https://www.solebox.com/on/demandware.store/Sites-solebox-Site/en_DE/Account-ShowPaymenMethods) and setting it to PayPal PayPal is payment hold. Once you see the PayPal website you have been successful. No need to rush from that point on. **Please make sure to fully checkout with PayPal within the next 30-60 minutes. Once you see the order confirmation website the order is completed. You can find the payment link in your webhook or in the** [**history**](/getting-started/options/history)**.** ### Usage When you open the Solebox module you'll see the following screen.
You can choose between two modes: `Human mode` and `Requests Mode`. You can also allow Pepper to `Automatically login` by using credentials specified in settings. You can also allow Pepper to `Automatically add to cart` an item for you or wait you to cart manually otherwise. You can also allow Pepper to `Automatically remove from cart` if the item that you carted is not available for checkout. You can use the `save mode if available`. It's a safer way of checkout regarding the bot protection. You can `use load links when available`. If this option is not used, every link will be converted into the general product page link (which most of you want. TL;DR only tick this if you know what a load link is and want to use it) `Finalize checkout`should always be turned on - but you can deactivate it if you want to do some testing without checking out. `Loop after checkout` will let Pepper retry for another checkout after a successfull one. Well, what about the two modes? The **Human mode** will simulate all the steps you manually are used to. So, after carting (manually or automatically) Pepper will open the checkout page in another tab and go through all checkout steps. The **Requests mode** will "talk" directly with the backend. It works in background but you'll see the status in the popup that opens inside the product page. {% hint style="info" %} **We highly recommend to use Human mode for drops and Requests mode for daily / non-protection restocks!** {% endhint %} ### Settings
Fill in your **credentials** if you want to allow Pepper to login you automatically. Trust us, is really useful because Solebox will logs you out after a small time frame. About **desired sizes** you can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.4, 36** and so on. {% hint style="info" %} Be careful, if you are using a LOAD link from your cookgroup, Pepper will ignore your desired sizes and will try to cart the size related to your LOAD link. {% endhint %} #### Commons issues > Oh f\*\*\*, I was blocked by PX, wtf Pepper is doing? Pepper isn't responsible to raise the PX. It's up to you, it depends on how you "move" yourself inside Solebox website, how many pages you visit and what you do on the site. So the solution is: try to find your strategy to avoid be blocked (proxy, movements, auto or manual cart, etc) > Wait wait wait, I checked out my item but when the PayPal page is opened I cannot proceed. It seems that the page cannot be loaded. Are you behind a proxy? If yes, that's the answer. Many proxy providers are banned on PayPal, so.. copy the checkout link and pay with your local ip. More issues [here](/getting-started/common-issues). # Snipes What will be reported here will be useful for all Demandware sites. ### Prerequisites You obviously need to have a Snipes account. You should also must have set up your **default shipping** and **billing address**. You could do that by visiting your [address book settings](https://www.snipes.com/addresses). If you want to be faster during checkout also preselect your preferred payment method by visiting the payment settings page and setting it to PayPal PayPal is payment hold. Once you see the PayPal website you have been successful. No need to rush from that point on. **Please make sure to fully checkout with PayPal within the next 30-60 minutes. Once you see the order confirmation website the order is completed. You can find the payment link in your webhook or in the** [**history**](/getting-started/options/history)**.** ### Usage When you open the Snipes module you'll see the following screen.
You can choose between two modes: `Human mode` and `Requests Mode`.‌ You can choose between two modes: `Human mode` and `Requests Mode`. You can also allow Pepper to `Automatically login` by using credentials specified in settings. You can also allow Pepper to `Automatically add to cart` an item for you or wait you to cart manually otherwise. You can also allow Pepper to `Automatically remove from cart` if the item that you carted is not available for checkout. You can use the `same tab for checkout`. This means Pepper will not open a new window after carting, but remain in the same and fulfill the checkout. You can use the `save mode if available`. It's a safer way of checkout regarding the bot protection. You can `use load links when available`. If this option is not used, every link will be converted into the general product page link (which most of you want. TL;DR only tick this if you know what a load link is and want to use it) `Finalize checkout`should always be turned on - but you can deactivate it if you want to do some testing without checking out. `Loop after checkout` will let Pepper retry for another checkout after a successfull one. Well, what about the two modes? The **Human mode** will simulate all the steps you manually are used to. So, after carting (manually or automatically) Pepper will open the checkout page in another tab and go through all checkout steps. The **Requests mode** will "talk" directly with the backend. It works in background but you'll see the status in the popup that opens inside the product page. {% hint style="info" %} **We highly recommend to use Human mode for drops and Requests mode for daily / non-protection restocks!** {% endhint %} ### Settings
Fill in your **credentials** if you want to allow Pepper to login you automatically. Trust us, is really useful because Snipes will logs you out after a small time frame. Be careful of coupons and coin usage as this is mostly disabled on droptimes. About **desired sizes** you can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.4, 36** and so on. {% hint style="info" %} Be careful, if you are using a LOAD link from your cookgroup, Pepper will ignore your desired sizes and will try to cart the size related to your LOAD link. {% endhint %} ### Region switcher You know that stock isn't always shared between Snipes region and only addresses that matches the Snipes region you are using for checking out can be used. Well, on your monitor most probably LOAD links are printed and 99% of them are on `.com` domain. If you are an `NL` (example) based user and click on a `.com` link, you'll be redirected to `.nl` main page. That's really annoying because you need to manually edit the link to match your region. The solution is provided by Pepper: define a profile and fill it with your address country (don't forget to save) and Pepper will take care of all Snipes links, rewriting them to the correct region for you when necessary. In short: for Snipes you will always get redirect to the Snipes locality matching your selected Pepper profiles address. ### Commons issues > Oh f\*\*\*, I was blocked by PX, wtf Pepper is doing? Pepper isn't responsible to raise the PX. It's up to you, it depends on how you "move" yourself inside Snipes website, how many pages you visit and what you do on the site. So the solution is: try to find your strategy to avoid be blocked (proxy, movements, auto or manual cart, etc) > Wait wait wait, I checked out my item but when the PayPal page is opened I cannot proceed. It seems that the page cannot be loaded. Are you behind a proxy? If yes, that's the answer. Many proxy providers are banned on PayPal, so.. copy the checkout link and pay with your local ip. More issues [here](#commons-issues). # ProDirect ### Prerequisites ProDirect module is **logged user only** - an account is needed for Pepper on this website. \ You can easily add it as you usually do with other store accounts.\ \ **Important:** fill all accounts data (shipping address, billing address and phone number). If your account is incomplete Pepper will stop his execution and will open the checkout page. It is proven that they cancel multiple orders from the same account. Prepare some accounts with (slightly) jigged addresses (billing addresses too!) and pay with different credit cards and/ or PayPal accounts. Don't forget that they check for credit card fraud, so put your real billing address in the field (can be slightly jigged though). By default Pepper will automatically start in two cases:\ \- once you reach a visible product page\ \- if enabled - for hyped drops with queue - once you click on a special link that we will provide in a dedicated channel. {% hint style="warning" %} For most drops, it has been mandatory to have an UK address. {% endhint %} ### Usage There is **Requests mode** and **Human Mode** available. Request Mode uses the address set in the account.\ Human Mode uses the profiles address if the account has a different country than the profile. You can allow Pepper to `Automatically login` by ticking the related options and it will use the specified credentials into site module settings for logging you in. You can allow Pepper to `add to cart` the product. Self explanatory. You can allow Pepper to `Finalize checkout` (ACO) by ticking the related options. Pepper can `catch monitor pings`. This means pinged products will automatically open in your instance. If you want to let Pepper to only cart your item just untick this option and Pepper after adding the item to cart will immediately open the checkout page. In this way you can close the checkout manually. If you see a charge from your bank but Pepper seems to be stuck in the checkout/ got no email, congrats you got a checkout! Go to your [order history](https://www.prodirectsoccer.com/my-account/order-history/) tab and insert your order ID after this link to recieve the order confirmation email:\ ### Bozo mode Our bozo mode will help you get to a checkout faster! Just go to the homepage and you will see following bar:
Click on the Only for Bozos button and let Pepper do the rest. You will see once it's ready to go!\ From that point on just follow the usual ProDirect process. ### Common issues Some of the most common issues, you can see all [here](/getting-started/common-issues). \ "There is a problem with items in your cart" \ Solution: The size is out of stock or the checkout is locked, try carting a different one. *Phone number j1g only inputs 3 digits* \ Solution: Fix your pepper profile. You need to input the amount of X's that a normal phone number contains in that country so that pepper can replace them. So put something like +4402XXXXXXX "Unable to parse right informations from given pid. Aborting." \ Solution: Be sure to be on the newest update. If you are, then we probably paused sauce. Pausing the sauce should be only if we noticed weird activity, but you'll be notified if that happens. ### Account generator To use our own, homemade account generator, you have to open the homepage of Prodirect. Make sure to **activate the module** and **select a mode**. At the bottom of the page is our helper bar with the input field and other buttons.
For the account generator, you will only need profiles, the input field and the `generate account` button. Create a profile for Prodirect in Peppers profiles tab, even [XXX jig](https://docs.pepperscripts.com/getting-started/options/profiles) it if you want! This profile will be used to set up your shipping and billing address in the newly created accounts. If your shipping and billing address don't match, don't worry! \ Create your billing profile and name it `PDS Billing` to get used for setting up the billing address. Now to the creation part: First you open up the page, log in, you input you specific mail (e.g. ) or your catchall domain (e.g. @pepperscripts.com), then place a colon (:) and insert your preferred password after. After hitting the `generate account` button, it will clean up your session, create the account, log in and set the shipping & billing up! The finished accounts are saved in your accounts tab as `PDS Generated {country} {number}`. ### Settings Our module supports PayPal and Credit Card as payment method. Linked profile informations in Pepper module settings will be only used for checking out with credit card. As usual, you can define which sizes you want to checkout in Pepper module settings. You can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * for shoes Pepper will use **EU sizing** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **37, 38, 38.5, 39, 42.6** and so on. {% hint style="info" %} Keep in mind that even if you specify a size range, if you click on our special LOAD links, Pepper will ignore this range by giving precedence to the desired size build inside the link. {% endhint %} # Shopify ### Prerequisites Shopify is mostly guest checkout, but you will need an account for certain sites. Pepper will take care of it, you just need to create the same account on all shops where login is required. Shops that need an account: * Goodhoodstore * TheNextDoor * StarcowParis Launches Since we don't want to checkout random products on random shops, we take care of our own whitelist. We support three payment methods but we **strongly** recommend to use credit card as preferred one. It is faster and basically always enabled on all shops. ### Usage There is only **Requests mode** available, however, you can let it switch to human mode after a successful add to cart. Shopify is all about speed: Pepper will automatically preload your checkout (if needed) in order to have a faster checkout process. You don't need to input a preload product, Pepper will take care of it. What about queued drops? Yes, Pepper will help you. All the instructions will be pushed in a dedicated channel inside our discord. The "Automatically mirror products once found" option will help you monitor different things on different instances but still cop on them all! It works like this: {% hint style="info" %} Lets say you have 2 instances and monitor the keywords `travis olive` on instance 1, but instance 2 monitors the keywords travis phantom. If you now have the[ CLI in mirror mode](/getting-started/cli/mirror-product-page) open and one of the instances catches a product, it will be automatically mirrored to the other instance without you having to use the shortcut. {% endhint %} This can help if you don't want to monitor too many things at once due to ratelimits. ### Region switcher Some shops are country restricted. What that means? They ship only to certain countries. Pepper can take care of it if you want. You just need to create some default Shopify profiles named with the following format `Shopify COUNTRY_CODE`. So for example: TheNextDoor is FR only. Suppose that your default profile linked to Shopify module has `DE` as a shipping country. If you want to run on TheNextDoor just create a new profile named `Shopify FR` and, once on it, Pepper will use it instead of your default profile in order to checkout. ### Monitoring With our monitoring function, you can of course automatically monitor a specific product once entered into the product page but also **multiple product groups at the same time**. To use it you just need to activate the module, go on the desired page and you'll see following helper bar:
To separate groups, use a comma `,` character.\ Example: `Jordan 4, Jordan 1` To put negative keywords, that Pepper will filter out, use a minus `-` character in front on the excluded keyword\ Example: `Jordan 1 -Mid -Red` will catch all Jordan 1 that doesn't have `mid` and `red` in his name. If you want to have the best experience and efficiency while monitoring: keep our [CLI ](/getting-started/cli)opened. Another reason for keeping the CLI opened while monitoring is that you can monitor behind proxies by just put all of them inside [`shopify.txt`](/getting-started/cli/proxies) file.\ This is the best way you avoid being rate limited while monitoring.\ You can also change your proxies while monitoring. Our CLI will detect all the changes and those will be automatically applied without interrupting your workflow. Product matches, proxy problems and changes and, more in general all monitoring activities, are reported inside your [logger](/getting-started/options/logger). If you encounter a password page, you can handle it via the CLI. Read more about that [here](/getting-started/cli/available-sites#shopify). ### Settings It is required to define a profile as well as a catchall mail or regular mail address in the settings.\ Choose your payment method. Optionally, set a size preference. About **desired sizes** you can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.8, 36** and so on. # Supreme See our [Shopify guide](/supported-sites/shopify). # Airdom ### Prerequisites You only need a Pepper profile and money! ### Usage There is only `Request Mode` available. You can allow Pepper to `automatically monitor` the productpage. You can allow Pepper to `finalize the checkout`. ### Settings Select the profile you want to use for a checkout. You can chose between credit card and PayPal as payment method. Enter your E-Mail, can be a catchall too! About **desired sizes** you can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.4, 36** and so on. # Asics ### Prerequisites Asics is **guest checkout only** - no account is needed for Pepper on this website. ### Usage There is only **Requests mode** available.\ \ You can allow Pepper to `automatically monitor` an out-of-stock product. You can allow Pepper to `finalize the checkout`. Either you * Wait for Pepper to automatically start on droptime * Force start yourself {% hint style="danger" %} But in any case, keep the [CLI ](/getting-started/cli)opened! {% endhint %} {% hint style="info" %} Don't close the product page even if checkout fails multiple times. That's totally normal. {% endhint %} ### Settings The guest checkout requires your to define a catchall mail (*recommended*) or regular mail address in the settings. Our module supports PayPal and Credit Card as payment method. You can use coupon codes. {% hint style="info" %} Keep in mind that checking out with PayPal will use the code, even if you decide to not pay. {% endhint %} You can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * for shoes Pepper will use **EU sizing** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **37, 38, 38.5, 39** and so on. # AWLab WARNING: please be super careful with this module as it is lightning fast - one wrong click might buy you bricks if you have activated "finalize checkout" + CC payment in the module. ### Prerequisites You don't need any account as we will use guest mode to checkout! ### Usage When you open the AWLab module you'll see the following screen. ![](/files/-Mk7520-ICdX5DoPveie) The mode we will be using is `Requests mode`. AWLab uses guest checkout only - so no need for any login data! You can allow Pepper to `Automatically add to cart`an item for you or wait you to cart manually otherwise. You can also let Pepper automatically remove out-of-stock things in your cart, as well as letting Pepper monitor out-of-stock product pages! Just for testing you can also disable the checkout finalization. The **Requests mode** will "talk" directly with the backend. It works in background but you'll see the status in the popup that opens inside the product page. #### Automatic monitoring Once you activate the setting "Automatically monitor product" you should stay on the product page and let Pepper do its magic. As AWLab restocks in waves which we will monitor without getting you blocked by the page. This works especially well with our [Captcha Harvester](/getting-started/cli/captcha-harvester) - as the harvester will be linked to the monitor! *Please note: this mode is only available on AWLab right now!* #### Captcha on AWLab AWLab requires a captcha on checkout (most of the time). If a captcha is required Pepper will now take a look into the captcha bank of our [Captcha Harvester](/getting-started/cli/captcha-harvester) first and if no captcha is available it will use the 3rd party solvers you defined in your settings. ### Settings ![](/files/-Mk75083JV8DjCZlhjxj) Please create **profiles** for each of the AWLab regions (IT, ES, EN) in your [profile](/getting-started/options/profiles) settings. Of course, only if are able to use those regions. If you don't have an address in IT or ES - please just use EN region (it is not only for Great Britain but most EU-countries). Once you created the profiles you can select them in the AWLab module settings. As we run guest mode only please setup a catchall or mail address as your **checkout e-mail**. About **desired sizes** you can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.5, 36** and so on. # Footdistrict Maybe you already know that Footdistrict sells hyped items. You must have a **verified account** in order to buy these hyped items. You can learn more on that argument by visiting their [FAQ](https://footdistrict.com/en/faq) page under the *Verified Users* section. Please don't ask us when they will "open the door" to another verification wave. ### Prerequisites You need to have a Footdistrict account. If it is a verified one, as we said before, you will be able to checkout hyped (premium) items, only non-premium otherwise. You also must have set up your **default shipping** and **billing address**. You could do that by visiting your [address book settings](https://footdistrict.com/en/customer/address/). If you are running with a verified account **you must** define a profile inside the Pepper profiles page with valid card data. These informations will be used to checkout. ### Usage When you open the Footdistrict module you'll see the following screen. ![](/files/XdGwoBzeGcxk7RrWFyIu) There is only a single **Hybrid mode**. Pepper will detect which type of product are you running on and enable a full Requests based mode for non-premium products and an hybrid mode for premium ones.\ \ `Automatically login` will enable a request based login. You can allow Pepper to `Automatically add to cart` by ticking the related options and it will pick a size specified into site module settings. Just for testing you can also disable the checkout finalization by unticking the `Finalize checkout` option but... be careful. Don't over-test, they easily ban your accounts. Trust me, they do. ### Settings ![](/files/Kp20KOyA3N62wzUNq4pw) Make sure to setup your Footdistrict account in the PepperScripts account management and also select a checkout profile! Footdistrict does not have a real payment hold - so it is recommended to select Credit Card as payment method. Inside the Footdistrict module settings you can only specify which size you want to use when `Automatically add to cart` option is enabled. You can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.5, 36** and so on. # Lockwood ### Prerequisites An account is needed on this website. Business to business (B2B) information is usable for a tax-free checkout. ### Usage There is only **Requests mode** available.\ \ You can allow Pepper to `automatically log into your account` . Pepper can `empty cart before starting` a checkout process. You can allow Pepper to finalize checkout. ### Settings Our module only supports PayPal checkout, as it is payment holding method. {% hint style="info" %} This means seeing the PayPal window is a successfull checkout, no matter how long you take to pay! {% endhint %} You can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * for shoes Pepper will use **EU sizing** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **37, 38, 38.5, 39** and so on. # LuisaViaRoma (LVR) ### Prerequisites You need to have a LuisaViaRoma account. You should also must have set up your **default shipping** and **billing address**. You could do that by visiting your [address book settings](https://www.luisaviaroma.com/myarea/addresses). **You have to be logged in to your LuisaViaRoma account!** It is advised to log out/ clear cookies and login the night before an announced drop. ### Usage When you open the LuisaViaRoma module you'll see the following screen. There are **two modes**: **Requests mode** and **Gift mode** - **currently, Requests mode is the one you have to run!** Gift mode (referring to the "gift" option of LVR) is often disabled on drops. **Requests mode options**: Enter up to 3 workers to determine how many parallel tasks should be running. Putting 2 or 3 can result in a soft-ban in the worst case but from our experience 3 works just fine for now. Be aware that LVR is currently rate limiting very hard, so for maximum chances you should run different Pepper instances with Proxies! **Auto start on product page** can be disabled if you don't want Pepper to automatically run the product once you open a new product page. This can be useful if you want to prepare you want to change your **multicart settings** (available in the Pepper toolbar when visiting a product page on LVR). If you disable this setting you will have to press the "FORCE START" button in your Pepper toolbar to start your checkout process once you are visiting a product page. Define a default multicart size that pepper will use once it has carted an item! If you want pepper to not just cart, but also buy the product you chose, you need to check the field "**Finalize Checkout**" (this should always be activated for LVR). **Loop once completed** means that once all concurrent workers have checked out Pepper will restart them automatically. Keep this activated as well because most of the time you want as many checkouts as possible. How does the **Requests mode** work? If the Product you want to buy is **in stock**, Pepper will try to cart the product 20 times. If carting is successful, Pepper will start the checkout process and pay with the desired way of payment. If carting is not successful after 20 tries, Pepper will reload the product page and start over. If Pepper is in the state that the server answers with uncartable once it tries to cart, this could be due to being **cached**. We advise you to reload the product page once you see monitor activity or checkouts coming in. If the Product you want to buy is **not in stock**, Pepper will automatically start monitoring the product. The **automatic monitor mode** will check every X seconds (see settings below), if the Product available to purchase. Earlier we already talked about **multicarts** on LVR - but what exactly does this mean? Just as on Zalando, you can put a high number of items in your cart and during checkout only the really available number of items will be checked out - ignoring the non-available quantity. In the multicart settings which are available in the Pepper toolbar when visiting any product page on LVR, you can define a number between 0 (empty) and 5. This setting will be **saved for every different product individually** once you press the "SAVE" button right next to it! This setting will be stored forever - but you can overwrite it with a new value whenever you like. The global multicart option is settable next to the workers amount. The Pepper toolbar also lets you **clear your cart** and **sync your cart** with something you carted via the LVR app! ### Settings ![](/files/WcQfBtEyxZZMX0dlEzt8) First choose your desired Profile. For **payment method**: please use PayPal as a preferred option as CAD (cash in advance) is often disabled during hyped drops. You can permanently link your PayPal account to your LVR account by doing a dummy checkout manually, paying with PayPal and cancelling the order right after it. During the checkout process you will find a box to save your payment option. The **Monitor Delay** will determine in which timeframes Pepper will check if a product is available to purchase. The number entered is in milliseconds. For example: 2500 milliseconds are 2,5 seconds. About **desired sizes** you can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.4, 36** and so on. # New Balance ### Prerequisites New Balance is **guest checkout only** - no account is needed for Pepper on this website. They are used to cancel multiple orders from the same address / payment method / ip. It is strongly recommended then to use different address (slightly jigged) and different payment methods / PayPal accounts. To be as clean as possible also hide yourself behind fast DC or residential proxies. By default Pepper will automatically start monitoring if there are no sizes available for checkout. Once the product will become available Pepper will detect it and will start to checkout it. ### Usage There is only **Requests mode** available.\ \ You can allow Pepper to `Automatically add to cart` by ticking the related options and it will pick a size specified into site module settings. You can also allow Pepper to automatically switch the product region, depending on wherever your profile is set to. {% hint style="info" %} This means a spanish checkout address will lead you to newbalance.es, no matter what NewBalance link you open. {% endhint %} Pepper can `catch monitor pings`. This means pinged products will automatically open in your instance. Because they are strict about one order per profile, we integrated a `rotate profile` button in the helper bar for a fast switch! In regards to PayPal issues, the helper bar has a `clear session` button which is optimal to use before a drop is about to happen. ### Settings New Balance only allows one checkout per profile - so make sure you use individual profiles if you are running multiple instances or any other bot at the same time. The guest checkout requires your to define a catchall mail (*recommended*) or regular mail address in the settings. Our module supports PayPal Express, PayPal and Credit Card as payment method. Keep in mind when using PayPal Express as payment method, Pepper will automatically check out and the address saved inside your PayPal account will be used. Inside the New Balance module settings you can only specify which size you want to use when `Automatically add to cart` option is enabled. You can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * for shoes Pepper will use **EU sizing** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **37, 38, 38.5, 39** and so on. ### Scheduled drop Usually they drop exactly at 10:00:00 AM by also enabling a queue. You simply should click on custom links we provide in *#newbalance* channel **2 mintes before** drop time. Pepper will sleep until droptime is reached. Make sure that you sync your PC time - if your time goes late then Pepper will start late. Prefer product links instead of load ones and specify in which sizes you are interested in via sizes field in New Balance Pepper settings. Aren't you able to open our custom links exactly at drop time? Take a look at our [Routine scheduler feature](https://docs.pepperscripts.com/getting-started/cli/routines-scheduler)! # Nike (FCFS) for FLOW releases and restocks can be run via our extension If you are looking to run SNKRS/Nike LEO and DAN draw releases please refer to the [SNKRS module documentation](/supported-sites-cli/snkrs-raffle-drops) ### Prerequisites Nike module is **account only**: you need to link an account in module settings for this website. They are used to (soft)bans a lot and in order to avoid being blocked with a BPE (Business Processing Error) you should use your real info. As much real and clean your accounts are, as much you'll benefit from them. ### Usage Our module is full requests. You don't need to manually interfere with the module while running. Pepper will take care of everything. There are some options you can customise. You can let pepper to: * `Automatically log in` by using the account you linked in module' settings * `Automatically clear cart` everytime you enter in a product page * `Automatically mirror monitored products` when monitoring multiple pids via the helper bar, in that way you will save proxies since once some sizes will be found in-stock, the same product will get mirrored across all your instances * `Finalize checkout` to let pepper pay for your order * `Loop after checkout` to let pepper restart once a checkout is done * `Use account defined credit card` you will learn more about that later in the guide ### Settings You can enter into module' settings by just pressing the classic cog icon near the on/off toggle button. Here you can define: * which account pepper should use when doing auto login * which profile should be used as a reference for website region and default address filler * which payment method you want to use * optionally a coupon that will be applied (if not applicable it will be automatically removed) to every product * which multicart size you want to run (according to maximum value allowed on the specific product) * which sizes you want to run for as you are used to specify with other modules (LA, FA, multiple ranges, specific sizes and so on). ### Payment methods Currently **PayPal**, **Credit Card** and **Sofort** are available as a payment method. If you want to run Sofort be sure that it is available on your region. You can just run a simple test checkout and if not available you'll get an error on checkou time. If you can whitelist Nike into your Credit Card settings do it. \ On FLOW restocks speed is crucial. \ Avoiding being blocked by a 3ds would be a big advantage. Inside module options you saw that you can reuse the Credit Card that it is saved into your account.\ That will speed up your checkout flow but since Nike always asks for the related CVV every time, the linked profile you selected in settings has to have the right CVV into it since it will be used for checkout. ### Account details Nike is used to bans and block you at checkout time with an error that is called BPE or Business Processing Error. \ There isn't a real recipe to avoid this but for sure being accurated with shipping and billing informations will increase your chances to avoid being blocked.\ So in order to minimise your changes in being blocked use a billing address that matches the one used by your payment method, independently if Credit Card or PayPal (especially this one). ### Common errors #### BPE or Business Processing Error As stated in the section above, there isn't a real recipe for fixing that.\ The best thing you can do is try to remove billing address, shipping address and rewrite them. If that doesn't work try to change chrome instance and account. #### Product not buyable Are you seeing this inside pepper popup while running? \ No worries, it just means that the size you are running for is out-of-stock. #### Reservation inventory issue As the previous error, that means that while placing your order the item went out of stuck.\ You were just unlucky, next time will go better 🤓 # Skatedeluxe ### Prerequisites You need an account on their site **with a default address set already** and a Pepper profile. Note: They have an account tier system, PRO > AM > FLOW. Learn more [here](https://www.skatedeluxe.com/en/premiumclub-howto). ### Usage There is only `Request Mode` available. You can allow Pepper to: * `automatically login`. * `add to cart on scheduled drops`. * `automatically clear cart` before starting a checkout. * `automatically add stickers` which are free if your order value is over 100€. * automatically preload. This will speed up your checkout process. * `monitor on product page`. This will monitor the out-of-stock product for further stock. You can use the [CLI](https://docs.pepperscripts.com/getting-started/cli) with proxies to avoid ratelimits. * `multiple cart` items. Self explanatory. * `finalize the checkout`. For **maximum speed**, disable automatically clear cart and free stickers. Additionally, do a preload before droptime. Pepper will monitor "coming soon" productpages by default. You can use the [CLI](https://docs.pepperscripts.com/getting-started/cli) with proxies to avoid ratelimits. ### Settings Select the account and profile you want to use for a checkout. For delays, you can differentiate ATC, checkout and monitoring delays in milliseconds if you want to. You can chose between bank transfer and PayPal as payment method. About **desired sizes** you can: * leave Pepper to randomly choose an available size to cart (if you want Pepper that carts for you) by leaving this field empty * let Pepper choose the *first available size* by putting **FA** * let Pepper choose the *last available size* by putting **LA** * let Pepper choose all sizes between a range that you specify by putting something like **36-44** * let Pepper choose one size available between some specific sizes that you specified by putting something like **42, 43, 41.4, 36** and so on. # Ugg ### **Prerequisites** For Pepper to work on Ugg you need the following things: * some good and fast proxies that are matching your running region * a fully setup [profile](/getting-started/options/profiles) including phone number etc. * at least an existing Ugg account saved into accounts page (you can still use our built-in account generator) * a catchall for fastly generate new accounts * for full potential the [CLI](/getting-started/multiple-instances) up and running If all these prerequisites are fulfilled, its time to set up the extension! ### Usage For Ugg, only requests mode is available. First head to the extension in Chrome and tick the boxes you want to use in your checkout flow. It is highly recommended to use: * "**Automatically start on product page**" * **"Reuse preload if available"** * "**Finalize checkout**" * **"Catch monitor pings"** As another option you could also let Pepper clear all existing items from your cart automatically. In the module settings, you should enter the account you want to run with and the profile. Then select your payment method (all payments methods aren't payment hold) so a frictionless (no 3DS) credit card is the best choice. Sofort is good too but you need to pay as fast as possible. You can also add a coupon code that will be used for the checkout. {% hint style="info" %} An account can use only one coupon, no matter what. So once close a checkout and pay for it switch to another one in order to checkout products at discounted price. No matter if unidays or newsletter one. {% endhint %} The **shipping address** will be taken from your **selected profile**! ### Helper bar Some quick functionalities are available by using our helper bar at the bottom of any Ugg page (it will appear only if the module is enabled).

Ugg module helper bar

By clicking on the "Generate account" select field another option will pop up. If you need any infos please ask in a ticket, avoid talking about this publicly will preserve the loop (take it as your advantage because once clipped... it's over. #### Account generator Easy like it seems. You just need to: * disable auto login from module settings * logout (if you are currently logged in) on Ugg website * put a catchall like in the screenshot and a password separated by `:` * click on "Generate account". If you don't have a catchall and you just want to use your own email you just need to write it in the same format e.g. `your.email@gmail.com:PepperFTW24_` Every account that has been generated will be automatically saved inside the account section of your module, ready to be used. #### Preload As expected will let you preload all needed infos and will give you the possibility to checkout in a faster way than the normal flow. Useful if you keep enabled also the session keeper inside the module settings. #### Clear cart Self explained ### Best practice We strongly advise you to avoiding overtesting. They tend to quickly ban your ip and your browser fingerprint. If you are in that situation you can try to use our DataDome button inside the helper bar that will properly appear only in the blocked page. If you get prompted to solve a captcha, please do it manually. If the loop between "You have been blocked" page and the captcha page persists.. try to change ip (residentials are working better than isps, most of them are banned) and hit again the datadome button. If the issue still persists... change browser instance and use another proxy. As reported inside the Usage section, talking about coupons.. once closed a discounted checkout, generate a new account and run with it: you can use a discount only once per account. # Zalando ### **Prerequisites** For Pepper to work on Zalando you need the following things: * a **cartable** Zalando account (restocks that are open for non-cartable accounts are super rare) * a fully setup [profile](/getting-started/options/profiles) including phone number etc. * your Zalando account saved in [Pepper accounts](/getting-started/options/store-accounts) * for full potential the [CLI](/getting-started/multiple-instances) If all these prerequisites are fulfilled, its time to set up the extension! ### Usage For Zalando, only requests mode is available! First head to the extension in Chrome and tick the boxes you want to use in your checkout flow. It is highly recommended to use "**Automatically login**" and "**Finalize checkout**". It is also very useful to use the allow multiple cart feature - as Zalando allows you to checkout even if not all items in your cart are available at the moment! As another option you could also let Pepper clear non-checkoutable items from your cart automatically. ![](/files/81KyFFO17MpAEJtJFAxX) In the Zalando settings, you should enter the **desired Zalando account** for the current Chrome instance you want to use, the **desired profile** that you want your items to be shipped to. Then select your payment method for the preload and *maybe* add a maximum price (to avoid buying the resell pairs some monitors ping, not required though). If you want to, you can set your own carting and checkout delays (not required). You can also add a coupon code (not required)- And of course the desired size of shoes you want to checkout (not required). ![](/files/PEIJzJAp5kiIejT7teW0) Now with this all setup, you are ready to run Zalando. However there are some quirks and features that you need to know: Pepper will pay via the defined payment method you choose in the extension. During scheduled drops you have to use PayPal as there is a small cart hold. During random restocks you should use Cash on Delivery! Recently, some resell stores made listings on the Zalando marketplace, which uses the same product page as the regular product. In order to avoid buying those overpriced pairs you can define a maximum price for your checkouts! Originally, Pepper is designed to handle all the delays automatically and that will most likely give you the best user experience - however, if you think you know better: you can freely configure all the delays inside the settings! The **shipping address** will be taken from your **account** or your selected **profile**! It is strongly advised that you check that both **addresses are correct** and matching! If the address of your profile is not matching the pre-saved address of your account - a new saved address will be created. ### Payment Method It is strongly advised to **manually select the preferred payment method** in your account by going to the checkout manually **at least once**! This means, the day before a scheduled drop, you should manually go through the checkout process and select **Paypal** as the payment type to avoid issues during preloading and checkout! ### Preloading {% hint style="danger" %} Never use the preload function while monitoring a product as this will result in checking out a dummy item instead of the wanted one! {% endhint %} To guarantee a fast checkout process, **preloading** the checkout **is necessary!** To do a preload, simply click the "preload" button. Due to the new system of Zalando, you need to do a exclusive preload until 1h before the first exclusive drop. The exclusive preload will not work if you do it 5min before the next drop, like with the non-exclusive preload. Additionally, there is a button to preload the queue. This is, of course, only useful if there is a queued drop.
After you clicked the preload button, a popup will appear where you can see if your preload was successful. If the popup says "**Cart emptied. Preload done**", you are set for the drop. If you are running multiple instances, you can also do the **preload with the CLI.** Pepper chooses a random product to do the preload, if you want to preload with a specific item however you can do that. You do not need to visit any product page. ### Monitoring and Sleeping {% hint style="danger" %} Make sure your devices time matches [the real time](https://time.is/), so the monitor function can work properly. {% endhint %} If you are on an OOS product, Pepper will automatically monitor the product and check if it comes back in stock. If that should be the case, Pepper will try to checkout. If you are on a product that is going to be released soon, Pepper will read the remaining time until the product goes live and "sleep" until then. As soon as the product goes live, Pepper will start the checkout process. ### Best practice We strongly advise you to use the Pepper [autojig feature](/getting-started/options/profiles) to avoid cancellation of orders or clipping of accounts! Do some test checkouts to be sure everything works as intended during drop time. Fixing problems during a drop will be too late! Different Regions of Zalando require a varying amount of data from the user. Some regions require a phone number, some do not. Just to be sure that no errors will occur, fill out your [profiles](/getting-started/options/profiles) **completely** with **valid** informations!