User Manual Part I - eConnect for M3 - v20.3.0

eConnect banner

Table of contents

GENERAL INFORMATION

System Overview

LeanSwift eConnect for Infor M3 provides a powerful, seamless integration between Magento and Infor M3 ERP. The product consists of a base Magento extension that extends standard Magento functionality and offers several transactions to ensure your eCommerce websites contain up-to-date information from your M3 ERP. There exist a number of optional add-on extensions too for additional functionality

LeanSwift eConnect for Infor M3 is available for Magento Open Source and Magento Commerce and for Infor M3 version 7.x and above. It is also compatible with multi-tenant cloud editions of Infor M3 (Cloudsuite).

LeanSwift eConnect for Infor M3 employs a layered architecture to allow flexibility in supporting different versions of Magento and Infor M3 and to allow independent upgrades.

Go to Top

Architecture with Magento API

eConnect Architecture

Go to Top

eConnect-base v5.0.0

Go to Top

New in this version

LeanSwift AMQP Connection

Provided new amqp Connection type Configuration for handling the eConnect related BOD in separate rabbitmq. After saving the configurations the command php bin/magento setup:leanswift-amqp needs to be run. The Configuration are in global scope and has the following fields, Host, Port, User, Password and VirtualHost.

AMQP Connection

Enterprise connector Removal

BOD information send to eConnect REST API directly. Instead of sending to rabbitmq eliminating the Enterprise Connector.

Additional Entity Attribute Mapping

The feature allows administrator to configure API based on the entity type. API is triggered when corresponding BOD received.This allows removal of Custom BOD for the Product, Customer and Order.

To Configure or view APIs go to Leanswift > eConnect-ION > Additional Entity Attribute Mapping. Configured API details are displayed in tabular format with details such as ID, Program, Transaction, Entity, Query, Comment and Action. ‘Select’ and ‘Edit’ are two actions that can be performed with the configured APIs.

Additional Entity Attribute Mapping

When a new Api needs to be configured, click on Add Program

Attribute Mapping Configuration

Program

The API program name needs to entered here.

Transaction

The transaction (such as select, get or add )specific to the program is configured in this field.

Entity

This dropdown is to select if the API entity is Customer, Product or Other.

Query

Query text field is applicable only for ExportMI (Select Transaction).

Comment

Any comments or important notes can be mentioned in Comments text field such as ‘System generated program. Delete action was restricted’.

Attribute Mapping Configuration2

Input Rows

The API input needs to be configured here. The Input includes ‘Magento Field’ which is a dropdown, Corresponding ‘M3 field’, ‘Default’ value for the api field, Action (with bin symbol ) to delete the configured field if required.

Output Rows

The API output needs to be configured here. The Output includes ‘Magento Field’ which is a dropdown, Corresponding ‘M3 field’, ‘Default’ value for the api field if the output field is empty, Action (with bin symbol ) to delete the configured field if required.

NOTE

Stock and price Custom BOD will work like before.

Go to Top

Transactions

eConnect 20.3.0 includes the following set of standard transactions like its previous versions:

These transactions can, if necessary, be modified and new transactions can be added to fulfill specific customer requirements.

Go to Top

User Interface

During setup, the Magento Admin panel is used to configure which transactions should be used and how they should function.There is also additional background configuration within the Connector.

Validated versions

Go to Top

Points of Contact

This document and the software it describes are provided by LeanSwift Solutions Inc. For additional information regarding support, licensing, functionality etc. please contact LeanSwift Solutions Inc. via contact form at http://www.leanswift.com or email info@leanswift.com

Go to Top

Organization of the Manual

This manual is not intended to cover any standard Magento functionality or user experience. The Magento user experience is customized and slightly different in each eCommerce implementation, though the general workflow is similar.

This manual describes the configuration of LeanSwift eConnect for Infor M3 with ION. For a detailed description of the standard transactions, please refer to Part II of the User Manual - LeanSwift eConnect for M3 20.3.0.

This manual includes the configuration required within LeanSwift eConnect Magento extension via the Magento Admin panel.

Go to Top

Acronyms and Abbreviations

CONFIGURATION

Magento Configuration

To support the use of LeanSwift eConnect for Infor M3, configuration is required within Magento, in LeanSwift eLink, in ION and also within the M3 ERP system. This section covers the configuration within Magento.

Log in to Magento Admin Panel using the URL provided to you and the applicable user credentials.

Magento

Go to Top

System Menu

Configuration

Configuration

Also pay attention to which configuration scope you're working under.

Configuration-scope

For further information about Configuration scope in Magento, please refer to the following article:

http://www.magentocommerce.com/knowledge-base/entry/understanding-store-scopes

Configuration/LeanSwift

Navigate to the LeanSwift Solutions sub-menu down in the left-hand side configuration menu.

Here, there will be several sections under the LeanSwift sub-menu.

Configuration-scope

Configuration/LeanSwift/eConnect

The eConnect-ION section contains the vast majority of the settings for base eConnect, and the details of each group is covered in the following sections of this document.

The following sections are included in the eConnect configuration:

Configuration-scope

eConnect-base

The eConnect-base section contains settings to connect with eLink/ION/M3, some of which were earlier a part of the eConnect-General and Basic data configuration section.

eConnect-base has 2 sections

Configuration-scope

Import History

Whenever an initial load API(EVS002MI/Initiate) call gets triggered, that request and response information will be displayed in this grid. This API triggers the Show BODs. Entity Name can be customer, address, order, shipment, invoice, product, inventory, atp. To trigger the Initial load BOD, we pass Entity Name, From Date, To Date, No. of Actions, Search Query as input and the result will be the Job ID.

import history

Connectivity

The Connectivity section of eConnect-base has the following configurations.

econnect ebase config

Service Configuration

service config

M3 Connection Protocol

Provides a choice for the admin to choose between Leanswift eLink/ION version of eConnect. There are 2 options, Leanswift eLink and ION. eConnect uses the configuration based on the option chosen.

API Service URL

This is the service URL to connect to Infor ION

E-mail

All the errors will be sent to the email configured here

Error email template

Email template chosen based on theme fallback when “Default” option is selected

Debug/log data

This is to log data to check request and response data, specially when developing

Basic Data Configuration (M3 connection protocol - ION)

basicdata config

Company

The default company within M3. Setting can be defined on Default or Store level.

Division

The default division within M3. Setting can be defined on Default or Store level.

Authentication

The Authentication group contains the settings related to the web service authentication using the OAuth2.0 standard that eConnect employs.

This section is configured by LeanSwift during product installation.

Authentication (M3 connection protocol - ION)

ebase authentication

To ensure the security of eConnect, OAuth2.0 is always enabled by default.

The M3 User is the user with which we connect to ION APIs

We have a 'Test connection' button to verify if connection is up.

New in this version

Message Queue Configuration

The Section allows to configure the leanswift AMQP rabbitmq details in environment file. Changes are reflected by running the comand php bin/magento setup:leanswift-amqp.

Host

This is used to give the Host details of rabbitmq.

Port

This is used to give the Port details of rabbitmq.(Default: 5672)

User

This is used to give the User details of rabbitmq.

Password

This is used to give the Password details of rabbitmq.

VirtualHost

This is used to give the Virtual Host details of rabbitmq.(Default: /)

Authentication

Added new feature of allowing administrator to add the .ionapi file and required fields are auto populated.

eConnect M3 Connectivity

Added new System Integration in backend for connecting the eConnect API from M3 installed automatically. Access token retreived after authorizing the application. Retreived token used to configure in M3 API suite.

eConnect-General

The General section contains a number of basic settings that are generic for this instance of eConnect.

econnect general

General Configuration

Enable Config log

This is to log Config data during data feed from consumers

Use M3 order history

This parameter refers to the retrieval of order history from M3 from Magento front-end.

Select "Yes" to retrieve the order history from the ERP system in real-time when the user selects Order History in My Account. This will make order history seamless between Magento and the ERP and any order changes in the back-end ERP will be displayed in Magento instantly.

Select "No" to only use the order history from Magento when the user selects Order History in My Account.

Display Invoice

Set this option to 'Yes' in order to retrieve Invoice history details from M3. Please note that this does not apply to the B2C configuration when a single customer# in M3 is used for all orders.

In this case, the invoice history from Magento is always displayed by default.

Go to Top

eConnect-ION

Basic Data Configuration

The Basic Data Configuration section of the configuration contains a number of key settings needed for the various transactions within LeanSwift eConnect.

basicdata config

Facility

The default facility within M3. Setting can be defined on Default or Store level.

Warehouse

The default facility within M3. Setting can be defined on Default or Store level. This setting is currently used as input to all transactions except the Order Entry.

Price Code

This refers to the Price List within M3 from which the list price/MSRP/Retail price is synchronized for a site. This setting is optional and can be left blank. Also note that if prices for a site should be synchronized, the 'Price' attribute must also be included as part of the mapping within the 'Production Synchronization' setup that's covered later in this manual.

Currency code

Only required if 'Price code' is filled in and is then used to ensure the right price list in M3 is used for price synchronization.

Order Type

The default order type to use for Order creation. This setting can be managed on a Default or Website level.

Document Class

The default document class is Co02. It is the class used while sending Order comments to M3

Go to Top

Shipping Method

This section manages the mapping between the Shipping methods that have been enabled within Magento (_Leanswift > eConnect-ION Configuration > Sales > Shipping Methods) and the Delivery method and term within M3.

shipping method

To add an additional mapping entry, simply press the 'Add' button, and select the Magento Shipping Method value to map

Then, in the right two columns (M3 Delivery Method & M3 Delivery Term) – key in the M3 values to which the Shipping method should be mapped:

Following this, remember to save the configuration by pressing 'Save Config' at the top of the page.

save config

Go to Top

Manual Sync Configuration

Maximum number of records that can be selected at a time for manual sync can be configured here. There are separate configurations to set limit for Product, Customer and Order modules.

manual sync config

There is a maximum limit of 200 beyond which manual sync cannot be done.

Go to Top

Customer General Configuration

general config

This section now contains the key parameters for how to handle customer creation, both for a B2B and a B2C site.

**NOTE! The 'Customer Template ID' field has dual function depending on whether the Customer Registration feature is used or not. For a single site, these features are mutually exclusive in that one is intended for B2B- and the other for B2C use. If ### Create Customer via IMS is set to 'Yes', Customer creation is done via IMS, else the regular econnect-ION workflow is followed. **

Create Customer On Registration

This feature is intended for a B2B setup where new customers are allowed to register themselves on the front-end.

customer general config

If Create Customer On Registration is set to 'Yes', and if Create Customer via IMS is set to 'Yes', the customer template IONCUST will be used to create a new customer number within M3 for each order being placed.

If Create Customer On Registration is set to 'Yes', and if Create Customer via IMS is set to 'No', the customer template mentioned under Customer Template Id will be used to create a new customer number within M3 for each order being placed.

eConnect will remove the Create Customer On Placing Order parameter as this indicates the site being configured is a B2B site where every customer always exists already when an order is place.

When Create Customer On Registration is set to 'Yes', this indicates that as new customers register from the Magento front-end, a customer record is added in Magento – and a customer in a preliminary status (status 10) is created within M3.

A manual process is assumed within M3, where a Customer service/Accounting responsible would review these preliminary customers (credit checks etc.) and if they are approved as a new customer the status in M3 is manually changed to active (20). While the customer status in M3 is preliminary (10), the customer in question can't place an order within Magento (eConnect performs a real-time check against M3 during the checkout process to validate the customer status). Products can be added to cart and the cart saved, but the checkout process can't be completed.

Setting Create Customer On Registration to 'No' disables the registration feature completely, which then in turn enables the Create Customer On Placing Order:

customer general config1

Create Customer On Placing Order

This parameter is intended to be used for B2C sites where a choice needs to be made whether individual customers should exist in M3 for each consumer, or if a single "common" customer should be used for all consumer orders received from Magento.

If Create Customer On Placing Order is set to 'Yes', and if Create Customer via IMS is set to 'Yes', the customer template IONCUST will be used to create a new customer number within M3 for each order being placed.

NOTE: In this case the first order has to be synced twice. During the first sync ERP number is generated, and for the next sync order will be sent to m3

If Create Customer On Placing Order is set to 'Yes', and if Create Customer via IMS is set to 'No', the customer template mentioned under Customer Template Id will be used to create a new customer number within M3 for each order being placed.

If a registered user is signed in, and as such already has a Magento customer# - a verification is always first performed to see whether there's a value on External Customer # or not. If not new customer# will be created in M3.

If Create Customer On Placing Order is set to 'No', then the same Customer template mentioned under Common Customer Id is used for each order created within M3.

customer general config2

Create Customer via IMS

If Create Customer via IMS is set to 'Yes', IMS is used to send customer information via BODs to ION If Create Customer via IMS is set to 'No', the regular ION workflow is enabled. When Create Customer via IMS is set to 'Yes', the prefix mentioned in the field ERP Customer Number Prefix is used when creating new customer in ERP system via IMS

User-defined Fields

User-defined Fields is used when Field Name and Value is to be added to UserArea section in CustomerPartyMaster BOD before sending to ION

Go to Top

Product Addition/ Synchronization

There exists functionality to conveniently map your M3 items to your Magento webshop. _Leanswift > econnect-ION > Configuration > Product Addition/Synchronization In the current version, simple and configurable products are supported using this process, for all other product types, the default Magento process of importing via CSV is in place.

You can control the Product sync in website level by choosing Yes/No option in the Enable field. Each of the features, addition of new items, and syncing of existing can be controlled independently of each other.

Set Enable to Yes to enable this feature.

Apart from this, Addition and Sync can be turned on/off individually.

The Dropdown attributes that need to be synced can be added in the Dropdown attributes field. Multiple values can be selected.

Batch size and Sync from Date features are removed in this version as sync happens instantly unlike in the eLink version which requires a cron to be triggered.

The New product status should be set to No to ensure the products do not appear in the webshop and set to Yes to appear.

'Style SKUs as Configurable Products' can be set to Yes if we want style items and can be set to No to save them as simple items

New in this version

product addition

product addition

Item price

Admin can now choose to sync price between MMSAPR and ODSAPR.

If MMSAPR is chosen, Price available for a product in MMS001 will get updated in product detail page of magento. When ever price is added/updated in MMS001 in M3, Item master BOD gets generated. When an item master bod gets generated, MMS200MI/GetItmPrice gets triggered ( which can be seen in ION.log) and the same gets updated.

If ODSAPR is chosen, Price available for a product in MMS017 will get updated in product detail page of magento. When ever price is added/updated in OIS017 ( For the Price list and currency mapped in Basic Data configuration, provided there is no customer mapped ) in M3, LSPriceList BOD gets generated during which MMS200MI/GetBasePrice API gets triggered and the price gets updated.

Note: If multi-website is enabled, Price can be set to work on website level or global. If Item price is set to different configurations in different website then Price has to be set to website scope. Otherwise Price from the configuration on the last website will be overriden to all websites.

Product attribute mapping

In order to ensure that the solution can deal with the flexibility and complexity of M3, the configuration allows you to specify what values from M3 should be mapped to the attributes which you have defined in magento. A Default field is provided to map a default value to any of the M3 fields.

attribute mapping m3

Product Addition conditions:

As the most common scenario faced is that your M3 instance will contain far more items than you wish to have available in your webshop, eConnect comes with the ability to provide configurable criteria for selecting which items to include from M3.

item addition condition

In Addition to this, we also have the option to choose if it is 'Any/All' of all conditions.

condition true

The main product tables are MITMAS, MITBAL and MITFAC.

Product Synchronization - Item Disabling

Configuration is provided to Disable the products in Magento.

Set yes to Disable the product status and map the required conditions.

item disabling

Product Synchronization - AttributeSet Mapping

Magento uses the concept of attributes sets which allows products with similar features to be grouped and share a common set of attributes. Shoes for example would maybe need different attributes than the rental heavy equipment item. In order to ensure that items are imported and synced to Magento using the correct set of attributes, configuration is provided to assist in defining what M3 values indicate the product attribute set which the item will belong to.

attribute mapping

Similar to category mapping, a feature has been provided to define the behavior for attribute sets which have changed or those which do have a matching M3 value as has been defined.

To enable this feature 'Change AttributeSet for existing products'is set to Yes

Product Synchronization - Category Mapping

When items are imported into Magento, they will need to have at least one product category to which they will be associated with. When this information is available in M3, this can be used to avoid duplication of record maintained.

category mapping

The category mapping is flexible enough to allow for more than one field in M3 to define which category it should belong to in Magento. The first step is to define the order and which fields in M3 will indicate category. The M3 Category source value should be entered in one continuous string.

Once the source is entered, Items get created into magento and the categories are created based on Source.

The first source value acts as a Parent and the rest of the source value forms sub-categories.

Once Category source is defined, any changes can cause abnormality in the behavior of product Addition/sync.In addition, a default category can be used for values which are missing values in the fields which have been defined for category mapping.

Go to Top

Customer Addition/ Synchronization

Customer Addition/Synchronizationcontains all settings related to fetching Customers from M3 and synchronizing Customer data. In this version, the following limitations apply:

Addition

Synchronization

customer addition

Enable

This setting provides the option to enable/disable the Customer Addition/Sync on website level.

Enable Customer sync

This setting provides the option to enable/disable the Customer Sync on website level.

Enable Customer Addition

This setting provides the option to enable/disable the Customer Addition on website level.

Customer Group Id

This setting provides the option to choose the group from which customers from M3 needs to be imported.

New Account Email Notification

This field sends a mail confirmation to the newly added customer when set to yes. The mail will have a 'Confirm Account' option. When clicked on that, user will get redirected to frontend page

Customer Master Mapping

This section allows for mapping of additional Customer related fields within Magento to Customer master fields in M3. The mapping works exactly the same way as for the previous two sections. Customer's Order type, Facility and Division can also be synchronized. When a customer has this data synchronized, this detail gets picked over the basic data while order is getting placed

Customer Address Mapping

This section controls how the Billing and Shipping Address for the customer in Magento is to be created based on the address details in M3.

The mapping is done in the same way as for Shipping methods and Product Sync for example. The Magento address attribute to map is selected from the drop-down list in the 'Magento Attribute' column. The M3 attribute this should be mapped to is then selected from the drop- down list in the 'M3 Attribute' column.

Go to Top

Sales

The 'Sales' section contains three key settings related to the sales order process from Magento to M3.

sales

Enable order comments

If set to 'Yes', this enables sending header-level comments [entered in the last step of the Checkout process] for the entire order to M3.

Allow Item Price

If set to 'Yes', this enables sending Price for the order to M3.

Capture Payment Online

This option set to 'Yes' will during Invoice creation in Magento [as part of the synchronization when the invoice details from M3 are used to create the Magento invoice] also invoke the 'Capture' transaction from Magento for credit card orders. If this option is set to 'No', it's assumed that capture of funds via whatever payment gateway is used within Magento is handled manually via a separate process.

Go to Top

Order Charges

The Order Charges group contains the settings related to how various additional charges within Magento, such as Tax- & Shipping (freight) should be handled by eConnect.

Tax Transfer & Tax Charge code: If Tax Transferis set to 'No', then dynamically the Tax Chargefield is not displayed as it doesn't apply:

order charges

When Tax Transfer is set to 'Yes', the Tax Charge field is visible:

taxcode

The drop-down for Tax Charge code provides dynamic values from M3 to enable an easy selection and reduce the risk for erroneous entry:

taxcode dropdown

Shipping/Freight Fee Charge Type

This setting provides the option to determine whether to in M3 handle the Shipping fee from Magento as a Non-stock item or an order header charge.

There exists an option to enable/disable, with which one can control whether to send the shipping charge to M3 or not,the parameter offers the user a simple selection between the two options:

order charges shipping

Depending on the selection, the following setting is dynamically adjusted. When 'Non-stock item' is selected as in the screen shot above, the user can select Shipping/Freight Fee Item Number in the field below. The selection is also here dynamic against M3 so that it provides the user with a simple drop-down of applicable items from M3.

If 'Charges' is selected, the following field provides selection of 'Shipping/Freight Fee Charge Code', and also in this case the list of available Charge ID's is dynamically retrieved from M3:

Order charges shipping dropdown

Gift Wrap Transfer

The Gift Wrap Transfer parameter controls whether or not to transfer Gift Wrapping related information from Magento. This information includes:

If Gift Wrap Transfer is set to 'No' – no information related to Gift Wrapping will be transferred from Magento to M3.

If Gift Wrap Transfer is set to 'Yes' – all of the above-mentioned information can be transferred (depending on what's been configured and is in use within Magento).

Setting the parameter to 'Yes', will also in this case dynamically open up a number of additional fields on the screen:

gift wrap charges

The Gift Wrap Charge Type parameter controls whether the Gift Wrapping related costs in Magento should be transferred over to M3 as Charges (Order- and/or Line) or Non-stock items.

As in the previous screen shot – if Gift Wrap Charge Type is set to 'Non-stock items' – the user is presented with selecting a non-stock item to use for (i) Order level gift wrapping charges and

(ii) Line level gift wrapping charges. These two non-stock items don't have to be different – they can both use the same M3 non-stock item value.

If instead the Gift Wrap Charge Type parameter is set to 'Charges' – the following two parameters are dynamically adjusted to Gift Wrap Order Charge Code & Gift Wrap Line Charge Code , offering a selection of Order-level and Line-level charge codes in M3 to handle Order-level Gift wrapping costs and Line-level Gift Wrapping costs.

giftwrap charges

Go to Top

Payments

The Payments group contains the configuration related to credit-card integration, payment terms & methods mapping, invoice fees etc.

payments

Re-authorization Amount (Credit Cards)

Single-authorization is used by eConnect, i.e. the credit card authorization created by Magento is transferred over to M3 without the need to re-authorize. This parameter will be removed.

Payment Provider

The mapping within this setup provides the link between Magento Payment Method values and Payment Terms & Payment Method values in M3. In the case of the mapping for the Credit Card Payment Method, the 'M3 Credit Card Provider' value also provides direct input to the order creation process.

Invoice Fee Charge Type

Invoice fees that can be imposed by certain payment providers can via this setting be handled two different ways in M3 – either as a non-stock item or as a [order header] charge.

invoice fee type

The selection made on this parameter will control which of the two values 'Invoice Fee Charge Code' or 'Invoice Fee Charge Item no' in the mapping below that will be used

Invoice Fees

This section is used if any Payment provider imposes some kind of transaction fee that needs to be represented on the order in M3. One example of this is the Swedish payment provider Klarna, that imposes a fee of about 25 SEK on each purchase when their service is used.

The fee corresponding to the value entered in the 'Invoice Fee Amount' column is added to the order either as a header charge or as a non-stock item depending on the previous settings.

In the example here, a fee of $2.00 would be added to each order as a non-stock item when the Credit Card payment option is used.

Go to Top

Price Synchronization

The Price Synchronization settings have been added to provide an option to enable or disable the real-time customer/item specific price call, as well as provide an option to increase site performance when needed.

price sync

Enable

Setting this parameter to 'Yes' enables the Customer special price to be updated in magento when there is a change in M3 price table. Setting to No will not update any changes in magento.

When his setting is turned On, Customer special price is displayed in frontend when the customer places the order.

Enable in Admin

Setting this parameter to 'Yes' enables the Customer special price to be updated in magento when there is a change in M3 price table. Setting to No will not update any changes in magento.

When his setting is turned On, Customer special price is displayed in the backend when customer places the order.

Go to Top

Inventory Synchronization

This setting provides an option for which stock to invoke when stock is updated in M3.

inventory sync

ERP Inventory Attribute Allows admin to choose between On-Hand/Available Inventory/Allocatable Net.

Go to Top

Initial Load/ Import

This feature enables to import the data from M3.

load import

Each of this section has a set of fields that allows to choose date range and conditions for the data to be imported.

import customers

Go to Top

BOD Mapping

BOD mapping

Bod Mapping can be used when we need additional M3 attributes( which are not available in standard BODs ) to save Magento attributes. This option can be given to save the custom attribute or override the existing attribute value with Xpath from BOD

Go to Top

Cron Settings

This section contains the basic setup for how often the LeanSwift specific background (cron) jobs should run. The actual configuration of the job in the screenshot below is not representative of a normal customer installation.

The setup will vary from customer to customer depending on a number of factors such as basic data volumes, ordering processes etc.

This section should always be reviewed within the project, and with the help of the LeanSwift Services team be adjusted to best fit each customer's environment.

Cron Settings

Cron settings for send orders to ERP: Cron expression to send ordes to M3 from eConnect

New in this version

Order API Configuration: Cron expression to intiate Order API’s configured in ‘Additional Entity Attribute Mapping’

Product API Configuration: Cron expression to intiate Product API’s configured in ‘Additional Entity Attribute Mapping’

Customer API Configuration: Cron expression to intiate Customer API’s configured in ‘Additional Entity Attribute Mapping’

Go to Top

Version Info

This last section provides information related to the version of the LeanSwift Magento extension that's installed.

Version Info

Go to Top

Magento Standard Functionality

The ERP connector does not override or impact any other functionality in Magento. Configure Magento using the Magento admin panel as required.

Go to Top

Exit System

Log out from Magento admin using the link at the top right.

Exit System

Go to Top