Skip to main content
A buyer can have several customer accounts with the same email address. This happens not only when the shop explicitly offers it, but also through imported customer data. An overview of these accounts therefore makes sense in almost every shop. The MA- tags serve two places. The customer account contains the entry point, that is, the check whether there are multiple accounts at all, and the link to them. The overview page itself contains the loop over the accounts with their data and the functions for each account. Guide: Offering a multiple account overview · Reference: Templates section
All tags on this page require a logged-in buyer. Without login, each of them is treated as an invalid tag, regardless of the template.

​
The entry point in the customer account

MA-Overview only takes effect from two accounts onward. With exactly one account, the area remains empty, and the entry point does not appear. That is as it should be, because an overview with a single entry helps no one.
If multiple account management is locked for the shop, the shop system hides both variants of the area tag, including {!MA-Overview}. Therefore, don’t rely on the negative area covering the “exactly one account” case. It only covers it as long as the function is available.
MA-Overview does not only apply in the customer account. In the email template for deleting an account, you use it to distinguish whether the buyer is deleting their only account or one of several.

​
Building the overview

You enter the template for the overview in the shop configuration shop.config in the <Templates> section with the MultipleAccountsOverview parameter. MA-Data only works there.
MA-Data as an area tag already takes effect from one account, whereas MA-Overview only from two. The two are therefore not interchangeable. On the overview page, MA-Data is the right tag, because a single account should also be displayed there.
The value tags also work as area tags and take effect if a value is available. This is worthwhile for company and last login, because both fields are often empty. Without an area tag, empty lines appear there.
MA-SubAccountID is not described in the previous documentation. It returns the ID of the sub-account and, in shops with sub-accounts, is the field by which the buyer actually tells their accounts apart. Customer number and name are often identical there.

​
Resetting the password and deleting the account

Both functions work via a confirmation email. The link in the template only triggers the sending; the change only happens after the click in the email.
Place the three messages outside the loop. Inside, they would appear for every account, even though they refer to a single operation.
Both functions must already be set up in the shop before they can be used in the overview. The links here only request the respective email.

​
Checking permission for a subshop

In a shop with several subshops, not every account may access every subshop. MA-SubShopPermission() checks this for the account of the current loop pass.
The tag needs exactly one subshop in the argument. Multiple entries, an empty argument or an asterisk as a wildcard are treated as an invalid tag. If you want to query several subshops, write several area tags one below the other.

​
The tags at a glance

MA-Overview and MA-OverviewLink belong in the customer account, and MA-Overview additionally in the email template for deleting an account. All other tags apply on the overview template, and the tags from MA-Position onward only within the @MA-Data loop. The values are output HTML-encoded.
  • Guide: Offering a multiple account overview
  • Guide: Login and registration
  • Reference: DA- (Deleting the customer account)
  • Reference: SP- (Setting the password)