reach-digital / magento2-guesttoshadowcustomer

reach-digital/magento2-guesttoshadowcustomer

magento2-module Compatibility: Not compatible Code Quality: Fail Tests: Fail Security: Pass

magento2-ReachDigital_GuestToShadowCustomer

Installation

composer require reach-digital/magento2-guesttoshadowcustomer

Cron Usage

n98-magerun2 sys:cron:run <number> reachdigital_guesttoshadowcustomer_convert

Introduction

  • Create more insight into the total amount of orders per unique visitors
  • In the backend there should be a possibility to create reorders for guests
  • Possibility to save Guests payment information

Functionalities

  • Create Shadow Customer if new guest order is placed.
  • Loop through all historical guest orders and create shadow customers.
  • Loop through all historical guest orders and link Guest to existing "Customer/Shadow Customer".
  • Added "Shadow Customer" column in Admin > Customer/Order Grid.
  • Added "Is Shadow Customer" information on Admin > Customer/Order Edit page.

Known Issues

  • Cancelling an MSP payment does not restore the cart properly (for a fix see this commit)
    • A similar fix is already applied for Mollie, see this commit

TODO

  • Config setting for enabling or disabling the blocking of password reset function if customer is shadow
  • Correctly set is_shadow if resetting password is enabled for shadow customers

Implement more tests:

  • Test that is_shadow flag is 0 when user registers
  • Test that is_shadow flag value is maintained when customer is updated through webapi
  • Test that is_shadow flag is 1 when shadow customer is automatically created
  • Test that password reset is not allowed if not enabled and customer is shadow
  • Test that password reset is allowed if enabled and customer is shadow
  • Test correct updating of customer is_shadow flag in customer_grid_flat table (see
    \Magento\Customer\Model\ResourceModel\Grid\CollectionTest::testGetItemByIdForUpdateOnSchedule and
    \Magento\Customer\Model\Indexer\AttributeProvider
    )

No changelog yet

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

Versions
Version Stability QA Status Compatibility Released
v1.4.2 stable Not tested Not yet tested Details 2026-06-03 09:03:38
1.4.1 stable Fail Not compatible Details 2026-05-29 09:22:52
1.4.0 stable Not tested Not yet tested Details 2026-05-29 07:05:16
1.3.4 stable Not tested Not yet tested Details 2025-05-14 14:16:41
1.3.3 stable Not tested Not yet tested Details 2024-11-12 13:24:01
1.3.2 stable Not tested Not yet tested Details 2024-05-22 06:59:20
1.3.1 stable Not tested Not yet tested Details 2023-10-25 14:05:09
1.3.0 stable Not tested Not yet tested Details 2023-10-19 08:04:01
1.2.0 stable Not tested Not yet tested Details 2023-07-31 09:27:23
1.1.7 stable Not tested Not yet tested Details 2022-11-28 15:00:33
1.1.6 stable Not tested Not yet tested Details 2021-10-29 14:01:02
1.1.5 stable Not tested Not yet tested Details 2021-10-27 09:59:27
1.1.4 stable Not tested Not yet tested Details 2021-10-26 14:05:25
1.1.3 stable Not tested Not yet tested Details 2021-09-20 09:14:55
1.1.2 stable Not tested Not yet tested Details 2021-08-19 09:58:51
1.1.1 stable Not tested Not yet tested Details 2021-06-09 11:51:25
1.1.0 stable Not tested Not yet tested Details 2021-04-20 13:55:03
1.0.0 stable Not tested Not yet tested Details 2021-04-20 13:54:01

Requires 2

Package Constraint
php ~8.3
magento/framework ~103.0.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 not tested Fail di error
2.4.8 Fail di error Fail di error
2.4.9 Fail unknown 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 73 4 errors, 69 warnings (ruleset: Magento2) — 15 auto-fixable with phpcbf
PHPMD Warning 25 25 rule violations (UnusedFormalParameter:18, EmptyCatchBlock:2, MissingImport:1, UnusedLocalVariable:1, CyclomaticComplexity:1)
Cpd Warning 2 2 duplicated chunks spanning 43 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. Cell → details modal.

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

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 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

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 1
2.4.8 Error Error
2.4.9 Error Error

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 Pass 0
Malware scan Pass 0

No license declared

This package's composer.json doesn't declare a license, homepage, or authors. Check the source repository for terms of use.

More from reach-digital

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.