Reconcile incoming inventory drift
Before you start
Section titled “Before you start”- You’ve noticed Shopify’s incoming does not match what Logistified expects from open POs and in-transit TOs.
- You are ready to choose the value Shopify should show for each mismatched variant/location pair.
- If another app also writes Shopify incoming, decide which rows Logistified should leave alone before applying.
- Open Settings → Variant Settings. On the Product & Variant Settings page, choose the Incoming Reconciliation tab. 2. Click Start reconciliation run. 3. In the wizard, keep Over, Under, and Negative selected unless you only want to review one case type, then click Start. 4. Wait for Logistified to build the expected incoming set and run a fresh Shopify query. 5. Review the table. Each row shows variant, location, Shopify incoming, Logistified expected incoming, Target, and the delta that will be applied. 6. Edit Target when Shopify should end at a value other than the default. The default is Logistified’s expected incoming.
- Deselect or remove rows you do not want to touch. 8. Click Apply selected and review the per-row result. 9. Use Run again if you want to verify the remaining drift after the apply finishes.
Worked example
Section titled “Worked example”Logistified expects 500 incoming for variant X at warehouse A; Shopify shows 350. The Target defaults to 500, so applying the row increases Shopify incoming by 150. If you know Shopify should stay at 350 because another tool owns part of that incoming, edit the Target or remove the row before applying.
Common failure modes
Section titled “Common failure modes”| Symptom | Likely cause | Fix |
|---|---|---|
| Apply fails | Shopify rejected the adjustment or rate-limited the request. | Wait, run the wizard again, and apply the row once Shopify responds normally. |
| Row has no fresh Shopify value | Shopify did not return a stocked inventory level for that variant/location. | Do not apply the row. Verify the variant is stocked at that Shopify location, then run again. |
| Same pair re-appears after applying | The underlying PO/TO plan still expects a different incoming value. | Fix the PO or TO directly, then run reconciliation again. |
| Applying would erase another tool’s incoming | Another app or manual Shopify process also writes incoming for the same pair. | Remove the row or set a Target that preserves the other system’s contribution. |
See also
Section titled “See also”- Inventory → Incoming reconciliation
- Purchase Orders → Receiving stock
- Transfer Orders → Inventory effects