---
title: How to fix receiving, stock corrections and imports that fail
url: https://tideswell.xyz/docs/troubleshooting/receiving-and-imports
description: Most of these are one cause. A Shopify connection missing a permission, which shows as a Reconnect warning.
---

> Documentation index: fetch https://tideswell.xyz/llms.txt to discover every page before exploring further.

# How to fix receiving, stock corrections and imports that fail



Anything that writes to Shopify shares one common failure, so check that first before working
through the specific cases.

## Check this first: the Reconnect warning [#check-this-first-the-reconnect-warning]

Open **Settings › Integrations** and look at the Shopify row.

**Reconnect** means the connection still works for reading but is missing a permission Tideswell
now needs. Reads look fine and writes fail, which is exactly the pattern that makes this
confusing.

A store connected before stock-writing permission was required shows that receiving is failing.
Until it is re-authorized, **receiving deliveries and stock corrections both fail**.

Fix it by **re-authorizing the existing store** rather than disconnecting it. That picks up the
new permissions and keeps everything else. See <Ref to="workspace-admin/integrations" />.

## Receiving a delivery [#receiving-a-delivery]

**Receive shipment is unavailable.** It is disabled on an order with no products and on a closed
order. Reopen a closed order first.

**A quantity is refused.** Quantities have to be whole numbers, so a mistyped decimal blocks the
save rather than silently becoming nothing.

**An amber warning says Shopify stock will not update.** That is the Reconnect case above. You
are never blocked from booking the delivery in: Tideswell records it and the Shopify half can be
retried afterwards.

**A receipt shows Failed.** Retry it from the receipt history, with its own confirmation. Retrying
is blocked on a closed order, so reopen it first.

**You are worried about double-counting.** You cannot. The same delivery is recognised and
reported as already recorded, which is what makes retrying safe.

**It says the stock updated but the record did not save.** Take that at its word and **do not
retry**. The number reached Shopify, and retrying would set it a second time.

**A line is recorded in Tideswell only.** That product is not tracked in Shopify, and you are
told how many lines that applied to. Nothing is lost.

Full detail in <Ref to="purchasing/receive-a-delivery" />.

## Correcting a stock count [#correcting-a-stock-count]

**The button is not there.** Correcting stock needs write access to the store surfaces, and it
only appears on rows that have a shipping location.

**The value is refused.** Whole numbers only, and an empty value is refused before the
confirmation opens.

**It says the stock changed since you loaded.** Somebody else changed it between you opening the
editor and confirming, so your write was refused rather than overwriting their count.

Reopen the editor, which now shows the current figure, and decide whether your number is still
right. Being refused is the safe outcome here.

**Everything fails.** The Reconnect case above.

See <Ref to="inventory/restock-cost-and-corrections" />.

## Imports [#imports]

**Rows were skipped.** The preview lists per-row errors before you commit, and reading it is the
point of it. The most common skip is a line already on the order, which is the safe outcome:
importing the same confirmation twice does not double an order.

**The header row is wrong.** The purchase order CSV expects specific column names. Fix the file
and re-import rather than fixing rows afterwards.

**Lots of lines did not match Shopify.** You are told to open the order and re-run the import to
match them. Unmatched lines are usually a SKU written differently by the supplier, or a product
not in Shopify yet.

An unmatched line still imports, but it cannot contribute to incoming stock or appear in reorder
maths, so it is worth correcting.

**It is taking a long time.** Matching SKUs against your catalogue is the slow part and a large
file does a lot of it. Let it finish rather than re-running.

See <Ref to="purchasing/import-orders-and-confirmations" />.

## Sending a revision to a supplier [#sending-a-revision-to-a-supplier]

**Send is blocked with lines missing.** Every line needs a confirmed quantity first. A blank one
would go out as zero, which reads to a supplier as "cancel this line".

**Send is blocked with no email on file.** The dialog offers a shortcut into the vendor profile
to add one.

See <Ref to="purchasing/revise-close-and-export" />.

## A homepage banner failed to publish [#a-homepage-banner-failed-to-publish]

Either your theme has no hero slideshow area that can be recognised, and the message says so, or
the connection is missing theme permissions, which the integrations screen names.

Both are covered in <Ref to="store/homepage-banner" />.