Documentation – Splio Sync extension for Magento 2 / Adobe Commerce

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.

You can follow the procedure written here: https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/tutorials/extensions.html?lang=en

1. Place an order for the extension through the Magento marketplace.
2. Make sure that the repo.magento.com repository exists in your composer.json file:

   "repositories": [
       {
           "type": "composer",
           "url": "https://repo.magento.com/"
       }
   ]

3. Update your Magento composer.json with the following lines in require and repositories sections:

   "require": {
       "home-made-io/splio-sync-m2": "^1.9.4"
   }

4. Enter your authentication keys. Your public key is your username; your private key is your password.
5. Wait for Composer to finish updating your project dependencies and make sure that there aren’t any errors:

   Updating dependencies (including require-dev)
   Package operations: 1 install, 0 updates, 0 removals
     - Installing home-made-io/splio-sync-m2 (1.9.4): Downloading (100%)
   Writing lock file
   Generating autoload files

6. To verify that the extension installed properly, run the following command:

   bin/magento module:status HMio_SplioSync

7. Enable the extension and clear static view files:

   $ bin/magento module:enable HMio_SplioSync --clear-static-content

   You should see the following output:

   The following modules have been enabled:
   - HMio_SplioSync
   
   To make sure that the enabled modules are properly registered, run 'setup:upgrade'.
   Cache cleared successfully.
   Generated classes cleared successfully. Please run the 'setup:di:compile' command to generate classes.
   Generated static view files cleared successfully.

8. Register the extension:

   $ bin/magento module:status HMio_SplioSync

9. Recompile your project: In Production mode, you may receive a message to “Please rerun Magento compile command”. The application does not prompt you to run the compile command in Developer mode.

   $ bin/magento setup:di:compile

10. Verify that the extension is enabled:

    $ bin/magento module:status HMio_SplioSync

    You should see output verifying that the extension is no longer disabled:

    Module is enabled

11. Clean the cache:

    $ bin/magento cache:clean

12. Disable maintenance mode:

    $ bin/magento maintenance:disable

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
$ 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.

First, you need to set the API key of your Splio universe.

To find it or create one, please go to your Splio backoffice, go to the menu « Users » below your username at the top-right of your screen, and go to the « API users » tab. More info here: Splio admin interface.

For security reason, it’s recommanded to create a new API user for the synchronization with Magento 2 / Adobe Commerce, even if you have some users already defined.

Fill a meaningful login (for example « splio_sync_m2 »), and copy the new key in the extension configuration in Magento 2 / Adobe Commerce, in the menu Stores > Configuration > Splio Sync > API > API key.

After setting the API key, please test the configuration with the button visible in same configuration section.

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.

When you are done defining the Splio universes API keys in the extension configuration, you can install the custom fields defined by the extension. These custom fields will store in Splio various informations about your contacts, their orders, carts and credit memos, and your catalog.

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 complete list of these custom fields can be found in the « Reference manual » part of this documentation.

For now, only the extension-defined custom fields are supported. A new version of the extension is in development to ease the integration and the support of more custom fields for your specific needs. It will require nonetheless the installation of a custom extension, of which an example will be provided by us when buying the extension.

Feel free to contact us 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 who are also newsletter subscribers in Magento
• Text message optins: You can choose the list gathering all you customers who accepted text message communication
• 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, 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 several hours, please use these buttons with caution.

You can choose to synchronize or not passed closed orders in this initialization step.

In Magento 2 / Adobe Commerce, closed orders are orders which have been completly refunded.

It can be useful if you want to have a more accurate vision of your orders on Splio. But it slows down your initialization, as the extension needs to create a ticket for the order and a ticket for each credit memo linked to it.

Also, if you use Splio Loyalty program, you may want to know that the loyalty program of Splio doesn’t use orders older than its beginning date to calculate the points assigned to each customer. So it may be useless to synchronize all your history of closed orders.

Obviously, after this initilization step, when a new order is refunded and closed in Magento 2 / Adobe Commerce, the order and the credit memo will be synchronized in Splio. THe previous paragraph only applies to the initialization step.

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 > Synced contacts, 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.

In case of an update of the email address by the customer in Magento 2 / Adobe Commerce, and if email addresses are used as identifier field for customers, a specific error occured, as Splio does not allow this update of the identifier field for a specific contact. To handle it manually, you can choose to remove the matching of this specific contact, and relaunch the synchronization job, for syncinc the customer in a new contact in Splio.

Into the menu System > Splio > Synced abandoned carts, 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 > Synced orders, a grid displays the list of the orders already synchronized with Splio.

Into the menu System > Splio > Synced credit memos, a grid displays the list of the credit memos already synchronized with Splio.

Into the menu System > Splio > Synced products, 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, downloadable and virtual products. 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.

A configuration field allows you to remove shipping fees from grand total, allowing you to not assign loyalty points on shipping fees.

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.

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.

The Splio Loyalty extension allows to integrate your Splio loyalty program in your Magento 2 / Adobe Commerce website.

To know more about this extension, please refer to the specific documentation available here.

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

In Splio, abandoned cards and orders are the same entity, distinct only by the « completed » flag.

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.

Description: on your job queue list page in admin menu System > To Splio Job Queue, a job is displayed in error, with the following message:

The contact « old.address@mail.com » has changed its email address (new address: « new.address@mail.com »), but the email address can’t be changed in Splio, as its the identifier field for contacts. Please review this issue with your contact in Splio.

Issue: when you choose to identify your contacts with their email address, you also indicate at Splio that this value can not be modified. But the email address modification by the customer is a basic feature of Magento 2 / Adobe Commerce. So when a customer is synchronized after the update of its email address, a specific error is returned by Splio API, saying that the unique key (email address) can’t be updated.

Solution: first, refer to your Splio contact to know the alternative solutions. You can also choose to handle it manually, by following this procedure :

1. Go to the menu System > Synced Contacts
2. Filter your contacts matching with the old email address of the customer (displayed in the error message
3. Click on the link « Delete the matching »
4. Go to the menu System > To Splio Job Queue
5. Select the synchronization job in error, and choose the action « Replay »

It will create a new contact in Splio with the new email address.

If you use Splio Loyalty program, you may want to know that the new contact will not have the loyalty data of the old contact. Please refer with your Splio contact to know what to do in this situation.