SmartDescribe Pro Performance, Large Catalogues and Optimisation Management

Guide 1.13 — Performance, Large Catalogues and Optimisation Management

Product: SmartDescribe Pro
Publisher: Cazgrae
Platform: WordPress and WooCommerce

1. Introduction

WooCommerce stores can contain hundreds or thousands of products, each with one or more images requiring descriptive alt text.

Managing image descriptions manually across a large catalogue can be time-consuming. SmartDescribe Pro helps streamline this work through AI-assisted optimisation and, where supported by the installed version, bulk processing, scheduled optimisation, configurable templates, and optimisation history.

This guide explains how to plan optimisation jobs, manage large product catalogues, reduce unnecessary API requests, monitor progress, and maintain reliable store performance.

The objective is simple: optimise image alt text efficiently without placing unnecessary strain on your website or wasting AI processing resources.

2. Understanding Optimisation Workloads

Not every WooCommerce store has the same optimisation requirements.

The time and resources required depend on several factors, including:

  • The number of products selected.
  • The number and size of images processed.
  • The AI provider being used.
  • The provider’s response time and usage limits.
  • Your web hosting resources.
  • The number of simultaneous background tasks.
  • Whether optimisation is performed individually, in bulk, or on a schedule.

A small store may be able to process products in relatively short sessions. A larger store may benefit from smaller batches and a more structured workflow.

There is no single batch size that is ideal for every installation.

Start with a baseline

Before optimising your catalogue, record a few basic details:

ItemWhat to check
Catalogue sizeApproximate number of WooCommerce products
Image workloadNumber of product images likely to be included
AI providerProvider configured in SmartDescribe Pro
Existing alt textWhether images already have useful descriptions
Hosting environmentAvailable resources and relevant limits
API usageCurrent provider usage and billing arrangements
Processing optionsIndividual, bulk, or scheduled features available in your version

This information helps you estimate the workload and identify potential problems before processing large numbers of products.

3. Preparing a Large Product Catalogue

Before running a bulk optimisation job, prepare your catalogue.

Step 1: Check your existing image descriptions

Some products may already have accurate, useful alt text.

Identify products that genuinely need attention rather than repeatedly processing images that are already satisfactory.

If your installed version offers options for handling existing alt text, review them carefully before starting.

Step 2: Review product images

Check for missing, outdated, or incorrect product images.

AI-generated alt text cannot reliably compensate for an incorrect image. If a product displays an outdated photograph, correct the image before optimising its description.

Step 3: Review product categories

Organising products into meaningful categories can help you plan manageable optimisation sessions.

For example, a handmade goods store might process:

  1. Ceramic products.
  2. Jewellery.
  3. Home decorations.
  4. Garden ornaments.
  5. Gift items.

This approach also makes it easier to review the quality of descriptions for similar products.

Step 4: Confirm your AI configuration

Before processing a large selection:

  • Verify that your selected provider is configured correctly.
  • Check that your API key works.
  • Review any available generation settings.
  • Confirm that your provider account has sufficient quota.
  • Understand the provider’s pricing arrangements.

Run a small test before proceeding.

Step 5: Back up your website

Create a reliable backup before making significant catalogue changes.

Your backup strategy should account for both the WordPress database and the website files, as appropriate for your hosting environment.

A backup provides an additional recovery option if a bulk operation or unrelated website problem causes unexpected changes.

4. Planning Bulk Optimisation

Bulk processing can reduce repetitive work, but it should be approached methodically.

Begin with a small batch

Start with a limited group of products that represents your catalogue.

Review the results for:

  • Accuracy.
  • Appropriate wording.
  • Consistent tone.
  • Correct use of product terminology.
  • Unnecessary keywords.
  • Unsupported claims.
  • Unexpected changes to existing descriptions.

Once the results are satisfactory, increase the workload gradually.

Use manageable batches

For large catalogues, divide the work into smaller groups instead of immediately selecting every product.

The ideal batch size depends on your hosting environment, the AI provider, and the features available in SmartDescribe Pro.

A practical approach is to:

  1. Run a small batch.
  2. Observe how long it takes.
  3. Check for errors or timeouts.
  4. Review the resulting alt text.
  5. Increase the batch size cautiously if processing remains reliable.

If errors begin to appear, reduce the workload and investigate the cause.

Avoid overlapping jobs

Do not repeatedly start new bulk jobs while earlier jobs may still be running.

Overlapping operations can make it harder to determine which products have been processed and may lead to unnecessary API requests.

Check the available progress information, status indicators, or optimisation history before restarting a job.

The precise controls depend on your installed version.

5. Reducing Unnecessary API Usage

AI processing may incur charges or count towards your provider’s usage limits.

Careful planning can reduce unnecessary requests.

Avoid repeated optimisation without a reason

Once an image has accurate, useful alt text, there may be little benefit in generating another version immediately.

Before rerunning optimisation, consider whether the existing description is incorrect, incomplete, inconsistent, or otherwise in need of improvement.

Test settings before large jobs

If your version supports writing tones, category-specific templates, or character limits, test these settings on a small selection first.

Changing settings after processing thousands of products may mean repeating work unnecessarily.

Review scheduled jobs

Scheduled optimisation can be useful for maintaining a growing catalogue.

However, the schedule should reflect your store’s needs.

Review:

  • How frequently jobs run.
  • Which products are eligible.
  • Whether products are repeatedly selected.
  • Whether the resulting descriptions require further review.
  • Whether API usage is consistent with your expectations.

Do not assume that scheduled processing automatically excludes previously optimised products. Confirm how eligibility and repeat processing work in your installed version.

Monitor provider usage

Use your AI provider’s account dashboard to monitor consumption and billing.

Where available, configure usage alerts or spending controls.

Remember that pricing and quotas vary between providers and account types.

6. Using Scheduled Optimisation Effectively

If your version supports scheduled optimisation, it can help reduce the amount of manual work required to maintain your catalogue.

Suitable uses

Scheduling may be useful when:

  • New products are added regularly.
  • Your catalogue needs ongoing maintenance.
  • You want to process selected groups outside peak business hours.
  • You prefer smaller, recurring workloads instead of occasional large jobs.

Establish a sensible schedule

Choose a frequency appropriate to your product update cycle.

A store that adds only a few products each month may not need frequent optimisation. A store adding products every day may benefit from a more regular process.

The appropriate schedule also depends on the plugin’s actual scheduling behaviour and your hosting environment.

Review scheduled activity

After enabling automation:

  1. Check that scheduled tasks are running as expected.
  2. Review any available completion or error information.
  3. Monitor API usage.
  4. Inspect a sample of generated descriptions.
  5. Adjust the schedule if the workload is excessive or unnecessary.

Scheduling should make catalogue management easier, not create a stream of unmonitored background jobs.

7. Managing Server Resources

SmartDescribe Pro runs within your WordPress and WooCommerce environment. Other plugins, theme functionality, hosting restrictions, and server load can affect processing reliability.

Common resource constraints

Potential problems include:

  • PHP execution time limits.
  • Memory limits.
  • Database performance issues.
  • Hosting resource restrictions.
  • Network timeouts.
  • External API delays.
  • Background task failures.

The relevance of each factor depends on how the installed version performs its processing.

Signs of a resource problem

You may notice:

  • Optimisation jobs stopping unexpectedly.
  • Requests timing out.
  • The WordPress administration area becoming unusually slow.
  • Intermittent errors during bulk processing.
  • Other website functions becoming less responsive.

One isolated error does not necessarily mean your server lacks resources. External API failures, network interruptions, and configuration problems can produce similar symptoms.

If performance deteriorates:

  1. Stop launching additional large jobs.
  2. Check whether existing jobs are still running.
  3. Test a single product.
  4. Review WordPress and hosting error logs.
  5. Check relevant server resource limits.
  6. Review the AI provider’s service status and account usage.
  7. Reduce batch sizes if supported.
  8. Contact your hosting provider or developer if the problem persists.

Avoid increasing PHP memory or execution limits without first understanding the issue and your hosting provider’s recommendations.

8. Monitoring Optimisation Progress

Good monitoring helps you distinguish successful processing from incomplete or failed work.

Use the progress indicators, dashboard information, history, or logs available in your installed version.

What to monitor

AreaWhat to look for
Job progressWhether the operation is advancing
CompletionWhether the selected workload finished
ErrorsFailed requests or products that could not be processed
API usageConsumption and unexpected increases
Output qualityAccuracy and usefulness of generated alt text
Website performanceUnexpected slowdowns or timeouts
Repeat processingWhether products are being processed unnecessarily

Keep a simple record

For larger projects, maintain a record of:

  • The date of each optimisation run.
  • The product group processed.
  • The approximate number of products selected.
  • Any errors encountered.
  • The results of quality checks.
  • Any changes made to settings.

This does not need to be complicated. A simple spreadsheet can help you track progress across a large catalogue.

Do not record API keys or other sensitive credentials in your tracking documents.

9. Maintaining Alt Text Quality at Scale

Processing a large number of images is useful only if the descriptions are appropriate.

Establish a quality standard

For your store, aim for descriptions that:

  • Accurately identify the visible subject.
  • Include important distinguishing details.
  • Use concise, natural language.
  • Avoid keyword stuffing.
  • Avoid unsupported product claims.
  • Reflect meaningful differences between images.

Review representative samples

After a bulk job, review a sample of products from different categories.

Include products with:

  • Straightforward product photographs.
  • Multiple views.
  • Complex patterns or colours.
  • Unusual shapes.
  • Personalised features.
  • Images that may be difficult for AI to interpret.

If you discover a recurring error, investigate whether the problem is related to the images, the AI provider, or the configuration before processing additional products.

Correct recurring problems

If generated descriptions are consistently too long, too generic, or stylistically inappropriate, review the settings available in your version before repeating the workload.

Where category-specific templates are supported, consider whether different product types need different descriptive approaches.

10. Troubleshooting Common Performance Problems

Problem: Bulk optimisation takes too long

Possible causes:

  • A large number of products or images.
  • Slow responses from the AI provider.
  • Provider rate limits.
  • Hosting restrictions.
  • Network interruptions.

Recommended actions:

  1. Test a smaller selection.
  2. Check provider usage and service status.
  3. Review available progress information.
  4. Avoid overlapping jobs.
  5. Contact your hosting provider if server-side problems persist.

Problem: A job appears to have stopped

Possible causes:

  • The request failed.
  • A background task was interrupted.
  • A timeout occurred.
  • The provider did not return a successful response.

Recommended actions:

  1. Check the job’s available status or history.
  2. Confirm whether any products were successfully processed.
  3. Review available error information.
  4. Test one product.
  5. Restart only after checking for an existing active job.

Do not assume a job failed completely simply because the interface stopped updating.

Problem: API usage is higher than expected

Possible causes:

  • Repeated optimisation.
  • Overlapping jobs.
  • A frequent schedule.
  • A larger-than-expected workload.
  • Unauthorised API use.

Recommended actions:

  1. Review provider usage records.
  2. Check the scope of recent jobs.
  3. Review scheduled optimisation settings.
  4. Investigate unexpected activity.
  5. Pause further processing until the cause is understood.

Problem: The WordPress dashboard becomes slow

Possible causes:

  • High server load.
  • Other active plugins or background jobs.
  • Resource limits.
  • Database or network problems.

Recommended actions:

  1. Pause new large optimisation runs.
  2. Check whether the slowdown continues when no optimisation is active.
  3. Review hosting and WordPress error logs.
  4. Test a small operation.
  5. Ask your hosting provider or developer to investigate persistent problems.

These are general operating approaches, not fixed technical requirements.

Small store

For a store with a relatively small catalogue:

  1. Configure the provider.
  2. Test several products.
  3. Review the results.
  4. Process the remaining products in manageable groups.
  5. Review the live product pages.

Manual optimisation may be sufficient if new products are added infrequently.

Medium-sized store

For a growing catalogue:

  1. Divide products into categories or logical groups.
  2. Test each group.
  3. Process products in batches.
  4. Review errors and output quality.
  5. Consider scheduled optimisation if your version supports it.
  6. Monitor API usage periodically.

Large store

For a large catalogue:

  1. Establish a documented optimisation plan.
  2. Back up the site before major changes.
  3. Use controlled batches.
  4. Avoid overlapping jobs.
  5. Monitor server and provider performance.
  6. Track completed work.
  7. Review samples from each product category.
  8. Expand the workflow only when it is reliable.

For very large stores, consult your hosting provider or developer before running substantial processing jobs on a production website.

12. Performance Checklist

Before beginning a significant optimisation project, confirm the following:

  • The AI provider is configured and working.
  • API usage limits and pricing are understood.
  • Existing alt text has been considered.
  • Product images are current and appropriate.
  • A website backup is available.
  • A small test batch has completed successfully.
  • The generated descriptions have been reviewed.
  • Batch sizes are appropriate for the environment.
  • Existing jobs have been checked before starting new ones.
  • Scheduled tasks have been configured deliberately.
  • Progress and errors can be reviewed using available tools.
  • A process exists for investigating failed jobs.

13. Final Recommendations

SmartDescribe Pro can help you manage image alt text across a growing WooCommerce catalogue, but effective optimisation requires more than simply selecting every product and starting a job.

For the best results:

  1. Prepare your catalogue before processing.
  2. Test your settings on a small selection.
  3. Use manageable batches.
  4. Avoid unnecessary repeat optimisation.
  5. Monitor API usage and hosting performance.
  6. Use scheduled processing only when it provides a clear benefit.
  7. Review output quality throughout the project.
  8. Maintain backups before substantial catalogue changes.

A reliable optimisation workflow balances speed, accuracy, cost, and website stability.

SmartDescribe Pro is a Cazgrae product. Available features, menu labels, processing methods, and scheduling behaviour may vary by installed version. Consult the documentation supplied with your installed release for feature-specific instructions.