WPC Checkout Field Editor for WooCommerce (Premium)
Antivirus scan
Powered by ClamAV
✅ Verified clean
This product file has passed our security filters.
Want to run a fresh ClamAV scan right now? Takes a few seconds and shows scanner version, signature DB and live result.
This can take 5 to 30 seconds.
Clean file Threat detected
No threats detected in this file.
- File
- Size
- Scanned
- ClamAV
- Signature database
⚡ Powered by ClamAV
Scan could not be completed
Report product
If you detected an issue (broken file, malware, inappropriate content, etc.) let us know and we'll review it ASAP.
Sign in to report
About WPC Checkout Field Editor for WooCommerce (Premium)
Every field you add to checkout is charged to everyone
A shop checkout grows by accumulation. Someone asks for the tax number for invoices, customer service asks for a second phone, logistics wants the floor and door number, and marketing wants to know how you heard about them. None of those requests is absurd on its own.
The problem is that they add up, and the cost is not paid by whoever asked. It is paid by the buyer who only wanted a shirt and finds fourteen boxes. Every extra field is one more chance that somebody gives up halfway.
Which is why the useful question is not what you can ask, but who you ask it of. A field that always shows up in order to handle 5% of orders is charging a toll to the other 95%, and that is where this plugin earns its place: not for the field types, but for the conditional logic.
What it does
- Visual editor to add, change, remove and reorder billing, shipping and notes fields, without touching code.
- Over twenty field types: text, number, email, select, checkboxes, radio buttons, date, time, date range, colour and file upload with preview.
- Conditional logic with AND/OR on payment method, shipping method, country, cart contents and the value of other fields.
- Fees tied to a field, fixed or percentage, and also per character, per line, per unit or per word.
- Custom sections placeable before or after the checkout parts that already exist.
- Uploaded files panel, with search, filters, thumbnails and orphan detection.
- Ready-made field templates for gifting, business or delivery preferences, plus JSON export and import.
Where conditional logic really shows
The three most common cases are almost always the same. The tax field that only makes sense if the buyer ticks that they are buying as a company. The delivery instructions that are only needed if they picked home delivery rather than store pickup. And the date, which only matters when there is something perishable or made to order in the cart.
In all three, the field can exist without getting in anybody else's way. That is the whole difference between a long checkout and one that adapts.
File upload needs a decision first
Allowing attachments at checkout solves a lot in print, signage or personalised gift shops, where the order means nothing without the customer's file. It is also the feature most worth thinking about before switching on.
A file uploaded by a customer is their data now sitting on your server, with everything that implies about keeping it only as long as needed and being able to delete it if asked. The orphan detector helps exactly there: it finds what was left behind by orders that never completed.
And it pays to limit types and size from day one. A wide open upload field on a public page is an invitation you did not mean to send.
Requirements and what it does not do
It needs WooCommerce and also works with block checkout, the newer editor format.
It only touches checkout. It does not change product pages, the cart, or gateway logic: if you need fields on the product page or before reaching the cart, this is not what you are looking for.
The fees it can add are the ones tied to a field. For fee rules by weight, by zone or by time of day, with no field involved, the right tool is another one and it is listed below.
Alternatives in the catalogue
There is more than one checkout field editor in the catalogue, and they are not the same: Flexible Checkout Fields, the ThemeHigh one and Checkout Field Editor and Manager. It is worth comparing which fits your theme before choosing.
If what you want is rule-based fees rather than fields, look at WPC Smart Fees. And if the field you wanted was a delivery date with capacity, that is better solved by WPC Delivery Date and Time Slots.
Frequently asked questions
Can I remove fields that WooCommerce ships with?
Yes, they can be hidden and reordered. Carefully: some are needed by tax and shipping calculations.
Does it work with block checkout?
Yes, it is compatible with the block format as well as the classic one.
Does the field data show up in the order and in emails?
Yes, it stays on the order. How it looks in emails depends on your email template.
Can I charge for a field?
Yes, with a fixed or percentage fee, and also per unit, line, word or character.
Can the configuration be moved to another shop?
Yes, by exporting and importing JSON.
How many fields are too many?
There is no magic number. The practical rule is that every required field has to justify the order it costs you.
Version history
-
v
1.0.2 Current 7 Aug 2026
Customer reviews
Sign in to leave a review. Only people who have the product can review it.
No reviews for this product yet.
Frequently asked questions
-
GPL (General Public License) is the license under which WordPress and most premium plugins/themes are distributed. It grants you the right to use, modify and redistribute the software in as many projects as you want, with no domain restrictions.
-
Yes. With membership you get automatic updates via our GPLClub Updater plugin (installed on your WP, detects new versions and applies them). With individual purchase, you get one year of manual updates from your account.
-
Depends on the plan. Monthly: 3 domains. Semi-annual: 7. Annual and Lifetime: 15. Individual purchase: 1 domain.
-
GPLClub offers its own support for installation, configuration and compatibility. For direct support from the original author (feature requests, product-specific bugs), a license purchased from the author is required.