Skip to content

Incoming reconciliation

Incoming reconciliationIncoming reconciliationA check that compares what Logistified thinks is on the way against what Shopify shows as incoming. Highlights variants where the two disagree so you can fix the drift. Read more → compares what Logistified expects to be on the way with what Shopify currently shows as incoming. When the two disagree, the wizard lets you review the difference and apply selected corrections.

  • Why drift happens
  • Where to find it
  • Pair categories
  • Running a reconciliation
  • When to use this manually
  • What reconciliation does not touch
  • See also

Shopify’s incoming counter changes when a PO becomes incoming or a TO is in transit. Logistified also keeps an expected incoming value from open POs and TOs. If a Shopify update fails, is delayed, or another tool changes incoming, the two values can diverge.

Background checks refresh Logistified’s inventory copy and can flag drift, but they do not automatically correct every mismatch. Use this page when you want to inspect the differences and choose what Shopify should show.

Open Settings → Variant Settings. The page heading is Product & Variant Settings; choose the Incoming Reconciliation tab and click Start reconciliation run. There is no “Inventory” page in the app; reconciliation lives under settings because it’s an admin task, not a daily workflow.

Each disagreement is categorised:

CategoryWhat it meansTypical cause
OverLogistified expects more than Shopify shows.A previous sync didn’t take.
UnderLogistified expects less.An out-of-app Shopify change.
NegativeShopify shows less than zero.Rare — usually a Shopify bug or a manual entry mistake.

The flow is a wizard, not a per-row action list:

  1. Click Start reconciliation run to open the wizard. Choose whether to include Over, Under, and Negative cases, then click Start.
  2. The wizard loads Logistified’s expected incoming from your open POs and TOs, then runs a fresh Shopify query for each (variant, location) pair before you can apply anything.
  3. You see a table with one row per mismatched pair: SKU, product/variant, location, Shopify value, Logistified expected value, Target, and the resulting delta. Filter by Over / Under / Negative if you want to focus.
  4. Edit the Target column to choose what value should end up in Shopify. It defaults to Logistified’s expected value, but you can type any number — including zero if you want to clear a negative. Use Remove selected to drop rows you don’t want to push, or Reset targets to revert all targets to defaults.
  5. Click Apply selected. Logistified updates Shopify so each selected pair lands on its Target value, then records that value as its latest inventory copy.

After a run finishes, a Run again button appears in case more pairs surfaced while you were applying.

Open this tab when:

  • A pair has been drifting for longer than a typical background check cycle and needs review.
  • You’re about to send a PO or hand off counts to a stocktaker, and want the numbers reconciled now.
  • A negative Shopify value is blocking another workflow and needs a deliberate human decision before being pushed up.
  • Another app or manual Shopify change may have touched incoming, and you want to choose the correct Target before applying.

A run only changes selected incoming values in Shopify and Logistified’s inventory copy. It does not update PO or TO line items. So:

  • If a PO line was wrong upstream, pushing Logistified’s expected value to Shopify won’t correct the underlying PO — fix the PO directly, then run reconciliation again.
  • If you set a Target that does not match the underlying PO/TO plan, the same pair may appear again on a later run.