Documentation – Splio Sync extension for Magento 2

Before the extension install, it must be ensured that the Magento environment is properly configured.

Please feel free to check among other topics:

• the cron tasks configuration, required for the proper functioning of the extension.
• the user rights configuration, required for the proper installation of the extension.

1. Place an order for the extension through the Magento marketplace.
2. Open a terminal and run the following command in your Magento directory:

   $ composer config repositories.private-packagist composer https://home-made-io.repo.packagist.com
   $ composer require home-made-io/splio-sync-m2
   $ bin/magento module:enable Silex_NewsletterApi
   $ bin/magento module:enable HMio_SplioSync
   $ bin/magento setup:upgrade
   $ bin/magento cache:clean

3. If Magento runs in production mode, you also must compile and deploy the extension’s static files:

   $ bin/magento setup:di:compile
   $ bin/magento setup:static-content:deploy

1. Place an order for the extension through the Magento marketplace.
2. Go in Magento admin, menu System > Tools > Web Setup Wizard.
3. Click the Extension Manager icon.
4. Within the Magento Marketplace Account section, click on New Purchases, and follow the instructions to install the extension.

The extension installation must be relatively quick (under 5 minutes). If this delay is exceeded, please check the log files.

Open a terminal and run the following commands in your Magento directory:

$ composer remove home-made-io/splio-sync-m2
$ composer remove simonlx/newsletter-api
$ composer config --unset repositories.private-packagist
$ bin/magento setup:upgrade
$ bin/magento setup:di:compile
$ bin/magento setup:static-content:deploy
$ bin/magento cache:clean

The Splio Sync extension for Magento 2 allows the synchronization of the customers, the newsletters subscribers, the abandoned carts and the orders between Magento 2 and Splio.

It synchronizes the following data of these antities :

• customers and newsletter subscribers: ID, email, names, gender, date of birth, phone number, VAT number, creation, last update, last connection and last synchronization date
• billing address of customers: address lines, city, zip code, country, company
• abandoned carts and orders: ID, store, totals in base and locale currency, creation and last update date
• abandoned carts or orders items: SKU, price, ordered quantity, totals in base and locale currency
• products linked to the items: names and descriptions in every locale used in your Magento instance, prices in every currency used in your Magento instance, brand, image, URL, stock level, categories, creation, last update and last synchronization date

The synchronization is done in almost real-time (less than a minute of delay), by adding non invasive synchronization tasks in a dedicated queue, and processed by a cron task.

The Splio Sync extension for Magento 2 also allows the synchronization of customers and newsletter subscribers as requested by GDPR.

Go in Magento admin, menu Stores > Configuration, then in the tab Splio Sync > API.

In the configuration field API key, place the API key displayed in the Splio admin interface.

You can check the proper functioning of the connection to the API by clicking on the button Test connection.

In case of error, feel free to copy the error message displayed and send it to the email address contact@home-made.io.

For more information on the API keys generation on Splio, please look at the dedicated documentation.

It’s possible to configure the extension to synchronize the abandoned carts of different websites on different universes in Splio.

To do so, go in Magento admin, menu Stores > Configuration, then in the tab Splio Sync > API. Then, change the scope to choose the website that must be synchronized in another Splio universe.

It’s a pretty advanced configuration, which has impacts on the synchronization process. Please feel free to talk about it at your contact within Splio in the first place.

Splio uses custom fields to save the most data possible on your contacts.

The installation is done by clicking on the button Install the custom fields in Magento admin, menu Stores > Configuration, then in the tab Splio Sync > API.

In case of multi-universes configuration, the custom fields will be created automatically on each of the universe configured. If an universe is added in the configuration during the lifetime of the website, it’s necessary to rerun the custom fields installation the same way.

The installation through the button does not delete the custom fields already existing, nor does it create duplicates. You can click again on the button without fear of impacts in the data existing in Splio.

The extension offers a list of custom fields already made. As for now, it’s not possible to change it without the intervention of a third party, who has access to the code and the database of Magento 2, through the inclusion of the extension override.

Here is the complete list of custom fields created by the extension:

• For the contacts: Magento ID, prefix, gender, VAT number, date of birth, zip code, city, country, et company of the default billing address, activation status, Magento store identifier, creation, last update, last connection and last synchronization dates
• For the products: Splio ID of the parent product, name and description in each locale used, URL, price in each currency used, stock level, creation, last update and last synchronization dates
• For the orders and carts: Locale currency, totals in the locale currency, last update
• For the oarders and carts items: Locale currency, totals in the locale currency

Feel free to consult your contact within Splio to obtain information about the development of the modification system of customs fields.

You can choose from the configuration panel in which Splio lists your contacts will be synchronized :

• Email optins: You can choose the list gathering all you customers which are also newsletter subscribers in Magento
• All contacts: You can choose to synchronize all your Magento 2 customers in a specific lists in Splio

Warning: if you have several Splio universes configured for a you Magento 2 websites, please be sure to configure the lists accordingly.

Two last structuring choices are to be made before the launch of the first synchronization.

For the products and the contacts, the extension allows users to choose which will be the attribute identifying the entity in Splio, among the list of attributes existing in the Magento 2 website.

For the products, the favored choices are the SKU and the Magento ID. For the contacts, the email address or the Magento ID. Nonetheless, any other attribute can be used.

If none of the favored attributes suit your context, here is the important points to take into account for choosing the identifier attribute

• it must be filled for all products or customers
• it must be unique for each product or customer
• it must be defined globally, so no overridden at website / store scope
• it must be saved as a text or as an option of a list

Feel free to consult your contact within Splio to define what is the best choice for you.

Once the synchronization is launched, it’s strongly discouraged to change the identifier attribute. The configuration fields are disabled once the synchronization is launched.

Splio allows users to identify contacts with the email address, the phone number or any custom fields defined in the universe.

The phone number is rarely filled out within an ecommerce website. So the extension handles three hypotheses regarding the contacts’ identification

• the contacts are identified in Splio by their email address: The email address is sent at Splio, being a default field.
• the contacts are identified in Splio by their Magento ID: A custom field called m2_customer_id synchronizes the Magento ID of the customer. Besides, this custom field is filled out whatever the identifier attribute.
• the contacts are identified in Splio by other data existing in Magento: it can be an external ERP ID saved in Magento, a VAT number, etc… In this case, it is mandatory to create a custom field in Splio, then to save within the configuration the ID and the name of the custom field, both of them being mandatory to the synchronization. To do so, go into Magento admin, menu Stores > Configuration, then in the tab Splio Sync > Contacts, and fill the configuration fields as such.

Before configuring the extension to synchronize the abandoned carts, you must create the store which will receive the carts within Splio.

Go in Splio, in the menu Data > Sales data, then in the tab Stores, and create one or more stores matching the stores in the Magento website.

The Splio Sync extension allows synchronizing the abandoned carts in a Splio store depending on the website or the store view on which it has been made. So you can create as many stores in Splio as there are store views in Magento, or only one store containing all abandoned carts existing in your Magento instance.

Once the stores are created in Splio, you can fill out their external ID in the configuration field of the Splio Sync extension.

Go in Magento admin, menu Stores > Configuration, then in the tab Splio Sync > Abandoned carts.

In the configuration field called Splio store external ID, fill out the external ID of the Splio store newly created.

By modifying the scope of the configuration, you can change the external ID of the Splio by website or store view.

You can choose which states orders are synchronized with Splio.

By default, only orders in « processing » states are synchronized.

After the configuration step, you can launch the synchronization.

To do so, go into Magento admin, menu Stores > Configuration, then in the tab Splio Sync > Job Queue, and change the value of the configuration field called Enable sync between Splio and Magento.

After that, for each entity synchronizable (at the time, only the abandoned carts), go in the matching tab, and change the value of the configuration field called Enable export.

Go into Magento admin, menu Stores > Configuration, then in the tab Splio Sync > API.

In the fieldset « Initialization » you’ll find 3 buttons to synchronize all existing data in Splio.

Warning: This operation can slow down the speed of the others entities during a few moments.

Into the menu System > Splio, several pages display information on the smooth running of the synchronization of the different entities.

Into the menu System > Splio > To Splio Job Queue, a grid displays the list of the jobs to be done to Splio, with their status, creation date and a potential error message. 

The jobs can be in one of the following statuses:

• pending
• running
• in error
• skipped: the entity’s data indicates that it must not be synchronized
• finished

The jobs finished or skipped are automatically deleted after their processing.

In case of error, the synchronization process try to rerun the job 4 times, before giving up. The jobs definitively in error stay visible in the grid, with the error message matching.

Into the menu System > Splio > Contacts synchronized, a grid displays the list of the contacts synchronized with Splio, a contact being either a customer or a NL subscriber, or both obviously. It includes the customers / subscribers deleted in Magento 2.

Into the menu System > Splio > Abandoned carts synchronized, a grid displays the list of the abandoned carts already synchronized with Splio, including those which have been deleted since (because they were converted as orders, or deleted by the customer).

Into the menu System > Splio > Orders synchronized, a grid displays the list of the orders already synchronized with Splio.

Into the menu System > Splio > Products synchronized, a grid displays the list of the products synchronized with Splio.

In Magento, products can be affected to several websites, thus synchronized with several universes in Splio. The column Scope allows to determine with which it has been synchronized, and with which identifier.

The extension offers two pages for tracking the smooth running of the synchronization into the menu System > Splio, Logs and API calls logs.

The first page displays information of the running of the synchronization of the different entities. The second one displays the calls made to the Splio API during the synchronization.

Authentication calls to the Splio API are never logged, for security purposes.

Those are primarily technical data, but which are very useful during errors resolution.

Nonetheless, you can choose to disable a part of logs (the least critical) in order to avoid populating the matching table in your database needlessly.

By default, logs are deleted after 7 days, and duplicated in a dedicated log file. The configuration allows modification of these behaviors nonetheless.

In case of error, feel free to send us the information contained in the matching tables, to ease the resolution of the issue.

The extension allows defining a delay before considering a cart as abandoned.

By default, this delay is valued at 36 hours.

The extension synchronizes only simple products (at the moment). If one of the products synchronized are a variation of a configurable product, or a part of a grouped product, the ID of the parent product will be saved in the custom field m2_parent_id, created by the extension.

The module send in Splio the totals in base currency in Splio. Meaning that the locale currency totals are send as custom fields, for the cart and its items.

As for now, custom fields of carts items are not displayed in Splio admin UX, but rest assured that the totals are also sent in locale currency for carts items.

When a cart is transformed in an order, deleted by the customer, or considered as inactive by Magento, the extension synchronizes its deletion in Splio, if the cart was previously synchronized.

When an order is synchronized with Splio, if the matching cart in M2 was already synchronized with Splio, it will be deleted first, as the order ID is different of the previous cart ID.

In compliance with GDPR, when a subscriber unsubscribe from you newsletter, if the contact list are correctly configured, the extension synchronizes its removal from the email optin contacts in Splio.

If the then-subscriber was only in the list configured in Magento 2 as the list gathering all email optin contacts, it will be removed from this list nonetheless, leaving it in no list in Splio.

If the then-subscriber was not linked to a customer, its unsubscription will be synced as a deletion in Splio.

If the module is configured to use a identifier attribute other than the email, and if the subscriber is not linked to a customer, and if it was not already synced with the module, there’s no way the module can know which contact it has to remove from the email optin list.

In compliance with GDPR, when a customer deletes its account, the extension synchronizes its deletion from the email optin contacts in Splio.

As for now, the deletion will only be effective if the customer was created by the module in the first place. This restriction will be removed in the next release of the module.

The extension use the API given by Splio. The names of the fields below refers to fields expected by the API. See here for more information.

Here is the list of the custom fields used by the addon for customers / contacts

Here is the list of the custom fields used by the addon for products

Here is the list of the custom fields used by the addon for abandoned carts / tickets.

Here is the list of the custom fields used by the addon for abandoned carts items.

If the module is configured to use a identifier attribute other than the email, if a newsletter subscriber is saved, it only ill be synchronized if it’s linked to a customer with the identifier attribute filled.