MRP
Data & Settings
How fresh is everything the purchasing plan runs on — and the repeatable way to refresh it: export the six NetSuite reports, drop them here, done.
Dataset freshness
Refresh the data (admin)
Export the saved searches from NetSuite (same ones as always: B2B + DTC warehouse inventory, All PO Report, Open Sales Order Detail, All Prices, Active Inventory Items) and drop them here — in any order, several at once. Each file is recognized from its columns, validated, stamped and stored; a costs file also refreshes the $ views. Every card above has a "How this is used" note spelling out its assumptions (which warehouses count as B2B vs DTC, what gets excluded, and why).
Sales history works incrementally: export just the recent months and drop the file — each month in the file replaces that month's existing rows, so re-uploads and overlaps never double-count. No need to re-export all of history.
▸Adjustment history & recovery— every save of the workbench adjustments, kept forever; restore any version
Loading…
Restoring never rewrites history — it appends the restored set as a new version, so any restore is itself undoable.
Service levels & ordering window (admin)
The service level sets how much safety stock the plan carries (95% ≈ 1.6σ, 99% ≈ 2.3σ of this SKU's own forecast error over its lead time). One business default, plus overrides for any attribute segment — the last matching rule wins.
The window widens the reorder threshold: with 30 days, a SKU reorders when its position can't carry through lead time plus a month of runway. The SO deferral uses the same horizon — an order shipping in March doesn't need stock ordered today if March is still beyond it. (Deferral activates once the NetSuite SO saved search carries a Due Date column.)