Dry Run & Test Mode

Test your imports without making changes to your store

Overview

Dry Run (Test Mode) allows you to run an import without actually creating or updating any items in your WooCommerce store. This is perfect for testing import configurations, validating data, and identifying issues before running the real import.

When running in Dry Run mode, PrimeLink processes all the data, validates mappings, and generates a detailed report showing what would happen, but doesn't write anything to the database.

What Dry Run Does

Processes Everything

Dry Run mode processes your import exactly as a real import would:

  • Reads Data: Loads and parses your source data
  • Applies Filters: Processes all filters and XPath queries
  • Maps Fields: Applies all field mappings
  • Validates Data: Validates data format and requirements
  • Checks Matching: Tests matching criteria for existing items
  • Simulates Creation: Simulates creating new items
  • Simulates Updates: Simulates updating existing items

What It Doesn't Do

Dry Run mode does NOT:

  • Create Items: No products, orders, customers, etc. are created
  • Update Items: No existing items are modified
  • Write to Database: No database changes are made
  • Send Emails: No notifications are sent
  • Trigger Hooks: WooCommerce hooks are not triggered

Enabling Dry Run Mode

Step 6: Options & Scheduling

Enable Dry Run mode in Step 6 of the import wizard:

  1. Navigate to Step 6: Options & Scheduling
  2. Find the "Dry Run / Test Mode" option
  3. Enable the checkbox or toggle
  4. Continue to Step 7 and Step 8 as normal

Advanced Options

Some advanced options may be available:

  • Limit number of rows to test (e.g., test first 10 rows)
  • Test specific data ranges
  • Skip certain validations (for testing purposes)

Dry Run Report

Report Contents

After running a Dry Run, you'll receive a detailed report:

  • Total Rows Processed: Number of rows from source data
  • Rows That Would Be Created: New items that would be created
  • Rows That Would Be Updated: Existing items that would be updated
  • Rows Skipped: Rows that would be skipped (filters, errors, etc.)
  • Validation Errors: Data validation issues found
  • Mapping Issues: Field mapping problems
  • Sample Data: Preview of how data would look

Error Details

The report includes detailed error information:

  • Row numbers with errors
  • Error messages and descriptions
  • Field-level validation issues
  • Suggestions for fixing errors

Using Dry Run Results

Review the Report

After Dry Run completes, review the report:

  1. Check total rows processed
  2. Verify number of items that would be created/updated
  3. Review any errors or warnings
  4. Examine sample data to verify mappings
  5. Check validation results

Fix Issues

If issues are found:

  • Fix data format issues in source file
  • Adjust field mappings
  • Update filters or XPath queries
  • Fix validation errors
  • Correct matching criteria

Run Again

After fixing issues:

  • Run Dry Run again to verify fixes
  • Repeat until report shows no errors
  • When satisfied, disable Dry Run and run real import

Best Practices

  • Always test first: Run Dry Run before any real import
  • Test with sample data: Use a small sample file first
  • Review thoroughly: Check all aspects of the report
  • Fix all errors: Resolve all issues before real import
  • Verify mappings: Check sample data matches expectations
  • Test incrementally: Test one section at a time if needed
  • Document findings: Keep notes of issues found and fixes applied

Common Use Cases

Testing New Import Configuration

  • Create new import configuration
  • Run Dry Run to test mappings
  • Verify data is processed correctly
  • Fix any issues found
  • Run real import when ready

Validating Data Format

  • Receive new data file
  • Run Dry Run to check format
  • Identify data format issues
  • Fix source data if needed
  • Re-test until validation passes

Testing Filters

  • Set up filters or XPath queries
  • Run Dry Run to see filtered results
  • Verify correct rows are included/excluded
  • Adjust filters as needed
  • Re-test until filters work correctly

Limitations

What Dry Run Cannot Test

  • Database Constraints: Some database-level constraints may not be detected
  • WooCommerce Hooks: Third-party plugin hooks won't run
  • Performance: Actual import performance may differ
  • External Dependencies: External API calls or services won't be tested
  • Image Downloads: Image download and processing won't occur

Important Notes

💡 Tip: While Dry Run is very thorough, it's still a simulation. Some edge cases or real-world scenarios may only appear during actual import. Always backup your store before running real imports, even after successful Dry Run tests.

Common Issues and Solutions

Dry Run Shows Errors But Data Looks Correct

  • Check validation rules - may be too strict
  • Verify data format matches expected format
  • Check for hidden characters or encoding issues
  • Review field mapping requirements

Dry Run Takes Too Long

  • Use sample data (limit rows) for testing
  • Test with smaller file first
  • Check server performance settings
  • Optimize filters and queries

Dry Run Shows Different Results Than Expected

  • Verify filters are applied correctly
  • Check matching criteria logic
  • Review field mapping transformations
  • Verify source data hasn't changed

Next Steps

🔄 Rollback & Tracking

Learn how to rollback imports if needed

Learn More →
⚡ Performance & Optimization

Optimize import performance and settings

Learn More →
📥 Creating Imports

Complete guide to creating imports

Learn More →