Affiliate Program

Hi,

With the affiliate system in HikaShop, each affiliate of a partner will be linked to that partner. When you edit a customer in HikaShop's backend, you'll have a setting "partner" with the partner user selected, so you can see "which customer belons to which dealer".
Also, with a mass action you can output a list / CSV of the users of a partner with a filter on the column user_partner_id and an action "Display the results" or "export CSV file".

Hi,

Yes, it is possible. You can configure banners in HikaShop to setup links you want to advertise to partners so that they can share their unique link with their customers. This way, the customers will be linked to them automatically.
www.hikashop.com/support/documentation/i...hop-banner-form.html
You can see an example of partner affiliate program page with some banners configured for our own website:
www.hikashop.com/my-account/affiliate-program.html

Hi,

It's possible for users to accumulate points with the user points system:
www.hikashop.com/support/documentation/257-using-points.html
Then, you can configure the "Provide points instead of fees" setting, under the Features tab of the HikaShop configuration for partners to gain points instead of fees.

Hi,

Let me address your questions one by one.

1. Points multiplied by quantity

This is the default behavior. When a customer buys 3 pieces of a product that gives 7 points, the points plugin will give 3 x 7 = 21 points. You don't need to configure anything special for that. If you're not seeing this behavior, make sure the points plugin's "Give points when using some" setting is set to "Give on full price" (which it is in your screenshot).

2. Paying with points (partial or full)

In your "Pay with Points" payment method configuration, you have "Partial payment" set to "No" and "Minimum (percent)" set to 100%. This means the customer must pay the full amount in points or not at all. To allow partial payment (points + money), set "Partial payment" to "Yes" and lower the minimum percentage. For example, setting the minimum to 0% would allow the customer to use whatever points they have and pay the rest with another payment method.

However, there is an important thing to understand: the "Pay with Points" payment method works as a standalone payment method. When partial payment is enabled, the remaining amount after deducting the points value will need to be paid with a second payment method during checkout. The customer would first select "Pay with Points", which deducts what it can, and then a second payment step is presented for the remainder.

3. Exchange rate configuration

Looking at your screenshots, there is an inconsistency in your exchange rates. In the "Pay with Points" payment method, you have 1 point = 0.25 EUR. But in the points plugin, you have 1 EUR = 1 point. This means the customer earns 1 point per EUR spent but each point is only worth 0.25 EUR when redeeming. Make sure this is intentional. If you want points to have a 1:1 value with EUR, set both to the same rate.

Also, you have the product custom field "userpoints" set to 7 for a product priced at 39 EUR. If you're using the custom field to define a fixed point cost for products, this means the product costs 7 points (= 1.75 EUR at your current 0.25 rate). If you want 7 points to cover the full 39 EUR, you would need to set the rate to approximately 1 point = 5.57 EUR. Alternatively, if you want each product to define its own point price independently from the EUR exchange rate, you can use the "Custom field for price in points" setting, which overrides the exchange rate calculation for that product.

4. Coupon workflow issue

The issue you described with the coupon being generated and the checkout going back a step is related to the "Virtual coupon" setting, which is set to "No" in your configuration. When it's set to "No", the system generates a real coupon code that the customer needs to apply manually, which causes the confusing workflow you described. If you set "Virtual coupon" to "Yes", the point discount will be applied automatically without generating a visible coupon, and the checkout flow will be smoother.

Regarding the points disappearing when a coupon is deleted: if "Return points on cancel" is set to "Yes" (which it is), the points should be returned when the order is cancelled. But if the customer just deletes the coupon without cancelling the order, the points may not be returned. This is expected because the coupon deletion is not the same as an order cancellation.

Hi,

Both issues you describe are caused by having the "Virtual coupon" setting set to "No" in your Pay with Points payment method.

When this setting is set to "No", the plugin needs to create a real coupon code to apply the discount. This can only happen at the "Finalize order" step, which is why the checkout goes back to the previous step to show the coupon. And if the customer deletes that coupon and leaves checkout, the points cannot be automatically restored because the system has no way to know that the deleted coupon was linked to a point deduction.

The solution is to set "Virtual coupon" to "Yes". In this mode:
- No real coupon is created. The point discount is applied automatically as a line on the cart.
- Points are only deducted when the order is actually confirmed.
- The discount is visible before the final confirmation step.
- If the customer leaves checkout without completing the order, no points are lost.

Note that when "Virtual coupon" is set to "Yes", you also need to enable "Partial payment" and make sure it is not set to "No". The virtual coupon mode requires partial payment to be enabled.

Regarding your exchange rates: with your current configuration (1 point = 0.25 EUR in the payment method, and "userpoints" custom field set to 7 on the product), the product costs 7 points regardless of its EUR price. The custom field overrides the exchange rate calculation for that product. So a customer needs exactly 7 points to buy this product with points. If 7 points is not enough to cover the full 39 EUR price and you want the customer to pay the difference, you need to enable partial payment.