Manage your bundle catalogue faster and with greater confidence: the Backoffice tells bundles and their components apart from single items, and links them together.

In a catalogue that mixes single items and bundles, you need to see straight away which item is part of another. The Items page now clearly flags bundles and their components. A bundle's detail page lists the items it contains and their quantities, while a component's detail page shows the bundles it belongs to. Every item listed links directly to its own detail page.

What this update means:

• Spot bundle items instantly as you browse the Items page in the Backoffice

• View the items and quantities linked to a bundle or component directly from its detail page

• Jump from an item to the bundles it belongs to, and back again, via direct links

Diagnose a failed carrier label directly in the Backoffice, without a chain of back-and-forth between your teams, OneStock support and the carrier's support team.

When a label request fails in store, the cause may lie in your configuration or with the carrier, and tracking it down often involves several support teams. The order history now shows the calls sent to the carrier and their outcome. Your teams can tell a misconfigured label template from a temporary carrier outage, and know immediately who needs to act.

What this update means:

• Label stuck in store: check from the order history whether the error comes from the label template or the carrier. Correct an incorrectly entered address so your store associate can ship the order.

Configure your delivery promise with Robin, OneStock's AI assistant, from initial setup to day-to-day adjustments, while keeping control over every change that goes live.

Configuring a delivery promise takes expertise and time, and changing it in production calls for caution. Robin knows each of its entities (delivery methods, carriers, routes, zones, restrictions) and how they relate to one another. It guides you step by step, applies your changes on request and suggests standard values whenever you create something new. Every change stays in draft until you approve it.

What this update means:

• Get a working promise in minutes, with Robin guiding you through every configuration step

• Apply a single or bulk change in one request, for example: "Move all pickup times from 17:00 to 18:00"

• Create complete entities from the outset: Robin suggests standard costs, delivery times and schedules so that nothing is missing and everything works straight away

Get help from Robin in every configuration tab, with no prior activation, and have the same experience as you do for the delivery promise.

Robin now opens in the same side panel as it does for the delivery promise, and you interact with it in the same way. Its answers are structured and take you straight to the relevant configuration page.

What this update means:

• Go straight to the right configuration page: Robin takes you there automatically

• Act faster with clear, structured answers

• Get help immediately, with no activation or setup required

Configure your Shopify connector more easily: settings are grouped by business area, and flow monitoring has its own dedicated space.

A Shopify connector covers orders, stock, delivery and your online store, each with its own settings. Its interface is now organised into two areas. Settings groups parameters by area: Connection, Orders, Stock, Delivery, Storefront. Monitoring tracks the flows between Shopify and OneStock: webhooks, products and stock. Setting labels have also been made clearer.

What this update means:

• Setting up a new store: configure the connector area by area, from connection to storefront

• Sync issue: check webhooks and product and stock flows between Shopify and OneStock in one place

Decide for yourself, field by field, how a Shopify order becomes a OneStock order, and test your mapping on real orders before activating it.

Every retailer has its own markets, custom fields and metafields, and how they translate into OneStock is a matter of configuration. Order mapping can now be configured for each connector instance, in a JSON editor with auto-completion of available fields. A "Draft" and "Active" version cycle and a test mode protect production. The documentation provides an annotated JSON structure, typical use cases and a ready-to-use AI prompt.

What this update means:

• Adapt the mapping to your markets, custom fields and metafields in a JSON editor, with auto-completion of available fields

• Work on a draft safely: the active version stays read-only, publishing requires confirmation and you can roll back to the last active version in one click

Secure the exchanges between Shopify and OneStock: every webhook goes through a queue, temporary errors are retried automatically and failed events can be replayed.

Exchanges between Shopify and OneStock rely on webhooks, which are exposed to temporary errors on either side. All connector webhooks, from orders to parcel statuses, now go through a queue processed by a dedicated worker, which detects duplicates. A temporary error triggers an automatic retry, without Shopify disabling the webhook. Failed events are set aside, kept in a history and can be replayed.

What this update means:

• Rely on automatic recovery after a temporary error, without the webhook being disabled

• Find failed events that have been set aside, and replay them

• Count on each event being processed once, never twice