'%20clip-path='url(%23canvas-clip)'/%3e%3cg%20clip-path='url(%23canvas-clip)'%3e%3cg%20transform='rotate(0,%20256,%20256)'%3e%3cg%20transform='translate(87%2087)%20scale(14.083333333333334%2014.083333333333334)%20translate(0%200)'%3e%3cpath%20fill='none'%20stroke='%23FFFFFF'%20stroke-linecap='round'%20stroke-linejoin='round'%20stroke-width='2'%20d='m18.064%2010.877l-4.89-7.26c-.42-.625-1.287-.803-1.936-.397a1.4%201.4%200%200%200-.41.397l-4.893%207.26C4.24%2013.715%204.9%2017.318%207.502%2019.423a7.13%207.13%200%200%200%204.168%201.572M15%2018a3%203%200%201%200%206%200a3%203%200%201%200-6%200m5.2%202.2L22%2022'/%3e%3c/g%3e%3c/g%3e%3c/g%3e%3c/svg%3e)
Search capacity and support for complex teams.
For high-volume teams that need custom capacity, API access, multi-store planning, dedicated resources, and rollout support.
The enterprise path
Match the operating model to the scale of the team.
The right enterprise conversation starts with catalog size, search volume, stores, integration needs, rollout constraints, and the evidence your team needs to retain.
Needs
Map
Capacity
Size
API
Connect
Rollout
Plan
Support
Operate
The merchant answer
Enterprise is for teams whose search requirements extend beyond a standard store plan: more capacity, multiple stores, custom rollout design, longer evidence horizons, or dedicated operating support.
Guides and field notes
Go deeper when the decision needs detail.
Use these practical guides for the context, merchant decisions, and acceptance tests behind the capability you are evaluating.
The path
Design the search operation your organization can actually run.
Enterprise fit is not just a larger SKU limit. It is the combination of capacity, integration, stores, rollout ownership, analytics horizon, and support that the business needs.
Map the operating requirement
Share store count, catalog size, expected search and update volume, markets, team ownership, integration needs, and rollout constraints.
Choose the right capacity and access
Plan custom limits, API access, analytics retention, dedicated resources, and support around the way the team will operate.
Agree the rollout and evidence path
Define ranking and rollout planning, acceptance queries, runtime checks, support ownership, and the evidence the team needs after launch.
Decision guide
Questions this capability should answer
Use these questions to decide whether this capability is the right next move for your store.
Is Enterprise the right fit?
Start with actual capacity, store count, integration requirements, markets, team ownership, and support expectations. Choose Enterprise based on operating needs, not a generic company-size label.
What should be custom?
Separate capacity, API, rollout, analytics, support, and solution-design needs so the agreement is specific and reviewable.
What happens before a broader rollout?
Define the acceptance set, protected queries, runtime and catalog checks, ownership, support path, and rollback expectations before expanding.
What is included
An enterprise conversation grounded in merchant needs
Bring the commercial, technical, and operating questions into one conversation before a multi-store or high-volume rollout.
Custom capacity
Plan search, catalog-update, and SKU limits around the organization’s actual operating envelope.
ParticleSearch API access
Discuss API access when the team needs a controlled integration beyond the standard Shopify storefront path.
Multi-store support
Coordinate requirements across stores, catalogs, markets, and teams instead of treating each rollout as an isolated decision.
Custom ranking and rollout planning
Translate the organization’s buyer jobs, protected queries, rollout stages, and acceptance criteria into a deliberate plan.
Long-term analytics retention
Keep the evidence horizon required for seasonal, multi-market, and longer-cycle operating reviews.
Dedicated resources and solution design
Align capacity, support, and solution design with the operational risk and complexity of the rollout.
A useful boundary
Good product decisions include what the feature cannot solve.
ParticleSearch gives your team more evidence and control. It does not remove the need for accurate product data, a clear merchandising goal, or a review of the result on your own store.
- Enterprise is listed at $2,799/month. Availability, limits, integrations, resources, and support terms should be confirmed for the specific organization.
- API access does not remove the need for schema, relevance, storefront, monitoring, security, and ownership decisions.
- Multi-store and dedicated-resource planning should be evaluated against the actual catalogs, traffic, markets, and operating model.
Keep exploring
See how this fits with the rest of the product.
Enterprise conversation
Plan the right search conversation for your team.
Share your stores, catalogue, markets, integration needs, rollout constraints, and support expectations. We will help turn them into a scoped next step.