Return-State Collapse
Return authorisation, label creation, carrier scan, refund trigger, and reimbursement route are treated as a single state. They are separate evidence layers, each with its own proof requirements.
Catalogue Contribution Trap
Platform catalogue logic accepts or processes changes outside the seller’s visible control, then leaves the seller exposed to attribution, compliance, or listing-state liability they cannot fully inspect, control, or reverse.
Override Without Feedback Loop
A human correction restores the visible outcome without changing the rule, signal, or engine responsible. The symptom disappears. The recurrence path remains intact.
Externalised QA
Sellers become the unpaid detection layer for platform defects they did not create, while the audit cost, escalation effort, and resolution risk are shifted onto the party least able to access the underlying system.
Historic Association Persistence
The platform retains a seller-ASIN, seller-brand, or seller-listing association beyond the seller’s active involvement. Compliance may read this as a current relationship after the seller-facing record has vanished.
Asymmetric Data Purge
The seller-facing record disappears at the same moment a compliance consequence becomes active. The seller loses the evidence needed to contest the penalty precisely when the penalty is applied.
Correction-Path Failure
The contribution path is stronger than the correction path. Harmful catalogue states can be created faster than legitimate parties can reverse them.
Platform State Without Seller Visibility
The platform makes a decision based on internal state the seller cannot see, query, export, or challenge. The decision is visible. The basis for it is not.
Offer-Level Enforcement / Account-Level Consequence
A single listing decision triggers account-level risk, suppression, or deactivation. The enforcement scope is broader than the visible issue.
Support Routing Boundary
Each team in the escalation path can receive the report, but not resolve the underlying issue. The seller receives activity without ownership and closure without correction.
Reporting Surface Mismatch
Different dashboards, emails, pages, reports, or support replies show incompatible versions of the same case state. The seller cannot identify which surface controls the outcome.