// changelog
Every entry is written when the change ships, by the people who shipped it, and it is the same list the product shows inside your dashboard.
// the record
When selecting products for a new launch, the review queue now asks for exactly as many products as needed to reach your target in one go — no more returning to approve the same queue multiple times. The system enforces a sensible ceiling so the queue stays manageable, and an empty result is shown clearly rather than treated as an error.
When reviewing import candidates, the product image now fills the card so you can judge the garment itself rather than a cropped thumbnail. Each candidate shows why it was ranked — either a sales figure from competitor data or its position in the source shop's best-seller list — so approving the top products is a decision you can stand behind. You can now approve in bulk, and the page shows how many were created immediately alongside how many are still being added to your store.
When you review candidate products during a launch, items that the sourcing shops themselves promote as best-sellers, trending, or most-loved are now ranked ahead of arbitrarily ordered results. This means the products most likely to perform well appear first, so you spend less time scrolling to find the strongest candidates.
When Magistry declares a known issue, the notice now shows on the specific page affected rather than only as a site-wide banner. A current notice about Theme Studio's GitHub connection is visible on the Theme and Launch pages, where you would first run into it.
When you review products sourced from competitor shops during a launch, cards are now ranked by each shop's own publicly-stated best-sellers so that the strongest candidates appear first. Previously, products were shown in arbitrary scrape order, requiring you to read through all staged cards to find the ones most likely to perform. Shops that do not publish a best-sellers collection are still fully included — they simply keep their current ordering.
If you're on the Theme Studio page or the launch wizard and a GitHub repository connection cannot be completed, a notice now appears right there explaining what is affected. Existing connected repositories continue to deploy without interruption. New connections will not complete until the issue is resolved.
The platform status page now has a dedicated Storefront component, so problems with Theme Studio and storefront publishing are reported under the right name instead of being grouped with catalogue updates. Known issues about the GitHub connection will now appear exactly where you would expect to find them.
When Magistry declares a known issue, a banner now appears directly on the page affected — so if a feature isn't working, you see the notice right there instead of having to check a separate status page. The banner is shown only where it is relevant and disappears automatically once the issue is resolved.
When transferring your theme repository to your own GitHub account, you now receive direct instructions and a link straight to the right settings page — no waiting for an email that was never sent. The handover card shows exactly two steps, both yours to take, so nothing is left ambiguous.
When something breaks and you report it, the status panel can now reflect a declared incident in the same place the automated health checks appear — one surface, never two that disagree. If your report is linked to a known issue, your feedback thread will show that it is recognised, in the operator's own words rather than a generic message.
You can now prove ownership of your company's email domain by publishing a DNS TXT record at _magistry.<yourdomain>, unlocking automatic workspace membership for colleagues who sign up with that address. Public email providers like Gmail are refused clearly rather than silently failing. The workspace admin page shows exactly what DNS answered so you can tell at a glance whether your record is in place.
Merchants connected to an agency can now see a Recent access list in their store settings showing which agency operators have entered their store and on what date. Agency users see the same information from their client list, including a clear notice when nobody has opened a store yet. Dormancy is only flagged after the ledger has had enough time to be meaningful, so a brand-new connection is never incorrectly marked inactive.
Your client book now groups multiple storefronts belonging to the same customer into a single company row, so you see one client rather than several unrelated lines. Priority is set by the worst-performing store in the group, keeping problem accounts visible at the top. Enabling a manager account now presents versioned terms you must accept before the conversion completes, and every acceptance is permanently recorded alongside the document version you agreed to.
The platform status panel in the header has been redesigned to match the notifications panel: a compact tab switcher with Status and What's new, a persistent outage banner pinned above whichever tab you're on, and a footer link to the full page when you need more detail. The panel always opens on Status if anything is not operational, so you never miss an incident because you last left it on release notes. Releases on the same day now appear in the order they were written rather than an arbitrary internal order.
The agency workspace page previously showed two sets of revenue numbers and store grids stacked together with no label telling you whose was whose. Now the page leads with your client book — each client's account number, their stores, and their ROAS — and your own stores sit under a clearly labelled section beneath. ROAS is shown as a dash rather than zero or infinity when a client ran no ads, and a client company name appears on a row only when that company owns more than one store.
A new status page at /dashboard/status shows whether each part of Magistry is operating normally, degraded, or experiencing an outage — updated automatically from the jobs the platform already runs. A coloured dot in the header bar appears whenever something is degraded or down, so you can tell immediately whether a problem is on our side or yours. If the status system itself stops updating, every component shows as unknown rather than falsely green.
When an agency requests access to a client's store, the client must share a short code alongside their account number — without it, the request is refused before it reaches them. This closes the door on unsolicited access requests from unknown agencies. Codes are on by default and can be rotated at any time from the client's workspace settings.
Every store and workspace now has a unique 10-digit account number you can read on the Settings page and quote to an agency or support team over the phone. A separate 6-character request code controls who may ask to link to your account — you can rotate it at any time, or turn the channel off entirely from Settings. Switching the channel back on after it was off issues a fresh code automatically.
Magistry now uses a single shell for both your store and your workspace, so the header, menu, and layout look and behave the same everywhere you go. Agency account holders will find their clients, reports, activity, and billing pool directly inside Workspace rather than in a separate area. The workspace overview now shows managed client stores at the top, so the portfolio no longer appears empty when stores are linked.
The in-app changelog now shows real release notes written for merchants, not raw commit messages. The roadmap carries measured, dated evidence for every claim rather than freeform descriptions. An unread dot appears in the navigation when new entries have been published since you last visited, and the dot clears the moment you open the page.
The Links page now shows every linked product group with images, lets you unlink individual products or entire groups, and lets you turn sync on or off per link rather than all at once. It also clearly explains what a link always shares (what products have learned from each other) versus what only activates when you enable sync. The page is now reachable from the Catalog toolbar, beside Suppliers and Export.
The photo matching that connects the same product across stores now recognises re-encoded or lightly cropped shots as the same image, so genuine matches are no longer missed. The review screen now shows each product at a size where you can actually tell garments apart, and the confidence blurb explains what the score means in plain terms rather than how it is calculated.
Cross-store image linking is now something each workspace explicitly enables, rather than being on by default for any multi-store account. If you have asked to use this feature, your workspace remains active; all other workspaces are off until you choose to turn it on. You can opt in using the Scan workspace button in your links settings.
System status measures itself from the work the platform does, so it sees a sync that fails and not a button that does nothing. Those now get said out loud: a known issue carries what is broken, what you would notice and what is being done about it, at the top of the status panel rather than behind a colour. Report something that turns out to be one of them and your own thread says so, in the same words.
When something looks wrong, the question is whether it is your setup or our platform, and nothing in Magistry answered it. System status now shows each part of the platform, what it covers and whether it is working, with an incident timeline when it is not. It measures itself from the work it does rather than from anything anybody remembers to update, so it is current whether or not we are looking.
One button beside your notifications carries both: the state of the platform and the newest releases. A coloured marker means something is degraded; a quiet one means there is something new to read. It was reachable only from the account menu before, which is a page nobody finds.
// direction
// stay current
// changelog list
// e-mails not sent yet · no tracking pixels
// see it run
Connect your store and choose the Brain's mode — in dry run every decision is logged with what it would have done, and nothing touches your store.
The Brain changes nothing until you choose a mode · Every action logged · Price, status and copy changes can be rolled back
We use cookies to run this site, to see which pages help, and to measure which ads bring people here. You choose per category; everything except the strictly necessary is off until you say otherwise. Cookie policy · Privacy
