Barcode Scanner (+Mobile App) – Inventory manager, Order fulfillment system, POS (Point of Sale) vs Exploit Scanner

✔ Find products/orders by scanning barcodes or by name/SKU/Id ✔ Manage product stock, prices and other product data ✔ Point of Sale (POS) – create orders by scanning barcodes This plugin for WooCommerce allows you to scan barcodes and manage your inventory/orders more efficiently. After barcode is scanned, plugin starts to search item automatically and displays product/order you were looking for. Also this plugin provides Point Of Sale (POS) functionality, so you can create WooCommerce orders right from the work place or checkout counter. You can also switch to the “Enter” mode and search products/orders manually by typing ID/SKU/NAME/etc – and product/order will be found. We pay a lot of attention to search speed optimization, so even shops with thousands of items can count on fast responsiveness and comfortable work. Plugin is fully compatible with WooCommerce. Main features of barcode scanner: Supports all types of barcode scanners Search of products by scanning barcodes Review & edit basic product information Manage stock quantity, price, etc. Search of orders Review order information Creation of new orders (POS functionality) Order fulfilment (item picking) functionality Auto actions* Auto actions allows you to increase or decrease product quantity automatically simply by scanning products, so you don’t have to change quantity value manually. It might be very useful for restocking items in your stock. By default plugin allows to do search by Product ID, SKU, Name, however you can specify any other custom field (like UPC, EAN, etc) by which search should be done. Please note: This is a free trial version, so it comes with some limitations. Possible use cases: Quick search of item: If you have to search for products/orders regularly and you type id/sku/name manually – you may increase your productivity by using barcode scanner. You will need to scan product/order barcode and it will be found as fast as possible without any additional interaction with keyboard. Point of Sale (POS): You can use barcode scanner as a Point of Sale (POS) system to create orders in offline stores. You simply scan products which your customer wants to buy, and you will see prices for each item along with total order price. POS functionality also includes proce adjustment for added products to the order and possibility to edit the end price of the order. POS also allows to specify order status, final order price, apply coupons, specify woocommerce user and have some other features. Restocking items: If you received a new products from your vendor, you can use “auto actions” to increase products quantity in WooCommerce simply by scanning items. Product quantity will be increased each time you scan a barcode and the good or error sound will be played. So, you even don’t have to look at the screen to understand if it worked or not. Your use case may be different, however barcode scanning & quick search is always helpful tool and can be adopted to stock management process. More information about Barcode Scanner plugin here: Barcode Scanner Plugin FAQ

This plugin searches the files on your website, and the posts and comments tables of your database for anything suspicious. It also examines your list of active plugins for unusual filenames. It does not remove anything. That is left to the user to do. Latest MD5 hash values for Exploit Scanner: 17e2ccfc834d691bc68cc5c64f9bed89 exploit-scanner.php (1.5.2) 1d5f9d6220fe159cd44cb70a998a1cd7 hashes-4.6.php fbdf61c17f65094c8e331e1e364acf68 hashes-4.6.1.php 477d128d84802e3470cec408424a8de3 hashes-4.7.php d53210f999847fbd6f5a2ecac0ad42f2 hashes-4.7.5.php Latest SHA1 hash values for Exploit Scanner: 1decc1e47a53d1cab9e8f1ef15b31682198367ee exploit-scanner.php (1.5.2) 5cec64380a2acdc876fd22fbbbbf8c335df1ed3f hashes-4.6.php 99d9e7be23a350f3d1962d0f41e7b4e28c00841e hashes-4.6.1.php 1eeab377a1afc6d776827a063678d2461b29e71d hashes-4.7.php 8c890a6af26bb74e9d17e5d2b21d6be27764da45 hashes-4.7.5.php See the Exploit Scanner homepage for further information. Interpreting the Results It is likely that this scanner will find false positives (i.e. files which do not contain malicious code). However, it is best to err on the side of caution; if you are unsure then ask in the Support Forums, download a fresh copy of a plugin, search the Internet for similar situations, et cetera. You should be most concerned if the scanner is: making matches around unknown external links; finding base64 encoded text in modified core files or the wp-config.php file; listing extra admin accounts; or finding content in posts which you did not put there. Understanding the three different result levels: Severe: results that are often strong indicators of a hack (though they are not definitive proof) Warning: these results are more commonly found in innocent circumstances than Severe matches, but they should still be treated with caution Note: lowest priority, showing results that are very commonly used in legitimate code or notifications about events such as skipped files Help! I think I have been hacked! Follow the guides from the Codex: Codex: FAQ – My site was hacked Codex: Hardening WordPress Ensure that you change all of your WordPress related passwords (site, FTP, MySQL, etc.). A regular backup routine (either manual or plugin powered) is extremely useful; if you ever find that your site has been hacked you can easily restore your site from a clean backup and fresh set of files and, of course, use a new set of passwords. Updates Updates to the plugin will be posted here, to Holy Shmoly! and the WordPress Exploit Scanner page will always link to the newest version. Other Languages Unfortunately for people using WordPress versions for other locales some of the file hashes may be incorrect as some strings have to be hardcoded in their translated form. Here are some file hashes for WordPress in other languagues provided separately by other members of the community: Japanese – thanks to Naoko German – thanks to Robert Wetzlmayr The hash files should only be declaring an array called $filehashes and the majority of the hashes should still be the same.