Is your feature request related to a problem? Please describe.
Currently there is no way to explicitly designate which address should be considered the user's default billing address versus the default shipping address.
This limits how address information can be exposed consistently through APIs and other platform features.
Describe the solution you'd like
At the user and user group, be able to configure:
- Default Billing Address
- Default Shipping Address
This would provide flexibility for Accounts (user groups) to have their default billing and shipping address, different than the individual user's defaults. This supports a scenario where an Account can have 100 addresses and 1000 profiles. Addresses may be getting retrieved based on customer number (so there are only 100 addresses in AccessUserAddress) but each individual user can have their own combination of default billing versus default shipping address.
Describe alternatives you've considered
Using custom fields. This introduces complexities to the project and are harder to maintain.
Additional context
This feature complements the Delivery API improvements but is valuable independently.
Best Regards,
Nuno
Is your feature request related to a problem? Please describe.
Currently there is no way to explicitly designate which address should be considered the user's default billing address versus the default shipping address.
This limits how address information can be exposed consistently through APIs and other platform features.
Describe the solution you'd like
At the user and user group, be able to configure:
This would provide flexibility for Accounts (user groups) to have their default billing and shipping address, different than the individual user's defaults. This supports a scenario where an Account can have 100 addresses and 1000 profiles. Addresses may be getting retrieved based on customer number (so there are only 100 addresses in AccessUserAddress) but each individual user can have their own combination of default billing versus default shipping address.
Describe alternatives you've considered
Using custom fields. This introduces complexities to the project and are harder to maintain.
Additional context
This feature complements the Delivery API improvements but is valuable independently.
Best Regards,
Nuno