WordPress stores for agencies: ten clients, one key.
The Agency plan covers ten sites for $499 a year or $1,349 once, with all 35 add-ons on each. Hand clients a Store Manager login, keep the credentials, and provision new builds from the REST API or WP-CLI.
Activate, deactivate, move.
Paste the same key into each client site under Ambikly → Settings → License. A site is identified by its domain, so staging and production count separately while both are activated; deactivating from the site or your account frees the slot. The key re-validates daily and never blocks a store.
- 10 activations per key
- Deactivate to move a slot between clients
- Lapsed key pauses add-ons only — data and orders untouched
Give clients a store, not the keys to the server.
Store Managers run the shop — products, orders, customers, coupons, shipping, tax, add-ons. Support Agents read orders, customers and reports. Neither can touch settings, payment credentials, webhooks or import/export; those stay with the Administrator account you keep. Roles self-heal on every admin load.
- Store Manager: change things
- Support Agent: read-only
- Every REST route enforces the same capabilities
- Owner — Store Manager
- Fulfillment — Store Manager
- Customer care — Support Agent
- You — Administrator (settings, credentials)
Theme it, script it, hand it over.
Storefront blocks render in PHP and follow the client’s theme; any template can be overridden from the theme’s ambikly/ folder. The setup wizard steps, products, zones, tax rates and settings are REST endpoints, and WP-CLI exports and migrates — so a new build can be a script, not an afternoon.
- Template overrides at {theme}/ambikly/
- Wizard steps as REST endpoints for scripted setup
- Product CSV import for catalog migrations
- Webhooks to your agency tooling, HMAC-signed
SITE=https://client-one.example
wp plugin install ambikly.zip ambikly-pro.zip --activate
curl -u agency:xxxx -X POST "$SITE/wp-json/ambikly/v1/setup/store" \
-d name="Client One" -d country=US -d currency=USD
curl -u agency:xxxx -X POST "$SITE/wp-json/ambikly/v1/setup/pages"
curl -u agency:xxxx -F [email protected] "$SITE/wp-json/ambikly/v1/import/products"What changes at the Agency tier.
| Item | Pro | Agency |
|---|---|---|
| Sites | 1 | 10 |
| Add-ons | All 35 | All 35 |
| Yearly | $199 | $499 |
| Lifetime | $549 | $1,349 |
| Support | Priority email | Priority email, 10 sites |
| White-label | No | No — not in the current release |
| Transaction fees | None | None |
Agency questions.
How many client sites does Agency cover?
Ten activations on one key. Deactivate a site from your account to free a slot for a new client.
Can I remove Ambikly branding for clients?
Not in the current release — there is no white-label option. Clients see “Ambikly” in the admin menu. The storefront carries no Ambikly branding at all.
How do I give a client’s staff access without making them admins?
Assign the Store Manager role (change products, orders, customers, coupons, shipping, tax, add-ons) or Support Agent (read-only orders, customers, reports). Settings and payment credentials stay with Administrators — you.
What happens to a client store if the Agency license lapses?
Pro add-ons pause on every site until the key is active again; settings and data are untouched and the free core keeps taking orders.
Is there a lifetime Agency license?
Yes — $1,349 once for 10 sites, or $499 per year.
Can I automate provisioning?
Every screen has a REST route with a permission check, WP-CLI exports products and orders, and the setup wizard steps are REST endpoints too — so a build script can create a store without clicking.
Build the first client store on Free.
Add the Agency key when the second client signs.