AACSearch supports several ways to ingest data — from CMS modules to a Custom API. The status of every integration is published openly.Choose an integration
Every integration is labelled as:
We don't call a Planned connector ready.
CMS module · Beta
Bitrix module with native search integration. Beta release; Marketplace publication pending.
CMS module · Beta
Module that indexes products and replaces catalogue search.
CMS module · Experimental
Plugin that swaps the built-in search for AACSearch.
CMS module · Planned
A native WooCommerce connector is on our roadmap.
Scheduled feed
Point AACSearch at a YML or XML feed — it pulls on a schedule.
API
Push documents and events from any stack with the ingest API.
Before you install:
Modules and feeds all land in the same collections you would populate with the import API, so switching the source later is a config change — not a reindexing project. Inbound payloads are HMAC-signed, and every sync run is logged.
Use the Custom API. AACSearch doesn't make you wait for a first-party plugin before you can integrate your own source.
Explore more
The best way to evaluate a search platform isn't reading one more comparison table.
Only then make the decision.