Multiple shops in different timezones. How does Crontap handle that?

One schedule per shop. Each schedule carries its own IANA timezone (Europe/London, America/Los_Angeles, Asia/Tokyo, anything tzdata recognises) and its own per-schedule headers. Cron expressions resolve in the schedule's timezone, so 22:30 means 22:30 locally for each shop.

Will Shopify rate-limit me if I poll the Admin API every minute?

It can. Shopify enforces a leaky bucket on the REST Admin API and a points-based budget on the GraphQL Admin API. For most shops a 5 or 10 minute poll is plenty, with bursts gated by the API itself. Crontap retries on 429 with backoff so the schedule self-throttles when needed.

Where does Action Scheduler fit on a WooCommerce store?

Action Scheduler is the queue. The WooCommerce spoke wires Crontap to the wp-cron.php tick that drains it. With Crontap pinging every minute, Action Scheduler's per-task scheduling becomes accurate, instead of only firing when a visitor happens to load a page.

Use cases · E-commerce

E-commerce cron jobs and scheduled API work

Shopify Flow fires on events. WooCommerce depends on wp-cron. The spokes below cover the polling, syncing and reconciliation work that needs a real clock behind it.

About this topic

E-commerce

2 itemsUse cases

Most e-commerce platforms ship event triggers but no cadence. Shopify Flow reacts when an order is created or a tag is added, not when 22:30 rolls over in the shop's timezone. WooCommerce has a real queue (Action Scheduler) but the queue only drains when wp-cron fires, which only fires on visitor traffic. The work that needs scheduling, polling the Admin API for new checkouts, generating end-of-day reports per shop, retrying abandoned carts, sits outside the platform's native triggers.

Crontap drives that work from the outside. One schedule per shop, in the shop's IANA timezone, with custom headers carrying the Admin API token or the REST credentials, retries for the inevitable 429s. The Shopify spoke covers Admin API polling at any cadence. The WooCommerce spoke fixes the wp-cron dependency so Action Scheduler actually drains. Both pair with failure alerts so a missed nightly inventory sync surfaces in your ops channel instead of next morning's audit.

Use cases on E-commerce

2 items

Related on Crontap

The same E-commerce topic, from other angles.

Blog on E-commerce2
See the blog pages tagged E-commerce.

FAQ

Common questions on E-commerce

Multiple shops in different timezones. How does Crontap handle that?: One schedule per shop. Each schedule carries its own IANA timezone (Europe/London, America/Los_Angeles, Asia/Tokyo, anything tzdata recognises) and its own per-schedule headers. Cron expressions resolve in the schedule's timezone, so 22:30 means 22:30 locally for each shop.
Will Shopify rate-limit me if I poll the Admin API every minute?: It can. Shopify enforces a leaky bucket on the REST Admin API and a points-based budget on the GraphQL Admin API. For most shops a 5 or 10 minute poll is plenty, with bursts gated by the API itself. Crontap retries on 429 with backoff so the schedule self-throttles when needed.
Where does Action Scheduler fit on a WooCommerce store?: Action Scheduler is the queue. The WooCommerce spoke wires Crontap to the wp-cron.php tick that drains it. With Crontap pinging every minute, Action Scheduler's per-task scheduling becomes accurate, instead of only firing when a visitor happens to load a page.

Topics across the site.

Every topic Crontap covers, in one row. Each one has its own page on the use cases surface.

Ready to fix it?

Point Crontap at any URL. Pick any cron. Done.

WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.

Get started See examples

Free forever tier ・ No credit card required

GET

/wp-cron.php?doing_wp_cron=1

Running

Your next schedule

Schedule

"every 5 minutes"