Klevu Synchronization

The FAQs are only applicable to v2/v3: Klevu Smart Search Module

1. Do the CLI commands operate independently from the Magento Indexers?
   Yes. The CLI commands (klevu:syncdata --alldata and --updatesonly) are independent of the Magento Indexer framework.

2. Are the klevu_product_sync and klevu_product_sync_stock Indexers legacy or deprecated?
   They are not deprecated, but they serve a different purpose. These indexers are primarily "pointers." In many versions, they don't use standard Magento _cl (changelog) tables, which is why your SQL query for "klevu%changelog" returned empty. Instead, Klevu tracks changes in its own internal tables.

3. How do we reduce the size of the GB log file?
   This is likely due to the Klevu Logger being set to "Debug" mode.
   Action: Navigate to Stores > Configuration > Klevu > Search Configuration > Developer Settings and change Log level to Info/Warning

4. Why do some commands use "Proxy" in the di.xml?
   You may notice many Klevu commands are defined as Proxies in the code. This is a Magento 2 design pattern to improve performance.

5. What is the difference between klevu:syncdata and klevu:syncstore?

   1. klevu:syncdata: This is a global command. It processes all entities (Products, Categories, CMS Pages, and Orders) across all enabled store views.

   2. klevu:syncstore: This allows for granular control. If you have a multi-store setup but only updated products in your "German" store, you can target just that store code. This is significantly faster and more resource-efficient than running a global sync for a single store update.

6. Does the sync process include Orders and CMS pages?
   Yes. When you run klevu:syncdata, the command handles more than just products. It automatically includes:
   CMS Pages: Ensures pages are searchable.
   Categories: Keeps your categories searchable.
   Orders: Syncs recent sales data to Klevu to power "Trending Products" and "Bought Together" AI logic.

7. When should we use klevu:images or klevu:rating?
   These are commands that don't need to run as often as the product sync:

klevu:images: Use this if you see broken images in search results or if you have changed your Magento image watermarks/resize settings. It recreates the images in pub/media/klevu_images.

klevu:rating: Use this if your star ratings in search don't match your product reviews.
It recalculates the average rating attribute that Klevu uses for sorting and filtering.

Note: Always run  klevu:syncdata --alldata after running these commands to push the new image paths or rating values.

8. Can we sync Categories or Orders specifically, without a full product sync?
   Yes. If you have a high-volume store, you can use targeted commands:
   klevu:sync:category: Syncs only category structure changes.
   klevu:syncorder: Syncs only checkout data. This is useful if you want to sync order data every 15 minutes for real-time analytics.

9. How does Klevu handle "modified" entities in --updatesonly?
   Klevu doesn't just look at the Magento "Updated At" timestamp. It maintains an internal mapping in the database.
   When a command is run with --updatesonly, Klevu compares the current product state against the last recorded sync state.

10. Can we disable or change the indexer mode?
    Yes, safe to change the indexer mode or disable it if not in use.