Moving from Stocky to UreyukiBox, start to finish

Before you start: one API key

The only thing to prepare is a Stocky API key — the credential that lets UreyukiBox read your Stocky data on your behalf. In Stocky, sign in as the store owner, click the person icon at the top right, open Preferences, choose API access, and press Generate.

Two cautions. The key is displayed once, so copy it there and then. And it is a credential: paste it into the UreyukiBox migration screen and nowhere else. A read-only key is all the migration needs, and you can delete it in Stocky once you are done.

The copy wizard, in four screens

1. 1. What will be copied

   The opening screen lists the four data types so there are no surprises. Read it and continue.

2. 2. Paste the API key

   The connection is tested on the spot. If it fails you get a message rather than a silent stall — a truncated copy-paste is the usual cause, so copy the key again from Stocky.

3. 3. Wait for the copy

   Progress is shown as it runs. It runs as a background job, so you can close the browser and reopen the wizard later to see where it got to. A few minutes is typical.

4. 4. Check the counts

   You get a per-item count of what was saved. If one item failed, the successful ones are already stored and you can re-run the copy for the failed item alone — re-running is idempotent, so nothing is imported twice.

The fields the API cannot reach

Reorder points, supplier lead times and stocktake history are absent from the Stocky API — they exist only in CSV exports. For what to export and how to keep the files usable, follow the Stocky CSV export guide; the short version is to save the raw files and resist re-saving them in a spreadsheet app.

Reorder points and lead times

Upload the Low Stock CSV in the migration screen and map the columns yourself — which column is the SKU, which is the reorder point. Column names differing between Stocky versions does not matter. Before anything is written you see a preview of how many rows would be added or overwritten.

Stocktake history

Stocky exports one file per stocktake, so a store with history has several. You can select them all at once. Importing them records the counts without moving any stock — Stocky already pushed those adjustments to Shopify when they were run, so re-applying them would double-count. What you get is the paper trail.

Minimum order quantities

MOQs are in neither the API nor any CSV, but Stocky lists them per vendor: open Vendors → your vendor → Order limits (headed “Variant minimum order values”) and you get a table of Product / Variant / SKU / Min Order. Select it, copy it, and paste it into the MOQ box in UreyukiBox.

You do not need to tidy it into a spreadsheet. Stocky right-aligns the quantity, so copying often drops the number onto its own line. UreyukiBox reads the paste by meaning rather than by position — it pairs each SKU with the next quantity that follows it — so header rows and wrapped lines are fine. Anything it could not match, whether an unknown SKU or a quantity with no SKU, is listed back to you rather than silently dropped.

What it costs, and the guarantee

Migration itself runs on the free plan — rescuing your data costs nothing, and you can do it before deciding whether UreyukiBox is your long-term home. What the imported data feeds into (reorder-point alerts, drafted purchase orders, landed cost, reports) is on the paid tiers, which come with a 14-day trial, so you can evaluate against your real data.

If the API copy fails to complete for a reason on our side, we refund the first billed month in full. The CSV and paste imports are outside that guarantee — whether a file imports cleanly depends on its columns, encoding and how Stocky wrote it, none of which we control. If one gives you trouble, write to [email protected] and we will look at it with you.

Common questions

Does this change anything in Stocky?

No. The copy only reads. Stocky is left exactly as it was, so you can keep using it as a reference until it goes offline.

Can I run the copy more than once?

Yes. Suppliers and purchase orders already copied are not duplicated; only new and changed records come across. Running it again close to the deadline is a reasonable way to catch anything you did in Stocky in the meantime.

Do I have to use Stocky to use UreyukiBox?

No. The migration is optional. A store that never used Stocky syncs from Shopify and starts drafting purchase orders from that alone.

What if I miss August 31?

Assume the data goes with the app. Both the API copy and the CSV exports depend on Stocky being reachable, so treat mid-August as your real deadline and leave room for the rush.