cronable
E-commerce automation

The busywork behind every order, handled the same way every time.

Cronable automates the work between your storefront, your shipping tool and your team. Big orders are flagged for a second look, low stock is flagged before you sell out, a plain-English sales digest lands every morning, and late shipments are caught while there’s still time. It runs on your own computer or server, its price doesn’t change with your order volume, and the AI assistant builds each workflow from a sentence.

On the canvas

Big orders flagged for a second look

Every paid order is logged. Orders over your threshold also get a quick AI read, and the summary lands in Slack for a person to check.

jobs/shop
Integrations

The tools your week is made of

A store runs on a storefront, a payment processor, a shipping tool and a few channels to reach customers and the team. These are the integrations this page uses.

Shopify

Shopify

The Shopify trigger fires on orders created, paid, fulfilled or cancelled, and on products and customers, by webhook or by polling with no public URL. The action lists and reads orders, products and customers, creates draft orders, or runs a custom query.

Integration details
WooCommerce

WooCommerce

The WooCommerce webhook fires on order, product, customer and coupon events. The action lists orders and products, creates products, or sends a custom request.

Stripe

Stripe

Start a chain on a successful or failed payment or a completed checkout, or list charges and get your balance on a schedule.

Integration details

ShipStation

List orders by status (awaiting shipment, on hold, shipped) and read shipments, stores and carriers.

EasyPost

Track a package, read trackers and shipments, and start a chain on each tracker update with the EasyPost webhook.

Klaviyo

Read profiles, lists, campaigns and metrics, or subscribe a profile to a list.

MailChimp

Mailchimp

Add a subscriber, list audiences and members, or pull campaign reports.

Integration details
Claude

Claude (API)

Summarize a day of orders in plain English, or read an order’s line items and notes and point out what looks unusual.

Integration details
Google Sheets

Google Sheets

Log every order or stock check as a row the whole team can read.

Integration details

Slack

Post the digest, the big-order summary or the low-stock list where the team already looks.

Integration details
Gmail

Gmail

Send a customer a short heads-up from your own Gmail address.

Integration details
Asana

Asana

Open a restock or follow-up task with the details already in it.

Integration details
Workflows

Four store workflows, step by step

Each one is a chain of jobs built from real Cronable job types, and every run is kept with its output and logs.

Big orders flagged for a second look

When a large order is paid…

  1. 1The Shopify trigger fires on Order paid and passes the whole order down the chain.
  2. 2A Sheets step logs every order, whatever its size.
  3. 3A Filter step lets through only orders above the total you set.
  4. 4A Claude (API) step reads the line items, totals and order notes and summarizes anything worth a look, like an unusual quantity or a rush request.
  5. 5A Slack step posts the summary to #orders for a person to check.

Your team reads the orders that matter, with the details already pulled out.

Low stock flagged before you sell out

When the morning starts…

  1. 1A daily schedule runs a Shopify custom query for active products and their variant inventory.
  2. 2A Code step keeps the variants at or under your reorder threshold.
  3. 3A Filter step stops the chain on days when nothing is low.
  4. 4A Slack step posts the list, and an Asana step opens a restock task with the same details.

Reordering starts from a list, not from a sold-out notice.

The day’s sales, in words, every morning

When you want the numbers without opening a dashboard…

  1. 1A daily schedule runs a Shopify step that lists the day’s paid orders.
  2. 2A Claude (API) step writes a short summary: revenue, order count, top products and anything notable.
  3. 3A Slack step posts it to #sales. Add a Stripe step on the same schedule for the payments side.

Everyone starts the day with the same numbers.

Late shipments caught while there’s still time

When orders sit unshipped too long…

  1. 1A schedule at 09:00, 13:00 and 17:00 runs a ShipStation step that lists orders awaiting shipment.
  2. 2A Code step keeps the ones older than your promise, two days for example, and formats a list.
  3. 3A Filter step stops the chain if there are none.
  4. 4A Slack step posts the list to the warehouse channel. If ShipStation can’t be reached, a failure handler emails you.

Late orders get a nudge internally before they turn into a support ticket.

What changes

What changes for the store

The same response to every order, and fewer things that depend on someone remembering.

Every order handled the same way

Logging, checks and notifications run on every order, not just the ones someone happened to notice.

Problems surface early

Low stock, late shipments and unusual orders arrive as a short list in Slack while you can still act on them.

A price that doesn’t grow with orders

Plans are sized by how many jobs you define, not how many times they run. A busy weekend costs the same as a quiet one.

You decide where order data goes

Store and payment credentials stay encrypted on your disk and masked out of every log. Order data goes only where your workflow sends it — through the relay if you use webhooks, to a model step if you add one.

The numbers you report on

  • Order-to-ship time
  • Stockouts per month
  • Orders shipped late
  • “Where is my order?” tickets
  • Time spent on daily reporting

We don’t promise figures. Cronable records every run, so you can measure these yourself, before and after.

Questions

E-commerce automation, answered

Where do my store and payment credentials live?

On the machine Cronable runs on. Shopify, WooCommerce, Stripe and ShipStation credentials are encrypted with AES-256-GCM in a local database, referenced by name in each workflow, and masked out of logs, output and the live stream. The workflow files themselves hold no secrets.

Do I have to expose my computer to receive Shopify webhooks?

No. Webhooks arrive through Cronable’s hosted relay: your machine keeps an outbound connection and collects each event, and the relay holds it for up to 24 hours if you’re offline. Webhooks need a paid plan. The Shopify trigger can also poll for new and updated orders, products and customers instead, with no public URL and no relay.

What happens when a step fails?

If ShipStation times out, for example, the job retries with backoff when you’ve set a retry policy. If it still fails, the steps that needed its output don’t run, and a failure handler tells you why by Slack, email or a task. Cronable can also email you whenever any job fails.

Can I see what happened to a specific order?

Yes. Each run keeps its trigger, status, timing, output and secret-masked logs, so you can open the run that handled an order and see what each step did with it. Run records are kept until you choose to prune them, and full log files are kept for 30 days by default.

Can the AI change orders or issue refunds by itself?

Only if you build a workflow that does. An AI step reads text and returns text, such as a summary or a label, and the next step decides what happens with it. The built-in assistant builds workflows on the canvas for you to review. It has no shell, browser or file tool and never sees a secret value. Anything it runs, and any change that could make a job run on its own, asks you to confirm first, and goes through the same roles and approvals as your own changes. For a team, Business adds SSO, role-based access, the audit trail and four-eyes change approval.

Does it work with WooCommerce and other platforms?

Yes. WooCommerce has its own trigger and action, and Square, Stripe, Klaviyo, Mailchimp, ShipStation and EasyPost are built in. For a platform without a dedicated integration, an HTTP job calls its API with a stored credential, and a webhook trigger can receive its events.

How much does it cost per order?

Nothing per order. You pay for the number of jobs you define (35 on Basic, 250 on Plus), and runs are not metered. AI steps run on your own model account, so that provider bills their usage directly.

Other solutions

Finance & accountingShort-term rentalsAI agents

Automate your operations.

Cronable is launching soon. Join the waitlist and we’ll email you the moment self-serve accounts — and the apps for Mac, Windows and Linux — go live.

Join the waitlist

If it happens on every order, it’s cronable.