Knowledge Base
Deviking Product feeds Pro

Deviking Product Feeds Pro Settings

The Settings page contains the global options that affect how Deviking Product Feeds Pro processes feed generation, stores history and logs, and handles plugin data during uninstallation.

These settings apply to the plugin as a whole rather than to one individual feed.

To open the settings page, go to:

Deviking Feeds → Settings

Only WordPress administrators can modify these global settings.


Performance & History

Generation Batch Size

The Generation batch size setting controls how many products are queried and processed at a time during feed generation.

Default value:

 
250
 

Allowed range:

 
50 – 1000
 

Deviking Product Feeds processes products in memory-safe batches instead of attempting to load the entire WooCommerce catalog into memory at once.

For example, if your catalog contains 10,000 eligible products and the batch size is set to:

 
250
 

the generator processes the catalog in multiple smaller groups.

When Should You Change the Batch Size?

For most stores, the default value of 250 is a good starting point.

You may consider using a lower value when:

  • the server has limited PHP memory;
  • feed generation causes memory-related errors;
  • the store contains very complex variable products;
  • many custom fields or attributes are processed.

For example:

 
100
 

A more powerful server may be able to use a larger batch size such as:

 
500
 

or:

 
1000
 

A larger value can reduce the number of database query batches, but it also increases the amount of data processed in memory at the same time.

Changing the batch size does not change which products or fields are exported. It only affects how the generation process is divided internally.


History Entries per Feed

History entries per feed determines how many previous generation results Deviking Product Feeds Pro keeps for each feed.

Default value:

 
25
 

Allowed range:

 
5 – 100
 

Each history entry can contain information about a generation such as:

  • generation date and time;
  • status;
  • number of exported records;
  • generated file size;
  • generation duration;
  • number of split files;
  • remote delivery results;
  • generation messages.

When the configured limit is exceeded, the oldest history entries are automatically removed.

For example, if the limit is:

 
25
 

the plugin keeps the latest 25 generation records for each feed.

Increasing this value provides more historical information but also stores more data in the WordPress database.


Maximum Log Entries

The Maximum log entries setting controls how many entries are retained in the global Product Feeds log.

Default value:

 
300
 

Allowed range:

 
50 – 2000
 

Logs can contain useful information about feed generation, errors and other plugin operations.

You can review them from:

Deviking Feeds → Logs

Once the configured maximum number of log entries is reached, older entries are automatically removed as new entries are created.

For most installations, the default value is sufficient.

If you are troubleshooting an issue or maintaining several feeds, you may temporarily increase the limit.


Data

Delete Plugin Data on Uninstall

The Data section includes the option:

Delete plugin feeds, rules, maps, settings, logs and history on uninstall

This option is disabled by default.

If it remains disabled and you uninstall Deviking Product Feeds Pro, plugin configuration data is preserved where applicable.

This can be useful if you intend to reinstall the plugin later.

If you enable this option before uninstalling the plugin, Deviking Product Feeds will remove its stored data, including:

  • feeds;
  • advanced filter rules;
  • category mappings;
  • plugin settings;
  • logs;
  • generation history.

Important: Enable this option only when you are sure you no longer need the existing Product Feeds configuration.

Simply deactivating the plugin does not trigger uninstall cleanup.


Save Settings

After changing any global setting, click:

Save Settings

The new values will then be used by subsequent plugin operations.

Changing these settings does not require you to recreate your existing feeds.


Global Settings vs Feed Settings

It is important to distinguish between global plugin settings and individual feed settings.

The Settings page controls plugin-wide behavior such as:

  • generation batch size;
  • history retention;
  • log retention;
  • uninstall data handling.

Configuration that applies to a particular feed is managed from the feed editor instead.

For example, the following are configured per feed, not from the global Settings page:

  • XML or CSV format;
  • Feed Template;
  • Attribute Mapping;
  • product scope;
  • Include / Exclude filters;
  • Advanced Filter Groups;
  • filename;
  • storage location;
  • generation schedule;
  • split-feed settings;
  • FTP / FTPS / SFTP destinations;
  • WPML language;
  • XML structure;
  • CSV settings.

This allows every feed to operate independently while sharing the same global performance and retention settings.


Other Configuration Areas

Some Product Feeds features have their own dedicated sections rather than being placed inside the global Settings page.

Dynamic Attributes

Go to:

Deviking Feeds → Dynamic Attributes

to create reusable values based on conditional rules.

Category Mapping

Go to:

Deviking Feeds → Category Mapping

to map WooCommerce categories to external marketplace or channel categories.

Logs

Go to:

Deviking Feeds → Logs

to review plugin and generation messages.

Tools

Go to:

Deviking Feeds → Tools

for maintenance and diagnostic operations such as rebuilding scheduled events or working with feed configuration tools.

Recommended Settings

For most WooCommerce stores, we recommend starting with the default values:

 
Generation batch size:      250
History entries per feed:   25
Maximum log entries:        300
Delete data on uninstall:   Disabled
 

There is usually no need to change these values unless you are troubleshooting performance, working with a particularly large catalog, or need to retain more generation history.

Deviking Product Feeds keeps global settings focused on performance, history, logging and data retention, while feed-specific options are configured directly within each feed.