Dox POS for WooCommerce

Muutosloki

0.59.1

• Fix: with Polylang, saving a product from the register no longer replaces the photos of its translations when the photos of the main product did not change. A translation can have its own photos (uploaded apart, with the alt text in its language); they are kept, and the translation only takes the main product’s photos when they change in the register.
• Technical: dox_pos_lang_copy_images() copies the photo and the gallery to a translation, each on its own, only when the main product’s one differs from the last one it saw (_dox_pos_lang_imgs); the first time, a translation that already has a photo or a gallery keeps it.

0.59.0

• New: stores in several languages with Polylang or WPML. Each product exists once per language, and the register showed it twice (or three times): in Sell, Inventory, Edit product, the Excel file, the stock counts and the codes the product form suggests. Now only the products in the store’s default language show, plus the ones with no language; a variation follows its product. Searching by the name in another language still finds the product, scanning the code of a translation sells the main product, and a web order placed in another language counts toward its main product in the best sellers.
• New: in Movements, when the translations share their stock, a change is written once, on the main product (also for a variation, matched by its attributes). The tools that keep the stock of the translations the same save the other translation too, and that second save was written as a second movement. When each translation keeps its own stock, its movements stay on it.
• New: a product created from the register is saved in the default language, whatever language filter the dashboard has.
• New: with Polylang, a product created in the register is also created in every other language of the store, linked as its translation and published, so it sells in every language from day one: same price, cost, photos, units, sizes and colors, and the categories in their translation (one with no translation is left out, and the register says so). The SKU of each translation ends in its language (VE-0012-EN), because WooCommerce does not allow the same SKU twice; the dox_pos_translation_sku filter changes it. It can be turned off in Settings > Products > Languages (”Also create in the other languages”).
• New: the product form (creating and ”Edit this product”) has a tab per language (ES, EN…) above the name and the descriptions. Each tab keeps the text of its language and saves it to its own translation; a dot marks a language that still has the main language’s text. Everything else is shared: editing the price, cost, photos, categories, units, sizes or colors from the register writes them to every translation (the dox_pos_lang_sync_price filter can keep the price apart).
• New: a translation that was left half made (the connection dropped or the server stopped while it was being created) is finished the next time, never made twice: when the register sends the same product again, when the product is saved from the register, or when it is opened in Edit product. A product missing a translation shows ”The English version is missing” in the form with a Create now button (with the setting on, it is created as soon as the product opens), and Inventory and Edit product mark it ”Missing in English”.
• New: the product form has a Short description, the line WooCommerce shows under the price.
• New: the categories in the product form are only the ones in the main language, and a category created from the register is saved in the main language.
• WPML: the register shows each product once and counts it once, as above. Creating the translations, the language tabs and the Missing marker are Polylang only: with WPML the translations are still made in WPML.
• Stock still changes only through WooCommerce, so whatever the store uses to copy stock between translations (Polylang for WooCommerce, WooCommerce Multilingual or a snippet) keeps working. Polylang (free) does not copy it.
• Technical: new includes/multilingual.php with dox_pos_lang_plugin(), dox_pos_lang_where() (a NOT EXISTS on the language terms of Polylang or on icl_translations of WPML, for products and for variations through their parent), dox_pos_lang_main_id() (with Polylang, a variation of a translation maps to the variation of the main product: the one it was copied from, marked with _dox_pos_lang_of, or the one with the same attributes), dox_pos_lang_assign() and, for the translations, dox_pos_lang_sync() (WC_Admin_Duplicate_Product to create them, then the shared fields copied without writing to the kardex). Each copy is marked in the same save that creates it (_dox_pos_lang_of, _dox_pos_lang and _dox_pos_lang_pending until it is finished), so dox_pos_lang_sync() can adopt an unlinked copy (dox_pos_lang_orphan()) or finish a pending one instead of making another; dox_pos_lang_missing() feeds lang_missing in the edit data and nolang in the catalog and the edit list; POST /products/{id}/translations creates what is missing. Creating or finishing a translation takes a lock per product and language (dox_pos_lang_lock()), so two requests at once never make two; a translation in the trash is left alone. WPML only filters the lists. Without Polylang or WPML they make no queries and leave every query as it was.

0.58.2

• Fix: in History > Sales, the By channel, By payment method and By salesperson lists no longer overlap. A long name, like a payment method called ”Daviplata o Bancolombia”, pushed its total over the next column; it now wraps onto a second line and the total stays in its own column.
• Technical: in assets/css/caja.css, .bl .chan can wrap and the first span of each .bl row takes min-width:0.

0.58.1

• Fix: in Orders, the lines of an order placed on the website now show the size and color the customer chose (”Ballet flats · 18-24 months”), like the orders made in the register. Before, they showed only the product name, so whoever packed did not know which size to take. When the piece shares units, its actual size still shows next to it.
• Technical: new dox_pos_order_line_name() in includes/orders.php, used by the order list and the order detail; it adds the attribute values of the variation that are not already in the line name (compared by segment, not as a substring).

0.58.0

• New: write off stock. In Inventory, add what is damaged, lost or given away and tap Write these off instead: it asks why (damaged or defective, lost or stolen, gift or sample, other), takes the units out of the inventory and notes the loss at what each unit cost. It is for products that never went through a sale, so there is no order to note the loss in. Only administrators and shop managers see the button.
• New: the written-off units show in Reports > Movements (filter Written off, with the reason and the cost per unit) and as a Written off figure in Reports > Daily cash, with the units and the loss.
• Technical: new reason writeoff in the stock log (dox_pos_stock_context( ’writeoff’ )) whose note carries the reason; the loss is read from those rows (-delta times unit_cost), no new table. includes/writeoffs.php: dox_pos_write_off() (needs dox_pos_can_see_losses(), refuses more units than the stock and products that do not track stock, subtracts from the real size when the line carries one), dox_pos_writeoff_reasons() (cfg.writeoff, empty for who cannot), dox_pos_writeoffs_by_day() (totals writeoff, writeoff_units and writeoff_unknown in dox_pos_history_cash()) and REST route POST /writeoffs. New kind bajas in dox_pos_stock_kinds(). Needs a connection: it is not queued like the entries.

Full changelog: https://help.doxstudio.com/dox-pos-changelog/