Troubleshooting
“Test connection” fails
Section titled ““Test connection” fails”- Check the mode and the storefront. Test mode needs the Playground to be activated for your account (Kaufland says this can take up to two weeks); until then use a read-only live check by switching to Live.
- Check for spaces before or after the Client Key and Secret Key. “The signature does not match” (
corrupted-signature) means a wrong Secret Key; “Invalid client key” (invalid-credentials) a wrong Client Key; amissing-or-invalid-request-headeranswer can mean that the server clock is more than five minutes off (the request timestamp is checked). storefront-not-configured: the chosen storefront is not activated for your seller account.- The Log tab shows Kaufland’s answer (masked): the problem type, the message and the field errors.
- Your server must be able to reach the provider over HTTPS (outgoing port 443) and have a current CA bundle.
Nothing happens after an order changes status
Section titled “Nothing happens after an order changes status”- Check Settings > General > Enable and the order status settings.
- Check the license status bar on the add-on pages.
- Open Jobs: queued jobs wait for cron. If the counts never change, the cron job is not running; run the command from the settings page by hand once.
A job is “Waiting to retry” or “Gave up”
Section titled “A job is “Waiting to retry” or “Gave up””The last error is shown in the list. Fix the cause (credentials, data, provider outage) and press Retry. Jobs are retried automatically after 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours before they give up.
Webhooks are rejected
Section titled “Webhooks are rejected”- Kaufland signs notifications with your Secret Key; the key of the mode you registered in must be the one saved on the Connection page. The Playground signs with a separate test key that Kaufland’s partner management hands out on request, so notifications from the Playground may be rejected.
- The web address must be the one on the Connection page, reachable from the internet over https and not behind a login or an IP filter. Registration fails when Kaufland cannot fetch the address (it must answer the challenge within 15 seconds).
- Rejected notifications are only a delay: orders are also read by the scheduled job.
- Rejected events are listed in the log with the action “webhook”.
A product stays “Waiting” or shows a Kaufland message
Section titled “A product stays “Waiting” or shows a Kaufland message”- New EANs: Kaufland processes product data asynchronously and may review it by hand (hours to days). After four hours the listing shows a retry message; press Retry later.
- “missing attributes”: map the listed Kaufland attributes on the Attributes page.
- “blocked on Kaufland”: the product is blocked by Kaufland (see the reason code in the message); contact Kaufland.
- A unit is not created for an EAN whose product data was rejected until the data is fixed.
An order is not imported
Section titled “An order is not imported”Orders wait until Kaufland moved every unit from open to need_to_be_sent (about 15 minutes after the purchase). Unmapped EANs are shown on the Orders page and retried every hour.
The cron address answers “Forbidden”
Section titled “The cron address answers “Forbidden””The key in the address is wrong. Copy the address again from the settings page.
Still stuck
Section titled “Still stuck”Contact us through https://cs-cart.kaviolabs.com with the add-on version, the CS-Cart version and the relevant log lines (secrets are masked automatically).