REEID COMPATIBILITY DIRECTORY

Explore WordPress products and their REEID Translate compatibility.

Browse WordPress plugins, themes, builders and product ecosystems, with compatibility status and integration details for REEID Translate Pro.

Browse the directory
Featured integrations

Verified integrations · Compatibility information · Products awaiting verification · Searchable directory

HOW THE DIRECTORY WORKS

Compatibility information, managed from one source.

Find products relevant to your WordPress stack and check their current REEID compatibility status.

  • Search by product name
  • Browse compatibility status
  • Open available integration guides

PUBLISHED COMPATIBILITY GUIDES

Explore the WordPress ecosystem with REEID Translate.

Search by product name to view compatibility status, available integration documentation, and supported multilingual workflows.

Wcik Pennsylvania Shipping

Wcik Pennsylvania Shipping — {"task": "Research and extract factual plugin content evidence for the specified Integration Category. Do not decide REEID support or compatibility.", "plugin_identity": {"name": "Wcik Pennsylvania Shipping", "slug": "wcik-pennsylvania-shipping", "homepage_url": "http://imran1.com/woo-checkout-pennsylvania-based-surcharge-fee-my-clients-custom-solution/", "plugin_url": "http://imran1.com/woo-checkout-pennsylvania-based-surcharge-fee-my-clients-custom-solution/"}, "official_search_domains": ["imran1.com", "wordpress.org", "plugins.svn.wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search when supplied evidence does not explicitly establish the evidence_focus values.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent content surfaces, fields, settings, or behavior.", "Do not decide compatibility, translation support, approval, or eligibility.", "Do not assign canonical surface identifiers or canonical surface types.", "Do not assign translation_candidate or similar decision fields.", "Do not use REEID capability contracts, blueprints, category profiles, or internal rules to infer support.", "Follow category_research.rules for what to investigate in this Integration Category.", "If evidence_focus is supplied, investigate every look_for_literal_terms value independently; do not stop after finding only some of them.", "For every evidence_focus value, search the allowed official sources for explicit supporting documentation before concluding that it is unavailable.", "A translation-category result is incomplete if any evidence_focus value has been neither supported by an observation nor explicitly accounted for in unknowns.", "For each evidence_focus value that remains unsupported after research, add a concise unknowns entry stating that official evidence for that value was not found.", "Evidence focus terms are search hints only. They are not proof that the plugin contains, manages, exposes, or supports those values.", "Never output an evidence focus term as an observation unless supplied evidence or an official source explicitly names that textual value.", "The supplied description, readme, FAQ, installation text, metadata, and documentation are evidence sources only; never treat their own prose as plugin-managed website content.", "Extract only literal evidence for explicitly named website textual values.", "text must be an exact phrase copied from the supporting supplied evidence or official source. Never invent, normalize, rename, summarize, classify, or semantically reinterpret it.", "evidence must be an exact supporting sentence or passage copied from the supplied evidence or official source and must contain or directly establish text.", "For translation-category observations, inspect supplied official evidence first. When the supporting passage exists in supplied evidence, source_url may be empty because provenance is validated against that official corpus. Use web research only when supplied evidence does not establish the value; for web-researched evidence, source_url must be the exact official page URL containing the evidence.", "Do not infer location, ownership, configurability, visibility, translation relevance, canonical type, or support.", "Do not create observations from documentation prose merely because that prose itself contains human-readable text.", "Do not create observations from FAQ copy, installation instructions, privacy notices, plugin metadata, requirements, ratings, marketing copy, or from the mere existence of containers, screens, forms, product pages, carts, dashboards, integrations, APIs, systems, widgets, blocks, or features. Official documentation or feature prose may support an observation only when it explicitly names or quotes the actual website textual value being documented.", "If the evidence does not explicitly name a website textual value, return no observation for it.", "features are for a concise human-readable capability summary, not a documentation inventory.", "Return 4 to 8 high-value factual capabilities that best explain what the plugin does.", "Group related settings and implementation details into broader capability statements instead of listing individual settings.", "Prioritize capabilities that help a prospective user understand the plugin's main functionality, important integrations, and distinctive behavior.", "Prefer stable product capabilities over minor configuration options, UI settings, technical implementation details, or repeated variations of the same capability.", "Do not include ratings, installation counts, version requirements, marketing claims, or promotional language.", "Do not repeat the same capability in different wording.", "Use concise factual sentences suitable for a public integration directory and search indexing.", "features may contain concise factual capabilities directly stated by the evidence, but features are not translation evidence.", "unknowns may record areas where the evidence does not explicitly establish a textual value.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name. Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name. Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand. Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording. The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity. When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7. Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name. If no shorter distinctive product or brand phrase can be selected safely, return the full plugin_identity.name.", "seo_keyword_candidates must contain 2 to 4 concise plugin-specific identity phrases based on seo_display_name, plugin_identity.name, and plugin_identity.slug. When the slug corresponds to a brand or product phrase present in the official name, include that phrase as a candidate. Do not return generic category-only phrases and do not assert REEID compatibility, verification, translation support, or other unsupported state claims."], "category_research": {"integration_category": "WooCommerce", "mode": "translation", "rules": ["Actively research official WooCommerce documentation for individual product text values managed by WooCommerce.", "Prioritize product titles or names, product descriptions including short or long descriptions, and product attributes including names, labels, options, or values.", "A product, product page, product block, catalog, variation, or attribute system is not itself a textual value. Extract an observation only when official evidence explicitly names or quotes the product text-bearing value."]}, "evidence_focus": {"integration_category": "WooCommerce", "look_for_literal_terms": ["product title", "product name", "product description", "long description", "short description", "product attribute", "attribute label", "attribute name", "attribute option", "attribute value", "attribute values", "name of an attribute", "value of an attribute", "values of an attribute", "values of the attributes"]}, "output_schema": {"observations": [{"text": "", "evidence": "", "source_url": ""}], "features": [], "unknowns": [], "seo_display_name": "", "seo_keyword_candidates": []}, "evidence": {"description": "WooCommerce Plugin that adds checkout fields and surcharge for shipping to pennsylvania state. A Custom solution for one of my client, On checkout page when you will choose billing or shipping state to pennsylvania, the additional fields will be displayed and he surcharge fee will be added to the order totals.\n Minimum Requirements\n WooCommerce 7.0 or greater\n WordPress 6.5 or greater\n PHP version 8.2 or greater (PHP 8.1 or greater is recommended)\n MySQL version 5.6 or greater (MySQL 5.6 is recommended)\n Automatic installation\n Log in to your WordPress dashboard\n Navigate to the Plugins menu and click Add New.\n Search and locate ‘Wcik Pennsylvania Shipping’.\n Click ‘Install Now’\n Manual installation\n The manual installation method involves downloading Wcik Pennsylvania Shipping’ plugin and uploading it to your webserver via FTP application. You may find more\n instructions on how to do this here (https://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation).", "sections": {"faq": "Can I go back to WooCommerce default settings at a later point?\n Yes. you can uninstall the plugin at any stage.", "readme_text": "===Wcik Pennsylvania Shipping===\nContributors: awanhrp\nlink: https://codeinform.com \nTags: WooCommere Pennsylvania Shipping checkout fields and surcharge\nRequires at least: 6.0 \nTested up to: 6.8.0\nRequires PHP: 8.2 \nStable tag: 1.4.0\nLicense: GPLv2 or later \nLicense URI: http://www.gnu.org/licenses/gpl-2.0.htmlWcik\n\n== Description ==\nWooCommerce Plugin that adds checkout fields and surcharge for shipping to pennsylvania state. A Custom solution for one of my client, On checkout page when you will choose billing or shipping state to pennsylvania, the additional fields will be displayed and he surcharge fee will be added to the order totals.\n\n= Minimum Requirements =\n* WooCommerce 7.0 or greater\n* WordPress 6.5 or greater\n* PHP version 8.2 or greater (PHP 8.1 or greater is recommended)\n* MySQL version 5.6 or greater (MySQL 5.6 is recommended)\n\n= Automatic installation =\n1. Log in to your WordPress dashboard\n2. Navigate to the Plugins menu and click Add New.\n3. Search and locate 'Wcik Pennsylvania Shipping'.\n4. Click 'Install Now'\n\n= Manual installation =\nThe manual installation method involves downloading Wcik Pennsylvania Shipping' plugin and uploading it to your webserver via FTP application. You may find more \n\ninstructions on how to do this here (http://codex.wordpress.org/Managing_Plugins#Manual_Plugin_Installation).\n\n== Frequently Asked Questions ==\n= Can I go back to WooCommerce default settings at a later point? =\nYes. you can uninstall the plugin at any stage. \n\n== Screenshots ==\n1. Manufacturers\n\n== Change log ==\n= 1.0.0 =\n* First Release\n* WooCommerce Plugin that adds checkout fields and surcharge for shipping to pennsylvania state"}}}

Product website WordPress.org
Shopping Cart
Scroll to Top