Order Status & Tracking Emails for WooCommerce

OSTE preserves email template overrides supplied by themes and other extensions. Those overrides can affect the available layout and style controls.

Yes. The plugin supports WooCommerce HPOS order screens and the legacy order table.

Yes. Plugin strings are translation-ready and custom status labels can be entered in your store language. You can use tools like Loco Translate for plugin translations.

No. Core WooCommerce emails remain available. For custom statuses, you can use the plugin template or choose a WooCommerce fallback email when the plugin template is disabled.

Assigning a role does not itself change native WooCommerce status behavior. Roles are also used by presets and role-based email automations, so changing a role can affect rules that use it. Paid-order, download and purchase-note behavior can be enabled separately for plugin-created custom statuses; core statuses keep their native behavior.

No. Presets and the wizard run only after an explicit administrator action. Status presets can create missing statuses; the advanced role-mapping tool only maps existing statuses. Neither changes existing orders. Suggested workflow and email rules start disabled.

The store owner creates one dedicated bot with BotFather and enables the Customer Telegram module. The bot can be created entirely from the Telegram phone app by opening the verified @BotFather chat; Telegram Desktop and Telegram Web are optional. Customers can opt in from a secure link in their WooCommerce order email or, when enabled by the store, from the My Account order actions in both the orders list and order details. The store can instead select a panel below the order details table or after the details section. Registered customers keep the association for future orders; guest associations apply only to the linked order and use the email invitation. Customers never need to create a bot and can revoke consent with /stop. The activation button is hidden after a customer connects; to test again, the customer sends /stop and then requests a new order email or uses My Account. The store can use one default message template plus optional templates for individual order statuses.

Only after explicit confirmation. OSTE first saves a backup of its current style option and provides a restore action. It does not change WooCommerce email options or options owned by other plugins. No style preset runs during installation, activation, updates, or page loading.

The versioned JSON file contains OSTE settings and rules. It never contains orders, customers, per-order tracking data, automation logs, scheduled jobs, or cron diagnostics.

Email automations never change status. The separate Workflow page can create explicit status-transition rules. Both rule types are disabled by default, revalidated before execution, and use WooCommerce Action Scheduler for delayed jobs.

A workflow rule can react when the first tracking code is entered or when an order enters an exact status. After an optional delay it can move the order to a selected status, or resend the email belonging to the current status without changing it. Adding further per-product tracking codes does not trigger the same event again. Each rule runs at most once per order; cancelled, refunded, and failed orders are protected by default.

No. Automation emails are additional messages. If a customer automation is configured with zero delay on the same status that already sends a WooCommerce or OSTE email, the customer can receive both. For this reason, an immediate customer rule cannot be enabled, scheduled, or executed until the administrator explicitly confirms the duplicate-email risk. Use status templates for the normal transition email and automations for intentional follow-ups or internal notices.

Each rule has its own policy. It can require the order to still match the trigger, continue after every later status change, or continue only while the order is not cancelled, refunded, or failed. New rules use the safest policy by default: the order must still match.

Yes. Choose a reference order to resolve real placeholders and preview the current unsaved editor content. A test email is sent only to the separate test address and never activates, saves, or schedules the rule.

Yes, only when the mail transport rejected the automatic email. The log offers a single-use retry that rechecks the current rule, order status, conditions, and recipient. Scheduling errors, cancellations, and test emails do not expose this retry.

No. The technical wc-completed status keeps its WooCommerce meaning even if its visible label is renamed. The workflow analysis shows the current label, while each store remains free to map operational roles to its own statuses.

Customers can see tracking information in status emails and in the My Account order details page.

Yes. You can use per-product tracking mode and assign a carrier, tracking code, and tracking link to each product row.

The plugin shows how many orders use that status and requires you to move those orders to another WooCommerce status before deletion.

Yes. The States Manager includes an orphan status recovery tool that detects unregistered order statuses and lets you move those orders to a valid WooCommerce status.

No. The slug is locked after creation to keep existing orders valid. You can still change the status label and color.

Yes. The Email Style Settings page includes a live preview and a test email option that sends the current preview to a chosen email address, not to the customer.

Yes. The order screen can resend customer-facing status emails for supported WooCommerce core statuses and plugin custom statuses without changing the order status.