Retired products and catalogue outputs: a Russian case
Review retirement statements, order decisions and the purpose of each catalogue output while preserving the evidence for any proposed successor.
A product can leave production while its catalogue record still has a reference use. A data handoff should distinguish the stated retirement event, any order decision and the purpose of each output.
ASAP describes product statuses and export controls in its Russian RVi project. The method below is PandaBuyNow editorial guidance.
Record exactly what has ended
Ask whether the statement concerns manufacturing, a supplier’s offer or the recipient’s own assortment. In a hypothetical situation, a manufacturer could stop producing a model while a merchant still holds units. Record the stated event, who supplied it, its applicable product and any effective date actually available. Keep a decision about accepting orders separate.
A successor needs its own relationship. A later model number, similar title or newer listing is insufficient on its own. Preserve a proposed successor as a candidate until the relevant manufacturer statement or responsible technical decision establishes what replaces what. Retaining the old record also preserves the context for that question.
Specify what each output should do
For the proposed handoff, distinguish a reference record from an instruction to offer the product for sale. A recipient may need discontinued items for historical enquiries even when they should be absent from a current purchasing list. State the purpose of each output before deciding its contents.
An instruction to include a record should not silently change its manufacturing status or its order decision. Ask what happens when inclusion and blocking instructions conflict. Write down the agreed priority, or require an unresolved outcome until the designated owner decides. The external account establishes that both kinds of control existed; the priority here must be designed for the new project.
Review a fictional retirement exercise
Use an explicitly fictional sample: CAM-R18 is marked production ended; a merchant separately reports four remaining units; CAM-N20 is suggested as a successor. The proposal is to retain CAM-R18 in a service reference file while withholding it from the recipient’s new purchasing list. None of those invented values describes the RVi project.
Ask the reviewer to resolve three concrete questions: does the service file retain CAM-R18’s retirement statement; does the purchasing output follow the written exclusion; and does CAM-N20 remain only a candidate when replacement evidence is absent? Then introduce conflicting output instructions and record the expected unresolved result. Passing requires the intended behaviour for each question, not merely a populated status column.
Agree the retirement decision before delivery
For a Chinese marketplace data brief, bring the affected source links, the recipient’s definition of retirement and an example of each intended output. Identify who can confirm continued sales and who can establish a replacement relationship. Ask which supporting statements are available before choosing the final fields.
The review can establish whether a proposed file carries those decisions and exceptions clearly. Applying a retirement in a live catalogue, changing order permissions or operating a continuing update process requires its own scope and recipient verification. Discuss the sample and the evidence needed with PandaBuyNow before agreeing delivery.