Ability to lock Inventory while a Pricing Update is being completed
There have been multiple instances in our 10 years using this product where the entire inventory file has been downloaded in order to bulk update pricing.
Between the download of the file and the upload of the new file, other users have made edits to descriptions etc and then that gets overwritten by the new file being uploaded.
A feature where you could stop any edits being made to any products, whilst still allowing use of other sales/purchase features etc would be a real benefit.
Comments
3 comments
This is a familiar problem. The more approriate or “proper” solution would be to allow data imports where only one or two key columns or “fields” are required if it is an update. Most other database type applications allow you to reimport with a subset of fields. This avoids the risk of overwriting other change in unrelated fields because you now only import updates for the relevant fields.
All you need is a simple, clear rule: An empty field will remove data, but a missing column is ignored.
It is not only descriptions and tags, etc. that are at risk, but live data like current avg cost. If you export your inventory list today and reimport in three day's time, you overwrite the current average cost that Cin7 has carefully calculated with every inventory movement…
(I used to export, then calculate/process data, then export a fresh inventory list and merge the changes before importing. A lot of uneccessary manual work. We have moved to our own API application to process our routine tasks outside Cin7 due to limitations.)
See also:
https://help.core.cin7.com/hc/en-us/community/posts/12019163949583-Product-Filters-Bulk-Editing
https://help.core.cin7.com/hc/en-us/community/posts/11403785110415-Improvement-to-Bulk-Updating-Inventory-both-within-Cin7-and-File-Import
@wordle unlimited We've run into the same issue during bulk price updates, and a temporary inventory lock or edit-freeze feature would be extremely helpful for preventing accidental overwrites of changes made by other users.
@Harper Rogers
Saying again: there is system calculated data which is included in a bulk update (e.g. current average cost) which requires more than a lock for user edits. You really need to lock down ALL transactions and edits if you want to preserve data integrity.
The correct solution is to allow granular updates, where you are able to upload only the relevant columns/fields.
My approach was to download inventory from Cin7 and process it. Then when I am ready, wait for a relative quite period of activity and download a fresh inventory list, merge just the changed fields into it from the processed data, and then upload back to Cin7.
Please sign in to leave a comment.