[WordPress] 外掛分享: Kledo

首頁 › 外掛目錄 › Kledo
WordPress 外掛 Kledo 的封面圖片
10+
安裝啟用
—
尚無評分
12 天前
最後更新
—
問題解決
WordPress 5.3+ PHP 7.4+ v1.8.1 上架:2021-08-30

內容簡介

Kledo 外掛將 WooCommerce 與 Kledo 會計軟體整合,當訂單達到特定狀態時,自動將銷售訂單和發票傳送至 Kledo。此外掛提供檢查和重新傳送未成功到達的工具,確保資料同步無誤。

【主要功能】
• 自動同步銷售訂單與發票
• 支援訂單狀態變更時自動創建
• 提供 Kledo 狀態檢查與重發功能

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.8.1) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Kledo」→ 直接安裝(推薦)
📦 歷史版本下載

原文外掛簡介

Integrates WooCommerce with Kledo accounting software. Sales orders and invoices are sent to Kledo automatically when orders reach the right status, every send is checked back in Kledo, and the plugin gives you the tools to find and resend anything that did not arrive.
Automatic sync

When an order moves to Processing, the plugin creates a Kledo sales order (if “Enable Create Order” is on in the Order tab).
When an order is Completed, the plugin creates a Kledo invoice (if “Enable Create Invoice” is on in the Invoice tab). The sales order is sent first and the invoice is linked to it.
An order changed straight to Completed, skipping Processing, gets its sales order first and its invoice once that sales order exists in Kledo. Turn off “Create Sales Order First When an Order Skips Processing” in the Invoice tab to send only the invoice for such orders.

Every send is checked back in Kledo
Kledo answers a send as soon as it has queued it, before it creates anything. The plugin therefore reads every sales order and invoice back from Kledo afterwards:
* Waiting for Kledo — accepted, not created yet; checked again automatically.
* In Kledo — found in Kledo, with its Kledo reference number.
* Failed in Kledo — accepted, but it never appeared in Kledo. It is not resent automatically (to avoid duplicates if Kledo is only slow); resend it from the order, the order list, or the Kledo Status tab.
* Send failed / Rejected by Kledo — the send itself failed or Kledo refused the data; the error says why.
Order list

A “Kledo” column shows the sales order and the invoice of each order separately, with the Kledo reference number on hover.
Filters “Kledo sales order” and “Kledo invoice” (Not sent, Waiting for Kledo, In Kledo, Failed) and an order date range (From–to; WooCommerce itself only filters by whole month).
Bulk actions “Kledo: Send sales order”, “Kledo: Send invoice” and “Kledo: Check status in Kledo” (up to 20 orders per click; anything already in Kledo is skipped).

Kledo Status tab (WooCommerce > Kledo > Kledo Status)

Summary cards and tabs per Kledo status: Waiting for Kledo, In Kledo, Send failed, Rejected by Kledo, Failed in Kledo.
Check status, Resend and Open order under each order number — Check status and Resend update the row without reloading the page.
Filters by transaction type, order date range and order number; a “What do the statuses mean?” panel explains each status in plain words.

Sync tab: orders that are not in Kledo yet

Sends Processing and Completed orders that are missing from Kledo — for example orders placed before the plugin was installed — 5 to 10 per minute. The next batch is only sent once Kledo has created the previous one, or after 30 minutes, when the orders Kledo is slow with keep being checked in the background. It pauses itself only when Kledo cannot be reached.
Never runs on its own after an install or update: the plugin only counts the orders of the last 30 days that are missing and shows a notice. You start it with “Process gradually”, and can pause, resume or cancel it.
Optional “Send Automatically Every Day” (off by default) sends the missed orders of the last few days every night.

Diagnostics tab: why did an order not reach Kledo?

Pick the order from a searchable list — orders not in Kledo or failed come first, each with its status, date, total and Kledo status — or type its number, and run a diagnosis. Eight checks run one by one — store, connection, settings, the order, the data that would be sent, status in Kledo, sending history, scheduled tasks — and the most likely cause is explained in plain words with what to do.
Optionally resend and record exactly what was sent and what Kledo answered.
Download the report (text, or JSON for developers) and send it to Kledo. The API key is never included and customer data is partly hidden by default.
“Record for 24 hours” logs every request to Kledo (source wc-kledo-debug) for problems that only happen now and then; it switches itself off.

Retries

Failed sends are retried automatically, about 5 minutes after the first failure and then at growing intervals up to 8 hours, for up to two days. Data that Kledo rejects is not retried, since it would be rejected again.
Retries and checks run on WordPress scheduled tasks (WP-Cron). If those cannot run on your host, overdue work is also processed when an administrator opens a wp-admin page.

Invoice-to-sales-order linking (Invoice tab)

“Link Invoice to Sales Order” links each invoice to its Kledo sales order, so Kledo closes the sales order once every quantity has been invoiced. On by default.
“Close Sales Order When Invoiced” asks Kledo to close the linked sales order immediately. On by default.

API Key Status (Configure tab)

Shows the saved key’s name, creation date, last use and expiry, with warnings 30 and 7 days before it runs out, and says plainly when Kledo rejects the key.
When the key is about to expire or no longer works, the Configure tab shows the steps to replace it and a button that opens the API key page in Kledo, so syncing does not stop.
The saved key is masked, showing only the company name and its last four characters.

Quick access

A “Settings” link on the Plugins screen, and on WordPress 6.9 and later every tab can be opened from the command palette (Ctrl+K / Cmd+K) by typing “kledo”.

Guide & FAQ tab

Everything above, step by step, inside the plugin: create the API key, set up sales orders and invoices, check and send orders, the Kledo Status, Sync and Diagnostics tabs, and answers to the most common questions. Searchable, and every settings tab links to its part of the guide.

Logging

Activity is written to the WooCommerce logger with source wc-kledo (WooCommerce > Status > Logs), and important outcomes are recorded as order notes.

Tutorial

延伸相關外掛

文章
Filter
Mastodon