Match and scoring type
Singles or doubles, rally or side-out — both read straight off the game you saved.
Run your session in PickleMixer, record the scores as you play, then export every game to a single import-ready file — built in DUPR's own club match-upload format, with the instruction rows already stripped out. Your club's verified DUPR organizer uploads that one file instead of re-typing a whole night of games by hand.
To be exact about it: PickleMixer doesn't submit to DUPR for you. There's no API between us — not yet. What it removes is the re-entry. The rotation, the scores, the names and the IDs are already sitting in one place, so the upload becomes a file picker instead of an evening.
The worst version of this job is uploading a hundred rows, watching DUPR refuse forty of them, and having no idea which player broke it. So before anything downloads, every selected game is checked against the rules DUPR actually enforces, and you get told where you stand — “18 of 24 ready”, plus the names of the exact players who are missing a DUPR ID.
Games that would be rejected are left out of the file by default. If you'd rather send everything anyway there's a checkbox for it, sitting next to a plain warning that DUPR will reject those rows — so it's a choice you make, never a surprise you discover afterwards.
The IDs themselves are checked at the point of entry too. A malformed ID is refused when you type or paste it, rather than quietly becoming a plausible-looking fake that only fails at DUPR's end. And the same ID landing on two players in your group is flagged by name, before it ever reaches a file.
Singles or doubles, rally or side-out — both read straight off the game you saved.
Your event label with the game's own local date appended, so nights stay separate.
Name and DUPR ID in each of DUPR's A1, A2, B1 and B2 slots.
One PickleMixer game is one DUPR game, so games 2 to 5 stay blank — as DUPR's template asks.
The header row is DUPR's own, verbatim, and the instruction rows DUPR tells you to delete before importing are already gone. There's no spreadsheet cleanup step — the file is import-ready the moment it lands in your downloads folder.
Uploading club matches is a permission DUPR grants, not something an app can hand you. Your club needs a verified organizer or director, and that person is the one who submits the file — we produce it, they upload it. A game that includes a player without a DUPR ID is held out of the file, so missing IDs never sink the upload.
The mixer stays free — no signup, no player logins. The export is built out of recorded game scores, and recording scores is part of the Pro plan, so the export flow needs Pro. DUPR IDs are entered once per player and reused from then on.
Not everyone in your group will have a DUPR ID, and that's fine. Those players still get PickleMixer's own private in-group rating, which is what balances tonight's courts and ranks your ladder leagues. The DUPR export simply leaves their games out and carries on.
No. PickleMixer produces a file, not a submission. We build your games into a CSV that matches DUPR's own club match-upload template, and a verified club organizer or director uploads it on DUPR's side. Nothing is sent to DUPR automatically, and no rating moves until DUPR processes that upload. What you save is the manual re-entry — not the upload step itself.
A DUPR club, and someone on your side who is a verified club organizer or director on DUPR — that permission is what lets a club upload matches at all. On the PickleMixer side you need each player's DUPR ID saved on their player record, and a Pro plan, because recording game scores is a Pro feature.
They need DUPR accounts — DUPR matches every row on an exact DUPR ID, so a player without one cannot appear in an upload. They do not need a PickleMixer login: the organizer enters each DUPR ID once, on the player's record or through a bulk CSV import, and players never sign up or install anything.
One row per game, using DUPR's template columns exactly: match type (singles or doubles), scoring type, event name, date, all four player names with their DUPR IDs, and the score. One PickleMixer game is one DUPR game, so game 1 is filled in and games 2 to 5 stay blank, which is what DUPR's own template asks for. The ten instruction rows DUPR tells you to delete are already gone, so the file is import-ready the moment it downloads.
Those games are left out of the file by default, and the export screen names the exact players who are missing an ID so you know who to chase. Games that ended in a tie or have uneven teams are held back too, since DUPR cannot represent them. You can tick a box to export them anyway, with a plain warning that DUPR will reject those rows. The point is that you never hand DUPR a file it is going to bounce. Players without a DUPR ID still get PickleMixer's own in-group rating, which is what balances your courts and ranks your ladder leagues.
No. You give the export one event name, and each game's own local date is appended to it, so a month of Tuesday nights arrives at DUPR as separate dated events rather than one giant blob. You also choose exactly which days and which games go in the file.
The mixer itself is free with no signup. The DUPR export is built from recorded game scores, and score recording is part of the Pro plan — so the export flow needs Pro. There is no separate charge for the export or for the number of games in it.
The mixer is free — open it, add your players, and run tonight's rotation. Add score recording with Pro, and every game you save is one more row already written into your next DUPR upload.