Does this change my existing addresses?

No. Existing records stay as they are. The split applies to new storefront input, and data is still stored in the standard Shopware field.

Does it work with my custom theme?

Usually yes. The extension builds on Shopware's standard templates. If the address form has been heavily rebuilt in your theme, some adjustment may be needed.

What about integrations with ERP or shipping providers?

Nothing changes for those systems, because the backend receives the unmodified standard field. That is exactly why the extension is built this way.

Why is the name different in the Shopware Store?

It has been listed there as "Disable 2 fields for street number/ salutation" since 2022. Store names cannot be freely changed after Shopware has approved an extension — it is the same product.

In the Shopware StoreCheckout & cart process

Split street and house number

Two separate checkout fields instead of one — while the backend still receives the plain Shopware address field.

Shopware Store: Disable 2 fields for street number/ salutation

View in the Shopware Store

Pricing and billing in the Shopware Store

At a glance

Street and house number as two separate input fields
Merging back into the standard Shopware field happens automatically
Salutation can optionally be hidden
Four interface languages, no configuration needed
Maintained since 2022 across eight Shopware generations

Features

Two fields instead of one: In the default checkout many customers put the house number in the wrong place or leave it out entirely. Two labelled fields make it unambiguous what goes where.
The backend stays standard Shopware: The split happens in the storefront only. The backend, exports and connected systems still receive the normal Shopware address field — no downstream process needs adjusting.
Optionally hide the salutation: If you would rather not collect a salutation, the field can be hidden in registration and checkout. That removes a required entry and avoids a categorisation not every store needs.
Four interface languages: German, English, French and Spanish are included. International sales channels need no separate snippets.
Install and done: The extension is active straight after installation. There are no mandatory settings to configure and no theme work required.

Shopware compatibility

Shopware compatibility per extension
Extension	6.0	6.1	6.2	6.3	6.4	6.5	6.6	6.7
Split street and house number	6.0 — Supported	6.1 — Supported	6.2 — Supported	6.3 — Supported	6.4 — Supported	6.5 — Supported	6.6 — Supported	6.7 — Supported

LegendSupportedNot supported

Requirements

Shopware 6.0 to 6.7

Frequently asked questions

Does this change my existing addresses?: No. Existing records stay as they are. The split applies to new storefront input, and data is still stored in the standard Shopware field.
Does it work with my custom theme?: Usually yes. The extension builds on Shopware's standard templates. If the address form has been heavily rebuilt in your theme, some adjustment may be needed.
What about integrations with ERP or shipping providers?: Nothing changes for those systems, because the backend receives the unmodified standard field. That is exactly why the extension is built this way.
Why is the name different in the Shopware Store?: It has been listed there as "Disable 2 fields for street number/ salutation" since 2022. Store names cannot be freely changed after Shopware has approved an extension — it is the same product.

Other extensions

In the Shopware StoreCRM

HubSpot CRM Integration

Customers, orders and products from Shopware into HubSpot — event-driven or on a schedule.

Technical name: VLPHubSpot
Shopware compatibility: 6.7.0.0 – 6.7.12.2

In reviewIntegrations & middleware

n8n Connector

Products, customers and orders as JSON to n8n webhooks — automation without building your own integration.

Technical name: vlp8n
Shopware compatibility: 6.7.0.0 – 6.7.10.1

In the Shopware StoreCheckout & cart process

SocialConnect

Technical name: VLPSocialLogin
Shopware compatibility: 6.5.0.0 – 6.7.12.2