Troubleshooting
“Test connection” fails
Section titled ““Test connection” fails”- “Client authentication failed” (HTTP 401): the client ID or secret is wrong or was revoked. Create a new pair in the bol Seller Dashboard (Settings, API settings) and enter it again.
- HTTP 403: bol blocks the account or the call (for example a blocked retailer account). Check your seller account status at bol.
- Check the mode: test mode talks to the demo environment, live mode to your seller account. Enter the credentials in the set of the mode you use.
- Check for spaces before or after the client ID and secret.
- Your server must reach api.bol.com and login.bol.com over HTTPS (outgoing port 443) and have a current CA bundle.
- The Log tab shows the bol answer (masked).
An offer does not go live
Section titled “An offer does not go live”The Listings page shows the reason from bol: “Price too high” (the price is outside what bol accepts for the product), “essential product information is missing” (content for the EAN must exist at bol), the offer is on hold, or the seller account or country shop is not allowed to sell it. A price below 1.00 or above 9999.00 is refused by the add-on before it is sent. An EAN must have 8 to 14 digits.
An order is not imported
Section titled “An order is not imported”- “No product mapping for barcode …”: map the product with that EAN on the Listings page; the import is retried.
- Orders of FBB (Logistics via bol) are only imported when Fulfilment is set to “Bol ships”.
- bol anonymises customer data when the customer asks for it; such orders arrive with the text ANONYMISED in the address fields.
A shipment is not accepted
Section titled “A shipment is not accepted”The log shows the text of bol’s process status, for example an order item that is already shipped or cancelled. Shipments are sent for the items that are still open.
HTTP 429 (rate limit)
Section titled “HTTP 429 (rate limit)”bol limits calls per endpoint. The add-on retries the job after a pause (5 minutes first). If it keeps happening, lengthen the sync interval.
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 and press Retry. Jobs are retried automatically after 5 minutes, 15 minutes, 1 hour, 3 hours and 12 hours before they give up.
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”Send the log export (secrets and tokens are masked) and the add-on version to support.