Every operator starts here
Day 1: new listing comes in, you review it manually, approve it, maybe send a welcome message.
Day 100: 15 new listings per week, 3 sellers need nudges about missing photos, 2 listings have pricing way outside category norms, and you haven't checked inactive sellers in a month.
This is the scaling wall. The work doesn't get harder — it just becomes impossible to do manually with consistent quality.
The automation spectrum
Not everything should be fully automated. The spectrum looks like this:
| Level | What happens | Example |
|---|---|---|
| Manual | You do everything | "Review each listing by hand" |
| Assisted | System flags, you decide | "These 5 listings have incomplete data — approve anyway?" |
| Semi-auto | System acts, you can override | "Listing auto-approved, quality score: 87/100" |
| Fully auto | System handles end-to-end | "Stale listing reminder sent on day 30, no operator input" |
Most operators need a mix. High-value decisions (first-time seller approval) stay at Level 2. Routine tasks (stale reminders, badge updates, renewal notices) go to Level 4.
What automated workflows look like in practice
Example 1: New listing flow - Listing created → quality score calculated → if score > 80: auto-approve → if score < 60: flag for review → notify operator of flagged items
Example 2: Seller health monitoring - Check all sellers weekly → if no update in 30 days: send friendly nudge → if no response in 14 days: flag as dormant → if dormant for 60 days: alert operator to decide
Example 3: Enrichment automation - Listing receives 50+ views → add "Popular" badge → listing price drops by 10%+ → add "Price reduced" indicator → all badges sync to marketplace template automatically
The key principle: rules you set, automation that runs
The operator defines the rules and thresholds. The system executes continuously. You check in when you want to — not because you have to.
See how Empasa's automation engine works for your marketplace. Start a free trial or view automation features.