Skip to main content

Week of October 5, 2026

This week was about building and checking loyalty logic before it goes live. You can describe a rule or flow in plain words and get a draft, then backtest a draft event rule against your past events to see what it would have cost. Chat and MCP clients can now manage most of the Hub, always behind a confirmation step. New organizations also get an industry package with the metadata, data models and roles their industry needs.

Highlights​

Draft a rule or flow with Weave AI​

A new Create Rule or Flow quick action in the Hub asks "What do you want to create?" and opens the matching editor. Its Describe it box takes a plain description: select Draft it and Weave AI decides whether you need an event rule or a flow, explains why, and shows a draft card you can open in the editor. Drafts can reuse your audiences and propose counter targets such as a punch card. Nothing is published until you choose to. Learn more

Event rule backtest​

See what a draft event rule would have done before you publish it. The Backtest section of the event rule sheet runs the draft against the latest published version over the last 30, 90, 180 or 365 days, or a custom range, and shows the cost change per currency, how many customers each version rewards and the top customers. The same comparison is available from GET /event-rules/{id}/versions/{version}/backtest and the backtest_event_rule MCP tool.

Chat and MCP cover much more​

Chat can now work with event rules, audiences, flows, offers, customers, coupons, tiers, badges, currencies, targets, event types, data models, metadata, environments and approvals. MCP clients such as Claude Desktop get 39 new tools with the same names and arguments. Every change chat proposes shows a Confirmation card and runs only after you press Confirm, and every MCP tool now requires the same scope as its API route.

Industry packages​

The platform ships Hospitality, Retail and Restaurant packages. A new organization gets the packages for its industries, and admins can list, preview with a dry run and install packages through /package-installations. Records a package installs are marked with its package_code and can't be changed or deleted.

Metadata hierarchies​

View metadata in the Hub as an org-chart tree or an outline, and link types and entries as parent and child. The API rejects links that would make a hierarchy loop back on itself. Learn more

Also this week​

New​

  • Inbound webhook lookups. Inbound webhooks can find a customer by identifier or unique email, and ingest sources can be Shopify-typed. Learn more

Improved​

  • Rate limit guide. The guide now covers limit buckets, plan multipliers, 429 and 503 responses and backoff. Learn more
  • New look. The Hub and dashboard use a new teal and sage style with Figtree headings and larger touch targets.
  • Chat models. Chat now runs on Claude Sonnet 5.5 and Claude Haiku 5.5.
  • Segment counts in the API. The CustomerSegment schema lists its member count and computation status, so SDK types include them.

Fixed​

  • Per-line-item awards. Rules that award an amount per line item now issue each item's own amount, and per-item caps apply per item.
  • Coupon returns. You can record a Return on a used coupon, and coupons show held and multi-use states. Learn more
  • Audience member counts. The Audiences list shows each segment's computed count and when it was last computed, not 0.
  • Hub sign-in. Reloading a page or opening a shared Hub link keeps you signed in on the same page.
  • Rewards Portal add-on controls. Only users who can manage the add-on see its enable and cancel controls.
  • Metadata forms. Create sheets start empty, and the type pickers no longer offer a type that would loop the hierarchy.