Kledo

Open WooCommerce > Kledo > Diagnostics, enter the order number and click “Run diagnosis”. It tells you the most likely cause and what to do. If it does not solve it, download the report and send it to Kledo support.

Kledo accepted the order but did not create it — the problem happened inside Kledo, and only Kledo’s logs say why. The plugin does not resend it automatically, so a slow Kledo cannot cause duplicates. Resend it from the order, the order list, or the Kledo Status tab, and run a diagnosis if it fails again.

Use the Sync tab. It lists the Processing and Completed orders of the chosen period that are not in Kledo yet, and “Process gradually” sends them a few per minute. Orders already in Kledo are skipped.

No. It only counts them and shows a notice. Nothing is sent until you press “Process gradually” in the Sync tab, or switch on “Send Automatically Every Day”.

Each transaction is dated with its order date, so reports of earlier months in Kledo change, and invoices reduce warehouse stock on that date. Kledo currently does not refuse dates inside a period you have locked (closed books), so choose a date range that does not reach into one.

No. The report is only stored in your store for 7 days, and only leaves it when you download it. The API key is never included, and the customer’s name, email, phone and address are partly hidden unless you tick “Include full customer data in the report”.

When on (the default), every invoice sent to Kledo is linked to its Kledo sales order, so the sales order’s invoiced quantities and closure follow that invoice. Turn it off only if you manage sales order closure separately in Kledo and do not want invoices from this store to affect it — an unlinked invoice never counts toward the sales order.

When on (the default), invoicing also asks Kledo to close the linked sales order immediately. Turning it off keeps the sales order open at the moment of invoicing, but Kledo still recalculates and closes it later if anything else changes the invoice or the order — this setting only affects the immediate close, not the eventual one.

On the “Kledo” column on the WooCommerce order list, or by running the “Kledo: Check Kledo status now” order action on an individual order, which records the result as an order note.

The Configure tab masks a saved key for display, showing only the company it belongs to and the key’s last four characters. The masked value is never treated as a new key — save a real key to replace it.

The Configure tab reads how much life the saved key has left and warns 30 and 7 days before it expires. If Kledo has already rejected the key, or if Kledo’s own automatic renewal replaced it with a different key, the tab says so directly instead of letting syncs fail silently.

The sync only stops by itself when Kledo cannot be reached. Check the connection in the Configure tab, then click “Resume” in the Sync tab. A sync paused by version 1.8.0 while it waited for one order is safe to resume. “Cancel” is safe too: orders already sent stay in Kledo.

Because some orders are on both lists, and the menu counts each order only once. For example: 20 orders are not in Kledo yet (Sync tab) and 11 failed in Kledo (Kledo Status tab). If 4 of them are on both lists, the menu shows 20 + 11 − 4 = 27. An order is on both lists when it failed in Kledo within the last 30 days, because the Sync tab can send it again too. The Sync and Kledo Status tabs show this sum whenever it applies.

Click ✕ to hide a message for 7 days; messages only appear on WooCommerce pages. Reminders — orders missing from Kledo, a nightly sync with failures — can be turned off with “Show Reminders” in the Configure tab. Warnings about a stopped synchronisation or a refused API key always show, because nothing reaches Kledo until they are dealt with.

The command palette integration needs WordPress 6.9 or later — earlier versions only expose the palette inside the block and site editors — and the manage_woocommerce capability. Confirm both your WordPress version and your user role.