Trust
Corrections policy
If a calculation, definition or source reference is wrong or outdated, QiiChain corrects the page and updates its reviewed date rather than preserving an inaccurate result.
Report a problem
If a calculation, definition or source reference is wrong or outdated, QiiChain corrects the page and updates its reviewed date rather than preserving an inaccurate result.
What to include
Provide the page URL, input that produced the issue, expected result and—when relevant—the source or standard you believe conflicts with the page.
How corrections are handled
A reproducible tool defect is fixed in the shared engine so every affected page benefits. A factual correction updates the content and reviewed date.
No silent certainty
When the source itself is ambiguous or the result depends on a trading partner, QiiChain explains the uncertainty instead of inventing a universal rule.
Evidence to keep
Keep a reproducible record for corrections policy so another person can verify the same conclusion from the same source values.
Keep the next verification close
Do not end the workflow at corrections policy. Link the result immediately to its verification step: scan the printed code, parse the encoded data, compare the GTIN with the product master, or compare the inventory trigger with open supply and recent demand. Keeping verification close to the calculation reduces the chance that an apparently clean result is copied into production before someone notices a mismatch.
Operational scenario
When corrections policy is part of replenishment planning, store the date range used to compute averages. A daily-demand average from a promotion month should not silently become a permanent baseline, and a supplier lead time measured before a process change may no longer describe current performance.
Downstream hand-off
After corrections policy, preserve the exact machine-readable value alongside any friendly display label. Users may want spaces, currency symbols or parentheses for readability, but scanners and calculations often require an unformatted source value. Keeping both forms avoids repeated parsing and accidental data loss.