What advanced settings are available for the RetailVista Magento integration?

The following advanced settings specific to Magento can be specified in the webshop settings:

PaymentTypeCodeRemoveLeader=<value>

This setting ensures that the specified value of this setting is removed from the payment method code, as received from a Magento order message. The problem with some Magento integrations is that the payment method code is too large and contains a long fixed prefix. This setting allows that prefix to be removed, leaving only the relevant part of the payment method code. The payment method code must start with this value.

Example value: PaymentTypeCodeRemoveLeader=buckaroo_magento2_

This removes the text 'buckaroo_magento2_' from a payment method code. For example, if the payment method code is 'buckaroo_magento2_ideal', then after applying this setting, only the code 'ideal' remains. A type of payment will need to be found for this code.

PaymentTypeCode=<value>

This setting ensures that all payments from Magento orders always go to the down payment type with this code. The payment method of Magento itself will no longer be considered.

TransportTypeCode=<value>

This setting ensures that all Magento orders are assigned the transport type with this code as the transport type. As far as is currently known, Magento itself does not provide a field in which the consumer's possible choice is recorded. If it later turns out that this is the case, this documentation will need to be updated.

For now, this is a mandatory setting!

SkipCreatedBeforeDateTime =<value>

This setting ensures that orders (Magento!) created before a certain date and time are always ignored. This can be useful in situations where integration becomes active from a certain date and where old sales orders should not be imported into RetailVista. The format of the date and time is yyyy-MM-dd HH:mm. If the specified date cannot be processed by RetailVista due to an incorrect format, the import will be aborted.