<p>I would suggest that date and place of birth would be more appropriate as custom fields on the User profile rather than attached to the address. They don't appear to have any relevance to an address, unless there's a very particular use-case you're building for.</p>

CC BY-SA 4.0
2022-10-24T09:04:47.787Z
The user orders a course for either themselves or someone else. This requires a date of birth and place of birth. This can differ per order so it made sense to put it in the Address but is not required. A profile field would be less favorable.
Rayco
CC BY-SA 4.0
2022-10-24T12:52:24.333Z
Ah. In that case, the data for date and place of birth are relevant to the order itself so I'd add them to the product/variant that's used for the course, rather than the address.
Martin Spain
CC BY-SA 4.0
2022-10-24T08:59:13.907Z
2022-10-24T08:59:13.907Z
Martin Spain
<p>I want my customers to enter their <strong>date of birth</strong> and <strong>place of birth</strong> during the checkout.</p>
<p>Do I have to overwrite the Address commerce model somehow? (<code>\craft\commerce\models\Address</code>).</p>
<p>Something else I could think of is adding custom fields to the user itself. Though I'm not sure if this is the correct way.</p>

<plugin-craftcommerce><php><plugin-craftcommerce2><models><addresses>
How can I best add additional fields to the Address form during the checkout
# How can I best add additional fields to the Address form during the checkout

(Asked by: username_0 on 2022-10-24)

I want my customers to enter their **date of birth** and **place of birth** during the checkout.

Do I have to overwrite the Address commerce model somehow? (`\craft\commerce\models\Address`).

Something else I could think of is adding custom fields to the user itself. Though I'm not sure if this is the correct way.

**Tags:** plugin-craftcommerce, php, plugin-craftcommerce2, models, addresses


---

## 1 answers

### Answer by username_1 on 2022-10-24. Score: 1

I would suggest that date and place of birth would be more appropriate as custom fields on the User profile rather than attached to the address. They don't appear to have any relevance to an address, unless there's a very particular use-case you're building for.

> **Comments:**
> **username_0**: The user orders a course for either themselves or someone else. This requires a date of birth and place of birth. This can differ per order so it made sense to put it in the Address but is not required. A profile field would be less favorable.  
> **username_1**: Ah. In that case, the data for date and place of birth are relevant to the order itself so I'd add them to the product/variant that's used for the course, rather than the address.  

---

