Features
Fixes1
- [i18n]Make store language the default for legal docs & translations
The latest updates, improvements, and fixes to Your Next Store. Subscribe via RSS. Curious what's coming? See the roadmap.
Every order carries an operational event log, rendered as a timeline of what happened and when — status changes, fulfillment steps and payment events in one column. Your team can add comments to it, so the reason behind a refund or a delayed shipment stays attached to the order instead of living in a chat thread.
Tag orders to match how your operation actually sorts work — priority, courier, fragile, whatever you use. A "packed" marker and a dedicated "To pack" view give the warehouse a single queue of what still needs boxing.
Select a run of orders in the list and act on all of them at once, which turns a morning of repeated clicking through fifty orders into one pass.
Toasts across admin have been redesigned, with the recolored wave treatment now covering every type, so success, warning and failure read differently at a glance instead of all looking alike. Failed product saves also name the field that's wrong rather than reporting a generic error.
The inventory list has a tighter layout and shows SKUs where you'd expect them, which makes matching a row to a shelf label or a supplier sheet a matter of scanning the page rather than opening each product.
Check-in endpoints and an attendee roster cover the door on event day: staff mark ticket holders as arrived and see, live, who is already inside and who is still expected. No spreadsheet printout, and no separate scanning app to buy.
Ticket holders can fill in a networking profile and browse a directory of everyone else attending, turning a ticket sale into a reason to show up early. Organizers get the connection layer conferences usually bolt on from a separate tool.
The collection editor is fully localized: labels, hints and validation messages all come from the translation catalog, so a merchant running admin in another language no longer runs into English-only strings halfway through building a collection.
Support conversations are readable and writable over the public API. Teams already running a helpdesk can pull store messages into it, or push replies back, without a person sitting in two inboxes.
Feedback sessions — the loop where comments pinned on a live store preview are turned into deployed changes — are now driven through the public API. Sessions can be started, inspected and finalized from your own tooling, which makes them usable as a step in a wider review process.
Connecting a custom domain to a store is now an API call. Agencies and anyone provisioning stores programmatically can attach a domain and follow its verification state without clicking through admin.
Checkout collects a buyer's tax ID through Stripe's TaxIdElement, so B2B orders arrive with a VAT or company number already attached instead of chasing it afterwards.
Collections can assemble themselves from rules instead of hand-picked lists. A recency rule keeps a New Arrivals collection limited to what actually arrived recently, and variant-attribute rules gather every product carrying a given size, color or material — set the rule once and the collection maintains itself.
The bundle editor now picks items at the variant level and stacks quantities, so a bundle can hold three of one variant and one of another without repeating rows. Item decks stack from the top and unfold as you work through them.
Bundles, loyalty, store settings, team management, newsletter campaigns, store analytics and subscriber lists (with bulk import) are all reachable through the public API, along with product assignment on subscription plans. Every new endpoint is registered in the OpenAPI spec, so generated SDKs and docs pick them up without extra work.