Skip to content

FAQ

Check, in order:

  1. General → Active is on for the currently selected sales channel (not just for “All sales channels”).
  2. The placement drop-down on the relevant tab — Product Page, Cart, Checkout, Checkout Register — is set to something other than disabled.
  3. The working-days rule is selected on the Settings tab. If no rule is selected, the plugin has no way to count working days and renders nothing.
  4. The HTTP cache (Varnish / app.cache.adapter) — flush it after configuration changes, the widget is rendered server-side.

The dates are correct in the preview but wrong on the storefront

Section titled “The dates are correct in the preview but wrong on the storefront”

A few things can cause this:

  • A different sales channel is in use on the storefront than the one selected in the admin. Switch the admin’s sales-channel picker to confirm.
  • The product has its own delivery time set and useProductDeliveryTime is on (or off, depending on what you expected). See Advanced → Product delivery time.
  • A Dynamic Product Group is overriding the configuration — disable Inherit from Dynamic Product Groups to confirm.

The clock is driven by client-side JavaScript. If you see only the skeleton or a static frozen value:

  • Open browser dev tools and look for a JavaScript error from the storefront bundle.
  • Check that the storefront theme is recompiled (bin/console theme:compile) after the plugin install.
  • If your CSP blocks inline event handlers, allow the plugin’s own bundle path.

The cutoff is part of the widget output, which is server-rendered and HTTP-cached. After changing it:

Terminal window
bin/console cache:clear

and flush any reverse-proxy cache (Varnish, Cloudflare).

Snippet fields edit one snippet set at a time. If your translation isn’t showing on the storefront:

  1. Confirm the snippet set is assigned to a sales-channel language.
  2. Switch the admin language picker (top right) to the language you want to edit and re-save.
  3. Clear the Shopware cache.

Holidays rule fires for cart-derived conditions

Section titled “Holidays rule fires for cart-derived conditions”

The plugin evaluates the holidays rule against a hypothetical future date, not against the current cart. If your holidays rule contains conditions that depend on cart state (cart total, customer group, payment method), those conditions won’t match the future-date scope and the rule will behave unexpectedly. Keep the holidays rule pure — only Date range / Day of the week style conditions.

Use the placement drop-down to move it (e.g. from besidePrice to belowAddToCard). For finer control, override the Twig template — see Storefront → Template blocks.

I want to show the widget on a custom page

Section titled “I want to show the widget on a custom page”

Two options:

  1. Add the Estimated Delivery CMS block to a Shopping Experience. See Storefront → CMS block.
  2. Include the widget Twig template from your custom theme. See Storefront → Template blocks.

I want different cutoffs per shipping method

Section titled “I want different cutoffs per shipping method”

Cutoff time is per sales channel and per weekday, not per shipping method. If you need that level of granularity, use multiple sales channels with different cutoff configurations, or override the widget twig and read the shipping method from the cart yourself.

Same answer — model each warehouse as its own sales channel, and the cutoff (and working-days rule) can differ per warehouse.

That’s almost always a snippet translation issue. Check Translation → Weekdays in the language you’re testing — the long and short snippets for each day must be filled in.