The Commerce 2.0 depends on the Profile module, and indeed it defines a bundled "customer" profile that runs Commerce Order logics and that is stick on a locked address field (as highlighted here: https://www.drupal.org/node/2820122#comment-12024424) and that is mainly used (needed) for collecting and attaching Billing Informations to each Order, and populate the user/customer Address Book.
With this logic it is very probable a new custom profile should be created to store general and further customer/user information (not strictly related to billing), such as sex, phone, age, whatever ...
In my opinion I would naturally call "customer" this new profile, but this machine name is not available, as it is used by Commerce to collect customer billing info.

That's why I would really propose/ask to rename the commerce "customer" profile name into something that better represent its commerce use, such as "customer_billing" or something similar ... (so that "customer" will be still available).

Comments

itamair created an issue. See original summary.

itamair’s picture

itamair commented
Issue summary: View changes
itamair’s picture

itamair commented
Issue summary: View changes
bojanz’s picture

bojanz commented
Title: Different naming for the "customer" profile mainly used for Billing Info » Document the usage of the "customer" profile
Category: Feature request » Task

It's also used for shipping information.
The logic for what goes on the customer profile VS what goes on the user / additional profiles is the same as it was in Commerce 1.x (with the previous commerce_customer_profile entity), nothing has changed here. Sex, age, etc have never belonged on the customer profile, cause a single user only has one sex/age, but does have multiple customer profiles.

Repurposing this for a documentation issue, where we need to explain all of that.

itamair’s picture

itamair commented

but in Commerce 1.x your where not basing on the profile2 module, but on commerce custom entity (isn't it?)
and at least it was (machine) named "commerce_customer", and not just "customer".
Here, too (at least) "commerce_customer" would then make more sense, stressing that is a commerce working profile (for billing and shipping, and whatever else commerce related needs).
With "customer" you are occupying / using a veeeery generic (and potentially misleading) profile machine name. IMO ...

mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented
Category: Task » Support request
Priority: Major » Normal

This is a 1.x vs 2.x mechanism discussion. Adjusting category and priority.

bojanz’s picture

bojanz commented
Status: Active » Closed (outdated)

Closing this. Our docs have been expanded in the meantime. Regardless of whether "customer" was good naming, we've been stuck with it for years now due to backwards compatibility.