WooCommerce Order Sync
Pull WooCommerce orders and customers into the app across stores you do not control.
What it adds
A sync of orders and their customers from a connected store, tolerant of custom statuses, taxes, currencies, and plugins.
What your agent is told to do
5
What your agent is told to do
5-
1
Treat the store's configuration as unknown at build time. Read the statuses, tax rows, currencies, and payment methods the store actually reports rather than hard-coding the defaults a stock install ships with.
-
2
Map any unrecognized order status onto a defined local fallback and keep the raw value alongside it. A plugin-defined status must never be read as complete by accident.
-
3
Verify every incoming webhook against the store's shared secret before acting on it, and key the resulting write on the store plus the order identifier so redelivery is harmless.
-
4
Hold a cursor for the sync and resume from it after an authentication failure or a rate limit. Do not restart the whole sync from the beginning after a transient failure; that reprocesses months of orders and buries the actual error.
-
5
Where the app also writes back to the store, stamp the origin of each write and ignore updates the app itself caused. This has the same shape as Shopify Order Import, so keep one shared import pipeline and vary only the provider adapter.
Edge cases it handles
8
Edge cases it handles
8- Self-hosted stores run arbitrary plugins. An order may carry statuses, fee lines, tax rows, and meta fields the app has never seen, and none of them may abort the import.
- An unverified webhook is an untrusted request from the open internet. Reject anything whose signature does not match, and never fall back to trusting the payload because the signature header was absent.
- Redelivery is normal and must be safe. Two deliveries of the same order update must leave exactly one local record in the same final state.
- Products and customers get deleted after the order that references them. The order must remain importable from the values it captured at the time, with the missing reference marked rather than the row rejected.
- If the app writes status back into the store, the store's own webhook returns that change. Ignore echoes of the app's own writes, or the two systems will trade updates without end.
- Expired credentials and rate limits are temporary conditions. Pause the sync, retain the cursor, surface the reason where an operator will see it, and resume from that point rather than dropping the window.
- Stores in other locales report dates in the site's own time zone and decimals with a comma separator. Normalize both on the way in rather than assuming one format.
- A store that is offline or mid-upgrade returns an HTML error page instead of structured data. Treat an unparseable response as a retryable failure, never as an empty list of orders.
Definition of done
8
Definition of done
8- Orders import from stores with custom statuses, tax rows, and plugin fields without failing.
- Unrecognized statuses map to a defined local state and the raw value is retained.
- Webhooks are signature-verified, and repeated delivery of the same event changes nothing after the first.
- Orders referencing deleted products or customers remain intact with the missing reference marked.
- The sync resumes from its last cursor after an authentication or rate-limit interruption, with the reason visible to an operator.
- Bidirectional updates terminate; no order oscillates between the app and the store.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Lemon Squeezy License Sync
Lemon Squeezy License Sync
Sync Lemon Squeezy orders and license keys into the app's entitlement state.
What it does
A verified event pipeline mapping Lemon Squeezy orders, subscriptions, and license keys onto local entitlements, with activation limits and revocation handled.
How it works
- 1 Verify the authenticity of every incoming provider event before it changes anything. An unverified purchase notification is a request from the internet to give away your product.
- 2 Keep an explicit server-side table mapping each purchasable variant to the entitlement it grants. Do not infer the plan from a product name, because names get edited for marketing reasons and entitlements should not move when they do.
- 3 Bind each license key to a single account on first activation and refuse to activate it against a different one afterwards, with a documented path for an operator to release a key that genuinely needs to move.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/lemon-squeezy-license-sync
Stripe Customer and Subscription Sync
Stripe Customer and Subscription Sync
Keep local billing state matching Stripe as subscriptions, invoices, and plans change.
What it does
A verified event pipeline that projects Stripe customer, subscription, and invoice state onto the app's own access records, with reconciliation for anything the pipeline missed.
How it works
- 1 Define one local projection of billing state per account: which plan, which status, which period it runs to, and whether access is currently allowed. Every entitlement check in the app reads that projection and nothing else.
- 2 Verify every incoming event as genuinely from the provider before acting on it, and record its identifier so a replay is recognised and ignored. Providers retry on any non-success response, so handlers must be safe to run repeatedly.
- 3 Store a timestamp or version with the projection and refuse to apply an event that is older than what has already been written. Events arrive out of order, and a stale cancellation overwriting a fresh renewal locks a paying customer out.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/stripe-customer-and-subscription-sync
Shopify Order Import
Shopify Order Import
Import Shopify orders into the app with money, fulfilment, and later edits accurately kept.
What it does
A resumable import of the connected store's orders, mirroring line items, discounts, taxes, and fulfilment state locally.
How it works
- 1 Separate the initial backfill from the ongoing feed. The backfill walks history in a stable order behind a resumable cursor; the feed applies live updates as they arrive.
- 2 Key every imported order on the shop identifier together with the store's own order identifier, so re-running the import updates existing rows instead of duplicating them.
- 3 Store money as an exact decimal with its currency alongside it, and keep both the shop currency and the presented currency where they differ. Do not convert to a single display currency on the way in, because the original amounts cannot be recovered afterwards.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/shopify-order-import
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.