The new version is compatible with Shopware 6.6.0.0 to 6.6.10.5 - and is now available via GitHub and in the Shopware Store.
Important changes
- JavaScript SDK updated to version 1.13.0
The integration has been comprehensively updated. In particular when usinginitAmsit is therefore advisable to check your own adjustments carefully. - Introduction of separate database tables for address metadata
→ The old tableendereco_address_extNot applicable
→ New tables with suffix_gh(guest/customer) or_sw(order)
New features
Flexible storage strategies for address corrections
Every store has different requirements when it comes to address data - be it in the checkout, during payment processing or in downstream systems. That's why we have introduced a new option in version 6.6.1 that gives you more control over the storage of corrected addresses.
In the Advanced settings of the plugin you will now find the option: "Allow overwriting of the native Shopware address fields"
This allows you to choose between two strategies:
- DeactivatedThe address corrections are only saved in the Endereco extension tables. The original Shopware address data remains unchanged.
→ This can lead to a poorer user experience, as inaccurate or non-standardized addresses are still displayed in the check-out. - ActivatedThe address check, including possible automatic corrections or street divisions, can overwrite the standard Shopware address fields.
→ This means that clean, standardized address data is also directly available for shipping, invoicing or third-party systems.
Advantage: Maximum compatibility - especially for stores with sensitive payment or ERP interfaces
Processing of additional information
Many addresses contain important information that was previously ignored - e.g. "Packstation 123" or "c/o Müller"
- The additional address field is now actively included in the address check.
- The integration supports the field in both the frontend and backend.
- This is particularly useful when checking special formats, such as for packing stations or addresses with PO boxes.
Advantage: Significantly increased validation quality by taking additional context clues into account.
Comprehensible address selection
Each address that has been successfully checked is now assigned a unique characteristic:
address_selected_automatically- The proposed address was accepted by the system.- address_selected_by_customer - The customers have actively selected from several suggestions.
Advantage: Traceability and evaluability - whether in customer service, invoice verification or automated processes.
Input Assistant can be deactivated
In certain markets (e.g. the USA), the automatic input assistantfield reordering or blocked autocomplete, for example, can impair the user experience. That is why there is now:
- A new option in the plugin configuration that allows the Input Assistant to be deactivated while validation remains active.
Advantage: This gives you more control over the front-end behavior - without compromising on data quality.
Improved security of proxy forwarding
In this version, adjustments have been made in the area of proxy forwarding to further optimize data transfer security. This further improves the stability and reliability of address validation, especially in more complex store setups.
Optimized session management
From now on, billing will be even more accurate:
- Sessions are only billed when validation has been completed - e.g. when an address has actually been confirmed.
- Incomplete checks in the front end are initially held back.
- Exception: With the CSV import all validations are counted immediately - as there is no user feedback here.
Important note:
An originally planned feature - the Display of test results in orders - had to be removed, as it caused problems in the ordering process. It will be added in a later release.
Download & Installation
You can find the new version as usual:
Both variants contain identical functions.
Note for integration teamsPlease check your adjustments to the JS-SDK and database structure before the update to ensure a smooth migration.
More details in the complete release notes on GitHub.