I don't know if it's SQL or NoSQL or some other hybrid db you're running on the stack so it's hard to say exactly what implementation makes more sense, but the gist is basically, well, it would be cool to be able to repopulate individual details of cards in a submission at the end of the grade/sales cycle in one go, whether via importing a CSV file that upserts each line and updates fields that have changed, or through an api call that repopulates the same data.

I'd love to have json as an option but I understand that the potential tech debt to build that out is much higher for most production apps. I do update my private apps with the dataset library in Python where all upserts and inserts and updates and insert-ignore and update-ignore can be done as Python objects - which are json adjacent, but I'll be damned if anyone else has this particular preference born entirely out of laziness. The plus to this is that in theory it allows for update across nearly all platforms even if it's by hand. Although the GraphQL API used by Fanatics Collect is actually quite easy to use even without introspection and one can simply copy/paste the return in json and it should be formatted uniformly.

But just an upsert function would do. The REST (sorry) can wait.