What customer management covers
The Customers section of the Admin Panel is where you manage the companies that buy through the storefront. A customer record represents the company account, and the people who sign in to the storefront do so under that company.
A customer record holds the company name, sync key, address, status, phone number and email. Company records are managed through ERP synchronization.
Companies and the people who sign in
One company can have several people who sign in, each with their own credentials. Activation connects a storefront login to an ERP contact so the shopper can see their prices, documents and history.
Activation links an ERP contact to a storefront login account. In a company's list of users, a user counts as active while it is linked to a login account and as deactivated when it is not. One person's login is a single credential that can be activated against several companies, so it is not an attribute of any one company. The email synced from the ERP may be missing, out of date or different from the address the person uses to sign in. The Customer Users table includes separate Email and Portal email columns.
Where you work with customers
The Customers list has the search fields Search for customer and Search by Sync Key, a Select all checkbox and pagination. Use Search for customer to find a customer, or Search by Sync Key to search by sync key. Each row shows the customer name, sync key, location, email, phone number and status. Selecting a row opens the full customer record. The list also offers Deactivate and Delete for selected rows, and Delete is unavailable while no row is selected. Company deletion is no longer supported because company records belong to ERP synchronization.
A customer record is organized into the tabs General Info, Sales Info, Customer Permissions, Customer Users and Shipping Addresses.
Tab | What it covers |
General Info | Holds the company name, sync key, address, status, phone number and email as read-only values. It also holds the Agent and Currency selectors. |
Customer Users | Lists the company's users, each marked active or deactivated according to whether it is linked to a login account. |
Shipping Addresses | Lists the company's shipping addresses for viewing only, because the ERP sync owns them. |
Agent and currency
The agent is the sales representative responsible for the account. The customer record has Agent and Currency selectors. On a customer record, Save starts out unavailable and becomes available after you change a field value.
The ERP as the source of record
The ERP supplies the company records managed through synchronization.
For questions of stock, tax, bookkeeping, payments, issued invoices, credit or a customer's legal identity, the ERP or another system your business names keeps the final say. Do not treat a customer record in the Admin Panel as proof of a company's credit position or accounting balance.
Deactivation, deletion and binding
When ERP synchronization unlinks a shopper from a company that can no longer open orders, the shopper can still sign in but loses access to that company's prices, ordering and documents. Deactivating one company's contact leaves that person's access to other companies intact.
Deactivating a company's user removes the link between that contact and the login account. Deactivation is an unlink only, so it does not by itself stop the person from activating again through the storefront. Admins can deactivate a user but cannot reactivate one, because reactivation happens when the customer goes through storefront account activation.
Registered Users appears in the navigation as its own item, separate from Customers. That list is made up of people who hold a storefront login rather than company contacts, and its detail view shows every company a login is activated for. Use the registered users list, not one company's page, when a change concerns the person's login itself.
Deleting a registered user removes the login permanently, and it disappears from the list. Deleting the login removes its links to every company it was activated for, and anyone already signed in with it loses their session. The login's past orders, payments and audit history stay in place under the company, just no longer linked to that login. You need write permission for registered users to delete a login, and super-admins can delete without a separate grant.
A super-admin can bind an existing login to a company from that login's detail view, in the section that lists its company activations. Use binding when a customer cannot activate because the phone on their ERP contact is missing or incorrect. Because binding skips the one-time code and opens the company's catalog, prices and orders to that person, double-check you have the right company first. You pick the company by its sync key or its external ID, whichever your store uses for activation. A second binding between the same person and company is turned down. To reverse a binding, deactivate the contact in the company's user list; binding and deactivating over and over piles up unused contact records.
Related

