A CrystalCommerce import reads the inventory CSV your CrystalCommerce store already exports and loads it into Oskii as counted stock, with each card's set, condition, language and finish kept.
What the CrystalCommerce import is for
If your online store runs on CrystalCommerce, your singles are already counted there. The import lets you bring those counts into Oskii without retyping them, so the counter kiosk can search what you actually hold.
It is a one-file-at-a-time upload. It is not an API connection, and Oskii does not log in to your CrystalCommerce account.
Which file Oskii reads
Oskii reads the inventory CSV that CrystalCommerce exports. Export it from CrystalCommerce; the steps vary by account.
That raw file starts with a few lines of preamble before the header row. Oskii looks through the first lines of the file for the header, so you do not need to delete them. Oskii also reads the Mass Create layout, which uses the columns Product Name, Category, Qty, Condition and Language.
Oskii recognises a CrystalCommerce file from its header row. It does not mistake a ManaBox export or an Oskii stock export for one.
How Oskii finds the card
A CrystalCommerce file names a card by product name and set name. It gives no set code or collector number. Oskii matches the folded card name, the folded set name and the language against its Scryfall catalog. If the file does carry a collector number, Oskii uses it too.
Oskii never guesses. If no card fits, the row is a problem row. If more than one card fits, the row is also a problem row, and you decide what to do about it. A card filed under a set it was never printed in is a problem row, not a best guess.
Conditions and finishes are kept
CrystalCommerce writes condition and language as variants, and Oskii reads both. A foil is marked in the product name or the category, and Oskii keeps it as a foil copy with its own count.
Conditions map onto Oskii's four grades. The finishes stay separate from each other, so a foil and a nonfoil of one printing remain two lines.
How to import a CrystalCommerce export, step by step
Do this once per category you want to bring in.
- Export your inventory CSV from CrystalCommerce (steps vary by account).
- Download the finished CSV.
- In the Oskii console, open Imports and upload the file.
- Choose the location the cards belong to. The export is named report and a number, so the file name cannot tell Oskii where it goes.
- Read the dry run. It shows each card that will be added, changed or set to zero.
- Check any problem rows. Confirm before applying a plan that would zero cards tied to problem rows.
- Apply the plan.
What the import changes
A CrystalCommerce export lists the products in the categories you ticked. Oskii treats it as a listed snapshot. A card the file lists gets the count the file gives. A card at quantity 0 is set to 0.
A card the file does not list is left alone. That is deliberate. One category is not your whole shop, so Oskii never assumes a missing card has sold out.
Because CrystalCommerce is another system's count, its file can go only into a location that system counts. Oskii refuses to apply it into a location Oskii counts itself, and it checks again at the moment you apply.
What the import never changes
An import never drops a hold. If a customer has a copy held and the file lists a lower count, Oskii keeps the held copy in stock and flags the card as a discrepancy for you to review.
An import never changes a cost a person entered. Locked costs stay as you set them.
The Sell Price and Buy Price columns are not read. The import carries counts, not prices. Market estimates come from Scryfall, and a price you set in Oskii is the Shop price.
A cost problem is a note, never an error. It never becomes a problem row, so it cannot zero a card.
Emailed exports wait for you
If your import sender list allows it, an export can arrive by email. Oskii always holds an emailed CrystalCommerce export for your review. It never applies one on its own.
Questions shop owners ask
- Which CrystalCommerce file does Oskii read?
- The CSV from Inventory, Products, Export, and the Mass Create layout with Product Name, Category, Qty, Condition and Language.
- Do I need to remove the lines above the header?
- No. Oskii looks for the header row near the top of the file and reads from there.
- What happens to cards that are not in the file?
- Nothing. A card the file does not list is left alone, because one category is not the whole shop.
- Will the 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 review.
- Does Oskii keep my CrystalCommerce prices?
- No. Sell Price and Buy Price are not read. The import brings in counts, conditions, languages and finishes.