Polski for WooCommerce -- WordPress 插件

开发者	motylanogha
更新时间	2026年9月15日 00:42
PHP版本:	8.1 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

Polski for WooCommerce is a free WooCommerce plugin for Polish online shops. It issues numbered VAT invoices, and helps you organise GPSR product data, the Omnibus lowest-price history, GDPR consents, the right of withdrawal, VAT ID (NIP) handling, unit prices, hooks for KSeF processes, DSA reports and storefront modules. The plugin is modular. You can enable only the features a given shop needs, for example GPSR, Omnibus, cart consents, withdrawals, unit prices, food data, a wishlist, a product comparison or AJAX search. Polski helps you configure the technical shop processes related to the Polish and EU market. It is not legal advice and does not guarantee regulatory compliance. Your shop configuration, terms, products and obligations always have to be verified for your specific business. Documentation and links

Documentation - plogins.com/polski/docs/
Plugin page - plogins.com/polski/
Source code - github.com/wppoland/polski
Bug reports and feature requests - github.com/wppoland/polski/issues
Discussions and questions - github.com/wppoland/polski/discussions
Polski PRO - plogins.com/polski-pro/

为什么选择 Polski for WooCommerce？

One plugin, many modules - GPSR, Omnibus, GDPR, right of withdrawal, product data and storefront modules in one place.
Built for Polish shops - features designed for WooCommerce stores selling in Poland or to Polish customers.
Free and open source - the core product, checkout and storefront tools are available at no cost.
Modern code - PHP 8.1+, a React admin panel, REST API and WP-CLI support.
WooCommerce blocks support - compatible with both the classic and block-based cart and checkout.
HPOS compatible - supports WooCommerce High-Performance Order Storage.

Key modules

GPSR product fields - manufacturer, importer and EU responsible person, each with a postal address and the electronic contact art. 19 asks for, plus product identifiers, safety warnings and instructions, split into a responsibility group and a safety group, including CSV import and export.
Omnibus price history - records and displays the lowest price from the last 30 days on discounted products.
Deposit scheme (system kaucyjny) - adds the statutory deposit to beverages in covered packaging, untaxed and on its own checkout line.
GDPR consents and checkboxes - configurable consents at checkout, registration and reviews, with a consent log.
Right of withdrawal and returns - requests from the customer account, e-mail confirmations and a request log.
VAT ID (NIP) and KSeF hooks - detection of orders with a VAT ID, a KSeF flag and hooks for invoicing integrations.
EU VAT ID check (VIES) - confirms a customer's EU VAT number against the European Commission's register and records the consultation number on the order.
VAT margin scheme - the art. 120 annotation on invoices for second-hand goods, works of art, collectors' items and antiques.
GTU markings - one of the thirteen JPK_V7 goods and services groups per product, printed against its own line on the invoice.
DSA reports - a point of contact, an illegal-content report form and an admin panel.
Shop health monitor - passive monitoring of frontend errors, checkout issues and sales anomalies.
Security incident log - an internal log of incidents, outages, vulnerabilities and follow-up actions.
Product environmental fields - a basis for green claims, certificates and expiry dates.
Verified purchase badge - a badge on reviews from customers who bought the product.
AI transparency (AI Act art. 50) - a clear "classified by AI" marker on return reasons processed by the optional AI classifier, filterable in the admin withdrawals list. The storefront disclosure of AI-generated product copy is a Polski PRO feature, since it labels copy from the Pro AI description generator.

Checkout, consents and returns

Consent checkboxes - consents at order, registration and reviews, with the option to enable only selected fields.
Omnibus price history - automatic recording and display of the lowest price from 30 days.
Right of withdrawal - withdrawal/return forms and requests from the customer account.
Double e-mail confirmation - e-mail address confirmation during customer registration.
Shop pages - link the terms, privacy policy and withdrawal content into WooCommerce notices.
Dispute resolution - an ODR information module for the shop's information pages.
Consent log - logging of consents with date, context, IP address and content version.

Product data and labelling

Unit prices - price per kg, litre, metre, piece or a custom unit.
Delivery time - estimated delivery time on product pages and product lists.
Tax information - gross/net messages and the VAT rate.
Price display - configuration of how prices are presented in the shop.
Food data - composition, nutrition values, allergens, origin, distributor and other fields for grocery shops.

Storefront modules

Wishlist - save products for later.
Product comparison - compare products side by side.
Waitlist - back-in-stock notifications for products.
Quick view - preview a product without opening the product page.
Gallery zoom - enhanced product image zoom.
Product video - add a video on the product page.
Product slider - a carousel of products and collections.
Infinite scroll - automatic loading of more products.
Product tab manager - configure the tabs on the product page.
AJAX filters - filter products without reloading the page.
AJAX search - live product search, matching the title, the SKU, category names and the values of the global attributes you choose to index.
Product badges - sale, new, featured and custom labels.
Promotional popups - popup campaigns in the shop.

Admin and developer tools

React panel - manage modules and settings.
REST API - an API for settings, checkboxes, legal pages, withdrawals and search.
WP-CLI - commands to manage selected features from the terminal.
CSV import and export - bulk management of product data, including GPSR.
Shortcodes - embed GPSR information, withdrawal forms, DSA reports and other elements.
Database migrations - versioned and safe updates of data structures.
Integration hooks - filters and actions for KSeF, invoicing and integrations with other plugins.
Audit scope - DPA, DSA, KSeF readiness, environmental-claim control, verified reviews and security incidents.

You may also like these plugins More free WooCommerce plugins from WPPoland:

Plogins Tiers - quantity and volume pricing tiers with a server-rendered price table.
Plogins Waitlist - back-in-stock waitlist that emails shoppers the moment a product returns.
Sieve - Search & Filter - fast AJAX product search and filtering for WooCommerce, with no jQuery.

Browse the full catalogue at plogins.com/ . Reporting a security issue: email hello@wppoland.com, and under our coordinated disclosure policy we confirm within two business days, assess within five, and patch a critical issue within seven days of confirming it.

1.37.9

Fixed: turning the "Right of withdrawal (14 days)" module off left most of it running. The withdrawal call to action kept appearing in customer order emails, the "Polski withdrawal" box kept rendering on the order edit screen, the plugin's own withdrawal order statuses stayed registered, and the per-product withdrawal exemption field stayed on the product editor. Eighteen services belonging to the module now refuse to register their hooks while it is off. This matters to any shop using the WooCommerce 11.1 native Order Withdrawal feature, which until now ran alongside ours. Reported by strid3rr on the support forum.
Note: the privacy exporter and eraser for withdrawal data deliberately keep running with the module off, so a GDPR request still reaches data the shop already collected.

1.37.8

Fixed: the order CSV export held every matching order in memory before writing a row, the stock CSV export held every product, and the daily double opt-in cleanup asked for every unverified account in one query. A store with a real backlog could exhaust the memory limit halfway through. Both exports now read their IDs in one query and hydrate 200 rows at a time, and the cleanup walks 200 accounts per query; the order export batch size is filterable via polski/order_export/batch_size, the cleanup batch via polski/doi/cleanup_batch_size.
Fixed: an export could repeat or lose a row. The list of IDs is fixed before the first row is written, so an order or product placed, saved or trashed while the export runs can no longer push a row into the file twice or out of it. A row whose order or product is gone by the time its batch is read is simply missing, and no other row moves. The values are read with the batch, not held from the snapshot, so an edit that lands before a row is read is in the file. An order keeps its row through a status change. A product does not: the stock export asks for published products, so one moved to draft after the snapshot has no row, the same as one that was trashed.
Fixed: both CSV exports sent their download headers before doing any work, so a fatal, an exhausted memory limit or a hit time limit reached the browser as HTTP 200 with a short file attached, which looks like a complete export. Each file is now built to a temporary file first, so a failure produces a visible error page again.
Fixed: the double opt-in cleanup advanced its position only past accounts it kept. If WordPress refused to delete an account, the loop re-read and re-attempted the same batch instead of finishing. Accounts it does not remove are now excluded from the next query, so every pass makes progress.
Changed: the expert review editor picks a product with WooCommerce's own search field instead of a dropdown that held every published product.
Changed: the stock export preview reports how many rows it is showing instead of the size of the whole catalogue, which is what made it load the catalogue.
Note: 1.37.4 through 1.37.7 were never released, so this is the first release after 1.37.3. 1.37.4 claimed a secondary sort made paging safe; it does not, paging over a table the store is still writing to repeats and skips rows whatever the sort is. 1.37.5 replaced the paging with hydration by ID, but asked the product query for post__in, which it does not accept: it overwrites that argument with its own empty include default and drops it, leaving the limit to hand back the newest products instead. On a catalogue of 450 products that export wrote 200 rows and lost 250. Products are now hydrated by include, two unit tests walk the export over a catalogue larger than one batch, and both of them run in the release preflight, next to a check that fails when a function in the source both queries products and mentions post__in. That check reads the source as PHP tokens, so it sees a call to wc_get_products() and a new WC_Product_Query, each written plain or with a leading backslash; it does not see a query reached through a variable function name, a callable string or a wrapper of our own, and it does not see arguments assembled in a different function than the call.

1.37.3

Fixed: arrow glyphs in the admin menu paths, and in the strings handed to translators. An arrow inside a translatable string makes the glyph every translator's problem and changes the layout in any locale that drops it.

1.37.2

Fixed: the hourly CRA incident check was scheduled but cleared nowhere, so the event outlived the plugin. A WP-Cron event stays in the options table once created, waking on every request to fire a hook nothing listens to. The store health check was also cleared on deactivation but not on uninstall. The list of events now lives in one place that both paths read, because keeping two copies by hand is how they drifted.

1.37.1

Security (high): the value social login used to tie a sign-in to the browser that started it was the same for every logged-out visitor for twelve hours, and the public address that begins the flow handed it out to anyone who asked. Someone could start a sign-in of their own, keep it unused, and send a customer a link that signed that customer in to the attacker's account instead of their own, where the address and order details they went on to enter would be the attacker's to read. Each sign-in now gets its own single-use value, held in a cookie, so a callback is only accepted from the browser that began it.

1.37.0

Security (high): social login signed a visitor in to an existing WordPress account whenever Google or Facebook reported a matching email address, without checking that the provider had actually verified that address. Anyone who could register with a provider claiming somebody else's address was handed that person's account, an administrator's included. The address must now be verified by the provider before any account is matched, and an account that can edit the site is never linked automatically: its owner signs in with a password as before. Social login is off unless you switched it on and entered provider credentials, so a default installation was never exposed.

1.36.9

Fixed: [polski_wishlist] and [polski_compare] rendered unstyled with dead buttons on an ordinary page. The assets loaded only on shop, product, product category and My Account pages, so a merchant who put either shortcode on a page of their own got markup with no stylesheet and no script behind it.
Fixed: three sentences on the withdrawal form were hardcoded Polish inside a JavaScript file, so every shop saw them in Polish whatever its language, while the form around them was translated. They now come from the server and are translated with the rest of the plugin.

1.36.8

Fixed: deleting the plugin left the per-user "dismiss" flag from the PRO notice in the database. Uninstall now removes it for every user, not just the one who dismissed it.

1.36.7

Fixed: food products published two and a half times as much sodium as their own label. Annex XV declares salt, Schema.org only has sodiumContent, and salt is sodium multiplied by 2.5, but the two were mapped straight across, so a product labelled 2.5 g of salt told Google it contained 2.5 g of sodium. The figure is now converted before it is published.
Fixed: the unit price in structured data carried a hardcoded Polish label, printed as-is on every non-Polish shop, and a private polski_unit_price key nothing reads. The label is translated and the private key is gone.

1.36.6

Added: the Food and supplements module now has fields. The Modules screen has always said you can enter ingredients, nutrition, Nutri-Score, alcohol content, country of origin and the food business operator per product, and until now the only way to write any of them was a CSV import, so a shop without a spreadsheet could not use the module at all. The Polski tab on the product screen carries all of them, with one input per nutrient instead of the importer's slug:value|slug:value syntax. Values typed here and values imported from CSV end up identical, so an export still round-trips.
Fixed: every multi-line field on that tab lost its line breaks when saved. The save pass ran sanitize_text_field over each value before choosing a sanitiser, and that function folds newlines into spaces, so a GPSR manufacturer address, a list of safety warnings, repair information and the substantiation of an environmental claim were all stored as one long line.

1.36.5

Fixed: Units, Allergens, Nutrients, Manufacturers, Delivery Times and a second "Brands" appeared under Products even when their modules were off. The six taxonomies registered on every request regardless of the Modules screen, so a shop that never turned on the food module or brands still got four admin screens it could not use, and the brands one sat next to WooCommerce core Brands under the same name. Each taxonomy now registers only when its module is enabled. Terms already saved are untouched and come back with the module.

1.36.4

Fixed: the GPSR manufacturer never reached the product's structured data, the data layer or the product feed. All three read a meta key the plugin does not write, while the field on the product screen saves under the GPSR key, so the manufacturer was simply absent from everything downstream.
Added: the "Buying as a company" answer is now shown on the order screen. It was stored on every order and displayed nowhere, so a merchant could turn the toggle on and never see a reply.
Added: product safety instructions, safety documents, food distributor and the product-level right-of-withdrawal exemption reason can now be set through the product CSV import and export. Their shortcodes and Elementor widgets read them and nothing could fill them in, so those blocks were always empty.
Removed: two order and user meta keys that were written and never read back, a copy of the checkout consent states (the consent log already records them, with its own screen and CSV export) and a social login provider name (the provider is already part of the stored provider ID).

1.36.3

Fixed: the plugin's WooCommerce emails could be silently absent for a whole request. Loading the mailer is not enough on its own: if anything built it before this plugin registered its filter, and third-party plugins do build it on plugins_loaded, the cached mailer was assembled without our classes and the filter could never run again. Measured in a test install: zero of the classes present instead of all of them. The mailer is now topped up when that happens.
Removed: an integration-detection class that could never have run. It was built by the service container but never listed as a hook subscriber, so nothing ever called it, and its one registration was on plugins_loaded, which has already fired by the time the plugin boots. Its signals had no listeners in either the free or the paid plugin. Nothing used it and nothing changes; the code is gone rather than left to read as a working feature. A build-time check now covers this shape across the whole plugin family, so a hook that can never fire cannot ship again unnoticed.

1.36.2

Fixed: a partial write to the settings REST endpoint overwrote every key the request left out with the packaged default, instead of leaving it as stored. For the storefront text keys that default is a translated string resolved at the moment of the request, so one such write stamped whatever language the request ran in into the database and the wording stopped following the shop's locale. An omitted key now keeps its stored value, and an empty request body no longer resets the whole group. The last ten releases are below. The full history is on the plugin's changelog page, plogins.com/polski/changelog/, and in changelog.txt inside the plugin folder. WordPress.org silently truncates a changelog over 5000 words, which is why this one is kept short on purpose.

1.36.1

Changelog: this readme now carries the last ten releases and links to the full history, instead of every release ever. WordPress.org silently truncates a changelog over 5000 words and only warns the plugin authors by email, so the page had been one release away from quietly dropping its oldest entries. Nothing about the plugin changes.

1.36.0

Added: the NIP field can now be required by what is in the cart, not only by the shop-wide switch. One place decides and it is filterable (polski/nip_required), so a paid rule that marks a product as needing the buyer's VAT ID on the receipt can make the field mandatory for that order. Enforced on both the classic and the block checkout, since the block field is registered before a cart exists and its own required flag cannot see one.

1.35.0

Fixed: the DSA report form's handler was registered for logged-out visitors whether or not the module was on. With the module off the table it writes to may not exist, so an anonymous submission was lost while the sender was still redirected to a thank-you page, and the shop notification was still sent. Nothing is registered now unless the module is on, and a check covers every public handler in the plugin so this cannot come back unnoticed.
Fixed: Quick View answered its AJAX call and rendered product markup even when the module was switched off. Its other three callbacks already checked; this one did not.
Fixed: searching by barcode missed WooCommerce's own GTIN field. The search matched only the plugin's fallback meta key, so a shop that filled in the GTIN field WooCommerce added in 8.4 could not find the product by its barcode at all.
Fixed: the environmental claim fields collected a claim's basis, its certificate link and an expiry date, and then showed none of it to anybody. The substantiation now appears on the product page. An expired certificate is labelled as expired rather than quietly presented as current proof, which is the failure the directive is about.
Added: polski_gtin as a CSV import and export column. The meta key behind it was read in six places and written by nothing, and the documentation already promised a column for it.
Docs: rewrote the CSV import and export page in all four languages. It listed about forty columns that do not exist, three filters the plugin never registered, and a validation pass that does not run. The column table is now generated from the plugin's own map, so it cannot drift again.

1.34.1

Corrected the PRO price shown in two places: this readme and the upgrade panel inside the plugin both said 69 EUR per year, and the charge is 99 EUR. Freemius is what actually bills and it was changed first, so for a short window both quoted a price the checkout did not honour. Nothing about the free plugin itself changes.

1.34.0

Fixed: six modules had a service in the plugin and no card on the Modules screen, so there was no way to switch them on: the compliance checklist, the business identification block, the complaint form template, the copyright and image credit shortcodes, the SBOM generator and the RODO training documents. Each now has a card, keeping the state it already defaulted to, so nothing changes on a shop until the merchant turns it on.
New: the modules registry and the module default states run through the polski/modules and polski/module_defaults filters, so an add-on can put its own cards on the Modules screen instead of gating a feature on a switch that exists nowhere.
A release check (tests/module-ids-are-reachable-check.php) now fails when a module id has a default state but no card in either plugin, which is what let this happen.

1.33.2

Listing only, no functional change. The short description now names JPK_FA and the NIP lookup, which the plugin has done for a long time without saying so where anyone searching would see it. Tags: "rodo" is dropped, because that search is dominated by cookie and newsletter plugins and this plugin does not appear in it at all, and "jpk" and "zwroty" take its place.

1.33.1

Fixed: the "withdraw from this order" link in the order email did not work for a logged-in customer. It led to "Oops, something went wrong on our side" instead of the form, so the withdrawal could not be started from the email at all. The link never carried a one-time token and the page demanded one. Opening the form changes nothing and the order's owner is checked separately, so the token is no longer required there; the form submission that actually files the declaration keeps its own, unchanged.

1.33.0

New: a GTU marking on the product, under Product data > Polski > Invoicing. Pick one of the thirteen groups from the JPK_V7 regulation, or leave it at no marking. The code is stored with the product and printed against that line on the invoice, so an order mixing marked and unmarked goods says which line the marking belongs to. Shipping and fees never carry one, and a product left unmarked prints nothing.

1.32.1

Fixed: the PRO promo was shown to people who had already bought PRO. It never checked whether the paid plugin was installed, so a paying customer kept being sold the thing they were running. It now disappears as soon as PRO is active.
Changed: the "Legal Email Attachments" module is now called "Legal texts in emails", because it attached nothing. It prints the text of your legal pages under the order table in four customer emails. The documentation described PDF files and a per-email-type document matrix that no released version ever had; that page has been rewritten to match the code, and the PDF version is a PRO feature. Reported on GitHub (discussion #49).
Changed: the PRO promo now also appears on the Modules, Settings and Reports screens, not only the Dashboard. It stays dismissible and never leaves this plugin's own screens.

1.32.0

New: AJAX search can look inside the values of the global product attributes you choose. Pick them under the AJAX search module; leave them all unticked and attributes are skipped entirely. Requested on GitHub (#72).
Fixed: "Search by SKU" and "Search by categories" were on the screen but no code read either one, so both did nothing whichever way you set them. They work now, and switching them off really excludes that data.
Fixed: the search dropdown never used any of the extra matching at all. It ran its own product query, while the manufacturer, GTIN and ingredient matching only applied to the main search page, so the dropdown and the results page could disagree about the same term. Both now go through one place.
New: electronic contact fields for the manufacturer, the EU responsible person and the importer, plus a postal address for the responsible person. GPSR art. 19(1)(a) asks for a postal and an electronic address, and there was nowhere to put the electronic one. Included in CSV import and export.
Changed: the product data panel splits GPSR into "Product responsibility" (who is answerable) and "Product safety" (warnings, instructions, identifier), and the storefront output does the same. A group with nothing filled in is no longer printed as an empty heading. Requested on GitHub (#63).
New: the polski/gpsr/data filter, so the values shown for a product can be supplied from elsewhere. Plogins Polski PRO uses it for reusable responsibility profiles.
Fixed: the changelog on the WordPress.org plugin page was cut off. WordPress.org truncates a readme changelog over 5,000 words and only tells the plugin author by email after the import, so the page had quietly been dropping its oldest entries. readme.txt now carries the last twenty releases and the full history stays in changelog.txt inside the plugin folder.
Release checks added for all three failure modes above: a changelog over the wp.org limit, and a product field that renders an input but is missing from the save map, so it accepts typing and discards it.

1.31.10

Fixed: the Omnibus "calculated from" setting did nothing, and the window it was meant to control was the wrong one. The lowest price was always measured up to now, so a running sale price competed to be its own lowest price and the notice could just repeat the current price. Measured from the sale's start date, as the setting says and as the Directive intends, the notice shows the lowest price in the 30 days before the reduction instead.
Note on upgrading: on a product whose sale has a start date, the figure in the notice can change, and it changes to the legally correct one. In the test case, a product reduced to 79 after selling at 250 and 300 showed "79" before and shows "250" after. Products with a sale price and no scheduled start are unaffected, because there is no date to anchor the window to; that is the common case.

Polski for WooCommerce

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: