ThreadCloud SOPs

For the ThreadCloud team only

Receiving

When the boxes arrive, you open the receiving page, count what’s in them, mark received quantities per variant, and print labels. This is the most physical workflow — usually done at the receiving table with a phone or tablet next to the open boxes.

When to use
The moment a shipment arrives. Don’t wait — receiving in ThreadCloud the same day keeps inventory and sell-through accurate.

What you’ll need

  • The physical shipment + packing list
  • A printer connected (Dymo 30334 or fallback — see Labels)
  • The order ID (find it in the email confirmation or under the order in TC)

The receiving flow

  1. Open the receiving page — Order → Receiving tab
  2. Enter received quantities per variant
  3. Save — FX rate locks the first time you save
  4. Print labels — one click, sends to Dymo
  5. Apply labels to the physical items
  6. Move to store shelves or stockroom

Stage 1 — Open the receiving page

Two ways:

  • From the dashboard: click the order → Receiving tab
  • From the URL bar: /app/orders/{order-id}/receiving

You see a grid of every style in the order, with its sizes and the ordered quantity per size. Each cell has an empty input next to it for the received quantity.

Stage 2 — Enter received quantities

For each variant:

  1. Tap the cell
  2. Type the count from the box
  3. Move to the next

Speed tip
If the entire shipment matches the ordered qty exactly (rare but happens), click Receive All as Ordered at the top. It pre-fills every received cell with the ordered qty. Then just spot-check and save.

When ordered ≠ received

If you got fewer than ordered:

  • Enter the actual count. ThreadCloud will mark it as a discrepancy in the order’s audit log.
  • The order will sit in PARTIAL status — fine for now. Resolve when the rest of the shipment arrives or when you accept the short.

If you got more than ordered (rare):

  • Enter the larger count.
  • Add a note in the discrepancy log.
  • Verify with the supplier — they may have over-shipped intentionally as a sample.

If a variant didn’t ship at all:

  • Leave it at zero. The order stays PARTIAL.

Stage 3 — Save & lock FX

Click Save Received.

What happens:

  • Received quantities write to Shopify’s inventory (immediately available for purchase)
  • The FX rate locks at the current rate from the multi-provider feed
  • The order’s total cost recalculates with the locked rate

Why FX locking matters
The FX rate snapshot is your cost truth. Even if rates fluctuate over the next 12 months, your margin calculations stay anchored to the rate the day inventory landed. Don’t override this.

If you need to set the FX rate manually (rare — only if the live feed is wrong):

  1. Receiving tab → FX Rate row → click the rate
  2. Type the override
  3. Click Confirm. ThreadCloud locks your manual rate instead.

Stage 4 — Print labels

Once saved, click Print Labels at the top of the Receiving tab.

A new tab opens with the label preview — one label per received unit, laid out for Dymo 30334 (57×32mm). Press Cmd/Ctrl+P, select the Dymo, print.

Label contents:

  • Brand name + style name
  • Colour
  • Size (large, on the right)
  • SKU (small, below)
  • Barcode (Code 128B of the SKU)
  • Retail price

Tip — print in batches
If you have 10 styles to receive but only the first 5 boxes are open, save those first and print just those labels. You can come back later for the rest — the print preview only shows labels for the just-saved batch.

If the printer fails

Three fallbacks, in order of how-close-to-TC-labels they look:

  1. Avery 5160 sheet labels on a regular printer — the print preview prints fine to any printer; just load sheet labels instead of Dymo rolls. Looks identical to the TC label, just on stickier paper.
  2. Shopify Admin native print — see the runbook printer fallback. Works because TC writes SKUs into the Shopify variant barcode field.
  3. Hand-write SKUs on tags — last resort. Use the SKU shown on the receiving page.

Stage 5 — Apply labels & shelve

Apply each label to its physical item. Move to the store or stockroom.

The order’s status flips:

  • PARTIAL if some variants are still at 0 received
  • RECEIVED once every variant has received qty ≥ ordered qty

Returning to a partial order

If a shipment arrives in two parts (common with EU suppliers):

  1. Receive what arrived in part 1 — save
  2. Order sits in PARTIAL
  3. When part 2 arrives, open the same Receiving page
  4. Enter the additional received qty (not cumulative — just what arrived in part 2)
  5. Save again

ThreadCloud adds the two saves together for the total received. The audit log shows each receive event separately.

Common mistakes

Receiving in CAD when you bought in EUR
If the order’s currency is EUR but you somehow set the receiving FX to 1.0, your costs are wildly off. Verify the FX before saving — it should be a normal exchange rate (e.g. 0.7 for EUR→CAD), not 1.0.

Forgetting to save before printing
The print preview reads from saved data. If you enter quantities but don’t click Save Received first, the print preview will show old data (or zero labels).

Receiving a re-order against the original order
If you placed a reorder for the same brand/season, the reorder is a separate order in ThreadCloud — even if the supplier shipped both together. Receive each order separately so sell-through math stays correct.

Reverse a receive

Made a mistake? You can reverse:

  1. Receiving tab → click Reverse Receive
  2. Select the variants and quantities to reverse
  3. Confirm — Shopify inventory reduces by that amount; the audit log records the reversal

Heads up
Reverse only works before any of the reversed variants have sold. If sales have already happened against the received inventory, email hello@threadcloud.io before reversing.

Next steps

  • Labels — print details + fallback options
  • Reorder — re-buy what’s selling
  • Trading — watch sell-through