What's new

When a GS1 code arrives in its readable form, with the identifiers in brackets, the batch number and the expiry date are now read correctly. Before, depending on the order the information appeared in the code, the expiry date could end up stored inside the batch number, or the batch could be dropped altogether. Codes carrying the scanner prefix, including the custom prefixes you have set up, are now recognised as well.

The estimated time for packing orders and their respective lines frequently appeared as zero. The estimation logic has been improved and is now saved when the order is created, ensuring that the planning and packing screens display an actual value. Orders created prior to this version retain the "old" value.

The welcome message Ticks prepares for a new company came out in English even when the account was set to another language. Your account's language is now identified correctly at the moment the account is created, so the first conversation and the information gathered about your company come out in your language.

Fixed several issues affecting Ticks' answers: it now reports on all your KPIs when you ask a general trend question (instead of just one), correctly labels operator rankings and time periods, no longer cuts off long answers, and only promises exported file contents it can actually deliver.

Client and reseller portal users could unintentionally access Ticks assistant tools meant only for your warehouse staff. This has been corrected — access now correctly follows each user's role.

Fixed several calculation issues in the Inbound and Put-Away KPI cards (non-conformities, pending work, productivity and top operators) and in how Reception KPIs are dated. As a result, some of these numbers — including historical ones — may now show different values than before.

Ticks got a cleaner look: a tidier header, quick actions on each message, a redesigned message box, and a slim collapsed view when you need the screen space.

Ticks now finds the right product even if you type the words in a different order than the product name.

The trial setup progress bar and checklist now accurately reflect what's actually happening, and your onboarding preferences are reliably saved.

Exporting a large result set through Ticks no longer cuts the file off partway through.

When Ticks can't produce an answer, it now shows a clear message instead of an empty reply.

Hardened Ticks so it only states facts and links backed by your actual data, and says so honestly when it can't find or verify something instead of guessing.

Admins and Supervisors could be wrongly blocked from some Ticks questions, exports or downloads meant to be available to them — that's now fixed.

Ticks now calculates operator productivity (picking/packing speed) strictly from real activity records, instead of occasionally estimating it.

A sync issue could make Ticks temporarily lose track of some Help Center articles, giving incomplete answers to "how do I..." questions — that's now fixed.

Clearing the reserves on a 3PL client's order could leave stock stuck as reserved at the picking location — that's now fixed.

When PrestaShop's address lookup failed, we could overwrite a known good delivery address with an incomplete one — that's now fixed, and the existing address is kept.

When you close an inventory it moves straight to "Closing" and the stock adjustments run in the background | you can leave the screen and carry on working. You get an email once it finishes, summarising any lines that could not be adjusted. If the close fails, the inventory goes to "Closing failed" and you can retry it from the inventory itself.

If you scan a product that has nothing left to pack, the WMS assumes you want to move it to another volume instead of making you unpack it first. It tells you which volume the units come from, shows the current volume on each batch option, and warns you if you pick the volume the product is already in. The requested packing zone is now also visible inside the field itself.

Registering packing no longer gets progressively slower as an order gains more lines. On large orders, the wait operators face when confirming packing is significantly shorter.

In the Shipping Orders list and on the carrier tab, the label icon turns green as soon as the label is downloaded, and the tooltip shows the date and time it was first printed. Available for NACEX and Correios Express. Labels printed before this version show as never printed.

When the actual collection or travel time was never captured, the picking order no longer shows "0" | it shows just the estimated time, clearly marked as an estimate.

Systems integrating with LogisticsWMS through the API now receive, in the reception confirmation, the original document line number for each received quantity | no more guessing which line each receipt belongs to.

You can now authenticate in the API documentation with your API client credentials and try requests directly. When a field is filled in incorrectly, the response names the field, the value received and, for fields with a fixed list, the accepted values, instead of a generic error. Creating products through the API now accepts the documented handling unit values.

The stock pushed to Shopify counted everything in the warehouse, including goods quarantined in quality zones, which could put items on sale that could not be shipped. It now counts only the locations in the store's shipping process plus the packing and loading zones.

On logistics-operator accounts, cancelling a shipping order failed whenever "All Clients" was selected in the top bar. Cancellation now identifies the client from the volume itself, independently of that selection. Server error messages also stop appearing as missing-translation text.

When an external system replied successfully but with no body, the WMS recorded an integration error on the order. A successful response is now treated as an acknowledgement; only an explicit rejection marks the integration as failed.

When closing an inventory, quantities with decimals were rounded down (2.5 became 2), producing wrong adjustments and differences. Decimal quantities are now respected.

Ticks previously answered top-selling product and client questions across the whole account, even when a specific warehouse was selected in the top bar. It now scopes those two rankings to the selected warehouse only (operator performance stays account-wide).

The reception screen no longer stalls between scans. The grouped view is now read-only and stopped writing to the database on every scan, so several operators can receive at the same time without the waiting time that was noticeable during high-volume receiving.

In multi-client warehouses, running a picking, packing or stowage picking required choosing the client in the top bar first. The application now identifies the client from the document itself, so operators can work with All Clients selected.

The stowage form was reorganised for small screens: the requested origin and product now appear inside the field itself, buttons no longer drop to a second row, the scan field is about 50% wider in stowage picking, and the Stow button now spans the full width.

On the reception, stowage picking and inventory screens, the header and the last-scanned line squeezed columns so tightly that a product description wrapped one character per line. They now keep their natural width and scroll sideways, taking up far less screen height.

When a reception line is communicated, or re-communicated, to MVO PT, the GTIN and CNP that were actually scanned are now sent, instead of whichever barcode happened to come first in the product catalogue. Retrying from a reception history now behaves exactly like the original attempt.

When MVO PT cannot be reached, the communication is now flagged in yellow as pending instead of marking the pack as rejected. The stored message also shows the real, complete reason for the failure rather than a generic technical text.

Searching by serial number in reception lines returned no results for products with a security device. Search and sorting now work in the lines list and in both grouped views.

The Finish button is now disabled while the close is running, preventing the same reception from being closed twice and two documents being sent to the connected system. If two users close at the same time, the second one gets a clear message saying the close is already in progress, instead of an error.

Refreshing the page directly on the receptions screen sometimes left the filters missing and the list empty until you navigated away and came back. The screen now waits for the warehouse to be available before loading.

In a stowage picking, stock is now reserved at the specific location the operator is sent to, rather than at the zone. Stock can no longer be allocated elsewhere in the meantime, leaving the operator at an empty shelf.

On orders that ship straight after picking, with no packing step, the reserve for the last line stayed stuck at picking after the order had already left. Those reserves are now released correctly, keeping available stock accurate.

When stock was rebuilt from movements, transfers and shipments lost their client, producing stock rows with no client and negative available quantities. The client is now kept, and the available quantity shown never drops below zero.

On accounts that manage stock for several clients, editing and saving a shipping order could clear the client it belonged to. This typically happened right before sending it to picking, leaving the order with no owner and out of that client's lists and portal. The client is now kept on every save, including on orders that arrive through file imports or integrations. Orders created from the client portal are always assigned to the signed-in user's own client.

When a customer who had already bought from your store placed a new order with a different delivery address, the address from their first order kept being used, and that was the address handed to the carrier. Incoming orders now refresh the saved address with the one on the new order: street, postal code, city and country are replaced together, so a new address is never mixed with leftovers from the previous one. Orders that carry no address leave the existing one untouched, and the customer's name and e-mail are always preserved. Applies to Shopify, WooCommerce, PrestaShop, Jumpseller and Shopkit stores. Note that the same delivery point is shared by all of that customer's orders, so an earlier order of theirs that hasn't shipped yet will also use the updated address.

Scanning a Code 128 label that isn't a product code, an 18-digit pallet licence plate for example, cut the code down to its first 14 characters and treated it as a product code, so the lookup found nothing. A scanned code is now only read as a product code when it genuinely can be one; anything longer is kept exactly as it was scanned.

A product's "Shopify" window now has a "Sync from Shopify" action that re-pulls that single product's image and barcode from your store, so you can repair a stale or wrong image (or a missing barcode) without running a full catalog sync. Manual images are always kept | the sync never overwrites an image you set yourself. This action is available to account administrators.

On the Picking Order screen, the two time indicators are now labelled "Retrieval time" and "Travel time" and show the "real time next to the estimated time", with a badge highlighting the deviation when they differ. This makes it much easier to spot pickings that took longer than planned.

In the "Manage Receptions" list, clicking the quality icon now opens a window listing exactly the items placed in quality for that reception | the same way the differences icon already works | so you no longer have to open the reception to see them.

When putting away or consolidating stock, a location that already holds one product can now also receive a "different product belonging to the same client", instead of being blocked. Locations are still protected from mixing stock from "different clients", so client separation is preserved.

When you expanded a product image, the dropdown menu could appear in front of it. The menu now closes before the image opens, so the enlarged image is always fully visible.

Searching products by an expiration-date range (with stock) now correctly returns only the products whose stocked lot falls within that range, instead of ignoring the date filter and returning all products with stock.

Deleting a shipping order that was imported from Shopify no longer fails with an error. The link to the Shopify order is now released first, so the order is removed cleanly.

When you scan an unknown barcode during a reception and create a new product from the pop-up, that barcode is now automatically added to the new product, so you don't have to enter it again by hand.

When syncing products from Moloni, an image you had already set on a product is now kept instead of being replaced by the one coming from Moloni, so your chosen product images are preserved.

In the cockpit, the "bulk assign" action now skips orders that are still waiting for their stowage picking and have no assignable work yet, matching what the row already shows. This prevents assigning tasks that can't be started.

Finishing a reception could occasionally trigger a background error while reading the reception type, in setups that process reception completion asynchronously. The reception data is now re-read safely, so completion runs reliably.

If a check for new in-app announcements failed once (for example due to a brief connection problem), announcements stopped refreshing until the page was reloaded. They now keep checking automatically, so you don't miss new announcements.

In the Moloni integration, the same source document could sometimes generate two shipping orders (or receptions), and therefore duplicate draft invoices, when the same document type and series was configured in more than one mapping. Saving a document mapping now blocks a duplicate source configuration, so each Moloni document is only picked up once.

On the reception screen, the "put in quality" dropdown was being cut off by the content below it, hiding some of the quality statuses. The menu now opens fully so you can pick any available status. The same fix was applied to the inventory operations screen.

When creating a new location or zone, the parent "location" dropdown was listing zones from every warehouse in your account. It now shows only the zones of the warehouse you're currently working in, so you can't accidentally place a location under another warehouse.

When moving from one product to another without leaving the product screen, some sections (Inventory tabs, Barcodes, Lots, Serial Numbers and Client Mappings) kept showing the previous product's data. They now reload correctly for the product you're viewing.

For users that belong to a specific client, the stock export and the stock indicators now include only that client's stock, instead of pulling in figures beyond their scope. The numbers shown and exported now match what the user is allowed to see.

Detail pages got a consistent redesign: key numbers now sit in a KPI strip at the top, and you can edit information inline without opening a separate screen. The layout and terminology now match across products, delivery points, your organization, and users.

Purely internal stock movements, like emptying a container or administrative stock returns, were being counted as regular warehouse operations, inflating the operation totals shown on organization and user statistics. These are now excluded so the numbers reflect actual warehouse activity.

It was possible to delete your own user account, or the last remaining administrator of your organization, leaving no one able to manage users. Both actions are now blocked.

Manually syncing stock to Shopify no longer times out on large catalogs, it now runs in the background and shows live progress. We also added a Force full re-sync option that re-pushes stock for every mapped product, even ones that haven't changed.

We added a safeguard so two near-simultaneous clicks can no longer create two carrier shipments for the same order. Retrying a submission now asks you to confirm first if a request for that order already exists.

NACEX shipments accepted by the carrier but not yet collected were showing as "Collected". They now correctly show as "Created" until the parcel is actually picked up.

Some delivery statuses (like Out for Delivery or Incident) showed with the wrong color in the order's carrier tab, and manually refreshing a Correios Express shipment could show an outdated status. Both are now fixed and consistent with the shipping orders list.

Orders using a carrier plugin set to manual communication were sometimes marked "Delivered" as soon as they were dispatched, instead of "In Shipping". They now correctly stay "In Shipping" until you use the "Submit to Carrier" button, and every carrier now shares the same single Ship button at dispatch.

Stock export reports have new columns for warehouse occupancy and product weight, giving you more detail for space and load planning without leaving the spreadsheet.

NACEX shipments now show a clearer tracking code and public tracking link on the carrier tab, and closing packing offers a one-click "Confirm with carrier label" option. Activating the NACEX plugin now offers to pre-fill a matching carrier for you. If a carrier integration briefly fails, connected e-commerce orders (Shopify, Shopkit, Jumpseller) are still fulfilled right away, and their tracking is filled in automatically once the carrier confirms it.

The product page has a new, simpler layout with two tabs (Overview and Inventory) where you edit each section directly, without a separate edit screen. It also shows new KPI cards for stock, rotation and average stock, a stock-over-time chart, and a Top Delivery Points panel showing which destinations receive the most of that product.

If a product on a document can't be matched in Moloni, the document is no longer closed automatically | you'll see a clear warning listing which products were skipped, so you can fix them first.

When picking and packing are done together, packing instructions now appear right after their related picking step instead of out of order, making the workflow easier to follow.

Fixed an issue that could occasionally generate duplicate picking instructions or instruct more than what was actually ordered on a line. Picking instructions now always match the exact quantity needed.

Fixed an issue where editing and saving a product could clear its ABC classification badge until the next automatic recalculation. Your product's ABC classification is now preserved when you make edits.

The Assignments chart in the Cockpit no longer shows an internal system placeholder as if it were an operator, packing quantities are now counted accurately, and the workload chart now reflects planned time for a more realistic view of each operator's day.

Shipping orders no longer show an integration badge or a “re-integrate” option when the tenant isn't actually connected to an ERP or invoicing system.

In the Cockpit, it's no longer possible to remove an operator from a picking or packing task that has already been completed, which used to reset the task's status and affect its history.

Internal stock movements created when a picking wave is cancelled no longer show up in Product → Stock → Movements, so that list now only shows the movements relevant to you.

NACEX shipping labels now always download and open correctly as PDF, instead of occasionally downloading as an unreadable file.

Finishing a reception or closing a shipping order could occasionally freeze for a long time when the connection to an external system (like an ERP) was slow to respond. This no longer blocks the process for other users.

In rare cases, an unexpected error could silently stop the system from automatically creating new picking and packing tasks for a warehouse until it was restarted. This is now caught and logged instead of stopping silently, and one warehouse's issue no longer affects the others.

The confirmation message shown when resending a user invite now displays correctly in Portuguese.