Odoo Community
Odoo Enterprise
Viindoo Cloud
Validate a transfer on the date it actually happened
A back-date prompt on validation - and the transfer, its moves, its lines, its valuation layers and its journal entries all carry that date.
Inventory Backdate (technical name viin_stock_backdate) is an Odoo 17.0 app for Odoo Community and Odoo Enterprise and Viindoo Cloud, built for warehouse operator, cost accountant, controller, auditor.
At a Glance
The facts of Inventory Backdate, version 0.4, in one place. Published by Viindoo.
Technical name
viin_stock_backdate
Odoo version
17.0 (Odoo Community, Odoo Enterprise, Viindoo Cloud)
Depends on
stock, to_backdate
Adds
7 new models, 1 extended model, 1 access group
Best for
Warehouse operator; Cost accountant; Controller; Auditor
Not for
It cannot post into a locked period.
Key features
A Validate with a Back Date prompt on transfers, The date reaches the moves, the move lines and the valuation layers, Accounting entries post in the period the movement belongs to, The same for inventory adjustments and for scrap, Restricted to a group, so back-dating is a permission, Everyone else validates exactly as before
How It Works
One prompt, at validation.
1
Validate, and say when
The date defaults to now; changing it moves everything the validation produces with it.
2
The transfer keeps that date
Nothing else about the transfer changes - the same operations, the same reservations.
3
And so does the valuation
The layers carry the back-dated date, which is what makes a closed period true.
What You Get
A Validate with a Back Date prompt on transfers
The date reaches the moves, the move lines and the valuation layers
Accounting entries post in the period the movement belongs to
The same for inventory adjustments and for scrap
Restricted to a group, so back-dating is a permission
Everyone else validates exactly as before
More Screens
Everything below was taken on a database seeded with real business data, on this series - not a mock-up and not a screenshot from an older version.
Valuation layers on the back-dated date
What This App Does Not Do
Read this before you buy. Everything below is something the app deliberately leaves to another app or to you.
It cannot post into a locked period.
Odoo's accounting lock still applies - back-dating is not a way past it.
It does not re-run reservations.
Stock availability is evaluated as usual; only the recorded date changes.
It is a permission, not a default.
Users outside the back-date group never see the prompt.
Future dates are not the point.
The wizard exists for recording what already happened.
Works Well With
Apps from the same stack, built to fit this one:
Manufacturing Backdate
The same for production orders - and it builds on this.
to_mrp_backdate
Who Should Use Inventory Backdate?
Warehouse operator
Records Friday's shipment as Friday's.
Cost accountant
Gets the valuation layer in the right month.
Controller
Decides who may back-date, because it is a group.
Auditor
Reads one date across the transfer, the stock move and the entry.
Frequently Asked Questions
What does Inventory Backdate do?
A back-date prompt on validation - and the transfer, its moves, its lines, its valuation layers and its journal entries all carry that date.
What does Inventory Backdate not do?
It cannot post into a locked period. Odoo's accounting lock still applies - back-dating is not a way past it. It does not re-run reservations. Stock availability is evaluated as usual; only the recorded date changes. It is a permission, not a default. Users outside the back-date group never see the prompt. Future dates are not the point. The wizard exists for recording what already happened.
Who is Inventory Backdate for?
Warehouse operator: Records Friday's shipment as Friday's. Cost accountant: Gets the valuation layer in the right month. Controller: Decides who may back-date, because it is a group. Auditor: Reads one date across the transfer, the stock move and the entry.
Which Odoo version and editions does it support?
Odoo 17.0 - Odoo Community, Odoo Enterprise, Viindoo Cloud. Upgrades to a newer Odoo series are a separate purchase for that series.
What does it depend on?
It installs on top of: stock, to_backdate. Odoo installs them with it.
How do I set it up?
One prompt, at validation.
What works well with it?
Manufacturing Backdate (to_mrp_backdate): The same for production orders - and it builds on this. Sales Backdate (to_sale_backdate): Orders confirmed on the day they were agreed. Stock & Journal Links (to_stock_account_moves_link): Following the back-dated entries back to the transfer.
Can I try it before buying?
Yes - the Live Preview button at the top of this page opens the module's own screen on a working database.
How do I get support?
Write to apps.support@viindoo.com with your Odoo version and the technical name viin_stock_backdate; pre-sales questions go to sales@viindoo.com.
Need help with Inventory Backdate?
For questions, implementation support or a custom feature, contact Viindoo.
Upgrades to a newer Odoo series are a separate purchase for that series.
All Viindoo apps: apps.odoo.com/apps/modules/browse?author=Viindoo
About Viindoo. Viindoo builds and maintains more than 1,000 apps on the Odoo App Store for the Community and Enterprise editions and runs them on Viindoo Cloud. A purchase of Inventory Backdate covers the 17.0 series: bug fixes on the module reach you through the store, questions go to apps.support@viindoo.com with the technical name viin_stock_backdate, and moving to a newer Odoo series is a separate purchase for that series. Source code is delivered with the module and stays yours to read and adapt.
Technical Requirement
Editions: Odoo Community, Odoo Enterprise, Viindoo Cloud
Changes log
0.4 - Latest on the 17.0 line
- The transfer's own done date is restamped after core writes the clock value.
- Inventory adjustments and scrap use the same prompt.
This software and associated files (the "Software") may only be
used
(executed, modified, executed after modifications) if you have
purchased a
valid license from the authors, typically via Odoo Apps,
or if you
have
received a written agreement from the authors of the
Software (see the
COPYRIGHT file).
You may develop Odoo modules that use the Software as a library
(typically
by depending on it, importing it and using its
resources), but
without
copying any source code or material from the
Software. You may distribute
those modules under the license of your
choice, provided that this
license
is compatible with the terms of
the Odoo Proprietary License (For
example:
LGPL, MIT, or proprietary
licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell
copies of the
Software or modified copies of the Software.
The above copyright notice and this permission notice must be
included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT
SHALL THE
AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING
FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE
SOFTWARE.