A ManaBox import takes the CSV you export from a ManaBox binder and turns it into counted stock in Oskii, one line per printing, finish, condition and language.
What the ManaBox import is for
Many shops already count their singles in ManaBox. The scans you already made in ManaBox are the fastest way to get a real count into Oskii, because every row names a printing by its Scryfall ID.
The import is a file you upload. It is not a live link between the two apps. You export a binder when you want Oskii's count to catch up, and you upload it.
What a ManaBox export looks like
A ManaBox export is a CSV with one row per card entry. Oskii reads it by header name, not by column position. The headers in a real export are:
- Name, Set code, Set name, Collector number
- Foil, Rarity, Quantity
- ManaBox ID, Scryfall ID
- Purchase price, Purchase price currency
- Misprint, Altered, Condition, Language, Added
The binder is the file name
ManaBox has no binder column. The binder is the file name without .csv. A file called All Commander.csv is the binder All Commander.
Oskii matches that name to a location in your shop. If the name matches a location's folder name exactly, the cards go there. If nothing matches, they land in Unsorted. So name your locations the way you name your binders, and the match takes care of itself.
Browsers and operating systems sometimes rename a download, for example All Commander (2). On a manual upload, Oskii tries the exact name first, then the name with that copy suffix removed, and warns you if the result looks like a duplicate location.
Every finish is its own copy
ManaBox writes normal, foil or etched in the Foil column. Oskii keeps nonfoil, foil and etched as separate finishes with separate counts.
The ManaBox ID is shared across finishes of the same card, so Oskii never uses it to tell copies apart. A card is identified by its Scryfall ID, finish, condition and language together. A foil and a nonfoil of the same printing stay two lines.
How to import a ManaBox export, step by step
These are the steps for one binder. Repeat them for each binder you want to bring in.
- In ManaBox, open the binder and export it as a CSV.
- Check the file name. It becomes the binder, so rename it to match the location it belongs to in Oskii.
- In the Oskii console, open Imports and upload the file.
- Read the dry run. It lists each card that will be added, changed or zeroed, and says why.
- Look at any problem rows. A row Oskii cannot resolve to a card is a problem, and applying a plan with problem rows makes you confirm that those cards will be zeroed.
- Apply the plan. Oskii applies the plan you reviewed, checking the counts against your stock as it is at that moment, so a hold placed after the dry run is still kept.
What the import changes
A ManaBox export is a full snapshot of one binder. For every card in that binder, Oskii sets its count to what the file says. A card that is in the binder in Oskii but missing from the file goes to zero.
That is why the file name matters. An export with no rows for a known binder reconciles that binder to zero. A file whose name matches no location changes nothing.
Oskii also remembers copies it sold between exports. If you sold a card at the counter and ManaBox still counts it, the next import does not bring the sold copy back.
A full snapshot is refused into a location that Oskii counts itself. Pick a location ManaBox counts.
What the import never changes
An import never drops a hold. If a customer has a copy held and the file says you have fewer, Oskii keeps the held copy in stock and flags the card as a discrepancy for you to look at. The dry run marks those rows as hold kept.
An import never changes a cost a person entered. A cost you typed in is locked. The Purchase price column in a ManaBox file only fills in a cost that was unknown, and only when the price is in US dollars.
A cost problem in the file is a note, never an error. An unreadable price, a price in another currency or a price of zero leaves the cost unknown and shows a note in the preview. It does not become a problem row, so it can never zero a card.
Oskii recognises a file by its contents, so uploading the same file twice does not count it twice.
Emailing the file in
On the Pro plan you can email a ManaBox export to Oskii instead of uploading it. Only senders on your import sender list are accepted. A file from anyone else is rejected unread and logged on the Imports page for 30 days.
An emailed file applies by itself only when the dry run is clean and within limits. Anything with a problem row or a discrepancy waits for you to review it.
Questions shop owners ask
- Does Oskii connect to my ManaBox account?
- No. You export a binder as a CSV and upload it. Oskii never logs in to ManaBox.
- How does Oskii know which binder a file belongs to?
- From the file name. ManaBox has no binder column, so the file name without .csv is the binder, and Oskii maps it to a location of the same name.
- Can an import remove a card a customer is holding?
- No. An import never drops a hold. The held copy stays in stock and the card is flagged for you to review.
- Will an import overwrite a cost I entered?
- No. A cost a person entered is locked, and an import never changes it.
- What happens if a card in the file is not recognised?
- It becomes a problem row in the dry run. You see it before anything is applied, and you must confirm before cards tied to problem rows are zeroed.