| | Hello there. Two official changes landed on Monday. The AI knowledge base now lives inside your admin, and the checkout footer folds every policy into a single link. Merchants are also trading warnings about fake Shopify Payments emails, and developers flag gaps in theme partials and staff permissions. In today’s newsletter, we’ll get into: - Knowledge base is now built into the admin under Sales channels, Agentic, and the standalone Knowledge Base app goes away on January 15, 2027.
- The checkout footer now shows one Terms and policies link that opens a modal with all your policies; nothing changes for you unless you are on Plus and want custom links.
- A merchant warns about a phishing campaign using fake Shopify Payments emails, so check the sender before you reply or click anything.
| |
|
| | 🧠 Knowledge base is now built into your admin. The page where you review and publish the facts AI agents get about your store now sits at Sales channels, Agentic, Knowledge base. Shopify drafts facts from your published storefront pages, and none reach agents until you publish them. Stores with fewer than 1,000 facts in the old app were moved over automatically; larger ones must re-add facts before January 15, 2027, per the Knowledge base changelog post. 📄 Checkout now shows one Terms and policies link. Instead of a separate footer link for each policy, checkout now shows a single Terms and policies link that opens a modal where customers pick the policy they want. Your policy text stays the same and there is nothing to do. Plus merchants who want their own links can hide the default footer and add their own policy links with checkout extensions, as the checkout footer update notes. | |
|
| | 🎣 Fake Shopify Payments emails are making the rounds. A merchant is warning about a scam campaign that sends emails posing as Shopify Payments. The message does not come from an official Shopify address, so check the sender, search it before acting and do not reply to it. If anything about your payouts looks off, sign in to your admin directly rather than through a link. The Shopify Payments scam warning has the details. 🛒 Has a hacked app ever hijacked your checkout? A newer merchant heard in Facebook groups about stores whose checkout was redirected to a scammer's page after certain apps were hacked, taking customers' payments. He wants to know if it happened to anyone here. If you have seen it, or know how to spot it, share what you know in the thread. 🔥 BFCM load problems often start in your checkout extensions. With a month to go, one developer says the checks most BFCM lists skip are about your own code, not image sizes. His first example: Shopify's infrastructure scales, but a custom checkout extension that waits on a third-party API may not under peak traffic. If you run extensions like that, read the full BFCM prep list before the rush. | |
|
| | 📊 Is a 40% contribution margin enough to launch on? A first-time founder launching a supplement brand in Australia is left with about 39 to 40% contribution margin after manufacturing, GST, shipping and fulfilment. He wants to know whether that is commercially viable before ad spend and overheads. If you have run the numbers on a similar product, weigh in on his margin question. 📦 Two orders, one address, two different names. A seller received two orders for the same item in different sizes, shipping to one address under a male and a female name. It is probably a couple ordering separately, but the buyers are not answering his offer to combine shipping. He is asking whether to play it safe, and the same-address orders thread is collecting how others handle it. | |
|
| | 🧩 Theme partials cannot fully replace section rendering. A theme team testing partials for variant changes, quick views and upsells hit two blockers: combining section_id with partials returns a 400 error, and the partial-rendering import map only loads on pages that render a partial at first. Their workarounds are an alternate template with no layout and an empty partial in the layout. The partials limitations report asks Shopify for fixes or clearer documentation. 🔑 Developers want apps to define their own staff permissions. A developer building a discount approval workflow for a large merchant says apps can only read broad Shopify staff permissions today, so they either reuse a native permission as a proxy or build their own role system. The app-defined permissions request proposes app-declared permissions such as discount approve or publish, assigned through Shopify roles and also usable in POS extensions. 📱 Shopify built Remote Dev so AI agents can test mobile apps. Shopify Engineering says it built an internal tool called Remote Dev so AI agents can build and test iOS and Android apps without overloading engineers' laptops. The team shared the engineering story behind Remote Dev in a post on Monday evening. | |
|
| | Three remote roles posted in the last two weeks, each linked to its own posting with the source named. Each posting is linked from the source named on its line, with the date it was posted. Check the details on the posting itself. | |
|
|
|
