On this page
  1. General settings
  2. Paths without an Admin field

Configuration Fields

This reference lists the settings exposed by mageb2b/customer-id in Magento Admin.

Configuration paths are included for controlled deployments and config:set. Use Magento Admin for normal changes so field validation and scope inheritance still apply. The extension status display is not listed because it reports installation state rather than a configurable value.

General settings

Field Configuration path Input Scope
Login with Customer ID possible customer_id/customer_id/login Select Default, Website, Store view
Auto increment for customer ID customer_id/customer_id/auto_increment Select Default, Website, Store view
Auto template for customer ID customer_id/customer_id/id_template Text Default, Website, Store view
Apply template also to already existing id's customer_id/customer_id/template_force_apply Select Default, Website, Store view
Next number range customer_id/customer_id/next_increment Text Default, Website, Store view
ID range is global customer_id/customer_id/idrange_global Select Default, Website, Store view
List of characters, which should not be allowed customer_id/customer_id/disallowed_characters Text Default, Website, Store view
Log Customer IDs while saving customer_id/customer_id/log_customerids Select Default, Website, Store view
Display Customer ID on customer dashboard customer_id/customer_id/display_customer_id_on_customer_dashboard Select Default, Website

Visibility dependencies:

  • customer_id/customer_id/id_template is available when customer_id/customer_id/auto_increment is 1.
  • customer_id/customer_id/template_force_apply is available when customer_id/customer_id/auto_increment is 1.
  • customer_id/customer_id/next_increment is available when customer_id/customer_id/auto_increment is 1.
  • customer_id/customer_id/idrange_global is available when customer_id/customer_id/auto_increment is 1.

Paths without an Admin field

These paths ship config.xml defaults but have no Admin field. Change them only via config:set when you know what you are doing:

Purpose Configuration path Default
Collision retry limit for non-range auto-allocation customer_id/security/max_recursion_attempts 1000

In non-range mode the generator retries each colliding candidate. When retries exceed this limit the customer save fails with Unable to generate unique customer ID after N attempts. The usual fix is more ID space (longer template numbers or a configured range), not a higher limit.