tig / postcode-magento2

tig/postcode-magento2

magento2-module Compatibility: 2.4.7 Code Quality: Fail Tests: Fail Security: Pass CC-BY-NC-ND-3.0

Are you the maintainer of tig?

Packagento pulls tig's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

Postcode Service Magento 2 extension

Latest Stable Version
TIG Postcode Service 2.4.7 versions
TIG Postcode Service 2.4.7 versions
TIG Postcode Service 2.4.7 versions
TIG Postcode Service 2.4.6 versions
TIG Postcode Service 2.4.5 versions
TIG Postcode Service 2.4.4 versions
Total Extension downloads

Introduction

With the Postcode Service you can auto complete a partly given address and check its validity.

This code base is an extension (plugin) for the Adobe Magento platform using the Postcode Service
API https://api.postcodeservice.com. The extension is available
and maintained free or charge. However, there is a fee
associated with using the Postcode Service, which is integrated with the extension. The
exact cost depends on the amount of usage. You can find detailed pricing information on the website
at https://postcodeservice.com/#compare-packages

3 Reasons for using the Postcode Service Adobe Magento extension:

  • Superfast performance due to specific code and design optimizations for Adobe
    Magento webshops
  • Accurate and reliable data, ahead of the market
  • Secure: Independent of logistics companies

Installation

We strongly recommend that you use a staging environment for the installation, and to also make a
backup of your environment.

Installation using composer (Recommended)

To install the extension login to your environment using SSH.
Then navigate to the Magento 2 root directory and run the following commands in the same order as
described:

Enable maintenance mode:

php bin/magento maintenance:enable

Install the extension:

composer require tig/postcode-magento2

Enable the Postcode Service Magento 2 extension

php bin/magento module:enable TIG_Postcode

Update the Magento 2 environment:

php bin/magento setup:upgrade

When your Magento environment is running in production mode, you also need to run the following
commands:

Compile DI:

php bin/magento setup:di:compile

Deploy static content:

php bin/magento setup:static-content:deploy

Disable maintenance mode:

php bin/magento maintenance:disable

How to update the extension

To update the Postcode Service Extension run the following commands:

composer update tig/postcode-magento2
php bin/magento setup:upgrade

Alternatively, install the extension manually

  • Download the extension directly
    from github by clicking on Code and then
    Download ZIP.
  • Create the directory app/code/TIG/Postcode (Case-sensitive)
  • Extract the zip and upload the code into app/code/TIG/Postcode
  • Enable the Postcode Service Magento 2 extension
php bin/magento module:enable TIG_Postcode
  • Update the Magento 2 environment
php bin/magento setup:upgrade

Configuration

After completing the installation process, the extension should be readily available in the backend
of your Magento webshop. From there, you can configure the extension according to your requirements:

  1. Go to Stores -> Configuration -> Sales -> Postcode Service

  2. Open the Configuration tab

  3. Change the Modus from "Off" to "Test" or "Live"

  4. Insert your Client ID and Api key (Secure Code). When you selected “Test” at the Modus, you can
    find test credentials below the fields - keep in mind there is a daily limit -.
    To sign up for a paid account and get your Client ID and Api key, simply
    visit https://postcodeservice.com and subscribe.

  5. In the 'Countries' section, select the country for which you wish to enable the Postcode Service.

  6. Flush your cache

Visual representation of the Postcode Service Magento extension during the checkout process

For Dutch postcodes

postcode_service_magento2-nl

For Belgium postcodes

postcode_service_magento2-be

For German postcodes

The functionality for Germany is similar to that for Belgium. Please refer to the preceding example
for a demonstration of its operation.

For France Postcodes

The functionality for France is similar to that for Belgium and Germany. Please refer to the
preceding example for a demonstration of its operation.

Further documentation

You can find the underlying Postcode Service API documentation
here: https://developers.postcodeservice.com

Frequently Asked Questions

Q: Which third party extensions are supported and compatible?

A: While our extension is compatible with many third-party checkout extensions, we do not provide
support for third-party checkout extensions from OneStepCheckout.com, Amasty, and MagePlaza.
Although there are numerous webshops that successfully use these extensions in combination with our
Postcode Service extension, we cannot guarantee their compatibility due to potential issues arising
from custom implementations. As a result, we are unable to offer support for any issues that may
arise from their use.

Requirements

Adobe Magento Open Source (Community edition) or Adobe Commerce (Enterprise version).

Version support

We follow the release support lines dates from
Adobe https://experienceleague.adobe.com/docs/commerce-operations/release/versions.html for the
version support of this extension.

Technical Support with the extension

See https://postcodeservice.com/support/

Release history

See https://github.com/postcodeservice/postcode-magento2/releases

About

The Postcode Service is a trademark of the Total Internet Group B.V.

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.7.0 stable Fail Magento 2.4.7 Details 2024-04-05 14:44:22
1.6.0 stable Not tested Not yet tested Details 2023-10-20 19:32:30
1.5.5 stable Not tested Not yet tested Details 2023-05-19 10:05:52
1.5.4 stable Not tested Not yet tested Details 2023-04-25 14:09:27
1.5.3 stable Not tested Not yet tested Details 2023-03-21 11:05:19
1.5.2 stable Not tested Not yet tested Details 2022-12-19 12:39:06
1.5.1 stable Not tested Not yet tested Details 2022-07-05 13:03:43
1.5.0 stable Not tested Not yet tested Details 2022-07-05 09:38:21
1.5.0-RC1 RC Not tested Not yet tested Details 2022-05-19 11:45:19
1.4.1 stable Not tested Not yet tested Details 2021-11-04 10:06:18
1.4.0 stable Not tested Not yet tested Details 2021-07-12 12:29:29
1.3.3 stable Not tested Not yet tested Details 2021-04-20 11:47:00
1.3.2 stable Not tested Not yet tested Details 2021-03-01 13:00:59
1.3.1 stable Not tested Not yet tested Details 2020-10-26 11:10:01
1.3.0 stable Not tested Not yet tested Details 2020-10-12 14:07:33
1.2.7 stable Not tested Not yet tested Details 2020-07-29 14:10:51
1.2.6 stable Not tested Not yet tested Details 2020-04-29 15:46:10
1.2.5 stable Not tested Not yet tested Details 2020-01-27 12:23:33
1.2.4 stable Not tested Not yet tested Details 2019-10-10 09:24:04
1.2.3 stable Not tested Not yet tested Details 2019-06-26 12:50:01
1.2.2 stable Not tested Not yet tested Details 2019-03-27 12:26:32
1.2.1 stable Not tested Not yet tested Details 2019-02-04 12:07:17
1.1.10 stable Not tested Not yet tested Details 2019-01-22 11:44:03
1.2.0 stable Not tested Not yet tested Details 2019-01-08 09:28:33
1.1.12 stable Not tested Not yet tested Details 2018-12-12 09:24:33
1.2.0-RC1 RC Not tested Not yet tested Details 2018-12-03 12:31:02
1.1.11 stable Not tested Not yet tested Details 2018-10-19 13:57:59
1.1.9 stable Not tested Not yet tested Details 2018-08-07 08:07:19
1.1.8 stable Not tested Not yet tested Details 2018-07-26 14:58:24
1.1.7 stable Not tested Not yet tested Details 2018-06-28 08:28:57
1.1.6 stable Not tested Not yet tested Details 2018-06-21 11:39:24
1.1.5 stable Not tested Not yet tested Details 2018-06-13 13:53:43
1.1.4 stable Not tested Not yet tested Details 2018-05-28 12:37:11
1.1.3 stable Not tested Not yet tested Details 2018-05-22 13:47:35
1.1.1 stable Not tested Not yet tested Details 2018-05-03 15:39:17
1.1.0 stable Not tested Not yet tested Details 2018-04-23 09:54:02

Requires 3

Package Constraint
magento/module-checkout >=100.2.6,<=100.2.11|~100.3|~100.4
magento/module-quote >=101.0.5,<=101.0.11|~101.1|~101.2
php ~8.1|~8.2

Requires-dev 3

Package Constraint
magento/marketplace-eqp ^1.0
object-calisthenics/phpcs-calisthenics-rules ^2.0
satooshi/php-coveralls ^1.0

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Fail di error
2.4.9 Fail di error Fail di error

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Fail 100 6 errors, 94 warnings (ruleset: Magento2) — 57 auto-fixable with phpcbf
PHPMD Warning 28 28 rule violations (UnusedFormalParameter:11, MissingImport:11, TooManyPublicMethods:2, UnusedPrivateField:1, NumberOfChildren:1)
Cpd Warning 4 4 duplicated chunks spanning 204 total lines (min-lines=5, min-tokens=70)
Composer validate Info 1 valid; 1 advisory note (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 24 24
2.4.8 24 28
2.4.9 28 28

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Error Error
2.4.8 Error Error
2.4.9 Error Error

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit N/A 0 no resolvable dependency tree to audit — Your requirements could not be resolved to an installable set of packages. Problem 1
Malware scan Pass 0
License
CC-BY-NC-ND-3.0
Homepage
https://postcodeservice.com
Authors

More from tig

View vendor
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.