Zalando
Getting started with Zalando
Last updated
Getting started with Zalando
Last updated
In the Tasks.csv file for Zalando, the following fields are required to be filled in:
PROFILE, MODE, PID, DELAY, PAYMENT METHOD and PROXIES, the rest of the colums are optional. By adding an additional column called DUMMY, you can let the bot know what dummy size pid the bot should try to use (You can also separate multiple dummy size pids with ; and the bot tries to rotate through them with every retry)
Current task limit is at 600 per instance
The email and password column are there if you want that the bot uses other credentials than saved in that profile, so you can basically overwrite it.
A template for Zalando can be seen below:
In the Zalando_Tasks.csv file for Zalando, the sizing option is in the pid column. Make sure to use the pids which have been provided by us in our discord. It's possible to run multiple pids at the same time with seperating them with ;. The will then rotate through each pid and try to cart one of them. With the newest update you can now also run multiple links / skus at once with the same format as stated above. Remember that it's not possible to mix them, you can't run link1;sku1;pid together.
When running a link or a sku, the bot will randomly pick a size for you. If you want to specify what size you want to check out, you need to use pids.
We do support three modes:
Session - The session mode is something which you should run before a drop, especially when it's an exclusive drop (most hyped drops are). Usually around a day before (could also be closer to drop, just harder to log accounts in). The bot will then just log into your accounts, save that session and stop the task. This makes logging in and more things during high security drops way easier and faster. Keep in mind that the sessions are region specific. Sessions can be used for currently two months and they can get reused for all the drops within that time frame.
Normal - This is the normal module which does everything from login, clearing cart, preparing checkout and checking out. In case there is a preharvested session for that account available, the bot will be able to use that one to log in quicker and easier.
Exclusive - Recently Zalando changed their way of handling most hyped releases. These do now require a special checkout flow, which is supported with this mode. We do recommend you, when going for a drop, to first harvest sessions with the Session mode, which basically logs you in, precarts a dummy and then preloads the checkout which speeds up the whole process during drop time.
Restock - That module works similarily to our Exclusive mode, but it has some improved handling for restocks. That's why we suggest to run this mode mainly on restocks and Exclusive obviously on initial.
Delays are in milliseconds. So if you input 1000 in the delays column, your tasks will refresh at a one second intervals.
Regarding address handling in your accounts, there are a few important aspects, which need to get explained first:
If you want that the bot uses the default shipping and billing address in your account, you can just leave the address info empty (country code is still required).
In case you want that the bot adds the address information from your profile.csv to your account, then you just need to fill out all of those columns in your profile.
For letting the bot adjust the billing address, you need to download the profiles.csv with the additional billing columns here. The bot handles the billing address with your billing information from profiles.csv the same way as mentioned in 1 & 2 regarding shipping.
For running hyped drops on Zalando, you will need an account which can cart those special items.
You need to let the bot make sessions beforehand. Let the bot run till every session is generated. These sessions can be used up to 2 months. This way you can smoothly log in your accounts and already has everything prepared for drop time.
The timer feature is very useful on announced drops / restocks which occur at a specific time. If leaving empty the bot won't check for it. We currently support two formats: HH:MM and HH:MM:SS - This allows you to start your tasks around 5-10 minutes in advance, so the whole login and checkout process can smoothly get prepared.
We recommend running unbanned Datacenter, Residential Proxies or even ISPs when running tasks on Zalando. We also advise using a server as they allow you to have the fastest speeds when running for drops.
