PrestaShop API error messages

PrestaShop

This page applies to PrestaShop stores using the Ciklik module. Running a Ciklik box store? See the box path.

Tip

At each renewal, Ciklik asks the module of your shop to create the order cart. If the module refuses, its message is recorded in the subscription’s renewal errors. This page lists these messages, the cause shown in Ciklik and the fix.

Prerequisites

• Knowledge of PrestaShop products and combinations (id_product, id_product_attribute)
• Access to the PrestaShop back office and to Ciklik

Error message reference

The “Cause in Ciklik” column is the label shown in the subscription’s Renewal situation panel.

Error message	Cause in Ciklik	What happens	Recommended action
Product not found for variant <id>	A variation of the subscription no longer exists in PrestaShop	Combination <id> was deleted from your catalog	See below
Product combination <id> not found	A variation of the subscription no longer exists in PrestaShop	The combination of a product added as an upsell was deleted	The customer can remove this product in My account > Your subscriptions, Non-recurring additional products section; otherwise, contact Ciklik support
HTML page (<!doctype html>…)	Your shop did not answer Ciklik	The shop returned a page (maintenance, protection, server error) instead of the module response	See Rebill and PrestaShop site unavailability
Invalid fingerprint: …	The subscription cart cannot be read, Ciklik has been informed	The module cannot read the cart information sent by Ciklik, for example after a module update	Contact Ciklik support with the subscription ID
Customer not found	The customer no longer exists in PrestaShop	The subscription’s customer was deleted from your shop	Check the customer in PrestaShop; if they were indeed deleted, cancel the subscription
Cart not found	Reason not identified, Ciklik support can help	The cart prepared for the renewal no longer exists	Nothing to do: Ciklik recreates a cart
Missing parameter : … or Bad parameter : …	Reason not identified, Ciklik support can help	Incomplete request between Ciklik and the module	Contact Ciklik support with the subscription ID

Most common error: Product not found for variant

Common pitfall: deleting a PrestaShop combination

This is the number one cause of recurring catalog-related renewal errors.

If you delete a combination (id_product_attribute) in your PrestaShop back office while subscriptions reference it, all affected renewals fail with Product not found for variant followed by the combination ID.

Typical scenario

1. You create a product “Coffee 250g” with two combinations:

   • Ground (id_product_attribute = 42)
   • Whole bean (id_product_attribute = 43)

2. Customers subscribe to the “Ground” combination (id = 42).

3. You reorganize your catalog: you delete the “Ground” combination to recreate it differently.

4. The new “Ground” combination now has id 87.

5. Result: all subscriptions that referenced id 42 fail with Product not found for variant 42.

Solutions

The subscription cannot renew until one of these actions is done:

Option 1: update the subscription product in Ciklik (recommended)

• From the Ciklik back office: Modify the product of a subscription
• Or via the Ciklik API for bulk changes

Option 2: enable the module option below, if your shop uses frequency mode.

Best practice

Before deleting any combination in PrestaShop, check that no active subscription references it.

Use the Ciklik API to list active subscriptions, then spot those whose content (content[].external_id) matches this product and combination:

GET /api/subscriptions?filter[activated]=1

Fall back to default combination if deleted

This module option automatically replaces, at renewal, a deleted combination with the product’s default combination.

1. In the PrestaShop back office, open the Ciklik module configuration.
2. Set Fall back to default combination if deleted to Yes, then click Save.

What to know before enabling it:

• Frequency mode only. The option works on subscriptions whose content holds the product and the combination (id_product:id_product_attribute), that is those created in frequency mode. In combination mode, the subscription only holds the combination ID: if it is deleted, the module can no longer find the product and the Product not found for variant error remains.
• Check the default combination. The customer receives the product’s default combination, not necessarily the one they chose. Make sure it suits a subscriber.
• Upsell products are not covered: a deleted upsell combination still gives Product combination <id> not found.
• Each replacement is recorded in the PrestaShop logs (Advanced Parameters > Logs) with the message “Falling back to default attribute for product…”. Then fix the subscription product in Ciklik so you no longer depend on the option.

Cart not found error

This error occurs when the cart prepared for the renewal no longer exists in your shop.

Possible causes

• Automatic cart cleanup: a cleanup module deletes old or “orphan” carts before the renewal is confirmed.
• Manual database purge: cleanup of the ps_cart and ps_cart_product tables without care.

Solution

Ciklik recreates a cart with the same products and completes the renewal. If the error comes back often, check your shop’s cart cleanup settings.

Diagnosis and resolution

Step 1: identify subscriptions in error

In Ciklik, the Blocked renewals lens of Sales > Subscriptions lists blocked subscriptions with their cause. Through the rebill-errors API:

GET /api/rebill-errors?filter[created_at_after]=2026-01-01

Step 2: analyze the error message

Refer to the reference table above to understand the cause.

Step 3: check catalog consistency

Compare:

• the product and combination ID of the subscription in Ciklik;
• the existence of this ID in the PrestaShop catalog.

Step 4: fix

Depending on the diagnosis:

• update the subscription product;
• recreate the missing items in PrestaShop;
• contact Ciklik support for complex cases.

FAQ

Q: How do I identify all subscriptions affected by a combination deletion?

The API does not filter by combination: list active subscriptions, then spot those whose content (content[].external_id) matches the combination concerned:

GET /api/subscriptions?filter[activated]=1

Q: Can I change subscription products in bulk?

Yes, via the Ciklik API. Contact support for help with bulk changes.

Q: Are these errors visible in the PrestaShop back office?

No. The module returns the message to Ciklik, which records it: you find it in the renewal errors of the subscription and of your site in Ciklik, or through the rebill-errors API.

See also

Understanding renewal errors (rebill errors)

Modify the product of a subscription

PrestaShop renewals explained