Release Notes

Release Notes

Every Core dna product, release by release, newest first. Each product ships on its own schedule.

Platform 2026.12

What’s new in Core dna Platform 2026.12

Personal Prices, Warehouse Pages and Order Tracking

Products can have a price for one person or one group. Each warehouse can have its own store page. Visitors can track an order with its number and email address.

Key highlights

  • Personal prices: give a product a price for one person or one group of people, in each currency.
  • Warehouse pages: give each warehouse a store page, with a listing of all stores at /stores.
  • Order tracking: visitors look up an order at /orders/track with the order number and the email address used when ordering.

Changes in behaviour

  • Email confirmation page: /confirm-email now shows a form, and the account becomes active when the visitor submits it. Replace your theme's users/users/confirm-email.html with a form that posts token back, and password and confirmPassword when $requiresPassword is true. The earlier template does not work with this page.
  • Registration with a known email address: a registration with the email address of an existing person now gets the reply "Please check your email to finish setting up your account." and no sign-in. The person gets an email with a link that is valid for two days. Check any script that expects a user in the reply of POST /cdna-api/register.
  • Inactive members: a member whose account is inactive can no longer sign in or use the API by any method. A site with the registration Status set to Inactive no longer signs new registrants in.
  • The /stores address: each site now answers /stores with the warehouse page listing. A page with the slug stores and the pages below it are no longer reachable. A custom URL or a rewrite at /stores still wins. Check your site for content at this address.
  • Refund calculation in the API: POST /cdna-api/orders/refund/calculate now requires a quantity on each refund item. A refund larger than the refundable amount gets a 422 with "Total exceeds available amount".
  • Special price of 0: a special price of 0 is now ignored, and the base price applies.

Personal prices

A product can now have a price for a specific person or for a group of people. A signed-in customer sees and pays that price in listings, the cart and the checkout. Guests and all other customers pay the general price.

Open a product in Transactions › Products › Products. When Use multi currency for products is on, each currency on the Pricing tab has a Personal prices list. When it is off, the list is on the Details tab under the default price. Choose Add person price or Add group price, pick the person or group, and enter the Price. The price can be 0.00.

A personal price replaces the base price and the special price for that customer, also when it is higher. A person's own price wins over the prices of their groups. Among group prices the lowest wins. When a customer belongs to several groups with a price and at least one is marked Sticky, only the sticky prices are compared. A personal price applies only in a currency that has a general price.

When a guest signs in, the cart is priced again for that customer. In templates, getFinalPrice() returns the visitor's price, getPricings() returns the general prices, and the new getPersonalPricings() returns the visitor's own personal prices. In the API, each pricing of a product has the new fields person, group, sticky and personal.

Template code
{* Show the visitor's price, and mark it when a personal price applies *}
<p class="price">{$product->getFinalPrice()}</p>
{if $product->getPersonalPricings()->count() > 0}
  <p class="price-note">Your price</p>
{/if}
{# Show the visitor's price, and mark it when a personal price applies #}
<p class="price">{{ product.getFinalPrice() }}</p>
{% if product.getPersonalPricings().count() > 0 %}
  <p class="price-note">Your price</p>
{% endif %}

Warehouse pages

Each warehouse can now have a page on the website, for example a store page. A warehouse page has a layout, revisions, translations, SEO settings, a custom URL and scheduled publishing, like other pages.

Manage the pages in Transactions › Inventory › Warehouse Pages. The warehouse edit screen has a new Page section with Add page. Each warehouse has one page, and the page can have translations. Deleting a page also deletes its translations. The warehouse is not affected.

Visitors see the list of pages at /stores and each page at /stores/{slug}. The theme supplies inventory/warehouse-pages/index.html, which gets $warehousePages, and inventory/warehouse-pages/show.html for a page whose layout has no template. /stores answers 404 while the site has no published warehouse pages. In templates, getPage() and getPageUrl() on a warehouse return its published page and that page's path.

Transactions › Configuration › Inventory has three new settings. Generate warehouse pages in sitemap is on by default. Warehouse pages per page is 50 by default. Order by sets the order of the listing. The API has new routes under /cdna-api/inventory to list, show, add, edit and delete warehouse pages.

Template code
{* Store listing: inventory/warehouse-pages/index.html *}
<ul class="stores">
{foreach $warehousePages as $warehousePage}
  <li><a href="{$warehousePage->getFullPath()}">{$warehousePage->getName()|escape}</a></li>
{/foreach}
</ul>
{# Store listing: inventory/warehouse-pages/index.html #}
<ul class="stores">
{% for warehousePage in warehousePages %}
  <li><a href="{{ warehousePage.getFullPath() }}">{{ warehousePage.getName()|e }}</a></li>
{% endfor %}
</ul>

Order tracking

Visitors can look up an order without signing in. They enter the order number and the email address used when ordering at /orders/track. The page shows the order's status, totals, items, fulfilments, shipments and tracking events. It does not show the customer's name or addresses.

The page is off by default. In Transactions › Configuration › Orders, turn on Enable order tracking page. Order tracking reCAPTCHA protects the form and is v2 Checkbox by default. The other options are v2 Invisible and Disabled.

The theme supplies orders/orders/track.html. The form posts number and email to /orders/track. After a successful lookup the template gets $order. When the details match no order, the page answers 422 with the message "We could not find an order matching those details. Check the order number and the email address used when ordering." Money values use the money methods, for example getTotalAsMoney(), and a shipment link uses getSafeTrackingUrl().

Template code
{* Order tracking page: orders/orders/track.html *}
<form method="post" action="/orders/track">
  <input type="text" name="number" required>
  <input type="email" name="email" required>
  {if isset($_csrfToken)}<input type="hidden" name="_csrf" value="{$_csrfToken}">{/if}
  {if isset($_recaptcha)}{$_recaptcha->getWidgetHtml()}{$_recaptcha->getScriptTag()}{/if}
  <button type="submit">Track order</button>
</form>
{if isset($order)}
  <h2>Order {$order->getNumber()|escape}: {$order->getFulfillmentStatusDisplay()|escape}</h2>
  <p>Total: {$order->getTotalAsMoney()}</p>
  {foreach $order->getFulfillments() as $fulfillment}
    {foreach $fulfillment->getShipments() as $shipment}
      {if !is_null($shipment->getSafeTrackingUrl())}
        <a href="{$shipment->getSafeTrackingUrl()}">{$shipment->getTrackingCode()|escape}</a>
      {/if}
    {/foreach}
  {/foreach}
{/if}
{# Order tracking page: orders/orders/track.html #}
<form method="post" action="/orders/track">
  <input type="text" name="number" required>
  <input type="email" name="email" required>
  {% if _csrfToken is defined %}<input type="hidden" name="_csrf" value="{{ _csrfToken }}">{% endif %}
  {% if _recaptcha is defined %}{{ _recaptcha.getWidgetHtml() }}{{ _recaptcha.getScriptTag() }}{% endif %}
  <button type="submit">Track order</button>
</form>
{% if order is defined %}
  <h2>Order {{ order.getNumber()|e }}: {{ order.getFulfillmentStatusDisplay()|e }}</h2>
  <p>Total: {{ order.getTotalAsMoney() }}</p>
  {% for fulfillment in order.getFulfillments() %}
    {% for shipment in fulfillment.getShipments() %}
      {% if shipment.getSafeTrackingUrl() is not null %}
        <a href="{{ shipment.getSafeTrackingUrl() }}">{{ shipment.getTrackingCode()|e }}</a>
      {% endif %}
    {% endfor %}
  {% endfor %}
{% endif %}

Other improvements and bug fixes

  • People who exist on a site without an account, such as guest checkout customers, can now register. They get an email with a link and set their password from it. The new Users setting Require Email Confirmation applies the same step to every registration.
  • Added the OAuth setting Link existing accounts on sign in for Facebook, Google and Microsoft. It lets a visitor sign in with that provider into an existing account with the same email address. It is off by default.
  • Added POST /cdna-api/orders/refund, which issues an order refund. It takes the same body as POST /cdna-api/orders/refund/calculate.
  • Fixed an issue where a refund that Stripe held as pending stayed pending. Orders and invoices now show the pending refund amount.
  • Fixed an issue where the Use gravatar switch on an author could not be turned off.
  • Fixed an issue where Yes/No columns in some admin listings did not sort, and where the Visible switches in the menu elements listing all showed as on.
  • Fixed an issue where the revision actions in the file manager showed translation keys, and where an older revision could not be deleted there.
  • Fixed an issue where changes made in the code view of a rich text field were lost on save.
Go deeper

Was this page helpful?

Your answer goes to the docs team.