Open Shop configurations in the Admin Panel menu to reach the Shop configuration page. The page includes the Synchronization and Account tabs described here.
Synchronization tab
Use this tab to decide whether each entity class is managed in the system or driven entirely by ERP data. Each control offers ERP and System. In system mode, the first synchronization can be performed through the corresponding setting in ERP Manager (sync once). In ERP mode, the data comes from the ERP.
Control | What it governs |
Categories | Whether category records are maintained in the system or come from the ERP. |
Currencies | Whether currency records are maintained in the system or come from the ERP. |
Packages | Whether package records are maintained in the system or come from the ERP. |
Users | Whether user records are maintained in the system or come from the ERP. |
Customer Roles | Whether a customer user's orders and finance roles are maintained in the system or come from the ERP. In ERP mode the Phonebook sync overwrites the roles, and in system mode they are managed manually. |
The Synchronization tab warns that switching to ERP loses settings made through the system.
Account tab
These settings define how customers are activated and identified, and what they can see before logging in.
Setting | What it controls | Options |
Account activation | Defines how the system matches and activates customer accounts using ERP identifiers and optional email or phone contact fields. | By sync key, By sync key and email, By sync key and phone, By sync key and custom field |
Account activation — custom field label | Holds the label the storefront shows above the custom activation input, used with the By sync key and custom field option. | Text field |
Account activation two-factor authentication | Controls whether activating an ERP customer user requires a one-time code confirmation sent to the supplied phone or email. | Yes, No |
Individual product list | Controls whether product visibility can be limited to a customer-specific product list instead of the full catalog. | Yes, No |
Show products to guests | Controls whether unauthenticated guest users can browse and view product cards and pages. | Yes, No |
Customer two-factor authentication | Controls whether customer users must complete email-based two-factor authentication after login. | Yes, No |
Customer login methods | Sets which login methods the storefront offers, and a store may offer more than one at once. | E-mail + password, userName + SMS code (passwordless) |
Compare userName in lowercase mode | When on, userNames that differ only in letter case are treated as the same userName; when off, the case must match exactly. | Enable switch |
OTP code lifetime (seconds) | Sets the lifetime in seconds of one-time codes, shared by login two-factor authentication and account-activation two-factor authentication. | Number field |
Show base price to guests | Controls whether unauthenticated guest users can see product pricing. | Yes, No |
Date format | Controls the display format of all dates across the application, such as orders, documents and shipping dates. | DD/MM/YYYY, MM/DD/YYYY, YYYY-MM-DD, DD.MM.YYYY, MM.DD.YYYY, YYYY/MM/DD |
Passwordless login
Passwordless login drops the password entirely: customers sign up with a userName and their mobile phone, and each sign-in asks for the userName plus a one-time SMS code. That code is always texted to the phone saved when the account was created, whatever number someone enters when signing in. Two-factor authentication for customers is skipped here, since the texted code already plays that role. This login method has no self-service account recovery, so an administrator corrects a customer's phone number when it changes.
Guest visibility
If guests may not see products, visitors who have not signed in find category pages empty until they sign in. For a guest, the price service returns no prices unless base prices are shown to guests.
Notes
On an unchanged page, Save is unavailable.
Comparing userNames in lowercase mode is effectively a deployment-time decision, so set it before the first registration. When the lowercase mode is on, the original casing is destroyed when a userName is written and cannot be recovered. Turning that mode on after accounts exist can also collide with rows that already exist.
Changing the OTP code lifetime affects both the login flow and the account activation flow.
Related