Data health
Signals that the database has drifted from physical or Shopify reality. The nightly check self-heals reservation drift.
A SKU on these orders had no BOM when they shipped, so those components were never decremented. Reprocess applies only the missed amount (never double-counts).
These components are below lead time + safety stock but are NOT flagged for reorder. This is the one failure that ends with an empty shelf — order them now and tell whoever maintains this.
A placed/partial PO has stock in transit that the component's "incoming" doesn't reflect. Heal recomputes it from the open PO lines.
These POs have blown their ETA, so their stock no longer counts as coverage — until this is healed the reorder calculator still believes it is arriving on time.
A stock claim was opened for these Shopify orders over an hour ago and never completed, so they hold no reservation. They clear themselves when the order's next fulfilled/cancelled webhook lands — look them up in Orders if they linger.
Lead-time discrepancies
Actual delivery differed from the stored lead time. Update the component value or keep it unchanged.
Refund reviews
A refund was issued on a shipped order. Decide whether the goods came back to the shelf or the customer keeps them.
🪄 Optimize order
Bundle critical items with parts on watch so each PO from this supplier covers everything that’s about to fire.
· placed · ✓ arrived · ETA
Components inventory
| Component | Status | On hand | Incoming | Daily use | Unit price | Coverage | Threshold | Last order | |
|---|---|---|---|---|---|---|---|---|---|
|
|
·
|
|
never ordered | ||||||
| No components match | |||||||||
Ysell ID:
Manual adjustment
Unit price
Expected uplift
Multiply the rolling forecast by this percentage until the date below — useful for a known campaign or fulfillment scale-up.
Transactions
| When | Reference | Δ | After | |
|---|---|---|---|---|
| No transactions yet | ||||
Products
Bill of materials
| Component | Qty / unit | On hand | Unit price | Coverage | Status | |
|---|---|---|---|---|---|---|
|
|
|
|||||
| No BOM lines | ||||||
Physical stocktake
Walk through each component and count what's physically on the shelf. The platform will show you the current system value — enter what you actually see, skip what you don't check, and we'll update the inventory at the end with a full audit trail.
Your progress is saved automatically — you can close and resume later.
Review changes
components will be updated · matched · skipped · not checked
| Component | Before | After | Δ |
|---|---|---|---|
| No changes — everything matched or was skipped. | |||
Current stock could not be re-read.
“Before” is from when this count started, so a component that moved since reads as “matched” and is missing from the list above — that one will not be written whether you apply or not. Everything the list DOES show is written against current stock, so applying still lands it. Retry the re-read if you can; otherwise apply, then re-count anything that showed as matched.
Current stock could not be re-read just before this was applied, so anything that showed as already matching was compared against an older snapshot. Re-count those components.
components updated. Transactions tagged .
counts did not land
Nothing was written for these — each one says why below. Re-count them from the components list.
-
counted · system said
Reorders & suppliers
Supplier order readiness
Higher score = more worth ordering today| Component | On hand | Incoming | Coverage | Qty to order | Unit cost | Line total |
|---|---|---|---|---|---|---|
|
|
||||||
| Total | ||||||
Open purchase orders
| PO | Supplier | Status | Lines · received / ordered | Total | Tracking | Placed / Arrived | Actions |
|---|---|---|---|---|---|---|---|
|
|
Partial arrival:
Record arrival — enter what ACTUALLY arrived
ComponentOrderedAlreadyArriving
Short shipment → PO stays partial, remainder still expected.
|
||||||
| No purchase orders yet | |||||||
Shopify orders
| Order # | Shopify ID | Fulfilled | Status | Error | Processed |
|---|---|---|---|---|---|
| No orders yet | |||||
Warehouse (Fulfillment-Box)
Their count is the source of truth for stock. Corrections land in each component's history as a stocktake, so they can be read back or undone.
| Component | Ours | Warehouse | Difference | Reading |
|---|---|---|---|---|
The sync moved our stock to the warehouse count and the write is confirmed landed. Each one is in the component's history as a stocktake and can be undone there. A correction that did NOT land is not listed here — it stays above as an open disagreement, with the reason the write failed.
| Component | Was | Now | Change |
|---|---|---|---|
Correcting these would count the same units twice: the order being picked, or the receipt we have not booked yet, moves them itself. The next sync corrects whatever is left over.
| Component | Ours | Warehouse | Difference | Why it was left |
|---|---|---|---|---|
What we declared against what Fulfillment-Box actually counted on arrival. A short count is a delivery that never fully landed.
| Shipment | Status | Declared | Counted | Short lines |
|---|---|---|---|---|
Suppliers
suppliers
| Name | Channel | Contact | Lead | MOQ | Currency | Status | |
|---|---|---|---|---|---|---|---|
| Active Inactive | › | ||||||
| No suppliers yet | |||||||
open POs · updated