Post-launch operations: calendar and owners

Daily or real-time#

• alerts for dangerous products, fraud, account takeover, and unusual payouts;
• DSA/GPSR notification queue and authority deadlines;
• checkout errors, payment-order-refund discrepancies;
• offers awaiting documents and attempts to relist blocked products;
• security complaints identified from complaints and reviews.

Weekly#

• cases approaching the 14-day deadline or other SLA;
• changes in seller data, permissions, and PSP account statuses/associations visible to the operator; changes to the account itself are controlled by Stripe if they occur solely with them;
• sample of new offers and high-risk categories;
• undelivered shipments, chargebacks, and negative balances;
• availability reports and critical barriers.

Monthly#

• reconciliation of commissions, payouts, refunds, and PSP reports;
• audit of users with administrative privileges;
• review of recurring defects and high-risk sellers;
• test of random price proofs from 30 days, acceptances, and consents;
• backup and restore test results according to schedule;
• moderation, complaint, recall, and response time metrics.

Quarterly#

• DAC7 aggregates and data quality before year-end;
• GDPR rights and deletion tests in subordinate systems;
• review of suppliers, integration permissions, and chain security;
• availability of the full purchase path and key changes;
• verification of category document validity and responsible persons.

Annually#

• re-evaluation of micro/small/medium status for DSA, PAD, P2B, and NIS2;
• re-verification of key seller data and BDO;
• DAC7 report by the end of January and information for sellers;
• BDO reminders by the end of February and March 15;
• review of terms and conditions, policies, ranking, and role division;
• audit of retention, RCP, GDPR risk, cybersecurity, and incident plan;
• product recall drill: can you find sellers, batches, and buyers within hours.