Show the chosen date/time on the order confirmation page after the checkout

The chosen date or time slot can be shown to the customer on the order confirmation page (a.k.a. "Thank you" page) just after the checkout.

For example:

Please note: this will only work if the date picker is set to show on the cart page. Unfortunately it won't work if the date picker is set to show on the product page. Don't hesitate to contact our support for more information.

To obtain the result above we need to inject a small script into this page.

  1. To do so, open you're shop's admin page;
  2. Go to Settings then Checkout;
  3. Add the following script in Additional scripts in the Order status page section:

{% assign tag_names = "Method,Delivery Date,Delivery Time,Pickup Date,Pickup Time" | split: "," %}

{% if order.attributes %}

<script>

window.BuuntoOrder = {

attributes: [

{% for tag_name in tag_names %}

{% if order.attributes[tag_name] %}

{ label: "{{ tag_name }}", value: "{{ order.attributes[tag_name] }}" },

{% endif %}

{% endfor %}

]

};

</script>

{% endif %}

Important: make sure to modify the first line to list all the possible attribute names you want to display. They need to be the exact same values that you've set in the app's Settings > Texts and Languages.

The values are defined in "Messages":

  • Method tag label - Default value: Method
  • Order tag date label (if applicable, check the value for both "Local delivery" and "Store pickup") - Default value: Delivery Date / Pickup Date
  • Order tag time slot label (if applicable, check the value for both "Local delivery" and "Store pickup") - Default value: Delivery Time / Pickup Time

Make sure each tag labels are separated with a comma without any extra spaces. For example:

{% assign tag_names = "Method,Local Delivery Date,Time Slot,Store Pickup Date,Time Slot" | split: "," %}


If these values are not exactly the same as set in the admin the dates won't show up in the confirmation page.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.