Store Sync Terms Schedule

Effective date: 28 August 2026

This Store Sync Terms Schedule applies to Store Sync supplied by JD Web Services Ltd trading as The Voice Concierge.

It supplements our main Terms and Conditions. By installing, subscribing to, accessing or using Store Sync, you accept both documents on behalf of the organisation you represent.

If this Schedule conflicts with the main Terms about Store Sync, this Schedule takes priority for that conflict.

1. About Store Sync

Store Sync connects an authorised WooCommerce store to an authorised HighLevel location.

Depending on the plan and configuration, Store Sync can:

Retrieve and store WooCommerce products and variations.
Process product and stock updates received through supported WooCommerce webhooks.
Retrieve synchronised stock quantities and availability information.
Search and retrieve product information.
Build WooCommerce cart and checkout links.
Check coupon eligibility and create authorised coupons.
Retrieve authorised order status.
Record back-in-stock interest.
Provide workflow actions and events.
Provide authenticated MCP tools for compatible AI agents.
Provide a plan-controlled products API.
Check required HighLevel setup assets.
Record usage, billing, activity, security and audit information.

WooCommerce remains the authoritative system for catalogue, checkout, payment and orders.

Store Sync does not copy the WooCommerce catalogue into the native HighLevel product catalogue.

2. Eligibility and authority

Store Sync is for business use only.

By using Store Sync, you confirm that:

You have authority to install Store Sync for the relevant HighLevel account or location.
You own or are authorised to manage the connected WooCommerce store.
You may grant the requested HighLevel and WooCommerce permissions.
You may instruct Store Sync to process the connected data.
Your agents, workflows and users are authorised to perform the enabled actions.

You must not connect a store, location, contact list or dataset that you do not have authority to use.

3. Supported platforms

The currently supported commerce and CRM platforms are:

WooCommerce
HighLevel

Compatible MCP clients may connect through the Store Sync MCP endpoint using valid credentials and permitted access profiles.

Other commerce or CRM platforms are not supported unless identified in the current Store Sync Documentation or application interface.

4. Installation and connections

Store Sync is normally installed through the HighLevel Marketplace and opened through an authorised HighLevel location.

You must:

Approve the permissions displayed during installation.
Complete the WooCommerce connection process.
Maintain valid platform accounts, subscriptions and credentials.
Ensure security software and hosting rules permit required API and webhook traffic.
Run and check the initial catalogue synchronisation.
Review the Setup Assistant and correct required assets.

Store Sync may register authenticated product.updated and order.updated webhooks in WooCommerce.

Webhook registration is best effort. A connection may complete even if the store rejects webhook registration, but automatic event coverage may then be reduced.

Connecting or reconnecting a WooCommerce store does not automatically initiate a full catalogue synchronisation.

5. Plans and feature access

The current standard plan model is:

Plan	Monthly subscription	Included monthly usage credit
Store Sync MCP Limited Agent	Free	$2.00
Store Sync MCP Agent	$47.00	$5.00
Store Sync Sales Agent	$97.00	$10.00

Store Sync MCP Limited Agent

Provides access to a restricted selection of catalogue, stock, cart, checkout, synchronisation and setup tools, subject to plan permissions.

Store Sync MCP Agent

Provides additional paid commerce tools, workflow actions, triggers, order lookup, supported APIs and dashboard functions.

Store Sync Sales Agent

Includes MCP Agent features together with supported sales-intelligence tools and agent templates.

The current HighLevel Marketplace listing and in-app plan details are authoritative for subscription prices, included credit and available features at the time of purchase.

Feature access is enforced by plan and, where applicable, MCP credential access profile. An unavailable operation is rejected and does not run.

Legacy plans that are no longer offered do not provide new subscription access unless an existing entitlement is explicitly maintained.

6. Included usage credit

Included usage credit is applied to eligible Store Sync operations before an additional external wallet charge.

Included credit:

Is a service allowance, not money.
Cannot be withdrawn, transferred or exchanged for cash.
Is not refundable as a cash balance.
Resets on the tenant’s monthly credit anniversary.
Does not roll over unless expressly stated otherwise.
May be corrected where an error, refund, reconciliation or abuse affects the balance.

An exempt or internally managed account may receive different billing treatment without changing the standard public plan rules.

7. Metered usage and wallet billing

Certain Store Sync operations are charged according to their applicable usage meter and the customer’s available plan entitlements.

Current standard usage prices

Operation	Price per use
Product lookup, including search, product details, variations, cross-sells and upsells	$0.01
Stock check using synchronised inventory	$0.015
Cart or checkout-link creation	$0.04
Coupon creation	$0.05
On-demand catalogue synchronisation	$0.50
Sales-intelligence operation	$0.05
Discount application, order status lookup and back-in-stock registration	$0.02

Individual tools and workflow actions are charged according to their applicable active meter.

Where an operation is available through multiple authorised interfaces, such as MCP tools, workflow actions or the Store Sync dashboard, the applicable usage charge may be the same regardless of how it was initiated.

Included credit and wallet charging

Included monthly usage credit is consumed first.

Where eligible usage exceeds the available included credit, Store Sync may submit the remaining eligible charge to the HighLevel wallet, subject to the applicable billing configuration and safeguards.

You authorise charges resulting from operations initiated through your authorised users, AI agents, MCP clients, workflows and API integrations.

Spending controls

Store Sync applies billing and security controls intended to reduce unauthorised or excessive usage.

These may include:

Per-operation charging limits.
Rolling-period spending limits.
Account-specific spending restrictions.
Rate limiting and abuse prevention.
Plan and access-profile permission checks.
Billing availability and wallet funding checks.
Transaction reconciliation and duplicate-charge safeguards.

Operations may be refused or stopped where spending limits are reached, required authorisation is missing, billing is unavailable or another applicable safeguard prevents execution.

Spending controls reduce financial exposure but do not guarantee that every authorised operation will be free of charges or that every requested operation will succeed.

Uncertain billing outcomes

Where a billing transaction has an uncertain outcome, Store Sync may hold the affected transaction for investigation and reconciliation rather than automatically repeating the charge.

Billing records may be retained to investigate discrepancies, support refunds or adjustments and meet applicable accounting obligations.

Operations not normally metered

The following are not normally charged as separate usage operations:

Customer dashboard access.
Setup checks.
Setup-verification submissions.
Coupon eligibility checks.
Automatic WooCommerce webhook processing.
Back-in-stock notification completion and failure-recording actions.
Outbound trigger delivery.

A change in an applicable meter, plan or billing arrangement may affect future usage charges. Material pricing changes will be handled under the main Terms and applicable Marketplace rules.

8. Product and catalogue information

Store Sync may retrieve and store:

Product and variation identifiers.
Product names, descriptions and images.
SKUs.
Prices and currency.
Stock quantities and stock status.
Variation attributes.
Categories, URLs and relevant product metadata.
Upsell and cross-sell relationships.

Catalogue synchronisation

Full catalogue synchronisation takes place only following an explicit authorised request.

This may be initiated through:

The Sync Now function in the Store Sync dashboard.
An authorised administrator action.
An enabled HighLevel workflow action.
An authorised MCP sync_now tool request.

Background processing may complete an already requested synchronisation job. It does not initiate an unscheduled full catalogue synchronisation.

Store Sync does not operate an automatic once-per-minute full catalogue synchronisation service.

WooCommerce stock updates

Where supported webhooks are correctly configured and delivered, WooCommerce may notify Store Sync of stock changes to existing products or variations.

These webhook updates can update relevant stored stock information without initiating a full catalogue synchronisation.

Webhook processing depends on the connected store, its configuration, network availability and successful event delivery.

Stock information and accuracy

Store Sync’s product and stock tools normally retrieve information from the synchronised Store Sync catalogue.

The stored stock figures reflect the latest successfully processed synchronisation or applicable WooCommerce webhook update.

They are not independently verified against WooCommerce during every tool request.

Synchronised stock information may become outdated where:

The connected store changes without delivering an applicable webhook.
Webhook delivery fails or is delayed.
A synchronisation has not recently completed.
The connection or store becomes unavailable.
Product or variation information has changed outside the latest processed updates.

Store Sync does not guarantee that a stored stock quantity represents the exact number available at the moment an AI agent requests it.

You are responsible for the accuracy and legality of information supplied by your store and for confirming stock availability before fulfilling an order.

9. Orders and payment information

Where enabled, Store Sync may process the first WooCommerce order update that reaches processing or completed as an order_confirmed event.

The event can include:

Order ID and number.
Status, currency, total and date paid.
Line items, product names, variation IDs, quantities and totals.
Billing name, email address and telephone number.
Payment method name.
Coupon codes.
Whether Store Sync originated the checkout.

The event is deduplicated per connected store and order.

If an order first reaches processing and later reaches completed, Store Sync does not create a second confirmation event for that same order.

Store Sync does not receive or store full payment-card numbers, card security codes or payment-account passwords through this feature.

WooCommerce and the merchant’s payment provider remain responsible for payment processing.

10. Carts, checkout links, coupons and discounts

Store Sync may build links that send a shopper to the connected WooCommerce store.

Store Sync does not host the WooCommerce checkout or directly take payment from the shopper.

Eligible plans may check coupon eligibility, create restricted coupons and support authorised discounts.

You are responsible for:

Approving coupon and discount policies.
Setting appropriate percentage, product, email, expiry and usage restrictions.
Testing checkout links and tax treatment.
Preventing unauthorised or excessive discounting.
Complying with consumer, advertising, tax and pricing law.

A coupon or discount action must not be treated as financial, tax or legal advice from us.

11. Workflows, events and webhooks

Store Sync provides plan-controlled workflow actions and operational events.

Current supported actions and events are described in the Store Sync Documentation.

You are responsible for:

Selecting the correct triggers and actions.
Testing workflows before live use.
Preventing loops and duplicate customer communications.
Keeping destination URLs under your control.
Protecting internal webhook secrets.
Verifying the effect of automated actions.

Store Sync uses delivery logs, authentication and signatures where configured, idempotency controls and retry limits.

These safeguards reduce but do not eliminate the possibility of duplication, delay or delivery failure.

An event indicates what Store Sync observed. It does not guarantee that every downstream HighLevel workflow, webhook destination or third-party service completed successfully.

12. MCP tools, AI agents and API access

MCP and API access requires valid tenant-specific credentials and the relevant plan entitlement.

Individual MCP credentials may be restricted to particular access profiles, tools and permissions.

Customer responsibilities

You must:

Keep MCP credentials and API keys confidential.
Use credentials only for their authorised tenant and purpose.
Rotate or revoke credentials after suspected compromise.
Configure AI agents to use tools only when appropriate.
Review tool permissions and potential spending exposure.
Prevent prompts or users from causing unauthorised commercial actions.
Maintain appropriate control over connected third-party applications.

Third-party MCP clients

Store Sync supports authorised MCP-compatible clients.

Possession of a valid MCP credential may allow a compatible client to request the functions permitted for that credential, even where the client is different from the application in which the credential was originally configured.

A credential does not grant access beyond its associated tenant, plan and permitted access profile.

Customers must only provide credentials to trusted, appropriately authorised applications and integrations.

AI-generated responses

Product-bearing tools return information obtained from the connected WooCommerce store or its synchronised Store Sync catalogue.

Store Sync does not use generative AI to invent product catalogue records.

However, third-party AI agents may independently interpret, summarise or describe tool results inaccurately.

AI agents may also select different tools for similar requests, repeat failed requests or respond differently to delays and errors.

You are responsible for agent instructions, disclosure, access permissions and appropriate human oversight.

Repeated operations and idempotency

Store Sync uses idempotency and other safeguards to reduce unintended duplicate operations.

However, third-party MCP clients and AI agents may repeat tool calls without providing a stable operation or idempotency identifier.

Customers must not assume that all repeated operations will automatically be identified or prevented.

Store Sync may reject requests that breach permissions, security restrictions, spending limits or other applicable safeguards.

Order lookup or other restricted features may be unavailable unless the relevant plan, permission or feature entitlement is enabled.

13. Setup assets

Store Sync can check and, where authorised, help create HighLevel custom fields, tags and other supported setup assets.

Some assets or associations cannot be verified automatically through the available HighLevel API.

The Setup Assistant may request raw HighLevel evidence and record the supplied result.

You are responsible for checking that:

Assets were created in the intended location.
Names, keys, types and associations are correct.
Workflows use the correct assets.
Submitted verification evidence is accurate and unaltered.

Restricted templates or installation links are available only to entitled plans and locations.

14. Back-in-stock registrations

Eligible paid plans may register a HighLevel contact’s interest in an unavailable product or variation.

You are responsible for having a lawful basis for the registration and any later communication.

Marketing or promotional messages require appropriate compliance with UK data-protection legislation and the Privacy and Electronic Communications Regulations (PECR).

A registration is metered only when a new interest is successfully recorded under the applicable billing configuration.

Trigger delivery is not separately metered.

15. Withdrawal and cancellation requests

Eligible plans may provide a consumer-facing withdrawal or cancellation-request process.

Store Sync can receive, log and route a request, but the merchant remains responsible for:

Assessing whether the request is valid.
Responding within applicable legal deadlines.
Cancelling or changing the order in WooCommerce.
Issuing any refund through the payment provider.
Keeping required evidence and communications.

Store Sync does not provide legal advice and does not independently issue refunds.

16. Customer responsibilities

In addition to the main Terms, you must:

Keep the WooCommerce catalogue, stock and prices accurate.
Maintain valid read/write API access.
Review Store Sync logs and connection status.
Reconnect promptly after credential or OAuth failure.
Protect customers from incorrect or repeated automated messages.
Monitor included credit and HighLevel wallet availability.
Apply appropriate access restrictions to HighLevel users and agents.
Keep your own privacy policy and customer terms accurate.
Obtain lawful authority for order, contact and store processing.

You accept the commercial consequences of actions deliberately initiated through your authorised account, except to the extent caused by our breach or otherwise excluded by applicable law.

17. Security credentials

Store Sync credentials, API keys, MCP secrets, OAuth tokens and WooCommerce credentials must be treated as confidential.

Do not place secrets in:

Public browser code.
Public repositories.
Prompt templates visible to end users.
Analytics events.
Unprotected documents.
Support emails or screenshots.

Credential permissions and management

Store Sync may issue profile-bound MCP credentials with separate permissions.

Where supported, customers should use separately issued credentials for different authorised integrations so that individual connections can be restricted or revoked without affecting unrelated integrations.

Store Sync may apply:

Tenant-scoped authentication and permissions.
Credential-version and revocation checks.
Plan and access-profile restrictions.
Rate limits and abuse controls.
Emergency access restrictions.
Usage and spending limits.
Security event monitoring and audit logging.

These safeguards do not remove the customer’s responsibility to protect access credentials.

If a credential may have been exposed, you must notify us promptly and revoke or rotate it using the available Store Sync controls or with assistance from support.

18. Availability and third-party dependencies

Store Sync depends on HighLevel, WooCommerce, WordPress, hosting, DNS, networks and related third-party APIs.

We do not guarantee that:

Every API or webhook will remain available.
A third-party response will be accurate or timely.
An operation will succeed when a platform is rate-limited or unavailable.
Every plugin, firewall or hosting configuration will be compatible.
Every AI agent will select a particular Store Sync tool.
Third-party agents will avoid retrying failed requests.
A tool call or AI conversation will complete within a guaranteed response time.
A third-party Voice AI service will provide uninterrupted speech while waiting for external tools.

Slow or unavailable services may result in delayed responses, failed operations or the need for additional verification.

Where an operation cannot complete, the relevant agent or workflow may need to provide a fallback response or refer the request for human assistance.

We may change, restrict or remove a feature where required by platform changes, security or law, subject to the main Terms and applicable legal requirements.

19. Data protection

Our Store Sync Privacy Notice explains how Store Sync processes personal data.

Where we process personal data on your behalf, the Store Sync Data Processing Agreement forms part of this Schedule.

You are normally the controller for shopper, order, contact, back-in-stock and related merchant information.

You must provide an appropriate privacy notice and establish a lawful basis for your processing.

Where you connect third-party AI agents, workflows, webhook destinations or MCP clients, you are responsible for evaluating their data-protection arrangements and ensuring that their use is lawful and appropriately disclosed.

Store Sync may separately process account, usage, billing and security information as a controller, as described in the Store Sync Privacy Notice.

20. Store Sync included with managed services

We may include Store Sync at no separate subscription charge as part of a qualifying Voice Concierge or managed-service plan.

Included Store Sync access applies only while:

The qualifying managed-service subscription remains active.
The relevant HighLevel account remains managed under our agency.
The Customer complies with the main Terms and this Schedule.
The applicable Store Sync installation and connected store remain authorised.

The included entitlement is a benefit of the qualifying managed service.

It is not a permanent Store Sync licence and cannot be transferred to another agency, HighLevel account or Marketplace subscription.

If the Customer cancels the qualifying managed service or transfers its HighLevel account away from our agency:

The included Store Sync entitlement ends.
Store Sync access may be restricted, disconnected or marked inactive.
Included credits and agency-specific plan allowances cease.
Store Sync tools, workflow actions, triggers, MCP access, APIs and synchronisation may stop functioning.
Store Sync data and billing status do not automatically transfer to another installation.

The Customer may continue using Store Sync after leaving our agency by installing or retaining Store Sync through its own eligible HighLevel account and purchasing a current Store Sync subscription.

The new subscription will be subject to:

The plans and prices available at that time.
Separate included credit and metered-usage rules.
New installation, authorisation and connection checks.
Any required Store Sync setup or verification.
The Customer’s or receiving agency’s own HighLevel and WooCommerce accounts.

Workflows, custom fields, tags and other Store Sync-related assets may remain inside a transferred HighLevel account.

Their presence does not provide an active Store Sync entitlement, and they may not operate until Store Sync is separately subscribed to and authorised.

21. Disconnecting a store

Disconnecting WooCommerce:

Stops new catalogue synchronisations and operations requiring the connected store.
Attempts to remove Store Sync webhooks from WooCommerce.
Removes the active local store connection and credentials.
May retain historical logs and records for the published retention periods.

If WooCommerce is unreachable, a remote webhook may remain temporarily.

Removing the local webhook secret prevents it from authenticating to Store Sync.

Disconnecting the store does not automatically uninstall Store Sync or cancel its Marketplace subscription.

22. Uninstalling Store Sync

Uninstalling Store Sync from HighLevel:

Ends application access for the location.
Stops new authorised MCP, API, workflow-action, trigger and synchronisation activity.
Attempts to remove registered WooCommerce webhooks.
Marks the Store Sync tenant as uninstalled.
Retains qualifying historical records for the published retention periods.

Uninstalling does not necessarily cancel the Marketplace subscription.

23. Cancelling the subscription

A Customer paying separately for Store Sync must cancel its Store Sync Marketplace subscription through the applicable HighLevel billing settings.

Disconnecting WooCommerce, deleting credentials, ceasing use or uninstalling Store Sync does not replace Marketplace subscription cancellation.

Where Store Sync is included with a qualifying Voice Concierge or managed-service plan, the included entitlement ends when:

The qualifying managed service ends.
The relevant HighLevel account transfers away from our agency.
The Customer otherwise ceases to meet the eligibility requirements.

A Customer leaving our agency must purchase a separate Store Sync subscription if it wishes to continue using Store Sync.

Charges already incurred and the current billing period remain subject to the main Terms and applicable Marketplace rules.

24. Suspension

We may restrict Store Sync where:

The plan or Marketplace installation is inactive.
Billing fails or credit and wallet funding are insufficient.
Credentials or permissions are invalid.
Use threatens security or platform stability.
Activity breaches the main Terms or this Schedule.
Continued processing would be unlawful.
Credentials are suspected of compromise or unauthorised use.

Security or fraud concerns may require immediate restriction without prior notice where reasonably necessary and legally permitted.

Restrictions may affect individual credentials, tools, accounts, connected stores or the entire Store Sync service, depending on the circumstances.

25. Support

Support is available through:

https://thevoiceconcierge.com/store-sync-documents/

Email: [email protected]

We aim to provide a first response within 24 hours.

Resolution time depends on complexity and third-party involvement.

Do not send passwords, OAuth tokens, API keys or MCP secrets to support.

26. Trademarks and independence

Store Sync is an independent integration.

WooCommerce and WordPress are trademarks of their respective owners.

Store Sync is not affiliated with, endorsed by or sponsored by Automattic Inc., WooCommerce or the WordPress Foundation.

HighLevel is a trademark of HighLevel Inc.

References to third-party products and services are for identification and compatibility purposes.

27. Changes

We may update this Schedule when Store Sync, billing, platform requirements or applicable law changes.

Material changes will be handled under the change provisions in the main Terms.

The current version will identify its effective date.

28. Contact

JD Web Services Ltd trading as The Voice Concierge

104 High Street
Mold, Flintshire
CH7 1BH

Company number: 11453166