內容簡介
將 WooCommerce 與 Kledo 會計軟體整合。
特色
在訂單完成時建立發票。
教學
外掛標籤
開發者團隊
原文外掛簡介
Integrates WooCommerce with Kledo accounting software: sales orders and invoices are sent automatically when orders reach the right status, with retries, a Transactions screen to monitor outcomes, and optional manual pushes from the order editor.
Automatic sync
When an order moves to Processing, the plugin can create a Kledo sales order (if enabled in settings).
When an order is Completed, the plugin can create a Kledo invoice (if enabled in settings).
Successful deliveries are recorded on the order; failures are queued for retry (see below).
How it works (lifecycle)
WooCommerce fires status changes; the plugin attempts to send the matching document to Kledo.
On success, the order is marked synced for that type (sales order or invoice) and any stale queue row is removed.
On failure, the transaction is stored in an internal retry queue with a scheduled next attempt time.
Automatic retries run until the sync succeeds, the queue entry is removed as stale, or limits are reached (see Retry system).
Retry system
Failed sends are retried automatically using a progressive delay: about 5 minutes after the first failure, then longer steps up to an 8-hour cap for later attempts (see code comments in the plugin for the full schedule).
Automatic retries stop when: the send succeeds; the entry exceeds the maximum number of attempts; or it stays in the queue longer than the maximum lifetime (two days from when it was first queued). In those stop cases the row may show as Failed and can still be retried manually from the Transactions tab.
Retries are driven by a WordPress scheduled event (WP-Cron). If cron spawning is unreliable on your host, the plugin can also process overdue retries when an administrator loads any wp-admin screen (fallback).
Transactions screen (WooCommerce > Kledo > Transactions)
Lists synced successes (from order meta) and queue rows (failed/retrying). Success rows are built from a scan of recently modified orders that carry Kledo sync flags; very old successes might not appear—use order search if needed.
Columns: Order (link and name when available); Type (order or invoice); Status (Success, Retrying, or Failed); Attempts (automatic try count for queue rows); Created At; Next Retry (queue rows); Last Error (truncated text; hover for the full message when truncated); Actions (Retry now on queue rows).
Filter by status (All, Success, Failed, Retrying), sort key columns, paginate, and use the advanced filter bar for type, exact attempts, a calendar day for Created At or Next Retry, and a “last error contains” search.
Screen Options let you hide optional columns and set how many rows per page.
Manual and bulk retry
On queue rows, use Retry now for a single row, or select rows with the checkboxes, choose Bulk actions > Retry selected, and click Apply. Requires the manage_woocommerce capability.
Use manual retry after fixing credentials, data, or outages, or when you do not want to wait for the next automatic run.
Manual sync on the order screen
A Kledo meta box and WooCommerce order actions can send or re-send the sales order or invoice according to the same rules as automatic sync (processing/completed and feature toggles). Re-sending after a successful sync may create duplicates in Kledo—confirm when prompted.
Logging and troubleshooting
Delivery and retry activity is written to the WooCommerce logger with source wc-kledo (WooCommerce > Status > Logs). Order notes also record important Kledo outcomes.
“Last Error” on the Transactions table shows the latest API or transport message stored for that queue row (sanitized and length-limited for safe display).
Best practices
Keep API connection and feature toggles aligned with how you process orders.
Ensure WordPress cron can run in production (real server cron hitting wp-cron.php is a common setup) if you rely on timely automatic retries; otherwise use the admin fallback or manual retries.
Use the Transactions tab after incidents to clear or retry stuck items.
Tutorial
