
外掛標籤
開發者團隊
② 後台搜尋「Stowtro – Back-in-Stock Alerts & Cart Recovery for WooCommerce」→ 直接安裝(推薦)
原文外掛簡介
Stowtro helps WooCommerce stores recover lost revenue from abandoned carts and back-in-stock waitlists. Notifications are delivered via your own email/SMS provider (BYOK – Bring Your Own Keys), and delivery runs outside your store’s WP-Cron. For reliable background scheduling and paced delivery, the plugin can connect to the Stowtro cloud service — see the External Services section below.
External Services
This plugin requires the following external services. Nothing is sent to any of them until you configure the feature that uses it.
1. The Stowtro cloud service (https://stowtro.com)
Used to schedule and pace restock notification delivery and abandoned-cart recovery timers outside WP-Cron. The plugin connects ONLY after you explicitly link your store from the plugin dashboard (“Connect to Dashboard”); activating the plugin contacts nothing.
What is sent, and when: While linked, stock-change heartbeats send the site domain, the affected product/variation ID and its stock quantity, and your plugin version. A daily health ping sends aggregate counts (subscribers, pending notifications, carts captured/recovered, sends per channel), the plugin/WordPress/WooCommerce versions, locale and timezone — never shopper personal data. In Cloud delivery mode (optional, per channel), notification recipient email addresses/phone numbers, the notification content, and your provider credentials are relayed via encrypted HTTPS to the Stowtro queue engine for dispatch. In Local mode, all sending happens directly from your own server with your own credentials.
Terms: https://stowtro.com/docs/terms
Privacy Policy: https://stowtro.com/docs/privacy
2. Resend (email sending — your own API key)
When you choose Resend as a channel’s provider and a restock alert or cart-recovery email is due, the recipient’s email address and the message content (built from your templates) are sent to Resend’s API to deliver it.
Terms: https://resend.com/legal/terms-of-service
Privacy Policy: https://resend.com/legal/privacy-policy
3. ZeptoMail by Zoho (email sending — your own API key)
Same as above when ZeptoMail is the configured provider: recipient email address and message content are sent to ZeptoMail to deliver the email.
Terms: https://www.zoho.com/terms.html
Privacy Policy: https://www.zoho.com/privacy.html
4. Brevo (email sending — your own API key)
Same as above when Brevo is the configured provider: recipient email address and message content are sent to Brevo to deliver the email.
Terms: https://www.brevo.com/legal/termsofuse/
Privacy Policy: https://www.brevo.com/legal/privacypolicy/
5. Amazon SES (email sending — your own AWS credentials)
Same as above when Amazon SES is the configured provider: recipient email address and message content are sent to SES to deliver the email.
Terms: https://aws.amazon.com/service-terms/
Privacy Policy: https://aws.amazon.com/privacy/
6. Twilio (SMS and WhatsApp sending — your own credentials)
When you choose Twilio as a channel’s provider and an SMS or WhatsApp notification is due, the recipient’s phone number and the message content are sent to Twilio’s Messages API to deliver it.
Terms: https://www.twilio.com/en-us/legal/tos
Privacy Policy: https://www.twilio.com/legal/privacy
7. Browser push services (Google/FCM, Mozilla, Apple — Web Push delivery)
When a shopper subscribes to Web Push notifications on an out-of-stock product, their browser generates a subscription that points at its own vendor’s push service (fcm.googleapis.com / android.googleapis.com for Chrome and Android, updates.push.services.mozilla.com for Firefox, web.push.apple.com for Safari). When a web-push notification is due, the plugin delivers the notification payload directly to that endpoint — the browser vendor then shows it to the shopper. The payload contains the notification title and body and the link to your product page; no email address or other personal data is sent to the push service.
Terms (Google/Firebase): https://firebase.google.com/terms/
Privacy Policy (Google/Firebase): https://firebase.google.com/support/privacy/
Terms (Mozilla): https://www.mozilla.org/en-US/about/legal/terms/services/
Privacy Policy (Mozilla): https://www.mozilla.org/en-US/privacy/
Terms (Apple): https://www.apple.com/legal/internet-services/terms/site.html
Privacy Policy (Apple): https://www.apple.com/privacy/
Subscriber and cart-capture data is stored in your own WordPress database; none of these providers receive it except as described above. Your provider credentials (API keys, SMTP passwords) are encrypted with AES-256-GCM before storage and are only used to send on your behalf.
Development
The admin dashboard (dist/assets/) is built from the TypeScript/Svelte source in src/ using Vite. All source files, build configuration, and the packaging script ship inside this package so the built assets can be reviewed and regenerated.
To rebuild the admin assets and the plugin zip:
Install the JS dependencies: bun install --frozen-lockfile (package.json also works with npm/pnpm).
Build the admin assets: bun run build (writes dist/assets/).
Install the PHP dependencies: composer install --no-dev (populates vendor/ from composer.json/composer.lock).
Package the plugin: zip the plugin folder (with stowtro/ as the top-level directory), after staging the runtime files and installing the production PHP dependencies as described above.
Third-party PHP libraries are managed with Composer — see composer.json and composer.lock for the exact packages and versions.
