Japanized for WooCommerce
| 开发者 |
artisan-workshop-1
shohei.tanaka mt8biz ssec4dev |
|---|---|
| 更新时间 | 2026年4月23日 16:30 |
| 捐献地址: | 去捐款 |
| PHP版本: | 6.7 及以上 |
| WordPress版本: | 6.9.4 |
| 版权: | GPLv3 |
| 版权网址: | 版权信息 |
标签
下载
2.6.4
2.7.11
2.2.5
2.2.6
2.2.8
2.6.3
2.1.5
2.1.7
2.2.1
2.2.14
2.6.26
2.6.27
2.7.17
2.1.9
2.6.21
2.7.14
2.7.15
2.0.0
2.1.0
2.2.16
2.2.4
2.1.2
2.2.18
2.2.19
2.9.6
2.3.3
2.3.6
2.4.0
2.4.1
2.5.0
2.8.2
2.1.16
2.3.2
2.3.4
2.5.4
2.3.1
2.3.5
2.5.6
2.5.7
2.0.6
2.2.11
2.2.17
2.8.3
2.1.13
2.5.2
2.6.15
2.0.5
2.0.7
2.1.14
2.1.3
2.2.13
2.5.8
2.2.15
2.5.11
2.5.12
2.1.1
2.2.21
2.5.13
2.5.5
2.6.0
2.6.1
2.6.2
2.6.8
2.7.16
2.6.6
2.6.7
2.0.3
2.9.7
2.9.8
2.6.11
2.6.13
2.0.1
2.0.4
2.3.7
2.3.8
2.6.10
2.6.16
2.6.42
2.6.5
2.7.13
2.9.5
2.9.9
2.6.14
2.6.22
2.1.4
2.2.7
2.6.24
2.6.33
2.8.0
2.8.1
2.6.37
2.6.40
2.7.2
2.7.3
2.1.8
2.5.1
2.5.10
2.5.3
2.6.12
2.6.25
2.6.28
2.6.29
2.6.30
2.6.31
2.6.32
2.6.34
2.6.35
2.6.36
2.6.39
2.6.43
2.6.9
2.7.0
2.7.1
2.6.19
2.6.20
2.7.4
2.7.5
2.6.17
2.6.23
2.6.41
2.7.6
2.7.7
2.7.8
2.7.9
2.0.2
2.1.10
2.5.9
2.7.10
2.1.11
2.1.12
2.1.15
2.1.6
2.2.0
2.2.12
2.2.2
2.2.20
2.2.3
2.3.0
2.6.38
2.7.12
2.8.4
2.8.5
2.9.4
详情介绍:
Japanized for WooCommerce is the essential toolkit for running a WooCommerce store in Japan. This plugin bridges the gap between WooCommerce's global features and Japan's unique e-commerce requirements.
Why You Need This Plugin
Running an online store in Japan requires specific features that standard WooCommerce doesn't provide out of the box:
- Japanese address formats with proper field ordering (postal code, prefecture, city, address lines)
- Name reading fields (Yomigana/Furigana) for accurate customer identification
- Delivery date and time selection that customers expect
- Popular Japanese payment methods like bank transfer and COD
- Legal compliance with Japan's Specified Commercial Transaction Act (特定商取引法) Who Should Use This
- Japanese e-commerce businesses using WooCommerce
- International stores shipping to Japanese customers
- Anyone who needs Japanese address handling and payment methods
- Stores requiring delivery date/time selection functionality Seamless Integration
- Name reading (Yomigana/Furigana) input fields for billing and shipping addresses
- Honorific title (様/sama) automatically added after customer names
- Japanese-style address format with proper field ordering
- Auto-fill address from postal code using Yahoo! API integration
- Company name field support Shipping & Delivery
- Delivery date and time selection at checkout
- Delivery time slot management
- Holiday and non-delivery day settings
- Weekend and specific date exclusions
- Delivery-related fields hidden when free shipping is applied Payment Methods
- Bank Transfer (Japanese banks)
- Japan Post Bank Transfer
- Cash on Delivery (COD) with fee calculation
- COD subscription support
- Pay at Store (over-the-counter payment)
- Paidy (Buy Now, Pay Later) - Official Japanese payment gateway Legal & Compliance
- Specified Commercial Transaction Act (特定商取引法) page creator
- Shortcode support for legal information display
- Customizable legal notice templates Additional Features
- Email template optimization for Japanese format
- Address validation for Japanese postal codes
- Affiliate integration (A8.net, Access Trade, Value Commerce)
- WooCommerce Blocks compatibility
- Security scanning and malware detection Note: Paidy Checkout are also available as standalone payment plugins.
安装:
Minimum Requirements
- WordPress 6.0 or greater
- WooCommerce 8.0 or greater
- PHP version 8.3 or greater
- MySQL version 5.6 or greater
- WP Memory limit of 64 MB or greater (128 MB or higher is preferred)
屏幕截图:
常见问题:
Do I need this plugin to use WooCommerce in Japan?
While WooCommerce can work in Japan without this plugin, Japanized for WooCommerce provides essential features that Japanese customers expect, such as delivery date selection, name reading fields (Yomigana), and local payment methods. It significantly improves the user experience for Japanese e-commerce.
Does this plugin work with WooCommerce Blocks?
Yes! Version 2.8.0 and later fully supports the new WooCommerce Blocks checkout experience, including delivery date selection and custom address fields.
How do I enable the postal code auto-fill feature?
You need to obtain a free Yahoo! Japan Application ID from the Yahoo! Developer Network. Once you have the ID, enter it in the WooCommerce → Settings → Japan Settings → Address Form section.(Classic Checkout only)
Which payment methods are included?
The plugin includes: Bank Transfer (Japanese banks), Japan Post Bank Transfer, Cash on Delivery (COD) with fee calculation, Pay at Store, Paidy (Buy Now, Pay Later), and PayPal Checkout optimized for Japan. Paidy and PayPal are also available as standalone plugins.
Can I use only specific features and disable others?
Yes, absolutely! All features are modular and can be enabled or disabled individually from the plugin settings. You only need to activate the features your store requires.
Is the plugin compatible with multilingual sites?
Yes, the plugin is compatible with WPML and other multilingual plugins. It automatically detects the language and adjusts features accordingly. Japanese-specific features are only applied when the site language is set to Japanese.
How do I set up delivery date and time selection?
Go to WooCommerce → Settings → Japan Settings → Delivery Date. You can configure available delivery times, set holidays, exclude specific days of the week, and customize the delivery date display format.
Does this plugin modify WooCommerce core files?
No, the plugin uses WordPress and WooCommerce hooks and filters. It doesn't modify any core files, making it safe to use and easy to update.
Where can I get support?
For support, please visit the plugin support forum on WordPress.org or check the official documentation.
Is this plugin free?
Yes, Japanized for WooCommerce is completely free and open source under the GPLv3 license.
更新日志:
2.9.9 - 2026-04-23
- Fixed - COD fee not applied in Classic Checkout (Shortcode) or Block Checkout because
jp4wc_calculate_order_totalsread fromwoocommerce_cod_settingswhile the JP4WC admin UI saves towc4jp-extra_charge_*options; settings are now merged at runtime with JP4WC values taking precedence - Fixed -
extra_charge_calc_taxesmismatch: React admin UI storedyes/nobut PHP expectedno-tax/tax-excl/tax-incl; legacy values are now normalised on read and the admin UI updated to a 3-way select - Fixed - Stale
jp4wc_gateway_idsession value could cause COD fee to be silently skipped in Classic Checkout (double session-check removed; gateway ID resolved once and passed through the entire calculation) - Improved - Block Checkout fee script now uses exponential back-off retry (100 ms → 10 s) instead of fixed 1500 ms / 3000 ms timeouts to wait for
wc/store/paymentstore readiness - Added - PRO-ready filter hooks for COD fee:
jp4wc_cod_fee_settings,jp4wc_cod_fee_name,jp4wc_cod_fee_amount,jp4wc_cod_fee_is_applicable,jp4wc_cod_fee_tax_class(all@since 2.9.8) - Changed - Minimum required PHP version raised from 8.1 to 8.3
- Fixed - Paidy webhook permission check rejected all notifications from Paidy (no
x-paidy-signatureheader) causing orders to remain "pending" and be auto-cancelled - Fixed - Paidy webhook signature verification used wrong option name
secret_key(non-existent); corrected toapi_secret_key/test_api_secret_keybased on test mode - Fixed - Bank transfer (
bankjp) account skip condition! isset( $account_names[$i] )was always false; replaced withempty( $bank_names[$i] ) && empty( $name )to properly skip blank rows - Added - Deduplication of bank transfer account entries on save and load to prevent double display caused by corrupted option data
- Fixed - Yomigana (読み仮名) fields not displayed in HTML emails when using Block Checkout; corrected meta key fallback from
_wc_other/to_wc_billing/and_wc_shipping/prefixes - Fixed - Yomigana displayed twice on order received (thank-you) page when using Block Checkout
- Fixed - Yomigana appearing as a separate bold
<strong>list below the formatted address in emails and thank-you page; now suppressed viashow_in_order_confirmation: falseand block render filter - Fixed - "(よみがなを確認するには「編集」をクリックしてください。)" message incorrectly appearing in new order emails
- Fixed - Customer email salutation showing first name only instead of full name (姓名); email context detection now uses
WC_Email::$sendingflag for reliability with WC 10.7+ BlockEmailRenderer - Added - Country is hidden from formatted address in emails and thank-you page when the store sells to only one country
- Fixed - White screen on frontend caused by fatal error in Paidy blocks support when gateway is not registered
- Fixed -
WC_Gateway_Paidy not foundfatal error on admin pages when WooCommerce is installed with a non-standard path (e.g. wp-env) - Fixed -
jp4wc_has_orders_in_last_5_daysundefined function error caused byis_woocommerce_active()returning false in non-standard install paths - Fixed - Google Calendar consultation button not displaying on some hosting environments (Xserver) due to CSP/WAF blocking external script injection; replaced with a plain link
- Added -
jp4wc_allowed_setting_keysfilter to allow add-on plugins to register their own setting keys with the REST API - Added -
jp4wc_setting_option_mapfilter to allow add-on plugins to map REST keys to their existing WordPress option names - Added -
jp4wc.settings.tabsandjp4wc.settings.tabContentJS filters via@wordpress/hooksto allow add-on plugins to inject tabs into the React settings UI
- Fixed - COD fee not calculating in Classic Checkout due to
is_admin()returning true for admin-ajax.php requests - Fixed - COD fee showing for non-COD payment methods in Classic Checkout (stale session value)
- Fixed - COD fee incorrectly displayed on cart page (now checkout-only)
- Fixed - Delivery date/time fields not appearing in Checkout Block (changed
class_existstointerface_existsfor IntegrationInterface) - Fixed - Delivery select placeholder showing WooCommerce auto-generated text instead of admin-configured label
- Fixed - Paidy order completion hook firing multiple times (added
paidy_capture_idguard) - Fixed -
_load_textdomain_just_in_timewarning in WordPress 6.7+ by deferring translations to afterinit - Fixed -
JP4WC_Frameworkconfig strings now lazy-loaded atinitpriority 2 to prevent early textdomain calls - Fixed -
WC_Paidy_Endpointinstantiation deferred toinitpriority 11 to prevent earlyWC_Gateway_Paidyconstruction - Removed - PayPal settings removed from admin settings UI and API