What fields arrive in each catalogue category

A category on the storefront answers for the type of product rather than for the delivery format: a text line and a profile file can sit next to each other inside one category. What exactly will arrive is told by the «Format» mark in the position title — but categories do have stable leanings, and knowing them is useful before you start choosing.

The price of that knowledge is measured in time. The replacement window is thirty minutes from the purchase, and if the fields in the delivery turned out not to be the ones your process was built for, you will be sorting it out inside that window rather than after it.

Below is a summary by storefront section. It describes what occurs in a category rather than a promise for every position: the composition changes together with the stock, and the mark in the title always outranks the table.

The set of sections is not constant either. A category is built from live counters: as soon as the stock on a tag drops to zero, the section leaves the storefront and the sitemap, and with a new supply it returns. That is how the catalogue is built rather than a fault, which is why memorising the number of sections is pointless.

The table reads like this: a row narrows the expectation down to a couple of options, and the «Format» mark in the title of the particular position picks one of them. The reverse order — the mark first, the category second — works too, and is more reliable.

The «With email» and «Accounts with 2FA» categories are built differently from the rest: these are cross-cutting sections that positions from different types of product fall into by a single contents feature. That is why the spread of formats inside them is the widest.

The contents mark in the position title is more reliable than the category. The category says which type the product belongs to, while the mark says what will physically end up in the line. If there is no mark, there will be no field, even if a neighbouring position of the same section has it.

It is worth remembering separately that a contents mark says nothing about the state of the account. «With Email» and «2FA» describe what you get in your hands, while «FROZEN», «For recovery» or «100% Valid» describe the shape the account is in. These are different groups, and confusing them is expensive.

«Email confirmed» stands apart. It is the status of the address inside the account, and a position with such a mark is not obliged to give the mail password. Access to the mailbox is what «With Email», «Gmail» and «Firstmail» answer for — and only they.

The marks add up: 2FA, Cookie and mail occur in one title at the same time. They are to be read as a list of what will arrive rather than as an assessment of quality — quality is described by other marks, from the state group.

First, the mail. It arrives only where the position title carries the mark «With Email», Gmail or Firstmail. The separate «With email» category gathers such positions from different sections, but marked positions occur inside other categories as well.

Second, the 2FA key. It exists only on positions with the 2FA mark, and in the Login:Pass|Cookie format it is physically absent: this shape has only two fields before the vertical bar.

Third, the cookie. The «IAM (No Cookie)» format ships a profile without one, and that is stated directly in the title. If your process is built on ready cookies, such a position will not do, although by every other feature it will look suitable.

A category stays silent about one more thing — access to the phone number. There is not a single such mark among the contents marks, so confirmations that arrive to a number are not covered by the batch. That is worth accounting for in advance rather than finding out inside the hand-over window.

All these cases have one thing in common: a missing field is not a defect of the batch if no mark promised it. That is the composition of the product, and it was visible in the title before payment. What counts as a discrepancy is the reverse — the mark stands there and the field is absent from the lines.

For text shapes the check takes seconds: copy the delivery and run it through the format converter on the site. It will show the number of parsed lines and which fields were found in them — that is enough to catch a discrepancy with the card before the load into your software.

• IGAM and IAM profiles are not parsed by the converter: the fields sit inside the file.
• The composition has to be checked within thirty minutes of the purchase — that is how long the replacement guarantee runs.
• A discrepancy with the card is a reason to write to the support bot with the order number and the SKU.
• The same run checks that the number of parsed lines matches the volume paid for.

What exactly to compare is prompted by the position title itself: every contents mark is one field that is obliged to be found. The list of short checks comes out at four or five points and is walked through in a minute on any batch.

For profiles the path is different: they are opened by the account manager, and checking the composition comes down to the profile importing and starting. That is why the software for such positions is prepared before payment rather than inside the window.

A separate check is needed where mail is in the set: access to the mailbox is verified by your own login, not by the presence of an address in the line. The address may stand in the delivery and still not open — and that is exactly a discrepancy with the description.

The order is the same for any category: compare the composition by the line, then log in selectively, and only then change anything to suit yourself. A change of password, mail or linked data before the end of the check removes the guarantee.