If you are selling B2B and require your customers to enter a VAT number, please activate this by going to the “System Configurations” -> “Customer Configuration” and then Enable: "Show VAT Number on Frontend” or set “Show Tax/VAT Number” to either Optional or Required. (See examples below).
If you are using Coupon codes on your webshop, please enable it in the Swiipe Settings. (See below)
If you wish to enable Google Autocomplete to your Swiipe checkout, make sure you have a Google API Key. If you do not have a Google API Key use this guide to aquire one: Google API guide
Go to “Swiipe settings” select “yes” to Enable Google Autocomplete and insert your Google API Key underneath.
Click on “Save Configuration”.
If you wish to add HTML-customs sections that are not already visible in the Swiipe checkout, you can simply navigate to “Swiipe Settings” -> “Custom Sections” and provide a selector for your section and choose where it should be displayed. Click on “Add Section” and “Save Configuration”. Remember that the HTML of your custom sections needs to be on the checkout page, for this to work.
(1) If you have local pickup points you will need to add the pickup point in the section shown below. This will ensure that your customers' addresses are not being linked to your pickup point, when they are logged in with Swiipe.
(2) If you have delivery plugins which are not currently supported by our plugin, you will need to enter the input values of the delivery method(s). This will ensure that your customers' addreses are not being linked with invalid delivery pickup points, when they are logged in with Swiipe.
In the above example this webshop has used Magento's native "Flatrate" delivery method as their local pickup point solution. In this case, if your customer is logged in with Swiipe and have an delivery address saved, our plugin would recognize the flatrate delivery method as a "deliver at home" method. It would then try to match the delivery method with the customer's address and therefore show it as a delivery option.
To ensure our plugin does not do this, the plugin needs to know not to match it.
As shown above, we can enter the value of the button (example 1 - shown below) for that specific delivery method. If needed, press the "Add" button to add more exceptions.
The plugin also recognizes wildcards, which means that if there are multiple pickup points that needs to be ignored, you can use the asterix (*) at the end of the line, to match all similar methods (example 2 - shown below).
If there are multiple local pickup points and they are all added by the Flatrate delivery method, they could have the following values:
In this case, you would be able to use the asterix (*) to match both (Example: flatrate*).