Store Sync Documentation

Last updated: 24 August 2026

This documentation explains how to install, connect, configure and operate Store Sync, the WooCommerce integration platform from The Voice Concierge.

Store Sync connects an authorised WooCommerce store to HighLevel. It retrieves and stores catalogue information securely, keeps product information current through manual syncs and WooCommerce webhooks, and makes store information available to approved HighLevel workflows, AI agents and external systems.

Availability depends on the Store Sync plan, the permissions granted during installation and any feature controls applied to the account.

What Store Sync does
What Store Sync does not do
Supported platforms
How Store Sync works
Plans, access and included credit
Usage charges
Installation and initial setup
WooCommerce connection and permissions
HighLevel connection and permissions
Store Sync dashboard
Product and variation synchronisation
Automatic WooCommerce updates
Product data processed by Store Sync
Orders and order-confirmed events
Carts and checkout links
Coupons and discounts
Back-in-stock registrations
HighLevel workflow actions
Store Sync events and triggers
MCP tools for AI agents
Setup Assistant and HighLevel assets
Public products API
Withdrawal and abandoned-cart requests
Activity logs and retention
Rate limits and usage controls
Security and account separation
Data processing and privacy
Store Sync included with managed services
Disconnecting or uninstalling Store Sync
Reliability and third-party services
Troubleshooting
Legal documents
Support
Company information

1. What Store Sync does

Store Sync provides a controlled connection between WooCommerce and HighLevel. Depending on the plan and configuration, it can:

Retrieve products and variations from WooCommerce
Store product names, descriptions, identifiers, SKUs, images, prices and stock information
Detect product, price and stock changes
Search a WooCommerce catalogue from an authorised AI agent
Perform live stock checks directly against WooCommerce
Build WooCommerce cart and checkout links
Check coupon eligibility and create authorised coupons
Look up WooCommerce order status when the feature is enabled
Record customer interest in out-of-stock products
Send product, order, sync and connection events to configured workflows or webhooks
Provide plan-controlled MCP tools for compatible AI agents
Provide a plan-controlled products API
Check whether required HighLevel setup assets are present
Record operational activity for support, billing, security and diagnostics

Store Sync is designed for business use. The person connecting a store must have authority to access that WooCommerce store and the relevant HighLevel account or sub-account.

2. What Store Sync does not do

Store Sync does not replace WooCommerce as the store, checkout, payment or order-management system.

In particular:

WooCommerce remains the authoritative source for products, stock, checkout and orders
Store Sync does not copy the WooCommerce catalogue into the native HighLevel product catalogue
Store Sync does not collect or store card numbers, card security codes or online-banking credentials
Store Sync does not process payments itself
Cart and checkout links send the shopper to the connected WooCommerce store
Store Sync does not guarantee that a third-party platform, API, webhook or workflow will always be available
Store Sync does not invent product data, stock values or prices using generative AI

Product information shown by Store Sync comes from the connected WooCommerce store or from the most recently synchronised Store Sync catalogue. Live stock tools query WooCommerce directly.

3. Supported platforms

E-commerce

WooCommerce

CRM, automation and AI agents

HighLevel
Compatible MCP clients and AI agents authorised through Store Sync

Additional integrations may be introduced in future versions. An integration should not be treated as supported until it appears in the Store Sync dashboard or official documentation.

4. How Store Sync works

The standard data flow is:

Store Sync is installed for an authorised HighLevel location.
The user opens Store Sync through HighLevel.
The user connects a WooCommerce store and approves the required access.
Store Sync retrieves the WooCommerce catalogue and stores tenant-scoped product and variation records.
WooCommerce product webhooks and subsequent syncs update the stored catalogue.
Approved dashboard features, workflows, AI agents and API clients use that information according to the account plan.
Live operations, such as stock checks or coupon creation, communicate with the connected WooCommerce store.

Store Sync keeps each HighLevel location and its connected store data separated from other customers.

5. Plans, access and included credit

Store Sync uses a three-plan model. Prices and included credit are configured in HighLevel and may be updated in the Marketplace listing.

Plan	Current monthly price	Included monthly usage credit	Main access
Store Sync MCP Limited Agent	Free	2.00	Core dashboard, catalogue tools, live stock, carts, checkout links, manual sync and setup tools
Store Sync MCP Agent	USD 47	5.00	Full MCP commerce tools, order lookup, coupons, discounts, workflow actions, triggers, public API and additional dashboard features
Store Sync Sales Agent	USD 97	10.00	All MCP Agent features, plus sales-intelligence tools and agent templates

Legacy plans are inactive and do not provide current Store Sync access.

Feature availability is enforced by the account plan. A tool or action that is not included returns an upgrade-required response and does not run.

Included usage credit resets according to the account’s monthly credit anniversary. Unused credit does not represent cash and is not transferable between accounts.

6. Usage charges

Store Sync uses fixed usage prices for metered operations. Included monthly credit is used first. When included credit has been used, further eligible operations may be charged to the connected HighLevel wallet. If billing cannot be completed, the operation stops instead of running without a recorded charge.

Operation	Usage price per unit
Product lookup	0.10
Live stock check	0.10
Cart or checkout-link creation	0.50
Workflow action, discount application, order lookup or registered back-in-stock interest	0.25
On-demand catalogue sync	1.00
Coupon creation	0.25
Sales-intelligence operation	0.10

Per-call unit limits, per-event caps and daily safety limits apply. A single request cannot create unlimited wallet charges.

The following are not metered:

Store Sync dashboard access
Setup checks
Setup-verification submissions
Trigger delivery, including order-confirmed and back-in-stock events
Automatic WooCommerce product webhook processing
Coupon eligibility checks, although coupon creation requires an eligible paid plan

The Marketplace listing and Store Sync billing information should be checked for the latest plan prices and usage terms before installation.

7. Installation and initial setup

The normal installation process is:

Install Store Sync from the HighLevel Marketplace for the intended account or sub-account.
Approve the HighLevel permissions displayed during installation.
Open the Store Sync custom page within the relevant HighLevel location.
Confirm the location purpose when prompted.
Connect the authorised WooCommerce store.
Approve the WooCommerce connection and the required read/write access.
Allow Store Sync to complete its connection checks and webhook registration.
Run the initial product sync.
Open the Setup area and verify the required HighLevel assets.
Configure any required workflow actions, triggers, internal webhooks, MCP clients or API keys.

Agency installations may create or reactivate separate Store Sync tenants for authorised HighLevel locations. Each location retains separate data, credentials, billing and plan access.

8. WooCommerce connection and permissions

Store Sync uses authorised WooCommerce REST API credentials with read/write access. Read/write access is required because Store Sync can read catalogue and order information, register WooCommerce webhooks and, on eligible plans, create coupons.

The connection may be used to:

Read store details and currency
Retrieve products and variations
Read prices, stock, images, attributes and product relationships
Perform live stock checks
Read order information for authorised order features
Register and remove Store Sync webhooks
Create coupons following an authorised request

WooCommerce credentials and webhook secrets are stored encrypted. They are not returned to the browser after connection and are not included in customer-facing logs.

Changing WooCommerce permissions, deleting API credentials, changing the store URL, blocking REST requests or installing security software that blocks API access may interrupt Store Sync.

9. HighLevel connection and permissions

Store Sync uses HighLevel OAuth. The access requested depends on the features needed by the application and can include permission to:

Read and create Store Sync custom fields
Read and create Store Sync tags
Add relevant tags to contacts
Read location information
Create or use authorised workflow-trigger subscriptions
Send authorised conversation messages for the withdrawal workflow
Resolve agency-installed locations
Record approved usage charges through HighLevel Marketplace billing

Store Sync does not require access to the native HighLevel product catalogue, calendars, campaigns, forms, surveys or payment orders for its normal catalogue integration.

HighLevel OAuth access and refresh tokens are stored encrypted. If HighLevel access is revoked or a token can no longer be refreshed, Store Sync reports that reconnection is required.

10. Store Sync dashboard

Dashboard access depends on the plan. Available areas can include:

Overview: connection state, plan, usage and recent activity
Products: synchronised products and variations
Setup: required HighLevel assets and verification status
Workflows: internal webhook subscriptions and test deliveries
Activity: sync, connection and operational activity
Secrets: Store Sync API and MCP credentials
Coupons: authorised coupon activity
Withdrawal: settings, requests, logs and embed configuration
Tracking: supported tracking settings
Support: support access and diagnostic information

Administrative views may also include tenant, billing, rate-limit, trigger, MCP, credit, audit and system logs. Customer accounts cannot view another tenant’s information.

11. Product and variation synchronisation

An on-demand sync retrieves the WooCommerce catalogue in pages and updates Store Sync’s tenant-scoped records.

The sync can:

Add newly discovered products and variations
Update existing product and variation information
Retain WooCommerce identifiers for later live operations
Record product relationships, including upsells and cross-sells
Detect relevant price, quantity, stock-status and product-detail changes
Emit configured events when qualifying changes are detected
Record a sync-completed or sync-failed event

Manual or MCP-triggered catalogue sync is a metered on-demand operation. Store Sync does not run the retired once-per-minute catalogue poller.

The stored catalogue represents the latest successfully processed WooCommerce information. A live stock check should be used when a current purchasing decision depends on exact availability.

12. Automatic WooCommerce updates

Store Sync registers WooCommerce webhooks automatically when a store connects or reconnects.

Current webhook topics include:

product.updated, used to process product changes
order.updated, used to detect the first confirmed purchase state

The platform performs a daily maintenance process that checks connected stores for missing Store Sync webhook topics and attempts to restore coverage. A store does not normally need to be reconnected solely because a newer Store Sync webhook topic was introduced.

Webhook registration is best effort. If WooCommerce rejects webhook creation, the store connection may still complete, but automatic event coverage can be reduced until the underlying issue is corrected.

13. Product data processed by Store Sync

Depending on the product type and available WooCommerce fields, Store Sync may retrieve and store:

Product and variation identifiers
Product names
Full and short descriptions
SKUs
Product and variation prices
Store currency
Stock quantities
Stock status
Variation attributes and options
Product images
Product status and availability
Product URLs
Category and other WooCommerce product metadata
Upsell and cross-sell relationships
The associated WooCommerce store connection

Store Sync may retain the WooCommerce product response required to support product tools and diagnostics. Access remains scoped to the authorised tenant.

14. Orders and order-confirmed events

Store Sync can register an order.updated webhook in WooCommerce. The order_confirmed event is created the first time an order reaches either:

processing
completed

The event is deduplicated by store connection and WooCommerce order ID. If an order first reaches processing and later changes to completed, the later status change does not create a second order_confirmed event.

The event may contain:

Order ID and order number
Order status
Currency and total
Date paid
Product and variation IDs
Product names, quantities and line totals
Billing name, email address and telephone number for CRM matching
Payment method name
Coupon codes
Store URL and connection ID
Whether the checkout originated from Store Sync

Store Sync does not receive or store card numbers, card security codes or payment-account credentials through this event.

Order-confirmed events are available on MCP Agent and Sales Agent plans and are not metered. Store Sync records a confirmed order once. It is not intended to provide a workflow event for every later WooCommerce order-status change.

15. Carts and checkout links

Eligible Store Sync tools and workflow actions can build WooCommerce cart or checkout links from selected products, variations and quantities.

Before returning a link, Store Sync validates the requested products against the authorised tenant’s catalogue and WooCommerce identifiers. The shopper completes checkout on the connected WooCommerce website.

A checkout link may include an authorised coupon where supported. Creating a cart or checkout link is metered at the cart-build rate.

Store Sync does not take payment and does not host the WooCommerce checkout.

16. Coupons and discounts

Paid plans can use Store Sync to check coupon eligibility, create a restricted WooCommerce coupon or apply an authorised discount during a supported checkout flow.

Coupon creation requires explicit confirmation and can use controls such as:

Percentage amount
Customer email restriction
Product restriction
Expiry date
Usage limit
Individual-use setting

Coupon eligibility checking is not metered. Successful coupon creation is metered. Coupon and discount tools are unavailable on the MCP Limited plan.

The merchant remains responsible for discount policy, consumer-law compliance, tax treatment and the financial effect of any coupon created through Store Sync.

17. Back-in-stock registrations

Paid plans can record that a HighLevel contact is interested in an out-of-stock WooCommerce product or variation.

The registration can store the contact, product and variation relationship and can apply the configured HighLevel tag. A workflow can then respond when the product transitions from out of stock to available.

The registration operation is charged only when a new interest is successfully registered. The later back-in-stock trigger is not metered.

Back-in-stock delivery depends on:

A valid contact ID
A matching tenant-scoped product or WooCommerce product ID
An active WooCommerce connection
Correct HighLevel tags, fields or workflow configuration
An active trigger subscription or internal webhook where required

18. HighLevel workflow actions

The current published Store Sync workflow-action keys are:

Action key	Purpose
`store_sync_start`	Run an on-demand WooCommerce catalogue sync
`store_check_stock`	Perform a live WooCommerce stock and price check
`store_create_cart`	Build a WooCommerce cart or checkout URL
`store_create_coupon`	Create an authorised shopper coupon
`store_create_coupon_v1`	Versioned alias retained for compatibility
`store_save_back_in_stock_interest`	Record contact interest in an unavailable product

Workflow actions are available only where the plan includes the relevant permission. Requests are tenant-scoped, rate-limited, billed where applicable and rejected when the action key is unknown.

The actions visible in the HighLevel workflow builder are controlled by the current Marketplace configuration. An action implemented by Store Sync may not be available until it has also been published and enabled in HighLevel.

19. Store Sync events and triggers

Store Sync supports the following operational events:

Event	When it occurs
`product_back_in_stock`	A product changes from out of stock to available
`order_confirmed`	An order first reaches processing or completed
`product_price_changed`	A product price changes between processed versions
`product_stock_changed`	A managed stock quantity changes
`product_out_of_stock`	A product changes to out of stock
`product_updated`	Relevant non-price and non-stock product details change
`sync_completed`	A catalogue sync completes successfully
`sync_failed`	A catalogue sync fails or a stale job is recovered as failed
`store_connected`	A store is newly connected or its connection is restored
`store_disconnected`	A connected store is disconnected

product_back_in_stock is the current published HighLevel Marketplace custom-trigger surface. Other events can be used through Store Sync’s configured internal webhook system and plan-controlled features. order_confirmed is a plan-controlled internal event.

Trigger deliveries use idempotency controls to reduce duplicates. Configured internal webhook deliveries can be signed. Failed deliveries can be retried up to the platform limit, after which they may be marked abandoned.

Stock events have distinct meanings. A quantity change can emit product_stock_changed, while a transition into or out of the WooCommerce out-of-stock state can additionally emit product_out_of_stock or product_back_in_stock.

20. MCP tools for AI agents

Store Sync provides an authenticated MCP endpoint for compatible AI agents. Access requires a tenant-specific MCP secret and a short-lived Store Sync token. Plan permissions, feature controls, rate limits, billing and tenant isolation are applied to every call.

Current tools are:

MCP tool	Purpose	General availability
`search_products`	Search the synchronised catalogue	All current plans
`get_product`	Retrieve one product	All current plans
`get_variations`	Retrieve product variations	All current plans
`get_product_cross_sells`	Retrieve configured cross-sell products	All current plans
`get_product_upsells`	Retrieve configured upsell products	All current plans
`get_stock`	Perform a live WooCommerce stock check	All current plans
`create_cart`	Build a cart link	All current plans
`create_checkout_link`	Build a checkout link	All current plans
`sync_now`	Run an on-demand catalogue sync	All current plans
`apply_discount`	Apply an authorised discount in a supported flow	MCP Agent and Sales Agent
`get_order_status`	Retrieve order status where the feature is enabled	MCP Agent and Sales Agent
`check_coupon_eligibility`	Check whether coupon creation is allowed	MCP Agent and Sales Agent
`create_coupon`	Create an authorised WooCommerce coupon	MCP Agent and Sales Agent
`register_back_in_stock_interest`	Record product interest for a contact	MCP Agent and Sales Agent
`get_customer_sales_summary`	Summarise authorised customer sales information	Sales Agent only
`get_next_best_action`	Return a rule-based next-action recommendation	Sales Agent only
`recommend_products_for_customer`	Recommend real catalogue products from authorised data	Sales Agent only
`check_store_sync_setup`	Check required Store Sync assets	All current plans
`submit_setup_verification`	Submit observed HighLevel setup evidence	All current plans

get_order_status also depends on the order-lookup feature being enabled for the tenant.

MCP product tools use the tenant’s synchronised catalogue or a live WooCommerce request. Store Sync does not call a generative model to invent catalogue content.

21. Setup Assistant and HighLevel assets

Store Sync can check and help provision the HighLevel assets required by supported workflows and agents. Depending on the account purpose and plan, these can include:

Custom-field folders and custom fields
Contact tags
Pipelines and pipeline stages
Workflows
Custom values
Custom objects and associations
Agent-related setup fields

The Setup Assistant distinguishes between:

Verified assets
Missing assets
Misconfigured assets
Assets that Store Sync is unable to verify automatically
Assets that do not apply to the current plan or location purpose

Some HighLevel resources cannot be verified reliably through the available API. In those cases, Store Sync can request raw observed evidence from HighLevel and record the submitted verification result.

Installation links for restricted assets are provided only to tenants entitled to receive them.

22. Public products API

MCP Agent and Sales Agent plans can use the authenticated Store Sync products API. It supports:

Product-list and search requests
Individual product details
Product variations

The API uses a tenant-specific API key, plan checks, rate limits and usage billing. Every product query is restricted to the tenant associated with the supplied key.

API keys must be stored securely and must not be placed in public browser code, public repositories, analytics data or client-visible logs.

The public products API is not available on the MCP Limited plan.

23. Withdrawal and abandoned-cart requests

Eligible paid plans can provide a withdrawal or cancellation-request experience connected to the merchant’s WooCommerce and HighLevel setup. Available dashboard areas can include:

Requests
Activity logs
Public embed configuration
Message and workflow settings

The feature can collect an authorised request, associate it with the correct tenant and store, update HighLevel contact information where required, and run the configured follow-up process.

The merchant is responsible for deciding whether a request is legally valid, responding within applicable deadlines and applying any refund, cancellation or order change in the appropriate commerce system. Store Sync does not provide legal advice and does not independently issue refunds.

24. Activity logs and retention

Store Sync records operational information needed for service delivery, billing, fraud prevention, security, troubleshooting and audit purposes.

Customer-visible activity can include:

Store connection and disconnection
Sync requests, completion and failure
Product and stock events
Workflow and webhook delivery
MCP tool activity
Rate-limit events
Credit usage and billing outcomes
Withdrawal activity

Current operational retention periods include:

Record category	Standard retention
System logs	30 days
MCP tool logs	30 days
Trigger delivery and suppression logs	30 days
Rate-limit event logs	30 days
Usage and billing events	90 days
Pending Store Sync checkout reconciliation records	90 days
HighLevel webhook delivery records	90 days
MCP audit logs	180 days
Platform audit logs	180 days
WooCommerce order-event deduplication records	180 days

Some short-lived security and deduplication records have shorter retention periods. One-time SSO replay markers may be retained for the life of the tenant to prevent a previously used launch assertion from being reused.

Retention periods may be updated where necessary for security, legal compliance or service operation. The current Privacy Policy governs personal-data retention and deletion requests.

25. Rate limits and usage controls

Store Sync uses tenant, action and pre-authentication limits to protect customers and the platform.

Current technical usage limits include:

Category	Standard limit
General MCP tool calls	300 per minute per tenant
Product lookups	300 per minute per tenant
Live stock checks	120 per minute per tenant
Setup checks	20 per hour per tenant
Setup-verification submissions	30 per hour per tenant
Outbound trigger deliveries	10,000 per day per tenant

Additional failed-authentication, API, webhook, billing and daily-spend controls apply. Some tenant-level limits can be reduced or adjusted for operational reasons.

When a limit is reached, Store Sync normally returns a rate-limit response and a retry period. Repeated attempts do not bypass the limit.

26. Security and account separation

Store Sync uses layered safeguards, including:

Tenant-scoped database queries
Row Level Security on tenant data
Separate credentials for each connected store and HighLevel location
AES-256-GCM encryption for stored credentials and tokens
Short-lived signed MCP tokens
HighLevel webhook-signature verification
Per-connection WooCommerce webhook signatures
Replay and idempotency controls
Server-side credential handling
Secret and personal-data redaction in logs
Rate limits before and after authentication
Audit logging for sensitive operations
Restricted customer and administrator access
Validation of outbound webhook destinations

Customer launch sessions are issued through a verified HighLevel SSO process. Customer session tokens are held in browser memory and are not deliberately stored in local storage, cookies or URLs by Store Sync.

No internet-connected system can guarantee uninterrupted operation or absolute security. Customers must protect their HighLevel account, WooCommerce administrators, API credentials, Store Sync API keys and MCP secrets.

27. Data processing and privacy

Store Sync processes only the information required for enabled features, security, billing, diagnostics and legal operation.

Depending on configuration, processed information can include:

WooCommerce store URL and store metadata
Product and variation catalogue data
Stock and price information
WooCommerce API credentials
HighLevel OAuth tokens and location identifiers
HighLevel contact IDs and tags
Customer name, email address and telephone number when required for order matching, back-in-stock interest or withdrawal processing
WooCommerce order identifiers, totals, statuses, line items, payment method name and coupon codes
MCP and API activity metadata
Usage, billing, security and audit events

Store Sync does not intentionally collect card numbers, card security codes, bank-login credentials or payment-processor secret keys as part of its normal operation.

Credentials and tokens are handled server-side and stored encrypted. Personal and secret-like fields are masked or removed from operational logs where appropriate.

For further information about lawful bases, subprocessors, international transfers, individual rights and deletion requests, see the Privacy Policy.

28. Store Sync included with managed services

Some Voice Concierge clients receive Store Sync at no separate subscription charge while their qualifying managed service remains active and their HighLevel account remains under The Voice Concierge agency.

This included access ends if the qualifying service is cancelled or the HighLevel account is transferred away from The Voice Concierge.

Clients who want to continue using Store Sync after leaving must purchase an eligible Store Sync subscription through their own HighLevel account.

Store Sync-related workflows, fields, tags and settings may remain in a transferred HighLevel account, but Store Sync synchronisation, tools, actions, triggers and APIs may stop working until a separate Store Sync subscription is installed and authorised.

Included credits, usage allowances and agency-specific Store Sync access do not transfer to another agency or subscription.

29. Disconnecting or uninstalling Store Sync

Disconnecting WooCommerce

Disconnecting a store:

Attempts to remove Store Sync webhooks from WooCommerce
Removes the local store connection and credentials
Stops new catalogue syncs and live WooCommerce operations
Emits the configured store-disconnected event before the local connection is deleted

If WooCommerce is unreachable, remote webhook removal may fail. Store Sync still removes the local secret, so a remaining remote webhook can no longer authenticate successfully.

Uninstalling from HighLevel

Uninstalling Store Sync:

Stops Store Sync access for that HighLevel location
Attempts to remove registered WooCommerce webhooks
Marks the tenant as uninstalled
Stops workflow actions, triggers, MCP tools, API access and new sync activity
Retains qualifying historical records for the published retention periods

Removing the application does not necessarily cancel a HighLevel Marketplace subscription. Subscription cancellation must be completed through the relevant HighLevel billing settings.

30. Reliability and third-party services

Store Sync depends on WooCommerce, WordPress, HighLevel, hosting, DNS, internet connectivity and their related APIs.

Changes or outages affecting those services can interrupt:

OAuth installation or reconnection
Product retrieval
Live stock checks
Coupon creation
Webhook delivery
Workflow execution
MCP tools
HighLevel wallet billing
Dashboard access

Store Sync uses retry, idempotency, audit and failure logging to reduce the effect of temporary problems. These controls cannot guarantee that every external request or workflow will succeed.

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.

31. Troubleshooting

If Store Sync is unavailable or data appears incorrect, check the following.

Store will not connect

Confirm that the website URL is correct and uses HTTPS
Confirm that WooCommerce is active
Confirm that the connecting user has administrator authority
Check whether a firewall, security plugin or hosting rule blocks WooCommerce REST API requests
Confirm that REST API credentials have read/write access
Check the Store Sync activity log for an authentication or connection error

Products are missing or outdated

Confirm that the store connection shows as connected
Run an on-demand sync
Confirm that products are published in WooCommerce
Check whether the product is returned by the WooCommerce REST API
Check sync activity for pagination, permission or server errors
Use a live stock check when current availability is required

Automatic updates are not arriving

Check whether Store Sync WooCommerce webhooks are active
Confirm that the WooCommerce webhook delivery URL has not been blocked
Review WooCommerce webhook delivery logs
Review Store Sync trigger and system logs
Reconnect the store if credentials or permissions were revoked

A workflow action or MCP tool is denied

Confirm that the action is included in the current plan
Confirm that the Marketplace installation and subscription are active
Check remaining included credit and HighLevel wallet availability
Confirm that the MCP or API credential belongs to the correct tenant
Check whether order lookup or another required feature is enabled
Wait for the supplied retry period if a rate limit has been reached

A trigger did not run

Confirm that the event actually met its trigger condition
Confirm that an active subscription or internal webhook exists
Check plan entitlement
Check trigger-delivery and suppression logs
Remember that order_confirmed is emitted only once per order
Remember that a move from processing to completed does not create a second confirmation event

Setup Assistant reports unverified assets

Review the listed evidence requirement
Confirm that the asset exists in the correct HighLevel location
Check the asset’s exact key, type and association
Submit raw HighLevel evidence where Store Sync requests it
Do not reinterpret HighLevel association values before submitting them

If the issue remains unresolved, contact Store Sync support with the HighLevel location ID, approximate time of the issue and relevant request or correlation ID. Do not send API keys, OAuth tokens, MCP secrets or passwords by email.

32. Legal documents

Use of Store Sync is governed by:

Store Sync Terms Schedule
https://thevoiceconcierge.com/store-sync-terms/

Store Sync Privacy Notice
https://thevoiceconcierge.com/store-sync-privacy/

Store Sync Data Processing Agreement
https://thevoiceconcierge.com/store-sync-dpa/

These documents supplement:

The Voice Concierge Terms and Conditions
https://thevoiceconcierge.com/terms-and-conditions/

The Voice Concierge Privacy Policy
https://thevoiceconcierge.com/privacy-policy/

Store Sync is provided for business use only.

33. Support

For help with installation, connection, billing or operation, visit:

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

Email: [email protected]

34. Company information

Store Sync is operated by:

JD Web Services Ltd trading as The Voice Concierge
Registered in England and Wales
Company number: 11453166
Registered office: 104 High Street, Mold, Flintshire, CH7 1BH