內容簡介
OrderGuard for Print on Demand 是一款診斷工具，專為解決印刷按需服務中的訂單同步問題而設計。它能夠檢查並告知使用者訂單未被處理的原因，並提供具體的解決方案，確保商店運作順暢。
【主要功能】
• 檢查未被處理的訂單
• 確認 REST API 是否正常運作
• 檢查永久連結設定是否正確
外掛標籤
開發者團隊
② 後台搜尋「OrderGuard for Print on Demand」→ 直接安裝（推薦）
原文外掛簡介
Print-on-demand sync fails quietly. Products stop appearing, orders do not reach the supplier, and the error message — when there is one — says nothing you can act on. The worst version of it is silent: a customer pays, the order sits in your shop, and nobody is making it.
Most of the time the cause is not the integration. It is one of six things on your own side of the connection, and all six can be measured without any supplier credentials at all. This plugin measures them and tells you, in plain language, what is wrong and what to do about it.
It is a diagnostic tool. It does not sync anything, it does not connect to any supplier, and it never asks for an API key.
What it checks
Which paid orders were never collected? Your supplier does not receive orders — it comes and fetches them, through the WooCommerce REST API, using a key WooCommerce keeps a “last used” date for. So your own database knows the last time anyone came to look. An order that is still waiting to be fulfilled, was placed after that visit, and has been sitting for over a day, was collected by nobody. This check names those orders and adds up the money in them. It needs no credentials to do it, because none of it happens at the supplier.
Is your REST API answering? Supplier integrations register REST routes and expect the supplier’s servers to call into your shop. This is the single biggest source of “sync failed” and of 404 errors during sync. The check asks your own REST API for a response, separates a TLS problem from a firewall problem, and confirms that the WooCommerce namespace is present. It runs from your browser rather than while the page is loading, so it can never freeze your admin — on hosting with a single PHP process, a site cannot answer its own request while it is still building a page.
Are your permalinks set to Plain? The WooCommerce REST API does not work with Plain permalinks. Sync fails with 404 and nothing explains why. One setting, one fix.
What is standing in front of your REST API? Security and caching plugins are the usual culprits, and the fix is almost never to remove them — it is one specific setting in one specific plugin. The check names the active plugins that are known to interfere and says which setting to open in each. It also reads the WordPress REST filters directly and names the code hooked onto them, so a block can be traced even when it comes from a snippet rather than a plugin.
Are your PHP limits big enough for your images? A generic “your memory limit is low” warning helps nobody. This check measures the largest product image actually in your catalogue and compares it against what this server accepts, and it flags an execution limit short enough to cut a sync run off part way through. That is what “it only syncs half the time” looks like from the inside.
What did an interrupted sync leave behind? Duplicate SKUs make suppliers overwrite or skip the wrong product. Orphaned variations stay in the database, invisible in the admin, and break matching at order time. Both are the residue of a sync that failed and was run again.
Works alongside
This plugin sits beside whatever integration you already use. It is compatible with stores running the WooCommerce integrations for Printful, Printify, Gelato and other print-on-demand suppliers, and it is useful whether or not you keep them. It changes nothing about your setup: it reads, measures and reports.
What it does not do
It cannot prove that a supplier’s servers, somewhere else in the world, can reach your shop. That test needs a request from outside your hosting, and this plugin makes no outside requests.
It cannot tell you whether an order that was collected was then accepted or rejected at the supplier. That answer is not on your server.
It fixes nothing by itself. Every finding says what to do; you do it.
It tells you all of this on the page, rather than implying a certainty it does not have.
External services
This plugin contacts no external services. The only network requests it makes are to your own site’s REST API, at your own domain, in order to test whether it answers. No data leaves your server.
