Deutsche Version →
Vermontas Nexus // Customer identity // Magento 2

Magento 2 customer identity and order control. Within a network of traces and relationships.

Vermontas Nexus is the identity and control layer for Magento 2 orders. Magento initially knows orders, customer accounts, email addresses and IP addresses as separate data points. Nexus makes their relationships visible, preserves confirmed identities as lasting knowledge and turns that context into clear actions: Stop fake orders deliberately, Prevent abusive reviews and Assign guest orders to existing customer accounts.

Explore Nexus Integrate or adapt Manual
Magento 2 · Hyvä and classic Magento frontends · DE · CH DE · EN · FR · IT · ready to integrate · adaptable when needed
Identity relationships Customer account · Email · IP
observed relationships
confirmed relationships
deliberate boundaries
The additional layer

Magento knows orders and customer accounts.
Nexus knows how they relate.

Vermontas Nexus adds an identity and control layer to Magento orders. Historical data remains untouched; Nexus adds a traceable relationship layer on top.

Magento

The data is already there.

Order
Customer account
Email address
IP address
Order history
Nexus

Relationships become visible.

Order ↔ customer accountA guest order can be assigned to an existing account.
Order ↔ email addressPrevious orders using the same address become visible together.
Order ↔ IP addressRecurring technical traces are shown as context, not as a judgment.
Identity ↔ previous ordersConfirmed relationships remain available as a separate knowledge layer.
Nexus does not change historical Magento data. It makes observed relationships visible and preserves additional knowledge where an administrator deliberately confirms a relationship as an identity.
A relationship is not automatically an identity

Observing is not the same as knowing.

Nexus deliberately separates technical matches from confirmed knowledge and from a boundary based on that knowledge.

01 // Observation

A relationship becomes visible.

The same email, the same IP or the same customer account are first and foremost traceable data relationships. Nexus shows them without automatically turning them into a judgment.

02 // Confirmed knowledge

Relationships become an identity.

The administrator can deliberately confirm multiple customer accounts, email addresses and IP addresses as belonging together. This knowledge is retained as an identity group.

03 // Boundary

A confirmed identity can be restricted.

An active identity group can be blocked as a whole. Attributes added later are automatically included in the blocking check.

Why Nexus?

Connecting identities is not an end in itself.

The value appears where relationships between orders become practically relevant: recurring fake orders, review opportunities created by those orders and guest orders that should be assigned to an existing customer account.

Stop fake orders deliberately

Recurring identities can be recognized through customer account, email address and IP address and, when needed, blocked through individual rules or as an entire identity group. Attributes added later to a blocked group are automatically included in the blocking check.

Prevent abusive reviews

If a shop derives review eligibility from completed orders, artificially created orders can be abused for exactly that purpose. Nexus blocks orders from known blocked identities before any later review eligibility can arise.

Assign guest orders to existing customer accounts

Guest orders can deliberately be assigned to an existing Magento customer account even when the order email differs from the account email. Historical order data such as addresses, items and prices remains unchanged.

An order enters Nexus

An order is rarely just an order.

Magento knows the individual record. Nexus places the available traces next to it and makes relationships to previous orders and known identities visible.

Order example
ORDER #1000432
Customer
Guest
EMAIL
orders@exampleshop.test
IP address
84.xxx.xxx.xxx
Customer account
not assigned
Same IP
Previous orders foundwith partly different email addresses
4
Same email
Order history visiblesame contact in additional orders
2
Customer account
Matching account availablecan deliberately be selected and assigned
1
Identity group
No confirmed relationship yetthe administrator can review the relationship and preserve it as lasting knowledge
○
From relationship to action

Recognize. Connect. Assign. Set boundaries.

The identity and control layer leads from an observed relationship to a deliberate action. Four actions form one coherent logic.

I // Recognize

Recognize relationships

Matching customer ID, email address and IP address bring existing order traces together in one place.

II // Connect

Connect identities

Relationships confirmed by the administrator are preserved as lasting knowledge in an identity group.

III // Assign

Assign orders

Guest orders can deliberately be assigned to an existing Magento customer account.

IV // Set boundaries

Set boundaries

Individual customer IDs, email addresses and IP addresses can be blocked deliberately. Confirmed identity groups can additionally be blocked as a whole.

Human decision layer

No automatic judgment.
Context before action.

Nexus does not calculate a suspicion score. A shared IP, a recurring email address or multiple orders are data first. Nexus shows the relationships. The administrator decides which relationships permanently belong to an identity and where a boundary should be set.

Nexus shows relationships so the administrator can interpret them. Only then is an order assigned, an identity connected or a boundary set.

Four functions in detail

Four functions of the identity and control layer.

Recognizing, connecting, assigning and setting boundaries work together wherever an order should be handled not merely as an isolated record but in the context of a known identity.

01 // Order blocking

Block deliberately.

Rules can respond to customer ID, email address and IP address For each attribute, the administrator separately decides whether it is part of the blocking rule.

Enabled criteria use OR logic. As soon as one of them matches, the order is blocked server side. The customer facing message and an internal admin notice can be defined freely.

Blocking rule
Customer ID1842active
EMAILissue@exampleshop.testactive
IP address84.xxx.xxx.xxxoptional
ResultOrder is blocked server sideBoundary
Customer account assignment
02 // Customer account assignment

Assign guest orders to an existing customer account.

The target account is selected through a native Magento customer grid with search, filters and pagination. Assignment is also possible when the order email differs from the customer account email.

Historical order data remains unchanged. Nexus creates the logical connection to the customer account without rewriting the email address, billing address, shipping address, order items or prices.

03 // Identity context

Make traces visible before a decision.

The identity context brings together orders sharing the same customer account, email address or IP address and additionally shows matching confirmed identity groups. This turns an individual order into a traceable context.

From there, the administrator can continue directly and, when needed, assign, connect or block. Direct order relationships and confirmed knowledge from identity groups deliberately remain separate.

Identity context
Order #1000432same emailrelationship
Order #1000187same IPrelationship
Order #1000112same customer accountknown
DecisionAdministrator reviews the relationshipHuman
Confirmed identity group
Customer accounts#481 Example Company#622 Max Exampleconfirmed
Email addressesorders@exampleshop.testmax@examplecustomer.testconfirmed
IP addresses84.xxx.xxx.xxxconfirmed
Group blockingentire confirmed identityactive
04 // Identity groups

Preserve confirmed relationships as knowledge.

Multiple customer accounts, email addresses and IP addresses can be assigned to one identity. That knowledge remains available for future orders.

An active identity group can be blocked as a whole. A match on customer ID, email address or IP address is then enough to block a new order server side. Attributes added to the group later are automatically included in the blocking check.

Technical foundation

Close to Magento. No additional platform.

Nexus extends existing Magento data and processes. Its core functions operate in the Magento admin and server side, so they are not limited to Hyvä.

PlatformMagento 2Orders, customer accounts and integration into the Magento admin.
FrontendHyvä independentAlso designed for classic Magento frontends.
Blocking logicServer sideIndividual blocking rules and complete identity groups are checked during order placement.
MatchingCustomer ID · Email · IPDirect matching plus recognition through confirmed identity groups.
LanguagesDE · CH DE · EN · FR · ITLanguage packs for the supported admin interfaces.
ModuleVermonta_NexusStandalone Magento 2 module.
Integration & adaptation

Nexus for your Magento store.

Vermontas Nexus provides a solid technical foundation. If an adjustment to your Magento environment is necessary or desired, it is implemented directly and professionally for the specific use case.

Complete at its core. Adaptable in detail.

Ready to integrate // adaptable when needed

A complete foundation. Integrated to fit.

Vermontas Nexus already provides the technical foundation. If Nexus fits as it is, it is integrated accordingly. If adjustments are useful or desired, they are incorporated where needed. You then receive a suitable proposal for integration, setup and handover.

  • Review of the existing Magento environment and the specific use case
  • Integration of the Nexus functions into the existing store
  • Order blocking by customer ID, email address and IP address
  • Identity context and confirmed identity groups
  • Complete blocking of confirmed identity groups
  • Assignment of guest orders to existing customer accounts
  • Setup of customer-facing messages and admin functions
  • Documented handover with the Nexus manual
  • Project-specific adjustments to the existing store environment where required
Ask about Nexus
Scope and price depend on your Magento environment and the specific requirements. You receive a transparent proposal before work begins.
Frequently asked questions

Questions about Vermontas Nexus

The key functional boundaries and decisions at a glance.

What is Vermontas Nexus?

Vermontas Nexus is the identity and control layer for Magento 2 orders. The extension makes relationships between orders, customer accounts, email addresses and IP addresses visible, preserves confirmed identities as lasting knowledge and connects this knowledge layer with customer account assignment and blocking logic.

Does Nexus only work with Hyvä?

No. The core functions operate in the Magento admin and server side. Nexus is therefore not limited to Hyvä and can also be used with classic Magento frontends.

Does Nexus automatically decide whether an order is problematic?

No. Nexus shows data and relationships. The administrator deliberately decides whether to confirm a relationship, assign an order or set a boundary.

What does the identity context show?

For the current order, Nexus finds previous orders that use the same customer account, email address or IP address. Already confirmed identity groups are shown separately as additional context.

What does customer account assignment change on an order?

The customer ID is set and the order is no longer marked as a guest order. Historical order email, billing address, shipping address, items, prices and other order data remain unchanged.

Do the customer account and order need to use the same email address?

No. Assignment is a deliberate administrator action. For example, an order using a company email can be assigned to an existing customer account with a different email address.

How does order blocking work?

A blocking rule can respond to customer ID, email address and IP address. The administrator separately decides which attributes are considered. As soon as one enabled attribute matches, the order is blocked.

What are identity groups?

Identity groups store relationships confirmed by the administrator. Multiple customer accounts, email addresses and IP addresses can be documented as belonging together without changing historical Magento data.

Can an entire identity group be blocked?

Yes. An active identity group can be blocked completely. If a new order matches the group's customer ID, email address or IP address, the order is blocked server side. New attributes added to the group later are automatically covered by the group block.

Can Nexus be integrated directly or adapted?

Yes. Nexus already provides the technical foundation and can be integrated directly into a suitable Magento environment. If adjustments are necessary or desired, they are implemented specifically for the use case.

Vermontas Nexus

Technology creates order.
Order creates peace of mind.

An identity and control layer for Magento shops where relationships between orders should be visible, confirmed knowledge should persist and boundaries should be set deliberately.

Discuss Nexus