Persian Kit

Plugin comparison

Reviewed October 8, 2026

Compare features, then inspect the results of specific tests.

Persian Kit

Reviewed source f05b63e

Persian WooCommerce

Version 10.0.5

Feature comparison

Based on documentation and source review.

What the symbols mean
SupportedNot includedNot verified — may be available

Support listed here does not mean every feature was tested.

FeaturePersian KitPersian WooCommerce
Dates and reports 4
Jalali dates in WordPressIncludedIncluded
Jalali order datesIncludedIncluded
Reports by Jalali datesJalali periods in WooCommerce AnalyticsJalali sales and revenue reports
Additional store reportsNo separate report reviewedInventory, stock value and customers
Checkout 7
Iranian provinces and citiesIncludedIncluded
Phone number validationIncludedIncluded
Postcode validationIncludedIncluded
Accept Persian digits in phone and postcodeIncludedIncluded
National ID fieldOptionalNot verified
Limit orders to selected provincesIncludedIncluded
Shorter checkoutFor all-virtual cartsFor download stores
Store settings 5
Text instead of a price“Call for price” when price is emptyCustom price text
Added currency optionsThousand toman and thousand rialToman, rial, thousand toman and thousand rial
Payment gatewayNot includedZibal included
Replace interface wordsNot verifiedWord replacement tool
Change admin fontIncludedIncluded
Requirements 2
Minimum WordPress6.86.8
Minimum PHP8.17.4

Form integrations may cover different fields. Changing a currency setting does not convert stored prices.

Sources & migration notes
Persian Kit documentationPersian WooCommerce

Review supported settings and Iranian address mappings before import. Persian WooCommerce Shipping is a separate plugin: its shipping methods, city rates, maps and SMS services do not transfer into Persian Kit.

Try any migration on a backed-up test copy first.

Test results

Each plugin was enabled separately on the same Persian WordPress site. Results apply to these settings and examples.

TestPersian KitPersian WooCommerce
Search for کتاب or كتابFound both sample postsFound one sample post
Jalali leap day and new yearBoth dates correctBoth dates correct
Stored dates after displayUnchangedUnchanged
Date format for software¹Original format preservedFormat changed

¹ One WordPress date function was tested. This does not establish how every feed or SEO plugin behaves.

Test inputs and exact output

Two posts were saved: one with Persian ک and one with Arabic ك. The saved text was not changed.

Persian WooCommerce changed both queries to Persian letters and returned the Persian-spelled post. Persian Kit also found the post saved with Arabic letters.

get_the_date(DATE_W3C) · same post2026-10-04T12:00:00+03:301405-07-12\+033012:00:00+03:30Visible date in both: 1405-07-12 12:00

Performance

Execution times varied between the homepage, search, admin and checkout. These local measurements do not establish a general speed ranking.

Homepage

Median PHP time · milliseconds
WordPress + WooCommerce45.7 ms
+ Persian Kit46 ms
+ Persian WooCommerce53.8 ms
30 requests per configuration. Lower means less server processing time.
All measurements & test settings4 screens · 30 samples each

The same small test site, with date features enabled. These numbers measure PHP execution on the server, not page loading in a browser. Each plugin performed somewhat different work.

Homepage

PHP median / p95, milliseconds
ConfigurationMedianp95
WordPress + WooCommerce45.7116.7
+ Persian Kit46115.9
+ Persian WooCommerce53.862.7

Search

PHP median / p95, milliseconds
ConfigurationMedianp95
WordPress + WooCommerce45.978.3
+ Persian Kit52.561.7
+ Persian WooCommerce60.196.7

Posts in admin

PHP median / p95, milliseconds
ConfigurationMedianp95
WordPress + WooCommerce62.798
+ Persian Kit67.7125.9
+ Persian WooCommerce69.2123.8

Classic checkout

PHP median / p95, milliseconds
ConfigurationMedianp95
WordPress + WooCommerce49.657.6
+ Persian Kit46.771
+ Persian WooCommerce60.998.7

Lower is better for this metric. p95 shows the slower end of the sample. Configuration and enabled work differ between plugins; close numbers are not a reliable ranking. Persian Kit’s spelling search was off for this date-focused benchmark. Memory, query counts and individual samples are included in the downloadable results.

Code checks

Plugin Check was run on all three plugins. Persian Kit’s own tests were also run; the other plugins’ test suites were not run.

Tests, coding standards & limitations

Persian Kit’s test suite

985 PHP tests and 163 JavaScript tests passed. Another 443 PHP tests and 3 JavaScript tests were skipped. These results do not validate every supported integration.

Coding standards, precisely

Persian Kit’s configured PHPCS checks passed: selected WordPress security, database, translation and API rules. Its formatting uses PSR-12. This is not full WordPress coding-style compliance or a security audit.

Plugin Check results and their limits

The same Plugin Check 2.1.0 static scan reported 0 errors / 8 warnings for Persian Kit, 157 errors / 215 warnings for Persian WooCommerce.

These counts are messages from an automated tool. They have not been individually reviewed and do not show which plugin is more secure. Persian Kit’s eight warnings concern integration hook names. Runtime checks and a manual security review were not performed.

About Plugin Check

METHOD & LIMITS

This comparison was prepared by Eram, the maker of Persian Kit, on October 8, 2026. The versions reviewed are shown at the top of this page.

Environment, limitations & downloads
  • WordPress 7.0.2 · PHP 8.3.33 · WooCommerce 9.9.7 · MariaDB 11.8.8 · fa_IR · Asia/Tehran.
  • A minimal theme, synthetic posts, one virtual product and classic checkout. WooCommerce was active in every run; each candidate was enabled separately. External requests and scheduled cron were disabled.
  • Not tested: real payments, checkout submission, block checkout, migration on a live site, large catalogs, every theme or the full PHP/WordPress compatibility matrix.