Quantity is a phone question, not only a budget question
Agencies and developers who keep one Yandex login per client often buy several accounts at once. The natural next step is to put the team's own work phone on every account, so recovery and sign-in confirmations reach someone in the office instead of a stranger's number.
Yandex sets a limit on that plan, and the limit should shape the quantity you choose. Working it out before the order is far easier than discovering it after an older account has quietly lost its secure number.
The rule in Yandex ID Help
According to Yandex ID Help, an account has one secure number, and a single number can be linked to up to 10 accounts. If you add a number that is already linked to 10 accounts, it is removed from the first account you registered with it, and that account's mailbox receives a notification.
The removal is the part that catches teams out. Nothing blocks you from linking an eleventh account; instead, an older account loses its secure number, and with it a recovery route you may still assume is in place. A notification in a mailbox nobody reads daily is easy to miss.
Counting it through for a twelve-client studio
Hypothetical: a web studio manages 12 client projects and wants one bought Yandex login per client, all tied to a single work SIM. Linking that SIM to all 12 would push the first two accounts off the number. The studio has three options: use two numbers, such as two staff work phones, and split the accounts across them; give two lower-priority logins another recovery route first; or buy fewer accounts by combining projects that never need separate access.
The studio splits the accounts eight and four across two work numbers, writes down which account sits on which number, and buys 12. Had it owned only one number and no other recovery route, buying 10 now and adding two later, once a second number existed, would have been the cleaner decision.
Notice what the count did not depend on: the age of the accounts, the store they came from, or how many clients the studio might win next year. It came from two facts the studio already had, the number of active client projects and the number of phones it controls. Run the same count with your own figures before you open the category, and the right quantity usually becomes obvious.
When fewer accounts are the better purchase
Separate logins earn their keep where Yandex grants access per login: a role on a client's site in Webmaster, a guest grant on an analytics tag, an account you may one day hand to the client. They add little for internal projects that will never be shared or transferred, and those can often live together under one login.
Also count the time each takeover needs. Every account's phone has to be replaced, and Yandex ID Help describes a waiting period when the old number cannot receive codes. If a large order consists of accounts that all need that route, stagger the purchases so you are not taking over a dozen accounts in one evening.
Keep a register of accounts and numbers
Once you run more than a handful of Yandex logins, a simple register prevents most surprises. Give each account a row: the client it serves, the secure number it uses, where its backup email points, the date you took it over and any phone change still pending. Add a column for the order it came from, so you can find the delivery record quickly while the dispute window is open.
Before linking a number to another account, count that number's rows. If it already serves ten accounts, the register tells you which account would lose it, and you can move that account to a second number first. Remember that the removal notice goes to the first account's mailbox, so sign in to the oldest accounts on a routine as well.
What a multi-account listing should tell you
On rStock, one order holds one product in the quantity you choose, so every account in that order follows the same description. Read it for phone status, recovery details included in the delivery, earlier use and age. Mixed needs, such as a few accounts for owner seats and several for read-only roles, may be served better by two orders from listings that each fit their purpose.
Buying in quantity does not change how Yandex treats each account. Its user agreement asks for valid registration details, makes each account holder responsible for activity under the login, and does not allow reselling access to Yandex services unless Yandex authorizes it. Use every account for real client work under those rules; holding accounts for spam or mass sign-ups is outside both Yandex's terms and this article.
Placing the order on rStock
rStock remains independent of Yandex; it is a marketplace for approved stores, not a Yandex service. Compare stores by rating, reviews, sales count and insurance balance, then pick the quantity your phone numbers support rather than the quantity that sounds tidy.
Payment comes from your rStock balance. The accounts appear as a delivery record on your order page, and the payment is held for the window shown there, so take over each account promptly, starting with the ones that will carry client work. Open the Yandex category with your count of numbers and logins in hand.