Published, purchasable products that are in stock or on backorder: simple products and individual variations of variable products. Other product types (bundles, composites, subscriptions, bookings and the like) need their product page, where their options are chosen, so the form doesn't offer them; developers can allow more types with the aovup_qof_product_types<\/code> filter. Variations with an \"Any\" option need the product page too.<\/p>\n\nThe product's catalog visibility can be \"Shop and search results\", \"Shop only\" or \"Search results only\" (handy for order-only items you keep out of the shop). Products set to \"Hidden\" are never offered.<\/p><\/dd>\n
Does it respect plugins that hide products from some customers?<\/h3><\/dt>\nThe form uses WooCommerce's own answers: a product that WooCommerce reports as hidden from the catalogue or not purchasable for the current customer is not offered. Plugins that hide products only by filtering the shop's product lists don't change those answers; with such a plugin, use the aovup_qof_product_orderable<\/code> filter to keep its hidden products out of the form too.<\/p><\/dd>\nCan guests use it?<\/h3><\/dt>\nYes, unless you choose \"Signed-in customers only\".<\/p><\/dd>\n
How does the paste box read my list?<\/h3><\/dt>\nOne product per line: the SKU, then the quantity, separated by a comma, semicolon, tab or space. A missing quantity counts as 1, and a header line \"SKU\" is skipped. A line whose quantity isn't a whole number above 0 is not added: it stays in the box with a message, so you can correct it.<\/p>\n\n
Up to 200 different SKUs are looked up at once, and the order list holds up to 200 lines. Lines past either limit stay in the box with a message saying so: add the list to the cart, then add the rest in a second step.<\/p><\/dd>\n
Can someone use the form to load my server?<\/h3><\/dt>\nThe search, the SKU lookup and the additions to the cart are public, like the shop itself, so each IP address can make up to 120 searches, 20 lookups and 20 additions to the cart a minute (several buyers in one office share an address, and IPv6 addresses count by their \/64 network). Past that, the form says so and asks them to wait a minute; nothing they typed is lost. With a persistent object cache (Redis or Memcached, for example) the counts are kept there, exactly, and search answers are reused for a minute; if the cache stops counting, the limits are off while that lasts and WooCommerce > Status > Logs (source \"aovup-qof\") says so. Without one, search answers aren't kept, so new searches don't add rows to your database. Signed-in shop managers aren't limited. Developers can change the limits with the aovup_qof_request_limits<\/code> filter and the reuse time with aovup_qof_search_cache_seconds<\/code>.<\/p><\/dd>\nMy store is behind a proxy, load balancer or CDN. Does that matter?<\/h3><\/dt>\nIt can. If the proxy doesn't pass your visitors' own addresses on to WordPress, every visitor seems to come from the proxy's address, so they all share one count, and 20 additions to the cart a minute become a limit for the whole store that can refuse real orders. When private, shared (CGNAT) or loopback addresses (such as 10.0.0.5, 100.64.0.1 or 127.0.0.1, also written as IPv6) reach the limits in 3 different minutes within 24 hours, Tools > Site Health, the Plugins screen and the settings tab say so, from one such address or several. Ask your host to pass the visitor's address on (for example with Apache's mod_remoteip or nginx's real_ip module), or return the visitor's real address from the aovup_qof_request_limit_ip<\/code> filter.<\/p><\/dd>\nDoes it send data anywhere?<\/h3><\/dt>\nNo. The plugin makes no outside requests.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.2<\/h4>\n\n\n- \"Add all to cart\" says \"1 product added to your cart\" for one product (the store words the count in its own language), and the messages about lines left in the box no longer say \"1 lines\".<\/li>\n
- A pasted line whose quantity isn't a whole number above 0 is no longer added with a quantity of 1: it stays in the box, and a message names it.<\/li>\n
- The notice after \"Add all to cart\" shows its \"View cart\" and \"Checkout\" buttons side by side in every theme (Twenty Twenty-Five staggered them).<\/li>\n
- When private, shared (CGNAT) or loopback addresses reach the request limits in 3 different minutes within 24 hours (a proxy that doesn't pass visitors' addresses on, so every visitor shares one count), Site Health, the Plugins screen and the settings tab say so and what to do.<\/li>\n
- A visitor whose session ended while the page was open (on a form for signed-in customers) is told to sign in again, instead of a general error, and a page whose security token is refused even after a fresh one says to reload it.<\/li>\n
- A persistent object cache that stops counting requests is now written to WooCommerce > Status > Logs, instead of switching the limits off silently.<\/li>\n
- The \"too many\" message for additions to the cart no longer names a button the customer may not have clicked.<\/li>\n
- Uninstalling: the data stays while another edition is installed, also from a renamed folder, and every site of a multisite network is cleaned up by its own setting.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- \"Add all to cart\" is limited too: 20 requests a minute per address, like the SKU lookup.<\/li>\n
- IPv6 addresses count by their \/64 network for all limits.<\/li>\n
- With a persistent object cache the limits count exactly; without one, search answers are no longer kept, so new searches don't write to the database.<\/li>\n
- A product that another plugin hides from the customer (WooCommerce's visibility filter, as B2B plugins use it) is never named in the form's messages.<\/li>\n
- Clearer messages when a limit is reached or the store doesn't answer.<\/li>\n
- Uninstall also removes the plugin's temporary data.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- First release.<\/li>\n<\/ul>","raw_excerpt":"A fast order form for B2B and repeat buyers: find products by name or SKU, paste a list of SKUs, add everything to the cart, order again.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/396049","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=396049"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/themealien"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=396049"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=396049"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=396049"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=396049"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=396049"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=396049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}