Stoneholl Related Customer Orders for Magento 2

Order context, without leaving the order.

Show other orders from the exact same store view in a compact native Admin table. Order number, creation date, status and an explicit match basis provide focused context without displaying customer names, email, addresses, amounts or payment details.

Clear matches and visible limits

Same customer account

Registered orders match a positive customer account ID and non-guest flag. The current profile and profile email are never read; guest and registered orders never mix.

Optional possible guest matches

A separate setting and permission enable strict order-snapshot email matching. Only the domain is lowercased; local-part bytes are preserved. Shared or recycled mailboxes do not establish identity.

Ten results per page

The native AJAX pager refreshes only the related-order block. A page input supports Enter; visible candidate coverage and match counts describe the bounded search window.

A bounded search, not complete history

Registered mode searches the latest 1,000 other account orders across stores; other-store orders consume this window but never appear. Guest mode searches the latest 1,000 other orders in the current store. A 1,001st candidate indicates that older orders were not searched. Results exclude the current order and sort by descending record ID. Store 0, missing stores, inconsistent identities and unsupported guest email snapshots are unavailable. No trimming, local-part case folding, plus-tag removal, aliases, Unicode conversion, phone or fuzzy matching is performed.

Offline, read-only and permission-gated

Rendering requires Magento_Sales::actions_view and Stoneholl_RelatedCustomerOrders::view. Guest matching also requires Stoneholl_RelatedCustomerOrders::guest_matches; configuration permission alone grants no viewing access. Disabled or denied blocks execute no related-order queries. Same-store filtering is not row-level authorization: roles with third-party order restrictions need verified query and target-access integration before view permission is granted. There are no order mutations, feature storage, telemetry or external requests. Email remains server-side in Magento 2 and is stripped from presentation state. This website uses fictional snapshots only.

Enable only the matching you need

Run composer require stoneholl/module-related-customer-orders:^1.0. Enable Stoneholl_Core and Stoneholl_RelatedCustomerOrders, then follow your normal Magento 2 upgrade, DI compilation, Admin static deployment and cache procedure. Under Stores > Configuration > Stoneholl > Related Customer Orders > General at Default scope, both Enable Related Customer Orders and Enable Possible Guest Email Matches default to No. Review role permissions and refresh role sessions. Free Core ^1.0 is required; Connector, pairing and paid entitlements are not required.

Release validation and runtime scope

Release documentation records Magento Open Source 2.3.7-p4 / PHP 7.4.33 and Magento Open Source 2.4.9 / PHP 8.5.9 installation, upgrade, Core-only DI, Admin static deployment, persisted-role configuration and authenticated AJAX/cache checks. Interactive pagination and preservation of unsaved order input were checked on 2.4.9. PHP 8.0 has parser coverage only. Other Magento/PHP combinations and Adobe Commerce are not runtime certified; third-party Admin layouts need placement verification.

Good to know

How can I see related customer orders in Magento2?

Enable Related Customer Orders to show other orders from the same customer account and exact store view. Possible guest email matches require their separate setting and view permission.

Does the count cover the customer’s complete history?

No. Counts and pages cover only eligible matches in the bounded candidate window. Older orders may not have been searched.

Does a matching guest email prove the same person?

No. Email matches are possible connections, not verified identity. Shared or recycled mailboxes can belong to different people.

Can another store’s orders appear?

No. Only the current order’s exact store view is displayed. Other-store account orders still consume the registered search window.

Can I merge accounts or export a full history?

No. The module is a read-only context block. Account linking, exports and complete-history searches are outside its scope.