What's new

You can now preview the cart and checkout pages before you apply a new look to your shop. The preview comes with a sample cart, so you can see straight away how your colours work on buttons and form fields. If your shop has no products yet, a neutral example is used instead. Your own cart stays untouched and no order can be placed from the preview, and these views are left out of your visitor statistics. Both pages are included in the check for readable colours.

While you set up your branding, you now see right away if a colour combination is hard to read. The check covers your accent colour as well as buttons, links, the header, the footer and labels, and it offers a better colour that you can apply with one click. There's also a button to check your own pages, which runs through the preview of your homepage, a product page, the featured page, search and login. For each page you see which element falls short, what the measured contrast is and which branding setting causes it, and clicking a result scrolls the preview to that spot. Text placed on a photo or a gradient can't be judged automatically, so it comes back as something to check yourself.

Business now includes an SEO screen where you write your own title and description per language for products, categories and pages, see a preview of the search result, and keep a page out of the search results if you want. When you change a page's web address, the old one sends visitors straight to the new page, on every plan.

You pick your company's country from a list, and the full country name shows up on your invoice, contact page and return confirmation. The label next to your company number follows that country, and the standard wording on the invoice now matches the language of the order.

The platform now runs on tijdelijkeshop.nl, so your shop lives under that address with your own name in front. Old links keep working and send visitors straight to the matching page.

A return confirmation could keep going out again and again, even after the return had already been handled. The message is now sent only once.

You can now switch to a different plan without having your shop set up again. An upgrade or downgrade you make applies to your shop right away.

Your dashboard now shows a short summary of visitors and sales, and the new statistics page gives you the full picture per period, compared with the period before. From Pro onwards you also get the funnel from product page to order, campaign data and a CSV export.

When a visitor agrees to analytics cookies, you get a fuller picture: sessions and time on site, new versus returning visitors, landing pages, campaigns, and the path from product page to order including where people drop off. Without consent you keep the cookie-free count, and individual sessions are kept for 90 days before only the daily totals remain.

Your shop now keeps a daily count of page views and unique visitors, along with where they came from, what device they used and which products and pages were viewed most. No cookie is involved and no IP address is stored, so visitors don't have to agree to anything for this.

Background tasks now run in separate lanes, so order confirmations and other messages go out right away even while a big import or a nightly run is busy. If something does sit waiting too long, we get a warning about it.

A shop's statistics page now shows the same details and buttons as the overview, including plan, theme, web address, status and pending invitations. That means you can log in as admin, send an invite or remove the shop right there.

Automated bots sometimes fired hundreds of requests a minute at our servers, which made pages slow for real visitors. Requests per visitor are now capped, so such a burst is stopped before it reaches your shop. Normal browsing and quick clicking through pages are unaffected.

While a platform update is being rolled out, visitors no longer have to wait a few seconds for a page to show up. The heaviest parts of the update now give the shop priority.

It's no longer possible for a product or order line to end up without a VAT rate, no matter how it was created. The dashboard notice about products missing a rate has been removed, since that situation can't happen anymore.

For existing orders the VAT details are saved once instead of being worked out again every time. Invoices, confirmation emails and order pages now consistently show the same rate.

When the cart drops below the minimum order value of a discount code, the code is kept and the customer sees how much more is needed before the discount applies. A code from a newsletter link is now also stored when the cart is still empty.

When you imported a file with several variants per product, the images kept replacing one another and a variant was often left with just one photo. Each variant now keeps its own images in the order they appear in the file, and importing the same file again no longer creates a second set of variants.

For some shops the statistics page failed with an error whenever the selected period included today. The page opens normally again.

If you adjusted your shipping, say by adding rates for extra countries, removing one you don't ship to, or linking products to a parcel type, your shop was still marked as having no shipping set up. That reading is correct now, and yesterday and today have been recalculated.

When you delete a customer, their stored session data and the admin notifications containing their name and email address are now removed as well. Previously those stayed behind in the background.

If your shop had paid orders, the dashboard or the statistics page could show an error instead of your figures. Both pages load again, and orders with a missing or differently written currency are counted together properly.

Events that fire the moment a page loads, like viewing a product, opening the cart or starting checkout, were sometimes dropped for visitors who had given consent. They now wait until the cookie choice is known and are then sent to Google Analytics or the Meta Pixel, or discarded if the visitor says no.

Uploading an image could fail because the server claimed to support a newer image format that it actually couldn't handle. We now check this properly and fall back to just the WebP version when that format isn't available.