How to install and configure EAS application on the Magento 2 store?

This article describes how to install and configure EAS application on the Magento 2 store.

Extension installation and setup

Before proceeding one need to identify method of handling taxes by EAS solution. 

EAS application supports 2 options. Standard and Full.

Tax handling mode Description
Standard

In this mode taxes are calculated by Magento 2 tax engine. EAS application processes paid orders only  and transfer data to EAS Dashboard.
This mode to be used when:
- One page checkout application used
- EAS application not able to inject into checkout process by unknow reason
- There are applications that changing address, cart content and/or prices on the "fly"
- Checkout process not finishing properly (new paid order not created)
- Most of orders amount delivered to EU is less than 150EU

Notice that Magento2 tax engine is not able to determine IOSS threshold, taxes will calculated for all orders IOSS and non IOSS.

Full

In this mode taxes are calculated by EAS solution and fully controlled by EAS. 
EAS application injects into the checkout process after customer fills delivery address, EAS application sends cart data to the EAS tax engine and update cart with proper calculated taxes. After, customer forwarded to the payment step.
Full mode is limited in use, because there are lot of Magento applications that manipulates checkout data on the "fly" and EAS application not able to handle these changes.

 

Before installation of the Extension is performed, one should backup internal Magento tax settings and deactivate other EU VAT related Extensions.

Backup of system and products settings before the Extension installation

Proper backup of your existing products setting is essential for ensuring safe removal of the Extension and safety of your commercial data. We recommend that procedures described in this section are to be repeated also after the Extension installation as part of quality assurance and data safety internal procedures. Export process is fully described on https://docs.magento.com/user-guide/system/data-export.html

The first step is to back up the system, media, and the database. Go to “System” → “Backups” to perform required backups (follow system requests while making backups).

Proper backup will enable full rollback if required.

As second step the merchandise data shall undergo backup, for which the following steps shall be taken:

  1. Choose the “System → Data transfer → Export” left menu option in the store administrators’ dashboard and then press the “Export” button.
  2. Select Products in the Entity Type drop-down control.
  3. Apply filters if needed.
  4. Scroll down to bottom of the page.

5. Export job will be scheduled, and you’ll receive notification message.

6. Your CSV file will appear in the File section.

7. Choose newly created file, in the column “Action” use “Download” in the “Select” control and save exported file to your desired location.

 Installation from Magento marketplace 

The Extension is available for download from the Magento marketplace:

https://marketplace.magento.com/easproject-eucompliance.html

Please, refer to the Magento extension installation documents to install the Extension:

https://experienceleague.adobe.com/en/docs/commerce-operations/installation-guide/tutorials/extensions

Extension initial configuration

Step 1. General EAS EU compliance Extension view

Upon installing the Extension, the “EAS EU compliance” settings page will be available in the Administrators portal of Magento store in Stores → Configuration → EAS PROJECT EXTENTIONS →  EAS EU compliance tab.

EAS EU compliance Extension setting page have 4 sections:

  • General
  • Credentials
  • Attributes
  • Advanced

Step 2. Connection settings

Input the following connection point for connection to EAS system API (item 1 above) in the Credentials section: https://manager.easproject.com/api. Sign up with EAS Project to obtain authorization keys (items 2,3) via the EAS self-registration system: https://easproject.com/reg

If you already registered, then obtain authorization keys in Merchant Dashboard (see EAS Dashboard

In the General section select “Yes” in the “Enable this solution box” 

Press “Save Config” button to save changes.

If wrong credentials are input Extension won’t activate and an error message will be displayed.

Step 3. Setting tax handling mode

If one chosen to use Standard mode, then need to set to Yes option "Standard solution"

Press “Save Config” button to save changes.

When finished, please configure your Magento tax engine to use proper VAT rates for EU sales. Follow this guide Adding EU VAT rates to Magento2 installation

Step 4. Assigning delivery methods

Delivery methods are assigned after the Extension is installed. The whole list of available shipping methods displayed in the General section of the Extension.

In the “Shipping methods by post” box choose all shipping methods that are to be considered as “postal” by clicking on them (chosen postal methods will be highlighted in blue color).

To exclude delivery method from “postal” just click once again on the selected Delivery method so that background color should be changed to white.

All other shipping methods (that are not included in the list of postal delivery methods) are considered as “courier” delivery methods.

Always press “Save Config” at the right upper corner of the page after any changes on the Extension set-up page.

Step 5. Multi Warehouse source selection option

In the same General sub-section it is possible to enable or disable multi source handling option for automatic warehouse selection (see Multisource handling)

In case it has to be Disabled, select “No” in Enable MSI field.

Alternatively, when multi source solution has to be enabled, select “Yes” in the ”Enable MSI” field.

Field MSI selection algorithm should be filled in accordance with the actually used source selection algorithm. Please, refer to Warehouse rules application for detailed explanation.

 

Step 6. Mapping of merchandise additional attributes

Straight after the Extension installation, the EAS system will create additional attributes for Merchant’s products.

 The Merchant shall ensure mapping of existing attributes to additional attributes created by the Extension. Mapping procedures depend on the number of merchandise attributes existing in the Merchant’s Magento E-shop setting 

The initial settings of EAS EU compliance system special attributes are presented in the Figure below.

The merchant shall analyze existing merchandise attributes that are present in the Merchant’s store to identify if currently existing attributes already contain the data that is needed for the operation of the EAS system 

 Identification and analysis start by checking the existing attributes. Go to the Stores → Attributes → Products menu option

All existing attributes are displayed in table view. Slugs for EAS system created attributes always start with the “eas_” prefix and are identified in the “Attribute code” column.

In the example Figure below all EAS system attributes are circled in red (5 attributes: “Act as disclosed agent”, “HSCODE”, , “Seller registration country”, “Warehouse country”).

Attribute analysis shall be made by the authorized and fully capable E-store administrator.

Analysis of the existing attributes is provided in the table below:

EAS attribute

Merchant preexisting attribute

Reason for matching

Act as (disclosed) Agent

No matching attributes

 

HSCODE

Harmonized system code

Both attributes are populated by the same data – customs nomenclature code (HS6+ code)

Reduced VAT for TBE

No matching attributes

 

Seller registration country

No matching attributes

 

Warehouse country

No matching attributes

 

Further actions based on the performed analysis are as follows:

  • Assigned to EAS system attribute “HSCODE” the Merchant attribute “Harmonized system code”
  • No assignment for the following EAS system attributes is to be done: “Act as disclosed agent”, “Reduced VAT for TBE” and “Seller registration country” and the attributes created by the EAS system will be used.

Mapping is performed in the respective section or EAS EU compliance Extension settings view. Compare to the settings shown at the beginning of step 5.

Press the “Save Config” button after mapping is complete!

The final step in the mapping procedure involves removal of EAS attributes that were created by the Extension but mapped to preexisting Merchant attributes. In our example, it is the following attributes that needed to be removed: “HSCODE”.

Deletion is done in the product attribute view. Go to the Stores → Attributes → Product menu option in the main view (see figure below), choose the attribute (“HSCODE” in the example) and press “Delete Attribute” in the opened windows to remove the attribute.

Confirm deletion by pressing Ok on confirmation window.

Step 7. Enabling of shipping to the EU countries

Proceed to Stores → Configuration and look up in General tab for 1st parameter – Country Options. Add either the whole Europe by clicking at “Use system value” box nearby European Union Countries list  or all individual European countries where you deliver to. EAS solution will be operational in all 27 countries of the EU. Make sure that all other regions where you deliver your products are displayed in Allow Countries list. In Figure below, then “Use system value” box is marked, all possible countries in the list are selected.

Step 8. Ensuring of existing of EU compliance tax settings

Standard mode handling taxes

If one chosen Standard mode for handling taxes on the Step 3, then you need to ensure that tax rates and rules for EU countries are properly setup. Please follow the article How to add VAT rates in Magento2 installation? It is assumed that your store not configured to collect taxes for EU countries at all. If you have configured taxes for some EU countries, please remove them as described below.

Full mode handling taxes

If the Merchant is not sure about the actions at this stage Merchant’s operator shall get in touch with EAS support team.

Current tax rate should be exported before any changes to tax setting in your administrative Magento dashboard are made. To perform export of tax rates.

  1. In your administrative view go to “Stores” → “Tax Zones and Rates”. Find “Export” button in the upper right corner, chose CSV or Excel in the fold out menu to the right of the button and press “Export” button.
  2. Save CSV/Excel file (to enable easy reinstall) to the nominated location (see Figure  below)

Deactivate any third-party Extensions that enable the calculation of EU taxes in your “Extension” options. Make sure to save any information /settings required for the installation/activation of these Extensions.

Go to Stores → Tax Rules left menu option and remove EU tax rules from the list, by selecting rule to be deleted and pressing button “Delete Rule” in opened window.

Any Non-EU country tax settings (for countries where the deliveries are made to) should be left in the list, while any tax settings for EU countries should be deleted manually 

Export the settings into the CSV file again (in case you need to upload only non-EU settings if something goes wrong, and all the non-EU settings need to be reinstalled separately). Use procedure described above and save CSV/Excel file separately from the file containing the full set of tax rates 

 

References

Multisource handling

EAS Magneto extension supports multisource handling, provided that the Merchant follows rules set in Warehouse country attribute assignment handling with automatic Magento multisource support of this manual. Stock configuration does not affect choice of source for filling “Warehouse country” attribute.  

There may be three situations that are implemented in a particular Magento store setting:

  1. Merchant supports multisource handling in the Magento environment and manages stocks in the Magento store see Warehouse country attribute assignment handling with automatic Magento multisource support

The consequences of this scheme application are as follows:

  • Merchant, as usual, manages sources and stocks to individual stores/views and handles the stocks.
  • Merchant sets fulfillment priority algorithms as usual (distance priority or source priority), if needed applying third party solutions and extensions.
  • Merchant does not fill the “Warehouse country” special attribute, EAS will use country warehouse of the Source that is chosen by Magento based on Merchant set priority algorithm.
  • EAS Magento extension will limit the Source during shipment to the Source chosen during the sale, i.e., even if there are more than one source assigned to the store/view only one will be available for the shipment.

Make sure that you set “Enable MSI” to ON in the EAS EU compliance setting (see  Step 5 of configuration process  for this scheme to be enabled)

2. Merchant supports multisource handling but does not use Magento environment for stock handling

The consequences of this scheme application are as follows:

  • Merchant keeps only one source (usually it is the default source set initially during the store installation).
  • No fulfillment priory is set.
  • Merchant fills the “Warehouse country” special attribute, EAS will use data from this attribute for tax determination. If EAS “Warehouse country” attribute is not filled, EAS will use country data from the Magento default source (or the only available source).
  • EAS Magento extension will limit the source during shipment to the source chosen during the sale.

Merchant should make sure that the default source country attribute is set to the real warehouse country. EAS Warehouse attribute has priority over Magento default source attribute.

3, Merchant does not support multisource handling

The consequences of this scheme application are as follows:

  • Merchant keeps only one source (usually it is the default source set initially during the store installation).
  • No fulfillment priory is set.
  • Merchant does not fill the “Warehouse country” special attribute (or uses the same data as in the Magento default source). EAS will use data from the Magento default source (or the only available source) for tax determination.
  • EAS Magento extension will limit the source during shipment to the source chosen during the sale.

Merchant should make sure that the default source country attribute is set to the real warehouse country. EAS Warehouse attribute might be left empty or can contain the same data as Magento default source attribute.

 

Warehouse country attribute assignment handling with automatic Magento multisource support

Logic described in this sub section is applied when Merchants use Magento environment for handling of merchandise location and apply multisource approach.

EAS Magento extension supports all possible operational situations with handling of stocks in Magento. It is decisively not described in this document how sources and stock assignments work in Magento since the goal of this manual is to describe EAS Magento extension behavior in existing and working settings. So irrespective of the existing stock/sources configuration EAS Magento extension will work in the described manner.

The schema with multisource support configured in the Magento environment by the Merchant will not require any changes to the existing multisource settings on the Magento level. But certain settings are still required for the EAS Magento extension. To ensure that EAS Magento extension supports multiple source option, the Merchant must set up EAS Magento extension for the multisource use for which “Enable MSI” option is to be set “Yes“ in the configuration section of EAS Magento extension.

EAS Magento extension also supports priority shipping algorithms but in case when EAS Magento extension is used such algorithms are applied during the purchase and not at the moment of the shipment decision (as the standard Magento process goes). Thus, to make sure that shipping is performed in accordance with the existing algorithm, the Merchant should choose the proper MSI algorithm (“Source priority” algorithm is chosen in the example below) – it should be the algorithm generally used by the Merchant for the operations. At the moment of the shipment the Merchant will not any longer be able to use the algorithm for choosing the warehouse for an actual fulfillment.

The Merchant will automatically be limited in the choice of warehouse at the moment of shipment – only the warehouse which was chosen by the shipping priority algorithm set in the EAS Magento extension at the moment of the sale will be allowed for the fulfillment. Setting the wrong algorithm in the EAS Magento extension may lead to items being shipped from less favorable warehouse.

Having enabled and set the MSI option and shipping algorithm, the Merchant does not need to set EAS “Warehouse country” attribute, all required country warehouse information for tax determination will be chosen from the existing configuration information on Merchant’s warehouses (see Figure below).

An example of multisource warehouse management is provided further. As selected in the Figure 20, MSI algorithm used for stock selection is set to Source Priority.

3 products with 2 different WHs have been selected and purchased (Figure below) in the store.

The following country fulfillment information is sent to the EAS backend. The choice of the fulfillment country is made by EAS Magento extension based on the priority algorithm set in the EAS Magento extension configuration page and items availability in warehouses (as such “cap de france” was sold from the French warehouse since 0 items are available in Germany).

Product name

Warehouse country

cap de france

France

Vneck Tshirt

Germany

Polo

Germany

Based on the warehouse country information it is clear that there will be 2 separate shipments created in the Magento shipment system – one from France and at least one from Germany.

 

To fulfill the shipment the Merchant’s operator performs the usual actions, so in the administrative menu the following options are chosen: Sales → Orders, the order is chosen from the list.

 

Ship button is pressed (Figure below).

For the first shipment EAS Magento extension has limited the shipment warehouse to the German warehouse (Figure below) – the ONE initially chosen by the extension.

Shipment information on the conclusion of the first shipment is presented in the Figure below items are being shipped from the warehouse in Germany.

Second shipment initiated in the same usual way by applying standard Magento instruments (Figure below).

For the second shipment EAS Magento extension has limited the shipment warehouse to the French warehouse  – the ONE initially chosen by the extension.

Shipment information on the conclusion of the shipment is presented in the Figure  item is being shipped from the warehouse in France.

 

As expected, 2 shipments have been created from 2 different warehouses  to fulfil the order. Shipment information coincides with tax determination data collected by EAS backend (see Table with products and warehouses above).

Additionally, EAS Magento extension provides notification on the shipment data to the Merchant to visualize basis for the tax determination decisions (see Figure above).