Product note: Starter playbooks in Arcanum Engine

When we first launched the Starter plan for Arcanum Engine, it came with three email playbooks.

They were useful. A merchant could watch inventory, receive a weekly revenue summary, and catch abandoned checkouts that might need attention.

But the experience was narrower than we wanted.

It was enough to show what Engine could do, but not always enough to help a smaller team build a real operating rhythm around it. Merchants could see the potential, yet often reached the edge of the plan before they had a chance to make it part of their day-to-day work.

The latest release changes that.

Starter now includes fourteen email playbook variants across revenue recovery, operations, retention, customer experience, and merchandising. The plan still allows three active playbooks at a time, and alerts are still sent through the merchant’s own Resend account.

The difference is that those three slots can now be used in far more useful ways.

A founder might choose a weekly revenue summary, a low-inventory alert, and a fulfillment warning. A small CX team might focus on abandoned checkouts, dormant customers, and high-value orders. A merchandising lead might watch slow-moving stock, orphaned products, and new-product readiness.

Starter is still intentionally focused. It just no longer feels like a preview of the real product.

Hollow read: The Starter playbooks use the same core trigger logic as their Growth counterparts. The main differences are where the alert goes and how many automations can run at once.

What changed

The original Starter playbooks are still there:

• Inventory Guardian: Alerts the team when tracked inventory falls below a set threshold
• Revenue Watch: Sends a weekly summary of orders, revenue, trends, and top products
• Winback Engine: Surfaces idle checkouts so the team can decide whether to follow up

We have now added email versions of several workflows that previously depended on Growth-level team channels.

That includes:

• Fulfillment SLA
• Back-in-Stock
• Refund Alert
• Daily Ops Digest
• High-Risk Order
• Dormant Customer Winback
• Review Accelerator
• VIP Recovery
• Slow Mover Digest
• New Product Launch Checklist
• Orphan Product Alert

These are not simplified placeholders created to fill out the Starter catalog.

For the most part, they use the same trigger logic as the Growth versions. Inventory Guardian watches the same inventory conditions whether the alert is delivered by email or posted to Slack. High-Risk Order still detects elevated fraud risk, although automatic order tagging in Shopify remains part of the Growth workflow.

We made that distinction deliberately.

A smaller merchant may not need Slack, Microsoft Teams, Klaviyo, or ten automations running at once. That does not mean they should receive a weaker version of the underlying signal.

Email is the delivery layer, not the customer journey

Starter alerts are sent to the merchant’s team. They do not email shoppers directly.

Before a playbook can go live, the merchant connects a Resend account under:

Settings → Email alerts

The setup includes a Resend API key, a verified sender address, and the team inboxes that should receive alerts. There is also a connection test, because finding out that an API key is wrong after the first important alert should not be part of the onboarding experience.

The install flow now shows a preview of the email during the Review step. Merchants can see what the alert will look like and who will receive it before activating the playbook.

We also made slot usage more visible in Command Center.

Starter allows three active playbooks. The interface now shows that usage clearly and warns the merchant when the final slot is about to be filled. The same check applies when a paused playbook is resumed.

There is nothing especially glamorous about plan-limit logic, but it matters. A merchant should understand the tradeoff while choosing a workflow, not after the system refuses to run it.

We wanted Starter to show its work

One of the easiest mistakes in automation software is to confuse activity with value.

An email arrives, so the automation must be working. A run appears in a log, so the system must be helping. A dashboard has several green indicators, so something meaningful must be happening.

That is not always true.

Starter merchants now get the same basic Command Center structure as Growth:

• A guided launch checklist
• A commerce operating score
• System coverage indicators
• A Results log for every playbook run

The launch checklist takes the merchant through the first important steps: connect alert delivery, set the commerce profile, install a playbook, confirm a successful run, and add Revenue Watch.

The operating score looks across five areas:

• Growth
• Operations
• Retention
• Experience
• Automation

When Engine finds a gap, it links the merchant to a relevant playbook rather than simply showing a lower score and leaving them to work out what to do next.

Results records each run, its status, and any useful directional impact. Depending on the playbook, that might include checkout value surfaced, an order flagged, a low-stock condition detected, or a product that needs merchandising attention.

The point is simple: getting an alert is useful, but knowing why it fired and what happened next is better.

Merchandising finally has a practical Starter path

Three of the new Starter playbooks focus on product and catalog hygiene.

Slow Mover Digest

This is a weekly view of products that still have stock but have not generated recent sales.

It does not decide what the merchant should do with them. It gives the team a cleaner place to start.

Some products need better placement. Some need a bundle. Some need a different story. Some probably need a markdown. The alert is there to surface the question before inventory quietly sits for another quarter.

New Product Launch Checklist

When a product is created, Engine sends a reminder to check the details that are easy to miss during a rushed launch.

That includes collection placement, merchandising readiness, and storefront visibility.

A product can be fully configured in Shopify and still be difficult to find, poorly grouped, or launched without the supporting pieces the team intended to add later.

“Later” has a habit of becoming permanent.

Orphan Product Alert

This weekly digest finds active products that are not assigned to a collection.

They may exist in the catalog, appear through direct links, and technically be available for sale. But from a shopper’s point of view, they can be almost invisible.

Growth merchants can install these workflows together as part of the broader Merchandising Ops system. Starter merchants install them one at a time and decide whether each deserves one of the three available slots.

Three slots can still cover a lot

The slot limit forces a decision, which is not necessarily a bad thing.

Most smaller teams do not need every possible automation running on day one. They need the few that remove the most uncertainty from the week.

An operations-focused setup might use:

• Inventory Guardian
• Fulfillment SLA
• Daily Ops Digest

That gives the team a morning summary and two exception alerts for issues that should not wait until someone happens to notice them in Shopify Admin.

A recovery-focused setup might use:

• Winback Engine
• VIP Recovery
• Dormant Customer Winback

That covers abandoned checkouts, valuable customer moments, and customers who have stopped purchasing.

A founder-led store might choose:

• Revenue Watch
• Inventory Guardian
• Slow Mover Digest

That creates a basic weekly rhythm around revenue, stock pressure, and products that are not moving.

There is no universally correct Starter stack. The right three playbooks depend on what the team is currently dropping, delaying, or discovering too late.

Where Growth begins to make sense

Starter is currently priced at $29 per month after a seven-day trial. Growth is $79 per month.

The difference is not just a larger catalog.

Growth includes:

• Ten active playbook slots
• Slack, Discord, and Microsoft Teams delivery
• Klaviyo, Recharge, and Gorgias connections
• Storefront tracking
• Commerce systems and industry packs
• The broader Engine playbook library

Some workflows remain Growth-only because they depend on data Starter does not collect.

Browse abandonment and cart abandonment require storefront tracking through the theme app embed or headless API bridge. Replenishment Reminder depends on subscription or reorder data.

Those are not arbitrary upgrade gates. The supporting infrastructure is genuinely different.

For most merchants, the point to upgrade should become fairly obvious. The team wants alerts in Slack. Three active playbooks are no longer enough. A workflow needs Klaviyo or Recharge. Storefront behavior needs to become part of the operating picture.

Until then, Starter should be able to do useful work on its own.

Getting the first playbook live

The setup path is intentionally small:

1. Install Arcanum Engine and choose Starter.
2. Connect Resend under Email alerts.
3. Set the commerce profile and primary goal.
4. Install the first playbook.
5. Trigger a test event.
6. Confirm a successful run in Results.

Inventory Guardian can be tested by lowering tracked inventory below the configured threshold.

Winback Engine takes a little longer because the checkout must remain idle for the selected delay, plus up to five additional minutes. The checkout tab should be closed after the email is entered. Engine will not treat a checkout as abandoned while the shopper is still actively editing it.

That last Results check is the important part.

Installing an automation is setup.

Seeing it complete a real run is when it begins to become part of the store.

Sentinel and Engine are beginning to work more closely

When Hollow Sentinel and Arcanum Engine are installed on the same store, Engine can surface opportunities detected by Sentinel inside Command Center.

The merchant can move from the detection into the matching playbook installation path.

We are still tuning how those recommendations are ranked. A Starter merchant should see the available email workflow when one exists, rather than being pushed toward a Growth version by default.

The useful measurement here is not how many recommendations Engine can display.

It is how quickly a merchant can move from a real issue being detected to a successful response running in the store.

What we are watching

There are several areas we are paying close attention to as this release gets used in real stores.

We want to see whether weekly merchandising alerts are enough to change behavior or whether merchants need more context before acting on slow-moving stock.

We are watching whether teams prefer Engine to handle operational detection while Klaviyo remains responsible for customer messaging. That separation feels sensible to us, but actual merchant workflows matter more than the diagram.

We are also measuring the handoff between Sentinel and Engine, particularly the time between detection, playbook installation, and the first successful run.

Storefront signals remain another active area. Browse and cart activity can be valuable, but only when the alerts are accurate enough to deserve a team’s attention.

These are product questions we are actively working through, not promises attached to release dates.

The bottom line

Starter used to be a narrow introduction to Arcanum Engine.

It is now a credible operating layer for a small Shopify team.

Fourteen playbook variants give merchants enough choice to cover the parts of the business that currently need attention. The three-slot limit keeps the setup focused. Resend keeps delivery simple. Command Center and Results make it easier to see whether the workflows are actually doing anything.

Some stores will outgrow Starter quickly. Others may run comfortably on three well-chosen playbooks for a long time.

Both are valid outcomes.

The plan should become too small because the merchant’s operation has grown—not because the useful workflows were held back from the beginning.