Roles and permissions<\/li>\n<\/ul>\n\nCodeBold Commerce Pro<\/strong> is a separate plugin, for shops that have outgrown that: more\nlocations and registers, transfers between them, stock valuation, restaurant service,\nunlimited label printing, and sales reporting split by outlet.<\/p>\n\nIt is a separate plugin rather than a licence key on this one, deliberately. A key that\nunlocks dormant code means the paid work is sitting inside everybody's copy of the free\nplugin \u2014 which WordPress.org does not allow, and which would make the word \"free\" above\nconsiderably less true.<\/p>\n\n
Switching from one to the other loses nothing either way. Everything this plugin records\nstays where it is.<\/p>\n\n
Works with the rest of the range<\/h4>\n\n\n- CodeBold Smart Filters<\/strong> \u2014 product filters for the shop and category pages<\/li>\n
- CodeBold Members<\/strong> \u2014 edit what each of your roles is allowed to do. This plugin's\npermissions appear there under their proper names<\/li>\n<\/ul>\n\n
Neither is required.<\/p>\n\n\n
\n- Install and activate WooCommerce, then this plugin.<\/li>\n
- Follow the setup screen: choose your outlet, register and receipt details.<\/li>\n
- Open POS<\/strong> in the admin menu and start a shift.<\/li>\n<\/ol>\n\n\n
\nDoes the till really work without internet?<\/h3><\/dt>\nYes, once it has been loaded. The screen, the products and the prices are cached, and\nsales made offline are queued on the device and sent when the connection returns. Card\nterminals are a separate matter \u2014 those need their own connection.<\/p><\/dd>\n
Will it fight with my other plugins?<\/h3><\/dt>\nIt writes stock through one path and orders through WooCommerce's own, so anything else\nreading either keeps working. Its own styles are prefixed, so it does not restyle screens\nbelonging to other plugins.<\/p><\/dd>\n
Can I stop a cashier giving discounts?<\/h3><\/dt>\nYes. Discounts, price overrides, voids, refunds, seeing cost prices and opening the drawer\nare separate permissions. Install CodeBold Members to change them with checkboxes rather\nthan code.<\/p><\/dd>\n
Does it support more than one shop?<\/h3><\/dt>\nYes \u2014 outlets and warehouses, each with their own stock, and transfers between them.<\/p><\/dd>\n
What happens to my stock numbers if I deactivate it?<\/h3><\/dt>\nThey stay. Stock lives on the WooCommerce product, as it always did.<\/p><\/dd>\n
My barcode labels print in the wrong place on the sheet<\/h3><\/dt>\nFour settings in the browser's print dialog decide this, and every one of them defaults to\nthe wrong value for label paper:<\/p>\n\n
\n- Paper size \u2014 A4 for sheets. For a label roll, pick the roll's own size, not A4, or you\nget one label per page.<\/li>\n
- Margins \u2014 None. The page already contains the exact margins your sheet needs. Adding the\nbrowser's on top shifts every label down and right.<\/li>\n
- Scale \u2014 100%. \"Fit to page\" is usually the default and shrinks everything by a few per\ncent, which is enough to miss the die cut and enough to make a barcode unreadable.<\/li>\n
- Headers and footers \u2014 off, or the page title prints across your top row.<\/li>\n<\/ul>\n\n
Rather than guess, use Print a test sheet<\/strong> on the Barcode labels screen. It prints the\nsame grid as outlines on plain paper, with a 100mm ruler. Measure the ruler to check the\nscale, then hold the page against a sheet of labels to check the position. A test sheet\ncosts one piece of paper; getting it wrong costs the labels.<\/p>\n\nIf every label is shifted the same way, the margins are the problem. If they drift further\nout as they go down the page, the scale is.<\/p><\/dd>\n
Which printer does it print to?<\/h3><\/dt>\nWhichever one you choose in that dialog. WordPress cannot select a printer \u2014 no plugin can,\nbecause the browser owns printing \u2014 so what this does instead is lay the page out correctly\nin millimetres for the stock you picked, and tell you what to set.<\/p>\n\n
Thermal label printers and ordinary office printers both work. The label sizes on offer\ncover A4 sheets of 65 and of 24, and a 58 \u00d7 40mm continuous roll.<\/p><\/dd>\n
How many labels can I print at once?<\/h3><\/dt>\nFifty per run in the free version, which covers labelling a shelf or a small delivery. If a\nrun would go over, it prints the first fifty and tells you how many were left out \u2014 nothing\nis lost, and you can print the rest in a second run. The paid version removes the limit.<\/p>\n\n
Every label size is available at every tier. If you have bought a label printer, telling\nyou the printer is a premium feature would be a poor way to meet you.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.9.15<\/h4>\n\n\n- A Help and support<\/strong> screen under the till menu, and a \"Get help\" link on the Plugins\npage. Three buttons \u2014 something is broken, I need something it does not do, a question\nbefore I buy \u2014 each open your own email program with a message already addressed to\nsupport@codeboldcommerce.com and the facts we would otherwise have to ask for (WordPress,\nPHP, WooCommerce and plugin versions, theme, active plugins) already at the bottom.\nNothing is sent from the screen itself; you see every word first and can delete any of it<\/li>\n
- The customer display no longer bounces to the sign-in page when a till opens it on a\nsecond screen before a cashier has signed in on the first<\/li>\n<\/ul>\n\n
0.9.14<\/h4>\n\n
Everything from 0.9.7 to 0.9.14, which were the versions reviewed for the WordPress.org\ndirectory:<\/p>\n\n
\n- Every cap is gone. There is no product limit, no register limit and no label limit in this\nplugin \u2014 a plugin hosted on WordPress.org is free software, and free software does not\nhave a meter. The paid features live in a separate plugin, CodeBold Commerce Pro, and\nnothing here waits on it<\/li>\n
- Renamed to CodeBold POS for WooCommerce, which is what it is<\/li>\n
- Loyalty points: earned on a sale, spent on a later one<\/li>\n
- A customer-facing display for a second screen, showing the sale as it is rung up<\/li>\n
- CSV export of sales, and a PIN so a shared till can tell cashiers apart without a\nWordPress sign-in each<\/li>\n
- A dark admin on the website's palette, and a pass over every screen for how it reads:\nform controls that stay visible under the mouse, six control states that had never been\nstyled, money lined up on the right everywhere it appears, and Stock Central that scrolls\ninside its own grid rather than the whole page sideways<\/li>\n
- Stylesheets are enqueued the WordPress way rather than printed into the page<\/li>\n
- Coding standards: the directory's own checker passes, and every remaining exclusion in the\nruleset says why it is there<\/li>\n<\/ul>\n\n
0.9.6<\/h4>\n\n\n- The till and the stockroom are now switches of their own, under a new Modules<\/strong> heading\non the Add-ons screen. A shop that only wants a counter switches the stockroom off; one\nthat only wants stock management switches the till off. Neither deletes anything<\/li>\n
- Switching a module off takes its options with it \u2014 no more answering \"yes, stock counts\nare on\" for a shop with no stockroom \u2014 but it never overwrites what you chose. Switch it\nback on and every option is exactly where you left it, and the screen says so while it\nwaits<\/li>\n
- Stock still moves with the stockroom switched off. The write path is not a feature and\ncannot be switched off; a sale still takes stock off the shelf. You simply stop having\nscreens to manage it on<\/li>\n
- Add-ons can no longer hide its own switch. It used to live under the stockroom menu, so\nswitching that off would have left the database as the only way back. It now follows\nwhichever menu exists, and becomes a menu of its own if neither does<\/li>\n
- Outlets & Registers follows the same rule, because an outlet is where stock lives and a\nregister is how it sells \u2014 a shop needs that screen whichever half it is running<\/li>\n
- The till switch now reaches the till itself, not only its menus. Switching Point of sale\noff closes the register's address and its endpoints, rather than hiding the menu while\n \/pos\/ carried on taking money<\/li>\n
- It will not switch off from under an open shift. That is a counted drawer with somebody\nstood behind it, and taking the screens away first would leave a database edit as the\nonly way to close it. The refusal names the register, who is on it and how long for, and\nlinks to Login Sessions so it takes a few seconds to clear<\/li>\n
- No equivalent guard on the stockroom, deliberately. An open stock take is a document and\nit keeps; nobody is holding cash for it<\/li>\n
\/pos\/<\/code> shows a plain page rather than a 404. That address is bookmarked and pinned to\nhome screens on machines nobody has signed into for months, and a browser finding nothing\nthere reports a broken shop<\/li>\n- Sales taken offline still land after the till is switched off. They already happened \u2014\nthe customer has the goods and the receipt, and the money is in the drawer \u2014 so refusing\nthem would not undo the sale, only lose the record of it. The page at
\/pos\/<\/code> finds what\na device is still holding and sends it. New sales are refused; work already done is not<\/li>\n- Stopping a person selling is still a permission, not a switch. Take
codebold_use_pos<\/code>\noff their role: it applies to that person, immediately, and a bookmark does not get round\nit<\/li>\n- Sales reports can be read one outlet at a time.<\/strong> They could not before, which was a\nproblem worth naming rather than quietly fixing: more locations is what the paid plugin\nis sold on, and every figure on the reports screen was answering for the whole business.\nA manager with two branches has one question \u2014 which one is making money \u2014 and the\nscreen could not answer it. Takings, sales, items, best sellers, hourly, daily, per\ncashier and the shifts table are all scoped now, including the fallback query used on\nhosts without MySQL's timezone tables<\/li>\n
- The outlet picker only appears when there is more than one outlet, so a single shop sees\nnothing new<\/li>\n
- Where the free plugin stops is now written down in one place rather than implied. One\nlocation, one register, thirty tracked products and fifty labels a print run, with the\ntill \u2014 offline selling included \u2014 complete and free. Restaurant service, transfers, stock valuation, more\nlocations and unlimited labels are CodeBold Commerce Pro, a separate plugin<\/li>\n
- The Add-ons screen lists what Pro adds rather than hiding it, as a labelled row with a\nlink instead of a switch that does nothing when pressed<\/li>\n
- Switching Pro off loses screens, never records. What a shop chose is remembered while it\nis gone, so renewing puts everything back rather than starting them over<\/li>\n<\/ul>\n\n
0.9.5<\/h4>\n\n\n- No more \"translation loading was triggered too early\" in the log. Two places built a\ntranslated catalogue only to read its keys: the capability list, and the shop-type list\nbehind every \"what kind of shop is this?\" question. Both now answer from a plain list of\nnames, and the labelled versions are built only for the screens that show them<\/li>\n
- Role names are stored untranslated, as WordPress core stores its own. add_role() freezes\nwhatever it is given, so translating it guessed the site language once and kept that\nanswer forever. CodeBold Members renames a role to anything you like, which is a better\nanswer than a guess<\/li>\n<\/ul>\n\n
0.9.4<\/h4>\n\n\n- Barcode labels: a test sheet. It prints the same grid as outlines on plain paper with a\n100mm ruler, so the scale and the position can both be checked before a sheet of labels\nis committed. A test sheet costs one piece of paper; getting it wrong costs the labels<\/li>\n
- The four print-dialog settings that decide whether a sheet is usable are now named on the\nscreen itself, where they are needed, rather than in a manual nobody opens<\/li>\n
- The label size, quantity and chosen fields are remembered per user, so the daily job is\ntwo clicks. Remembered per user rather than per site: two people stocking shelves may be\nfeeding two different printers<\/li>\n
- The screen says how many labels a run will produce before it is printed, so nobody meets\na limit for the first time on a printed sheet<\/li>\n
- One run prints at most 50 labels. Over that it prints the first 50 and says how many were\nleft out and what to do about it \u2014 the purchase-order picker's rule, that truncation is\nreported rather than silent, applied here too. Every label size stays available<\/li>\n<\/ul>\n\n
0.9.3<\/h4>\n\n\n- The inventory Dashboard opens. It was registered before the menu that owns it, so\nWordPress filed its page under one name and looked it up under another. The menu item\ndrew correctly and answered a click by refusing access<\/li>\n
- Reports no longer come back empty when asked for a range that already carries a time.\nThe time was appended a second time, the result could not be parsed, and an unparseable\ndate was being read as 1970 \u2014 so a trading day reported nothing<\/li>\n
- Units sold, best sellers and the X and Z reports count order lines rather than stock\nledger rows. A shop that does not track stock, or has not switched tracking on yet, now\nsees its real figures instead of zeroes beside real takings<\/li>\n
- A product nobody has counted yet is no longer reported as out of stock. It was counted\ntwice over \u2014 once as untracked, and once, in red, as out<\/li>\n
- The shifts table no longer prints the opening float under a heading reading \"Expected\".\nExpected cash is worked out when a shift closes; until then that column is blank, as the\ntwo columns beside it already were<\/li>\n<\/ul>\n\n
0.9.2<\/h4>\n\n\n- The till beeps when an item goes on the sale, and gives a lower double note when\nsomething is refused. A shop floor is noisy and a cashier is looking at the customer,\nnot the screen<\/li>\n
- The sound is synthesised rather than played from a file, so it still works with the\nregister offline and adds nothing to download<\/li>\n
- A speaker button in the toolbar turns it off, remembered on that device<\/li>\n<\/ul>\n\n
0.9.1<\/h4>\n\n\n- The till shows a garment's size as its own badge instead of appending it to the product\nname, where a two-line caption cut it off. A rail of one dress in six sizes is six tiles\nwith the same photograph \u2014 the size was the only thing telling them apart, and it was\nthe part being hidden<\/li>\n
- Attribute values show the name the shop typed, not the slug: \"Extra Large\", not\n\"extra-large\"<\/li>\n<\/ul>\n\n
0.9.0<\/h4>\n\n\n- Recipes. Set what a dish is made of on the product's own Recipe tab; selling it takes\nthe ingredients out of stock, through the same single write path as everything else<\/li>\n
- Recipes can nest, and a recipe that would contain itself is refused when it is saved<\/li>\n
- A dish's cost is worked out from its ingredients rather than stored, so it never\ngoes stale<\/li>\n
- Refunding a meal returns its ingredients<\/li>\n<\/ul>\n\n
0.8.0<\/h4>\n\n\n- Kitchen tickets: send a round to the kitchen, watch it on a screen, mark it started,\nready and served<\/li>\n
- Sending is safe to retry. A till that lost its connection and sent again does not put\nthe same food on twice<\/li>\n
- Cancelling a line after it was sent shows the kitchen a cancellation instead of\nremoving the row<\/li>\n<\/ul>\n\n
0.7.5<\/h4>\n\n\n- Added this readme, and corrected the plugin description: product filters and memberships\nare separate plugins and were never part of this one<\/li>\n
- The suite now tells any installed role editor what its permissions are called<\/li>\n<\/ul>\n\n
0.7.4<\/h4>\n\n\n- Stock Central uses the full width of the screen, and its columns can be chosen<\/li>\n
- The POS landing page explains itself, and opens the till in a new tab<\/li>\n
- Purchase orders can be entered as a size-by-colour grid<\/li>\n<\/ul>","raw_excerpt":"Sell over the counter from the same WooCommerce shop you sell online from. One till, one stock figure, one set of orders.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/362556","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=362556"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/codeboldtech"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=362556"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=362556"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=362556"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=362556"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=362556"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=362556"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}