iPhone 13, 128 GB9 990 Kčre-posts daily · 06:00
Case study · InzerPro, own productOne listing. Every marketplace. On schedule.
On Czech and Slovak second-hand marketplaces, listing age decides visibility, and power sellers were re-posting dozens of ads by hand every morning. InzerPro does it for them, unattended.
www.inzerpro.cz4marketplaces fully automated
~165categories, one picker for all
24/7unattended scheduled posting
1person, design to on-call
01 / Problem
New listings sit on top. Old ones sink.
Resellers, small e-shops and car dealers were deleting and re-posting dozens of ads by hand every day, and competitors still buried them overnight. The marketplaces sell paid promotion but give small sellers no automation at all: none of them has a public API.
Marketplaces InzerPro posts to
Before: delete and re-post every ad by hand, marketplace by marketplace
02 / Product
Write it once.
Pick the marketplaces. InzerPro posts, re-posts and deletes everywhere, on schedule.
- Bazoš.czposted
- Bazoš.skposted
- Bazar.czposted
- Bazar.skposted
- Aukrobeta
- No marketplace offers an API. Every connection is engineered from scratch and kept alive as the sites change.
- Five category trees, one picker. Aukro alone has ~5,800 categories; the crosswalk collapses them into ~165, and fixes are data edits, not releases.
- Every site rejects something. Photos, sections and limits differ per marketplace; listings are adapted to each automatically.
03 / Schedule
The morning runs itself.
00:0006:0012:0018:0024:00nightly test posts real listingsre-posts fire07:30 · seller wakes up, already on top
health check, every hour04 / Reliability
If something breaks, I know first.
InzerPro tests itself in production: real listings posted nightly on the live marketplaces, the whole posting path checked hourly. One email when something breaks, one when it recovers. Customers rarely notice either.
down · 1 emailrecovered · 1 email
Alerts only on change: a six-hour outage is two emails, not six.Scheduled jobs| ID | Action | Marketplace | Listing | Time | Status |
|---|---|---|---|---|---|
| 9312 | relist | Bazoš.cz | iPhone 13, 128 GB | 06:00 | done |
| 9311 | relist | Bazoš.sk | iPhone 13, 128 GB | 06:00 | done |
| 9310 | post | Bazar.cz | Skoda Octavia III 2.0 TDI | 05:45 | done |
| 9309 | relist | Bazar.sk | Detsky bicykel 16" | 05:30 | retrying |
| 9308 | delete | Bazoš.cz | Herna konzole PS5 (sold) | 05:15 | done |
| 9307 | relist | Bazoš.sk | Sedaci souprava, rohova | 05:00 | done |
Mockup with example data; the real dashboard is behind the app login.
41tables, all row-level security
34edge functions run every job
141database migrations shipped
133unit tests on every push
14live scenarios run nightly
55klines of code, one author
The nightly suite even signs real Stripe webhooks: checkout to tier update, verified in test mode.
05 / Partnership
Aukro gave us official API access.
Aukro is the biggest auction marketplace in Czechia and they do not hand out automation to anyone, they saw what InzerPro does and gave us the API in June 2026.
AukroOfficial API accessSince June 2026- #1
- auction marketplace in Czechia
- 4M+
- registered users
- 2003
- trading since
- ~5,800
- categories in their tree
- Account sign-in
- Category tree
- Required attributes
- Photo upload
- Listing created
- Price edited
- Listing ended
- Aukro came to us. A Czech e-commerce agency introduced us, and their commercial people offered the API access, we did not have to push for it.
- One real API, four built by hand. Aukro is the only marketplace here that has an API at all, the rest we built ourselves and keep alive as the sites change.
- 5,800 categories into 165. Their category tree alone is thirty times bigger than the picker a seller sees, we mapped it once and keep it as data.
06 / Beyond re-posting
Re-posting got sellers in the door. It kept growing.
The screens below are the product's own demo mode.
Have a process a computer should own?
InzerPro automates a manual daily workflow end to end, with paying customers. If your team burns hours on work like this, I build the system that takes it over.
A workflow that runs itself, with the monitoring to prove it.