# Shopify Editions 2026: What Actually Changed for Store Owners Running Support > Shopify Editions 2026 filtered for support impact: the default-on Agentic channel, the Knowledge Base app, and the returns confirmation step that matter. Source: https://arbyn.app/blog/shopify-editions-2026-what-actually-changed-for-store-owners-running-s Published: 2026-07-18 --- Shopify Editions 2026 shipped more than 150 updates in its Summer release alone, and most coverage of it reads like a changelog: a long list of features grouped by department. For a store owner running support, a small number of these updates actually change what shows up in the support inbox, and they're not the ones getting the most attention. Shopify releases Editions twice a year, and each one gets covered the same way across the ecommerce press, ranked by department or by how many features shipped, rather than by which ones actually touch a customer conversation. I read every Editions release the same way now: not what's new, but what's about to change my ticket volume. Odera Joseph Echendu, Founder, Arbyn The Change With the Biggest Long-Term Implication: Agentic Is Now Default-On The Summer '26 "Everywhere Edition," announced June 17, 2026, made the Universal Commerce Protocol enabled by default on every Shopify store, not an opt-in feature a store has to activate. UCP is the standard that lets AI shopping agents read a store's catalog and build carts, meaning every Shopify store's products became discoverable to AI agents automatically, without a separate setup step. Alongside this, a new "Agentic" section now appears in every store's admin, listed as its own sales channel with a quick-access link in the left-hand navigation, giving a single place to see how products surface to AI agents, track agent-driven performance, and manage AI channel connections. Making this section useful, rather than just present, requires specific catalog hygiene most stores haven't prioritized yet: consistent product attributes, accurate catalog structure, and complete metafield definitions, since structured product data is exactly what determines whether an AI agent surfaces a specific product accurately or misses it entirely. This connects directly to the Instant Checkout retirement covered elsewhere on this blog, where the reported failure mode was inaccurate product data breaking the experience at the exact moment a purchase needed to happen. The Agentic admin section gives a store owner the tools to check this data quality directly, but checking it isn't automatic just because the section exists. This matters for support planning specifically because it removes the "should I activate this" decision entirely. A store that hasn't looked at its own Agentic admin section since this rolled out may already be receiving AI-referred traffic and orders without having made an active choice to participate, which means the support-volume planning covered elsewhere on this blog, expecting a WISMO or sizing question two to five days after an AI-referred order lands, applies by default now rather than as something a store opts into deliberately. Shopify's Own Knowledge Base App: A Free Tool Worth Understanding, Not Confusing With a Support Agent Alongside the Agentic default, Shopify introduced a free Knowledge Base app that feeds FAQ content directly to AI shopping agents. This is explicitly not a customer-facing support tool. It's a structured content layer that lets external AI agents, ChatGPT, Gemini, Copilot, answer questions about a store using content the store owner controls, separate from whatever FAQ page already exists on the storefront itself. The app also lets a store owner see what questions customers are actually asking these AI agents, which is a genuinely useful, previously invisible data source about pre-purchase questions a store never used to have visibility into, and one worth checking periodically even for a store not actively managing its Agentic presence, since it surfaces question patterns a store's own support channel might not be capturing. The practical task this creates, rather than eliminates, is duplicate content maintenance: a store now has its customer-facing FAQ page, its own support tool's knowledge base if it uses one, and this new Shopify-hosted Knowledge Base feeding AI agents, and keeping all three consistent as policies or products change is a new, easily overlooked maintenance burden. A store updating its return policy needs to remember there are now potentially three places that policy lives, not one, and a policy updated in only one of the three creates a genuine risk: an AI shopping agent citing an outdated return window because the Shopify Knowledge Base app was never updated to match a policy change made on the storefront itself, or vice versa. This is a new category of accuracy risk that didn't exist before external AI agents had a direct feed into store-controlled content, and it's worth a specific line item in whatever process a store already has for updating policies, rather than assuming the Knowledge Base app updates itself alongside a storefront FAQ edit. Fulfillment and Inventory Changes With Direct Support Implications Several less-headlined changes in Shopify Editions 2026 affect support volume more directly than the flashier AI announcements. A returns confirmation step now requires marking a return as physically received before sales and tax reports update, which improves return accuracy and reporting, according to multiple 2026 Editions summaries, but also means a customer checking their refund status immediately after shipping an item back may see it as still pending until a store owner manually confirms receipt, a new source of "where's my refund" contacts distinct from the WISMO category covered elsewhere on this blog. This is exactly the kind of change that reads as a minor accounting improvement in the release notes and shows up weeks later as a genuine, traceable spike in a specific complaint type, once enough customers have shipped a return and started wondering why their refund hasn't processed yet. Refunds can now be issued as store credit directly from admin or POS, regardless of how the original purchase was made, which gives a store owner a genuine retention tool for handling a return without losing the sale outright, but requires the support team to know when and how to actually offer it, since the mechanism existing doesn't mean it's being used in a customer conversation. A support agent unaware this option exists will default to a standard refund every time, missing a genuine retention opportunity Shopify Editions 2026 specifically built in but that requires a deliberate decision to actually use. Inventory transfers now carry a full audit trail connected directly to purchase orders, and partial shipments can create multiple linked transfers rather than one messy record, which reduces the specific kind of internal confusion that leads to a support agent giving a customer inaccurate stock information. Orders can now be filtered by custom metafields, total value, and weight for smarter fulfillment workflows, and duties, taxes, and totals now recalculate automatically when changes are made to unfulfilled orders, reducing a specific category of billing-discrepancy questions that used to require manual recalculation and a follow-up email to the customer explaining the correction. New carrier additions, Purolator in Canada, SEUR in Spain, BRT in Italy, alongside carrier preference settings letting a store prioritize preferred carriers per zone, give more control over exactly the kind of delivery variability that drives WISMO contacts in international markets specifically. A quieter change worth flagging directly: orders can now be grouped into batches and fulfilled through a customizable pick, pack, scan, and ship workflow, and customers can request to cancel an order before fulfillment or return it after fulfillment directly from the order status page, rather than needing to contact support to initiate either action. This is a genuine self-service deflection mechanism for two request types that previously required a support conversation to even start, and a store that hasn't checked whether this is enabled and correctly configured on its order status page is leaving a real deflection opportunity unused. The specific mechanics of this self-service cancellation and return request worth understanding before assuming it works the way a store owner might expect: the customer's request still needs a store's own review and approval in most configurations, it isn't a fully automatic, no-human-involved cancellation, which means the feature reduces the friction of a customer initiating the request without necessarily removing the human decision point on the store's side. A store treating this as fully automated, without checking how approvals are actually routed, risks a customer assuming a cancellation request was processed the moment they submitted it, when in practice it's sitting in a queue waiting for a store owner or support agent to act on it, which is itself a new potential source of confusion if expectations aren't set clearly on the order status page copy itself. What Most of the 150-Item List Doesn't Touch Support At All It's worth being explicit about what this Editions cycle shipped that a support-focused store owner can safely skim past. Native B2B net terms with automated invoicing, expanded multi-currency payouts to the US, Hong Kong, and Singapore, a B2B Flow automation builder for auto-approving wholesale orders, and multi-location entity management under one admin are all genuinely significant for stores running wholesale or enterprise operations, but none of them touch a typical DTC support conversation. POS v11's unified staff permissions, offline checkout mode, and handheld terminal hardware matter enormously for a store with physical retail locations and not at all for a purely online store. Developer-facing changes, expanded API access, Hydrogen compatibility improvements, expiring OAuth tokens, matter to whoever maintains a store's technical infrastructure and are invisible to the support team and to customers. This isn't a criticism of Shopify's release cadence, a platform serving millions of stores across wholesale, retail, and pure DTC operations should ship features across all of those use cases in the same release. It's a reminder that "150+ new features" is not the same claim as "150+ things your support team needs to know about," and treating every Editions announcement as equally urgent is a good way to spend time on B2B automation details while missing that the returns confirmation step quietly changed what a "where's my refund" conversation actually requires. Sidekick's Growing Scope, and Why It Stays a Different Tool Sidekick continued evolving this cycle into a fuller store-management assistant: it can now help forecast inventory needs by looking at sales velocity and current stock, generate purchase orders directly from that forecast, and support multi-step admin tasks rather than single commands, with 20-language support added to broaden who can use it globally. One limitation worth flagging for any store actually relying on this: there's currently no way to store supplier minimum order requirements, so Sidekick's purchase order recommendations don't yet account for a supplier's minimum quantity or dollar thresholds, meaning a store owner still needs to manually check Sidekick's suggestion against known supplier minimums before finalizing an order. The connection between Sidekick's expanding admin scope and support operations is indirect but real: a store owner spending less time on manual inventory forecasting and purchase order drafting has more attention available for the customer conversations that actually need a human's judgment, the escalations, the edge cases, the ones a support agent, human or AI, flagged as needing owner-level attention. This is a genuine, if modest, second-order benefit of Sidekick's growth, freed owner time that could go toward support quality, though it depends entirely on a store owner actually redirecting that freed time toward support rather than toward some other part of the business. This is worth stating plainly given how often "Shopify AI" gets used as a catch-all term covering everything from customer-facing chat to internal admin tooling: Sidekick is a tool for the store owner managing their own store, not a customer-facing support agent, and its growing capability doesn't change what a store needs to handle actual customer conversations, which remains the job of whatever support tool is installed for that purpose. A store owner impressed by Sidekick's expanding admin capabilities should not conflate that with progress on the separate question of who's handling customer support conversations, since the two are entirely different products solving entirely different jobs. What to Actually Do With an Editions Release Going Forward The practical filter worth applying to any Editions release, this one or the next, is the same one worth applying to individual Shopify checkout changes covered elsewhere on this blog: does this create a hard deadline, does it touch how customer data gets entered or displayed, and does it change what shows up in a support conversation versus purely what happens in the admin. Most of what shipped in this cycle, POS improvements, B2B tooling, developer API changes, matters enormously to specific store types without touching support ticket volume directly. The Agentic default-on change, the Knowledge Base app's content duplication burden, and the returns confirmation step are the three from this cycle that actually belong on a support team's radar, not the full 150-item list. A practical process worth adopting for every future Editions release, rather than reading the announcement once and moving on: skim the full list for anything with an explicit deadline first, since those create binary before-and-after risk the way the Scripts retirement did earlier this year. Second, scan specifically for anything touching order status, returns, refunds, or address handling, since those are the categories most directly tied to support conversation volume and type. Third, check whether anything changed silently that a support team would only discover through a customer's confused question, the returns confirmation step being the clearest example from this cycle, a change that reads as a minor accounting improvement in Shopify's own release notes but generates a real, predictable new complaint pattern once customers start noticing their refund status sitting at "pending" longer than expected. Fourth, and specific to any AI-related announcement in an Editions release going forward: confirm whether the change is customer-facing, like the Agentic default, or store-owner-facing, like Sidekick's growing admin capabilities, since Shopify's own framing doesn't always make that distinction obvious at a glance, and conflating the two leads to either overestimating what's changed for customers or underestimating what's changed for the store owner's own workload. Where This Points None of the changes covered here require Arbyn to integrate directly, since Arbyn's job starts once a conversation begins, regardless of which Editions-era feature generated the order or the question behind it. What does matter is treating each Editions release as a support-planning input, not just a platform news item: a default-on Agentic channel means AI-referred order volume, and the support conversations that follow it, apply to every store now rather than the subset that opted in, and a returns confirmation step means a specific new category of "where's my refund" contact should be expected rather than treated as a mystery when it shows up. The honest reading of Shopify Editions 2026 for a support-focused store owner isn't the 150-item list Shopify itself publishes. It's the much shorter list of changes that actually touch a customer conversation, and those are worth tracking release over release, independent of which changes get the most attention in the broader Editions coverage. Every future Shopify Editions release deserves the same filter: skip the department-by-department feature count, and go straight to what changed in how a customer's order gets entered, tracked, returned, or refunded, since that's the part of any Editions release that actually shows up in a support inbox weeks later. --- ## Pricing - **Arbyn Starter** - $0/month, permanently free. 150 conversations / month. Resets 1st of each month. - **Arbyn Agent** - $99/month flat, unlimited conversations. Or $990/year (2 months free, saves $198, 17% off). - **There is no trial.** Billing starts immediately on the Agent plan. The free Starter plan is permanent. - The conversation cap is the only difference between plans. There is no feature gating. ## Channels Live today: **support email** and **on-site live chat**. That is the complete list. SMS, Instagram DMs, Facebook Messenger, WhatsApp and Voice are on the roadmap and are NOT live. Arbyn does not edit orders or change line items. Money-moving actions (cancel, refund, discount, gift card, reship, return) require the store owner's approval, and then Arbyn performs them. Running them fully autonomously is a beta authorization and is in development. Shipping address changes are already autonomous. ## What Arbyn does on a Shopify order - **Change the shipping address**: Live. Arbyn does this on its own. Arbyn updates the shipping address on the Shopify order itself, inside the conversation, and writes the change to the order timeline. - **Cancel an order**: Live. You approve it, then Arbyn cancels the order. Anything that moves money waits for the store owner's approval. That is a deliberate control, not a missing feature. Once you approve, Arbyn fires Shopify's order cancellation itself and confirms it to the customer. - **Issue a refund**: Live. You approve it, then Arbyn issues the refund. Arbyn prepares the refund against the original payment method and sends it to you. On approval it files the refund in Shopify. You can cap the value it is allowed to prepare, per channel. - **Apply a discount**: Live. Arbyn creates a real Shopify discount and applies it to the cart, handing the shopper a checkout with the code already on it. It can also issue a discount code on an order once you approve it. - **Send a gift card, or reship an order**: Live. You approve it, then Arbyn does it. Arbyn creates the gift card, or raises the replacement order, in Shopify once you approve. - **Start a return**: Live. You approve it, then Arbyn opens the return. Arbyn opens the return in Shopify on your approval. - **Look up a gift card or store-credit balance**: Live. Arbyn does this on its own. "Do I have store credit left?" is a question most support tools answer with a human. Arbyn reads the balance itself, for a verified customer or from the code they give you, and reports the masked card, the balance and the expiry. If there is no card, it says so rather than guessing. - **Handle a subscription question**: Live. You choose what it does. Arbyn knows which of your products are sold as a subscription, shows that on the product card in the conversation, and sends a subscriber to their subscription management page to pause, skip or cancel. It answers how your subscriptions work from your own knowledge, but it does not read an individual customer's contract, so it will not state their renewal date or status. Most cancels are a customer with product piling up, and the fix is getting them to the page where they can slow the cadence down. Reading the contract itself is on the roadmap. - **Answer support email and live chat**: Live. Arbyn reads every inbound support email and every chat, works out the intent, pulls the live Shopify context, and replies in your brand voice. Money-moving actions (cancel, refund, discount, gift card, reship, return) require the store owner's approval, and then Arbyn performs them. Running them fully autonomously is a beta authorization and is in development. Shipping address changes are already autonomous.