Does someone keep placing fake orders in your Magento 2 store, perhaps using different email addresses or customer accounts each time?

Apart from the unnecessary work involved, such orders can interfere with your business processes and, in some circumstances, even be used to obtain opportunities for abusive product reviews.

Blocking a single email address often achieves little if the next order arrives with a different one.

But what if you could recognize connections between orders and take action based on what you already know?

Recognizing relationships between orders

Every Magento order contains information that may help identify recurring activity. Customer accounts, email addresses and IP addresses can provide useful clues about relationships between different orders.

Of course, a matching IP address alone doesn’t prove that two orders came from the same person.

That’s why it’s important to distinguish between observed relationships and identities that have actually been confirmed.

Magento already stores the underlying order and customer information. What it doesn’t provide by default is a dedicated layer for preserving confirmed relationships between different customer accounts, email addresses and IP addresses.

This is exactly where Nexus for Magento 2 comes in.

From individual clues to confirmed identities

Nexus makes relationships between orders visible and allows you to connect multiple customer accounts, email addresses and IP addresses to a confirmed identity group.

The important distinction is that Nexus doesn’t automatically decide who belongs together.

You review the available information and decide which relationships should be preserved.

Once an identity group has been confirmed, that knowledge remains available for future orders.

Blocking known identities

Individual customer accounts, email addresses and IP addresses can be blocked using configurable rules.

You can also block an entire confirmed identity group.

If a new order matches an enabled blocking criterion, Nexus can stop the order directly on the server during order placement.

And if you later add another email address, customer account or IP address to an already blocked identity group, that attribute is automatically included in the group’s blocking rules.

This makes it possible to respond to recurring problematic activity without repeatedly starting from scratch.

Assigning guest orders to existing customer accounts

Nexus also provides another useful feature that is independent of order blocking.

You can assign existing guest orders to Magento customer accounts afterwards, even when the email address used for the order differs from the one registered with the customer account.

The order is linked to the selected account while its original email address, billing and shipping addresses, products and prices remain unchanged.

This can be particularly useful when customers place orders with different email addresses or when existing guest orders need to be associated with the correct customer account.

No automatic fraud scoring. No unnecessary guesswork.

I deliberately designed Nexus without an automated fraud scoring system.

A matching IP address, an unusual order or a recurring email address doesn’t automatically mean that someone is acting dishonestly.

Nexus provides the information, makes relationships visible and allows you to enforce the restrictions you consider necessary.

The decisions remain yours.

This approach combines useful technical controls with the experience and judgment of the person managing the store.

Developed for Magento 2

I developed Nexus to address problems that can arise in real Magento projects, particularly when individual blocking rules are no longer sufficient.

The extension works with Magento 2 and is not limited to Hyvä. Its core functionality operates within the Magento administration and on the server side, making it suitable for traditional Magento frontends as well.

Nexus is available through my software brand Vermonta and can be integrated or adapted to individual project requirements where necessary.

Discover Nexus for Magento 2

If recurring fake orders, unclear customer identities or guest order assignments are causing unnecessary work in your Magento store, Nexus may be a useful addition.

You can find more information about its functionality, technical requirements and integration options on the Vermonta product page.

Explore Nexus for Magento 2

Proceed at your own risk. Test on a staging system or at least make a complete database backup first!

DELETE FROM sales_order WHERE ... ;
DELETE FROM sales_order_grid WHERE ... ;

Clear the Magento 2 cache afterwards and verify that the intended orders were removed.

$order->getFoomanSurchargeAmount();

. This no longer works in Magento 2. Instead, Magento 2 provides extension attributes. The following code retrieves surcharges from different Fooman extensions for further processing:

$extAttr = $order->getExtensionAttributes();

if (!$extAttr) {
   return;
}

$foomanGroup = $extAttr->getFoomanTotalGroup();
if (empty($foomanGroup)) {
    return;
}

$totals = $foomanGroup->getItems();
if (empty($totals)) {
    return;
}

foreach ($totals as $total) {
    $description = $total->getLabel();
    $baseAmount = $total->getBaseAmount();
    $baseTaxAmount = $total->getBaseTaxAmount();
    $amount = $total->getAmount();
    $taxAmount = $total->getTaxAmount();
    $identifier = $total->getTypeId();
    $qty = 1;
    /** Process the surcharges ... */
}

Viel Erfolg :-)!

php bin/magento config:set system/security/max_session_size_admin 0

php bin/magento config:set system/security/max_session_size_admin 0

That should resolve the issue.

php bin/magento config:set system/security/max_session_size_admin 0

Use the following MySQL command to specify the next Bestellung bekommt:

ALTER TABLE sequence_order_1 AUTO_INCREMENT = 123456789;

    $transactionId = $order->getPayment()->getLastTransId();

$transactionId = $order->getPayment()->getLastTransId();

getItemsCollection() ?>
    
        getParentItem()) continue; else $i++;?>
        
            getItemHtml($_item) ?>
            getItemExtraInfoHtml($_item) ?>
        
    

with

getItemsCollection() ?>
    
    
        getSku()] = $_item;?>
    
    
    
        getParentItem()) continue; else $i++;?>
        
            getItemHtml($_item) ?>
            getItemExtraInfoHtml($_item) ?>
        
    

Done. If you open the detail page of an order with 2+ items, they should be sorted by SKU.