YayMail Addon for Order Delivery Date Pro WooCommerce - WordPress Plugin

A Setup Guide for YayMail Addon for Order Delivery Date Pro WooCommerce

YayMail Addon for Order Delivery Date Pro WooCommerce does not create a delivery date for the customer. Its role is more specific: it connects the data collected by Order Delivery Date Pro for WooCommerce to the YayMail email editor. This lets you build an order confirmation or another supported email so the selected date, time slot, and related details are easy to find, appear in the right context, and do not look like an arbitrary line beneath the product table.

This guide walks through the full workflow: what needs to be installed first, where the add-on's responsibilities end, how to choose the right email, add a compatible element or shortcode, enable the template, and test it with a real order. It also explains how to distinguish the email design from the rules that control slot availability at checkout, and how to find the cause when a customer sees a date on the site but not in the email.

This guide is for WooCommerce store owners and administrators whose order fulfillment depends on a delivery date or time window: bakeries, florists, local grocery delivery services, meal-prep businesses, pickup services, or stores that schedule courier windows in advance. If you only need to recolor standard WooCommerce emails, YayMail may be all you need. If Order Delivery Date Pro already supplies the delivery details, this add-on helps format them in supported emails.

The basic test is straightforward: the customer first chooses an available date and time slot; the order then saves those details; the appropriate email receives them as dynamic data; and YayMail displays them in the layout. If something goes wrong, look for the point in that chain where the expected state is no longer visible.

Where the Add-on Fits in the Checkout Workflow

This setup has four distinct parts. WordPress provides the environment and user accounts; WooCommerce creates the order and triggers transactional emails; Order Delivery Date Pro for WooCommerce displays dates and time slots at the cart or checkout according to its own rules; and YayMail handles the email template design. YayMail Addon for Order Delivery Date Pro WooCommerce connects the last two parts by making the delivery extension's data and elements available in the YayMail editor.

This distinction matters in practice. The add-on cannot fix a situation where the customer has no available time slot. You need to diagnose the schedule, restrictions, holidays, cutoff times, or other Order Delivery Date Pro rules. Rearranging a block in YayMail will not fix email delivery either: WooCommerce generates the email and hands it off to the mail system through a separate workflow. Likewise, seeing a date in the order details does not mean it appears where the customer expects it in the email.

What information passes through the integration

The customer chooses a date and, if the store has enabled them, a time slot. Order Delivery Date Pro saves those details with the order. When WooCommerce triggers a supported notification, YayMail builds the email using the active template. The add-on gives the editor access to display options that are compatible with that email type. YayMail's documentation notes that the available shortcodes depend on the template being edited: compatible options are available, while options that do not apply are disabled automatically. Do not assume that an element can be moved between a customer email and an administrative notification without checking first.

What the customer sees depends on three conditions lining up, not just on the email looking polished: the order must contain delivery details, the selected email must be triggered by the order's actual status, and the template must be saved and enabled. Always verify the setup with a test order that has an actual delivery date selected; previewing an empty editor canvas is not enough.

What the add-on handles and what the parent plugins handle

This map is useful even before installation. It helps avoid the risky habit of disabling extensions, changing the theme, and resaving the template whenever any symptom appears. Instead, ask one question: at what stage did the details disappear? If they are missing from the order, the email editor is not the cause. If they are in the order but missing from the preview, check the template and its dynamic fields. If the preview is correct but the email never reaches the inbox, investigate order statuses and deliverability.

Who Should Use This Setup, and When Is It Unnecessary?

This setup is especially useful when the delivery date is part of the customer's promise, rather than a minor operational detail. For example, a bakery may accept orders until a cutoff time, offer several delivery windows on delivery days, and need to repeat the selected window in the confirmation. Another common case is a local store where the customer chooses pickup or courier delivery, and the manager needs to see the selected day and time window when preparing the order.

It suits teams that want to change the email layout without editing theme files and do not want to guess the order metadata names by hand. The add-on provides a safer option: use the extension data YayMail makes available for the current template. This reduces the risk of inserting an unverified token that works in one email but appears as a raw technical string in another.

Use cases where the email design affects the workflow

• Local delivery with scheduled windows. The customer should be able to find the delivery day, time window, and fulfillment method without rereading the entire order table.
• Orders for special occasions. For flowers, baked goods, or holiday gift sets, confirming the agreed delivery date matters more than showing a decorative banner.
• Pickup by appointment. The email should visually distinguish the pickup or ready time from the address and product list.
• Staff handling new orders. A stable, easy-to-find location for delivery details in the administrative email saves staff from searching through order notes.
• Delivery reminders. If the parent plugin is configured to send reminders, test that layout separately from the initial confirmation. These messages reach the customer at different points in the process.

This setup may be unnecessary if the store sells only virtual products, does not collect delivery dates, or can rely on standard system emails. It also does not replace tools for sending SMS messages, tracking courier routes, calculating rates, managing inventory, or choosing a shipping method. Those tools can work alongside it, but they handle different tasks.

A practical rule of thumb: use the add-on when you need to do more than pass along data from Order Delivery Date Pro and want to place it meaningfully in a YayMail email template. If the data is not available or does not need formatting, configure the core workflow first instead of adding another layer to the site.

Before You Start: Four Dependencies and a Safe Test Setup

YayMail's official documentation lists four requirements for this integration: WooCommerce, YayMail, Order Delivery Date Pro, and YayMail Addon for Order Delivery Date Pro. Start by checking that these components work together, rather than by importing a polished template. Each one should have a clear purpose on the site. If the delivery plugin is disabled or its rules have not been saved, the add-on will not have the right data to display.

A short checklist before changing a live email

1. Back up the site or use a staging copy, especially if real customers already receive these emails.
2. Confirm that WooCommerce can create a test physical order and move it to the expected status.
3. In Order Delivery Date Pro, configure at least one available date and, if needed, one time slot.
4. At checkout, confirm that a test customer can actually select a date and complete the order.
5. Install and activate YayMail, then install the integration add-on. Avoid changing the theme, checkout fields, and mail plugin at the same time, or you will not know which change affected the outcome.
6. In WooCommerce, open the email settings and confirm that the notification you plan to test is enabled and uses HTML format. YayMail's documentation identifies HTML as a requirement for the editor.

A safe test setup does not have to be an abstract sandbox. You just need a way to place one repeatable order. Create a simple product with a clear name, choose an actual available date and time slot, then record the order number and capture its details. Use that order as the baseline for later tests. If you change only the layout while keeping the order and its conditions the same, you can quickly see whether the template stopped displaying the data or the delivery rules changed.

Check Order Delivery Date Pro rules before testing the email

The parent plugin's official documentation places schedule settings under Order Delivery Date > Settings > Delivery & Pickup Schedules. There, you can enable time-slot selection, make it required, allow a next available delivery option, and change the field label. You can define slots by day of the week or by specific date, and apply separate cutoff rules to them. These settings do not belong to YayMail, but they determine which details appear on the test order.

Do not make a field required just to make it visible. If the store can fulfill an order without a time slot, requiring one adds friction at checkout. If the operation really does require a reservation, make the field required and verify that the customer gets a clear error before payment and can see the selected value afterward. Most importantly, the storefront rules and the email wording should describe the same thing. For example, do not promise a courier window if the customer actually selected pickup.

Install and Test the Integration Without Risky Changes

Installation is more than adding another row to the plugin list. The dependencies need to be available in the right order. Start by activating WooCommerce and YayMail, then install and configure Order Delivery Date Pro, and finally add the YayMail integration add-on. This does not mean you need to remove existing components before updating them. The goal is to make sure the editor can find the data source when you open the template list and compatible elements.

Activation sequence

1. In the WordPress admin panel, open Plugins and confirm that all four components are active.
2. Save a basic working schedule in Order Delivery Date Pro, then select a date on the public checkout page.
3. Open YayMail. In the template list, find the email that makes sense to test first. This is usually a notification sent after an order is placed, but follow the actual workflow in your store.
4. Check the template's recipient, source, and status. These fields in YayMail help distinguish customer emails from administrator emails.
5. Open the editor and check the shortcode and element options. The integration only offers options that are compatible with the current template.
6. After making a small initial change, click Save, then click Enable if the template is not already active.

Do not click Blank on a working template just to experiment. The editor's documentation warns that a saved blank configuration is not automatically restored. If you need a new version, first duplicate the design using an available import method or work on a staging site. Do not replace the only working order confirmation in a live store.

First test: distinguish previewing from sending

YayMail's preview is useful for checking block placement and data from the selected sample order. It is not the same as sending an email, and it does not confirm that WooCommerce will run the right trigger. After previewing, use Send test email, then place an actual test order. Each step answers a different question: the preview shows whether the layout is assembled; the test email shows whether YayMail can generate it for an inbox; and the order shows whether the workflow triggers the right notification with the data the customer actually selected.

Minimum acceptance criteria after installation: the selected date and time slot appear on the order; the open template displays them through the add-on's available options; the template is saved and active; and the email arrives in a separate test inbox. Only then should you spend time on typography, colors, and secondary blocks.

Template Map: Where to Find Delivery Details in YayMail

After installation, many people edit the first email that looks like a confirmation. But the same design can serve different recipients and order statuses. In the YayMail template list, check more than the name: look at the recipient, source, active status, and last modified date. In an administrator email, a well-placed delivery block helps staff prepare the order. In a customer email, it should confirm the customer's selection without creating new ambiguity.

Choose the email by its trigger, not its name

For the first test, choose the notification that your test order actually triggers. WooCommerce sends different emails for different order states, and names such as Processing order or Completed order refer to the order's stage, not the design. Check the order notes and its specific log. If the test uses a different payment method or fulfillment method, the email you expect may simply not be triggered.

In the editor, select your test order from the sample dropdown. This matters because an empty sample makes it impossible to tell whether a field is missing or simply has no value. If the date and time slot are on the order but the compatible shortcode appears blank in the preview, do not try to hide the problem with static text. First make sure that the open template supports data from this extension.

Shortcode, element, or text block: choose how to display the data

The integration documentation describes two options: Order Delivery Date Pro shortcodes in the Shortcodes panel and a separate order element in the editor. Which one to use depends on your goal. If you want to display a set of delivery details formatted by the integration, start with the dedicated element. If you need to place one dynamic value inside an existing sentence, use a compatible shortcode in a text element. Do not copy code from another email just because it looks like the right one. The options in the current editor are a better guide to what applies.

Readability usually matters more than the number of fields. In a customer email, it is helpful to group the details in one compact block with a clear heading, then show the date and time together. The address, fulfillment method, notes, and product list can stay in their usual places. In an administrator email, the same details may belong near the order number and contact information, but they should not be mixed in with payment details.

A reliable layout for the delivery block

• A short heading, such as "Delivery details" or "Pickup time," that matches the actual use case.
• The dynamic date, added through a compatible integration option.
• The dynamic time slot, if one was selected and the recipient needs it.
• A brief explanation only if needed, such as asking the customer to contact the store if their plans change.
• A link to view the order, if WooCommerce already includes one and it fits the customer's workflow.

Do not add assumptions about the route, courier, or guaranteed arrival time. The add-on formats data; it does not create a new logistics guarantee. If the order contains a time window, label it as a time window. If the parent plugin allows the next available delivery option, do not turn that into a specific promised time in static email copy.

Configure an Email with a Delivery Date and Time

A complete setup starts by deciding what the recipient should do after reading the email, not by choosing a design. Customers need to confirm the order, date, and time window, then contact the store promptly if anything is wrong. Staff have a different task: understand the fulfillment requirements and prepare the order correctly. The same block can provide data to both audiences, but it does not have to appear in the same place or use the same wording.

Open the right template in YayMail and select the saved test order as the sample. Then find a place on the canvas where the details will not get lost among products, discounts, and the footer. In a customer email, the block usually belongs after the brief confirmation and before the order details. For administrators, a good place is near the order number, address, and fulfillment method. Put the date above the long product table so people can find it before they start reading the order contents.

Step 1. Add a separate block for the delivery details

Add a text or container block with its own spacing so it does not run into the header. Give it a neutral heading that matches your process. "Delivery details" may work for courier delivery; "Pickup time" may work for pickup. Do not use both at once unless the store can reliably distinguish them by fulfillment method. A customer who chose pickup should not receive an email promising courier delivery.

The heading has one job: help the reader find the information. Do not repeat the order number, address, or full store name in it. If the email has several promotional sections, keep the delivery block close to the transactional details and set it apart with a subtle background or border instead of oversized text. A predictable layout matters more than decoration in a business email.

Step 2. Use the list of compatible shortcodes

The top toolbar in YayMail has a Shortcodes panel. Open it while the template you are editing is selected. The integration documentation states that only values compatible with that template are available. This helps prevent a situation where an administrator inserts a string intended for another event and then spends time looking for an email delivery problem.

Insert the value through the interface instead of typing a similar-looking name by hand. Give it enough plain-language context to make the email easy to understand. A line with only a dynamic value and no label is hard to read, especially if the order has several dates: the order date, payment date, delivery window, and fulfillment deadline. Use a short label such as "Selected date" beside the supported value, then "Time window" on the next line if the customer selected one.

If a dedicated Order Delivery Date Pro element is available, test it first. It is a good fit when you need to display delivery details as a single unit. If the design calls for one field inside an existing sentence, you can use a text block with a selected shortcode instead. In either case, do not replace dynamic data with a static phrase such as "We'll deliver tomorrow." It will stop matching the order as soon as another time slot is selected.

Step 3. Match the template to the order's actual behavior

Save your changes with Save, then check the Enable toggle. YayMail lets you turn a custom template on or off to replace the standard WooCommerce version. If the layout is saved but disabled, the customer may receive the original WooCommerce email, making it look as if the add-on ignored your settings. If the template is enabled but WooCommerce does not trigger that event for the test order, the changes will not appear either. Always finish by checking the order status.

Also check the email format under WooCommerce > Settings > Emails. YayMail's documentation requires HTML format. Plain text cannot show the editor's design, and a multipart text-and-HTML format should be evaluated against the store's mail policy and email client compatibility. Do not change global sender settings for a single test. First make sure the selected notification uses the right format.

Step 4. Save a minimal version before adding decoration

For the first pass, build the block with a heading, date, and time slot. Check it in a test email. Only then add an explanation, order link, rescheduling terms, or brand colors. This order helps for two reasons. First, it is easier to see what disappeared after a new change. Second, email clients render HTML more strictly than browsers. Complex styling, deeply nested blocks, and large images can make an email harder to read even when the data is technically present.

WooCommerce's official guidance for HTML emails recommends checking the design in different clients and on different devices, keeping the email at a reasonable width, and avoiding clutter. That does not mean you cannot use YayMail for branded designs. It means the delivery date must remain easy to read in a normal email client, not hidden in a colorful box with tiny text.

Why Slot Selection and Email Design Need Separate Settings

A common setup mistake is expecting the email design to change which dates are available at checkout, or expecting a change to the cutoff time to update an existing design. These parts share data, but use different settings. Order Delivery Date Pro determines which dates and time slots the customer can choose. YayMail Addon for Order Delivery Date Pro WooCommerce determines how compatible data from that selection appears in a YayMail template.

Input, rule, state, and what the user sees

The add-on has a clear internal workflow. Its input is an order with selected delivery details. The governing rule is whether the specific email template type supports Order Delivery Date Pro data. The state changes in the YayMail editor: an element or shortcode becomes available and can be inserted into the active layout. The visible output is an HTML email in which the customer or administrator can see the date and time window from a sample order or real order. This is the chain that distinguishes the add-on from a general-purpose email editor.

In practice, before reporting that "YayMail does not show the time," identify the actual input. Did the test order have a time slot selected? Was the slot required or optional? Was the order saved before the email-triggering event? Is the open YayMail template one that the add-on supports? This is more useful than changing the block color or reinstalling everything at once.

Availability rules stay in Order Delivery Date Pro

The parent plugin supports schedules by day of the week and by specific date, a time-slot selection toggle, required fields, a next available fulfillment option, and custom slot restrictions. Separate cutoff settings can close a slot for same-day or next-day delivery. If the customer places an order after the cutoff and the earlier window is no longer available in the form, that may be the correct outcome, not an email problem.

Set up the business rules first. For example, a bakery may accept orders for a morning window until a certain time, then offer only an afternoon window. The customer should see only the available option in the form. After payment, the email should show that same selected window. If it instead says, "Contact the manager to confirm the time," the customer loses the confirmation they provided the information for.

Display rules stay in YayMail

YayMail does not need to know why a particular slot is closed. Its job is to display the details it receives. Do not write conditions into the template that the current configuration does not support, such as an absolute promise that "we always deliver on the day you order." If the store changes its schedule, cutoffs, or fulfillment methods, review the static copy next to the dynamic fields. The values update from the order, but static text stays as it was when the template was saved.

Good wording separates the confirmed detail from the instruction: "You selected the following time window," followed by the dynamic data. This neutral phrasing does not promise more than the order records and works for different dates. If there is a separate process for changing a selected time, include a brief way to contact the store. Do not imply that the site supports an option it does not provide.

Example: A Bakery Order Confirmation with a Delivery Window

Consider a bakery that delivers on Tuesdays, Wednesdays, and Fridays. Each available day has two windows: morning and afternoon. The goal is not to create an abstract, attractive email. The customer should see the same day and window they selected at checkout, and an employee should see those details in the administrative notification.

Set up the example order

Prepare one test product and one test delivery rule. In Order Delivery Date Pro, create or edit a schedule under Order Delivery Date > Settings > Delivery & Pickup Schedules. Enable time-slot selection, add two meaningful windows for several days, and make the field required only if the business actually needs it. Confirm that the test date is not a blocked day and is not closed by a cutoff.

Add the product to the checkout and select a date and morning window. Confirm that the date and time window appear before placing the order. If the store offers several fulfillment methods, repeat the test using the method the email is intended for. Do not assume that a selection behaves the same way for another method. Schedule rules may differ.

Create the customer email block

1. Place a test order with a selected date and morning window. Save the order number.
2. In YayMail, open the template the customer actually receives for this type of order and select the test order as the sample.
3. Add a small block titled "Delivery details" beside the order confirmation.
4. Use Shortcodes or a compatible element to insert the available Order Delivery Date Pro data. Do not replace it with a manually typed phrase.
5. Preview the email. Confirm that the date is present and the time window belongs to the same order.
6. Save the layout with Save and enable it if it is not already active.
7. Send a test email, then place another order with a different day or time window to rule out stale sample data.

That second order is important. One test with a single date only proves that some value appeared. A second test with a different value confirms that the email is actually using the order's dynamic data. If the second email still shows the old time window, do not publish the template. You may be looking at a preview, using the wrong sample order, or using the wrong integration element.

Administrator email: a different task calls for a different layout

Create a separate configuration for the staff email. You might put the delivery block above the product list and below the order number. Use operational wording such as "Prepare for the selected time" only if that reflects the actual business process. The administrator needs details they can act on, not a marketing-style confirmation. Do not copy the customer email in full if it makes the fulfillment time harder for staff to find.

After saving, place a new order and compare both emails with the order details. The date, time, and fulfillment method should match across all three places: checkout, the admin panel, and email. Consistency across these three places matters more than making them look identical. It helps prevent manual follow-up and fulfillment mistakes.

Changing or updating delivery details

Order Delivery Date Pro may allow administrators to change delivery details in the order, and, depending on the settings, let customers change them before the cutoff time. This is a separate workflow. Do not assume that an email already sent will be rewritten afterward. If the business changes the date after the order is placed, check which notification the customer actually receives and whether it includes the updated details. Test this separately; checking only the initial email is not enough.

Verify the Setup from Checkout to the Inbox

A proper test follows the data from one place to the next; it does not start and end in the editor. A repeatable test reduces the risk of an email that looks right for one sample but hides the data in the live store, has a disabled notification, or sends on a different event. Prepare a short test protocol and use it after any significant change to the schedule, template, order statuses, or mail system.

Five checkpoints

1. Checkout. Select an available date and time slot, then record your selection before payment.
2. Order details. After placing the order, open it in WooCommerce and confirm that the details were saved.
3. YayMail sample. Select that exact order in the editor and check how the available element or shortcode displays.
4. Sending. Confirm that the template is enabled, the WooCommerce notification is enabled, and the notification is triggered by the actual order status.
5. Inbox. Open the message in a separate test inbox and check that it is readable on both desktop and mobile.

If the field is already blank at step three, there is no need to check SMTP yet. If the email is not generated at step four, changing the shortcode will not help. If the message is marked as sent but does not reach the inbox, you have a deliverability issue, not an editor issue. This sequence saves time and preserves useful evidence: the same test order connects each observation.

Review the email from the customer's point of view

Open the email without thinking about how it was configured in the admin panel. Within a few seconds, it should be clear which order is confirmed, when to expect it, what the time window is, and what to do if anything is wrong. If the date appears only after scrolling through a long promotional section, or looks like a technical code, adjust its placement. If the store offers both delivery and pickup, test each one and make sure the wording does not conflict with the selected method.

Also test empty and edge cases. What happens when the time slot is optional and the customer does not select one? What does the customer see if the next available delivery option is enabled? You do not necessarily need a separate design for every case, but the email should not put a false label next to an empty value. If the expected behavior is unclear, use a more neutral layout and test it with a real order.

Check email delivery without jumping to conclusions

WooCommerce logs transactional email attempts under WooCommerce > Status > Logs. The source is usually named transactional-emails. Its official guide distinguishes sent, failed, disabled, and skipped states. This is more useful than guessing based on a missing inbox message. The notification may be disabled, the order may still be in a status that does not trigger the email, or the message may have reached the mail system and been filtered by the recipient's provider.

For better deliverability, use a sender address on the site's domain and a verified mail setup. WooCommerce specifically warns that personal email addresses from public providers are more likely to be filtered when the sender domain does not match. This is not an add-on setting, and adding more links to the template will not help. First use the log to confirm whether the message was generated, then investigate SPF, DKIM, SMTP, or the recipient's inbox rules.

Keep the Email Clear When the Schedule Changes

Delivery schedules change more often than email designs. Stores add holiday exceptions, close time windows, offer pickup, or change order cutoffs. That is why the template should not duplicate business rules that Order Delivery Date Pro already calculates. The email should reflect the customer's actual selection, not try to restate the entire availability matrix.

Separate dynamic details from static promises

Use two layers of copy. The dynamic layer contains the selected date and time made available through the add-on. The static layer explains what the recipient should do, such as where to get in touch with a question. The fewer unsupported timelines in the static text, the less likely it is to promise something that is no longer true. Instead of saying, "Orders placed after noon are always rescheduled," you could say, "See your confirmed time window below," if the email does not need to explain the store's internal rules.

If the store offers both delivery and pickup, align the terminology in Order Delivery Date Pro and the email layout. You can change the time field label in the schedule settings. This is useful when the customer chooses a pickup time rather than a courier's arrival time. Changing the label alone does not make the email fit each context automatically. Test each fulfillment method with a separate order and make sure the wording matches the service the customer selected.

Cutoffs and availability: what the customer needs to see

Cutoffs prevent customers from selecting a time slot that can no longer be fulfilled. Tyche Software's documentation describes individual cutoff rules for time windows: after a set time, a window becomes unavailable for same-day delivery. Avoid publishing these rules as fixed times in the email if they depend on several schedules. It is more important to show the confirmed selection and give the customer a clear way to contact the store with questions.

Test both sides of the cutoff separately: place one order before it and another after. The first should offer the earlier available window; the second should offer the next available one. Then compare each email with its corresponding order details. This confirms that the dynamic data comes from the current order, not from an earlier sample saved in the editor.

Delivery reminders are a separate type of email

Order Delivery Date Pro documents customer reminders and administrator notifications for upcoming deliveries. You can enable them and set their subject and format in WooCommerce email settings, while the automatic rule is set in the parent plugin's reminder section. Do not treat these as copies of the order confirmation. Customers read reminders closer to fulfillment, so the date, time window, and a brief next step matter more than a long description of the purchase.

Before applying a YayMail design to this type of email, check whether it appears in the list of available templates and which elements it supports. If it does not appear as an available template, do not try to imitate it with another notification. Record the limitation, use the standard email, and return to visual customization only if the required email type is confirmed as supported.

A Maintenance Routine for Keeping Delivery Dates in Sync

The setup rarely stays the same after launch. A store may add fulfillment methods, holiday exceptions, different order statuses, WooCommerce updates, or new support requirements. Reliable use of the add-on depends on a short change routine, not a one-time successful setup. The goal is to prevent a small schedule or template change from silently breaking the confirmation customers receive.

Keep one test order as a baseline

Document a baseline order in the store's internal instructions: product, shipping method, selected day, time window, test recipient address, expected status, and inbox address. Do not include real personal data. This gives you a consistent checkpoint after a major update to any of the four components or before publishing a new template.

A baseline order is also useful because visual editors often let you preview an email using an old sample. Without a reference, you might confirm that the layout looks good with populated data but miss that a new order uses a different format or that the time field is now optional. Run two tests: a standard order with a date and time slot, and an edge case using another available day or fulfillment method. If the business allows orders without a time window, make that your third test.

Keep a template change log

You do not need elaborate technical documentation. Record the date of each change, the notification affected, what changed, which test order you used, and the outcome. For example: "Customer email after order placement, delivery block moved above products, tested with morning and afternoon windows." This makes it easier to determine whether behavior changed after an update or was already present.

Pay particular attention to the Enable toggle. It is a small technical setting, but it determines whether customers see the custom template or the standard email. If multiple people edit templates or updates are involved, agree on a simple rule: one person changes the layout, another checks a test email, and then the active version is recorded. This reduces the risk of a draft accidentally replacing the working template.

Updates and compatibility

YayMail's changelog includes fixes related to displaying dates and times through order metadata, HTML templates, and integrations. The Order Delivery Date Pro changelog covers schedule behavior, compatibility with WooCommerce checkout options, and fixes to date data in email notifications. This does not mean you should update extensions on a live site without preparation. It does mean that after an update, you should check the full test order workflow, not just the Plugins page.

A safe sequence is: back up the site or use staging, update the components, test with the baseline order, then check the order, template, sent email, and transactional email log. If the add-on no longer shows an element after an update, do not edit plugin files or add unverified PHP. Check that all components are active, confirm that the selected template type is available, and review the official release notes. If you cannot explain the outcome, keep the last confirmed configuration temporarily and contact the developer's support team with the test order number and the symptom you observed.

Email Content: Make Delivery Details Easy to Understand, Not Just Visible

Customers read an order confirmation after they have paid or completed checkout. They do not know how WordPress works or which fields came from different plugins. The quality of the template is not measured by the number of dynamic tokens it contains, but by how quickly a customer can find the information they need. In a good email, the date and time answer the question, "When and how will I receive my order?"

Reading order for customers

Start with the confirmation, then show a short delivery block, followed by the order contents and secondary details. This matches what customers need to check: first that the order was accepted, then when to expect it, then which products they ordered. Long store descriptions, banners, and product recommendations should not separate the confirmation from the selected time window. If promotional content is necessary, place it after the transactional details.

Give the delivery block a clear reading order. Its heading tells the reader what the details refer to. Next comes the date, followed by the time window if there is one. If the fulfillment method is important, show it last. Short label-and-value pairs such as "Date" and the date or "Time" and the time window work well. A long sentence that buries the date among a greeting, order number, and general copy does not.

Reading order for staff

An administrative email should help staff decide how to prepare an order. It makes sense to show the order number, recipient, fulfillment method, and time near the top. But do not turn the email into a second order page with every technical detail repeated. Staff can still open WooCommerce for more information. The email only needs enough detail to prioritize the task: what to prepare, for which day and time window, and for which fulfillment method.

If the team handles a high volume of orders, agree on a consistent field order and keep it the same across templates. For example: date, time slot, fulfillment method. A consistent order reduces the chance of mistakes when staff read emails on a phone. It also makes support easier. If an employee reports a missing field, you will know which part of the template to check.

Neutral wording for dynamic values

The email should confirm the customer's selection without changing its meaning. For a date, use labels such as "Selected date" or "Pickup date." For a time slot, use "Selected time window" or "Pickup time." Choose the exact wording based on how the store operates. If pickup is available, avoid a generic phrase like "The courier will arrive." If the store offers delivery only, do not label every slot as a "ready time."

Do not put exact cutoff times, the number of available windows, or future availability guarantees in static copy if those values are calculated by schedule rules. Such statements can become outdated and conflict with what the customer saw at checkout. The customer email should reflect the saved order details. Explain the selection rules on the checkout page, in the delivery terms, or in a separate help article instead.

A good layout does not replace logistics. It confirms a selection that has already been made and saved, so customers and staff can read it the same way.

Integration Limits and Safe Boundaries for Customization

The add-on has a useful but narrow role. It does not add delivery rules on its own, turn an email into an order management tool, or guarantee that any custom field will appear in every notification type. That is expected: compatibility depends on the selected template. Recognizing this limit early helps prevent a fragile setup built around manually inserted values.

An optional field may be empty

If the time slot is optional in Order Delivery Date Pro, some orders may not have one. Do not design the email as if the field were always populated. First test an order with a selected time slot, then test a case where the business allows it to be omitted. If the element handles an empty value correctly, that is better than showing a static label with nothing after it. If the behavior is not confirmed, limit the layout to the configurations the integration actually supports and do not promise a time window for every order.

Do not edit core or plugin files to change the design

You should not need to change WordPress, WooCommerce, YayMail, or Order Delivery Date Pro files for this setup. Those changes are harder to maintain through updates and more difficult to diagnose. Start with the options in the interface: elements, shortcodes, saving the template, activation status, test emails, and Order Delivery Date Pro settings. If you need custom behavior, first find a documented extension point in the relevant product's official documentation and test it on staging. Do not add unverified snippets to functions.php just to change one email.

Caching and email: where the real risk is

Caching usually affects store pages, not emails that have already been generated. It can still affect a checkout test if the customer sees an outdated schedule or calendar scripts. If a slot does not appear on the page, first check the schedule, shipping method, and checkout in a clean session. Then review cache exclusions in the documentation for your optimization tool. Do not blame YayMail until you have confirmed that the date was saved to a test order.

If an email shows old details, distinguish between two cases. An old order should retain the selection made at the time and does not have to be recalculated. A new order placed after the schedule changes should have the current available options. Mixing up these cases can create a false impression of a caching or template conflict.

When This Setup Is a Good Fit

YayMail Addon for Order Delivery Date Pro WooCommerce makes sense when a date or time window is already part of the order and needs to be shown clearly and reliably in a supported email template. Start with one active notification and one repeatable test order. Confirm the details at checkout, in the order, and in the inbox. After that, you can expand the design and add other use cases without guessing where a problem started.

If you are ready to run that test, go to the section to download YayMail Addon for Order Delivery Date Pro WooCommerce, install it with its required dependencies, and first repeat the basic test with a separate order. That way, the designed email confirms a real delivery agreement instead of serving as attractive but unverified decoration.