Tools & integrations, read from an operations desk

Latest

Shopify lets AI agents finish checkout on merchant stores

Shopify has rolled out WebMCP support for checkout, including Shop Pay, to all eligible merchants. Three new tools — get_checkout, update_checkout, complete_checkout — let browser-based AI agents inspect a checkout, change fields like address or delivery, and submit the order once the buyer authorizes it, without scraping the page.

What changes for operators — If your company sells through a Shopify storefront, buyers can now complete a purchase entirely through an AI agent operating in their browser, rather than clicking through your checkout UI manually. That means your checkout configuration, delivery options and address fields are now effectively an API surface agents will read and act on directly, so any custom checkout logic, upsells, or manual verification steps need to keep working when the operator is an agent instead of a person. Teams that rely on checkout-page behavior for fraud checks or order edits should confirm those safeguards still trigger correctly when orders are placed via get_checkout/update_checkout/complete_checkout rather than the human-facing flow.

Microsoft Prunes Copilot Sprawl, Folds Apps Into One

If your team has been juggling several Copilot variants — one bolted onto Office, another standalone, maybe a third embedded in Teams or Windows — expect logins, permissions and saved chat history to shift as Microsoft merges them. Before that migration lands, audit which Copilot features your sales, support or ops staff actually open weekly versus which ones exist only because IT enabled them by default; Microsoft's own culling is a reminder that usage, not availability, should decide what stays in your stack. Companies that rolled Copilot into workflows via Power Automate or SharePoint integrations should also flag this for their admin to confirm no connectors silently break during the app merge.

Google Lets Users Strip Visible Watermarks From AI-Generated Images

For a 10-200 person B2B company, this is mostly a content-governance issue rather than an automation one: if your marketing or support team uses Google's AI tools to generate images for decks, ads, or knowledge-base articles, you can no longer rely on a visible watermark to distinguish AI-made assets from originals internally or externally. Teams that need to disclose AI-generated content for compliance, client trust, or platform policy reasons (e.g., ad platforms, marketplaces) should build their own tagging or metadata convention now — a simple naming rule or embedded invisible watermark check — rather than depending on the vendor's default visual marker, since that default is about to become optional.