Shopify Customer Sync
Keep Shopify customers current from app users without crossing stores or resetting consent.
What it adds
A sync that creates or updates a customer record in the connected store whenever an app user's details or consent change.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the app events that should reach the store — account creation, profile edit, address change, consent change — and sync from those events rather than sweeping every user on a timer.
-
2
Scope every request, every lookup, and every stored identifier to one connected shop. Treat the shop as part of the customer's identity, not as ambient configuration.
-
3
Store the provider's customer identifier against the app user per shop and match on it first, falling back to a normalized email address only when no identifier has been recorded yet.
-
4
Treat marketing consent as something the app records, not something it decides. Carry the consent the app actually captured, with its timestamp and source, and never mark a customer subscribed because they created an account.
-
5
Orders, line items, and fulfilment state are owned by Shopify Order Import; this brief owns the user-to-customer record only. Do not create or modify orders here, and do not write consent from an order payload.
Edge cases it handles
8
Edge cases it handles
8- A workspace connected to more than one store must never resolve a customer by searching across all of them. A lookup scoped to the wrong shop returns another merchant's customer and writes app data into their store.
- Email marketing consent and SMS marketing consent are separate states with separate legal basis. Granting one because the user accepted the other is a compliance failure, not a convenience.
- The store merges duplicate customers and staff delete them. A stored identifier that now points at a merged or removed record must be re-resolved rather than retried forever as a failure.
- Guest checkout produces customers with no account behind them. Do not assume every customer in the store has a matching app user, and do not create app accounts to close the gap.
- If the store also sends customer updates back into the app, each side must ignore the changes it caused itself. Stamp the origin of every write and drop the echo, or one edit will bounce between the two systems indefinitely.
- A user changing their email address must update the existing customer rather than create a second one under the new address.
- The app must not push a blank value over a field a merchant filled in by hand. Send only the fields the app genuinely owns.
- When a store is disconnected or its credentials are revoked, queued syncs must be discarded rather than retried against an account the workspace no longer controls.
Definition of done
8
Definition of done
8- Every request and stored identifier is scoped to a single shop, and a multi-store workspace cannot read across them.
- Email and SMS marketing consent are stored and transmitted independently, each with its captured timestamp and source.
- A user with a stored customer identifier updates that customer; a user without one is matched by normalized email before any record is created.
- Merged, deleted, and guest customers each resolve to a defined outcome rather than a repeating failure.
- Bidirectional updates settle after one pass, with no echo loop between the app and the store.
- Disconnecting a store stops all pending and future syncs for it.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
Paddle Subscription Checkout
Paddle Subscription Checkout
Sell subscriptions through Paddle with entitlements granted only by verified events.
What it does
A Paddle-backed subscription purchase and lifecycle flow where local access follows verified server events and prices stay under server control.
How it works
- 1 Hold the catalogue mapping on the server: which local plan corresponds to which provider offering, at which price and currency. The client passes a plan identifier and nothing about money.
- 2 Carry an account or workspace reference into the checkout so the subscription that comes back can be attached to the right tenant without matching on email address.
- 3 Grant access only from verified server-side events, and store the event identifier so a retried delivery changes nothing a second time.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/paddle-subscription-checkout
WooCommerce Order Sync
WooCommerce Order Sync
Pull WooCommerce orders and customers into the app across stores you do not control.
What it does
A sync of orders and their customers from a connected store, tolerant of custom statuses, taxes, currencies, and plugins.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/woocommerce-order-sync
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.