Robot starts the next movement after reset skipping the first position

your assumption is wrong. first because you assumed (never do that) and also because system obviously does not do what you expected.

one can write palletizing/depalletizing code using FOR loops etc as is common in training such (as KUKA Programming2) or examples shared here on the robot forum. reality is that those are starting point examples. in such case loop counters would be reset as soon as program is reset or restarted.

but reality is that in practice things are a bit different....

if restarting program meant that not just starting point in code was reset but also variables got reset, then your cell would need a lot of manual labor every time program is stopped for whatever reason.

normally you do not want to reset or re-initialize things like loop variables even if program is restarted because:

a) you don't want to replace pallet so robot can restart

b) you don't want to manually complete the job (this is why we have a robot, let it do palletizing)

c) failure to ensure correct start scenario when program is restarted will result in a crash.

etc.

so you really want to make sure that the initialization only takes place when new pallet is brought in, not every time program is reset or restarted or robot is rebooted. this way you can run partial load/unload of the pallet, then somewhere halfway through the sequence you can (intentionally or not, maybe there is a power outage) power everything down and go home for a weekend...

next time when you are back, just need to power up and press start. robot knows what is still on the pallet and can continue.

if you have a single robot, you may say it's not big deal. some floor worker will be given task of completing the job and making sure things are restarted in correct conditions. but if you have 500 cells and power goes out suddenly. your restart could take days instead of minutes.