JALIZA / INVENTORY & STOCKING
Independent workspace
Inventory intelligence / Stocking

Replenishment workspace

One plan across every warehouse and sales channel. Forecast demand, allocate shared stock, and net off incoming purchase orders.

Inventory safety / business performance

Company inventory overview

Order volume & turnover · 7 / 14 / 28 days

Ordered units are used for inventory turnover, not the number of orders. Overlapping sales windows are not added together.

Sales windowOrdered unitsDaily unit salesCurrent inventory cover · days

Week / month / quarter comparisons

To date versus the same elapsed part of the previous period. Weeks start Monday; months and quarters follow the calendar.

PeriodCurrent inventoryPrevious inventoryInventory changeNet slow-stock reductionCurrent receiptsPrevious receipts

Inventory is a point-in-time balance, never a sum of daily balances. Missing comparison snapshots show a dash. Slow-stock reduction is previous slow units minus current slow units; it may include reclassification, not just sales. Receipt totals require declared ERP coverage; partial recorded units are shown separately. Company receipts exclude internal transfers, while platform receipts count arrivals assigned to that platform.

Recorded inventory trend

Historical inventory & receipt data

Current imports save daily inventory snapshots automatically. Import older ERP snapshots and receipt records to populate prior periods. No historical values are invented.

Inventory health assessment

Health uses current visible sellable stock ÷ weighted daily ordered units: 7 days (50%), 14 days (30%), 28 days (20%), or your configured forecast weights. Missing 28-day sales renormalizes the available weights and marks the result incomplete. Company stock is counted once; shared platform inventory pools are not additive.

Health classification rules

Healthy: weekly cover under 30 days, subject to the higher-priority comprehensive bands. Risk: weekly daily sales at least 25% below the 28-day average, 14-day cover over 30 days, and comprehensive cover within 45 days; remaining 30–45-day transition cases are also Risk. Sub-healthy: comprehensive cover over 45 through 90 days, including the 60–90-day watch band. Slow-moving: over 90 through 180 days. Stubborn Slow-moving Inventory: over 180 days or no recent sales pace. Zero stock has no inventory aging exposure; stockout alerts remain separate. These are forecasts, not actual lot ages.

Slow-moving provision assessment

Aging starts at Xuchang shipment for Amazon (75 days) and TikTok Shop (45 days), and at Xuchang receipt for DTC (30 days). Months use 30 days. Only remaining sellable lot quantities are assessed. Eligible units indicate provision exposure; an amount requires ERP unit cost, currency, and a provision rate. Missing inputs never become zero. No accounting entry is posted.

SKU / lotPlatform / warehouseRemaining unitsAging startsAge / threshold · daysEligible provision unitsProvision amount
Platform submission · operator review · Dianxiaomi execution

Business master overview

0 demand lines selectedUp to 20 SKU-channel lines per batch
Customize stocking columns

Choose visible fields and move them into your preferred order. Saved for this account in this browser.

Period demand totals include pending, reviewing and approved submissions once per SKU-platform. Recommended forecast quantities are shown separately. SKU/SPU inventory totals follow role visibility; company-wide inventory is reserved for business managers. Stock attribution uses ERP allocations when supplied; otherwise it is the forecast planning allocation. Shared or unattributed stock is shown separately and counted once. A dash means hidden or unreported inventory. All new stocking enters Xuchang domestic warehouse before the final destination.

Actual stocking progress

Production completion → domestic receipt → shipment → destination arrival. These are ERP facts, not actions executed in this system.

SKU / demand referenceApprovedDomestic → destinationProduced / order completedDomestic receivedShipped / tracking目标仓库存ERP data updated

Dianxiaomi progress collection

The production stocking manager reviews and executes orders in Dianxiaomi. Sync verified cumulative quantities, tracking and warehouse receipt data here.

Import ERP progress records
Business owner · all platforms

Inventory control tower

Monitor SKU exposure, SPU slow-moving risk and cross-warehouse transfer decisions.

All-SKU inventory safety

SKU / SPUSellable stockOpen PO unitsUnmatched purchase requestsDaily forecastStock coverSPU factorRecommended purchase

Stock and transfer quantities are counted once across the business. Unmatched purchase requests exclude requests already linked to an ERP PO by ERP reference. Transfers reposition existing inventory; they do not add to total stock.

Owner transfer approval queue

Only non-Amazon source inventory can enter this queue. Pending and approved requests reserve donor surplus until rejected or recorded as completed.

SKU / managerPlatformSource → destinationQuantityStatusDecision / ERP reference

Inventory safety policy

No extra safety stock when total SKU sales across platforms are below 3 in 14 days AND below 5 in 28 days. Base platform forecast demand is retained.

SPU factors reduce the net purchase gap after stock and PO deductions. A seven-day forecast shortage is protected. Missing SPU mapping applies factor 1; missing 28-day sales disables extra safety stock.

Platform manager assignments

Assign one sales platform to each manager. Site sharing access is managed separately; assignments do not send invitations.

Platform manager workspace

Platform replenishment

Review your platform demand with visibility into every warehouse’s inventory.

Inventory & platform demand

Warehouse columns show sellable stock. Adjust the receiving warehouse and quantity, then confirm stocking in the rightmost column. Suggestions appear below each SKU; transfers still require owner approval. FBA 超出 45 天保护量且分给本渠道的库存已冲抵建议采购。

My platform transfer requests

SKUSource → destinationQuantityStatusOwner decision
SKU → inventory → calculation → warehouse demand

Replenishment workflow

Follow one SKU from current warehouse stock to its final replenishment destinations.

1 · Current inventory across all warehouses

See physical stock, reservations, sellable units and how the forecast uses each warehouse.

Inventory → demand connection

Allocated stock is a planning assignment, not an ERP reservation or warehouse transfer. Unallocated sellable stock remains in the shared pool.

2 · From sales forecast to replenishment demand

Every deduction below is traced back to a warehouse or a purchase order for this SKU.

Platform7d / 14d / 30d unitsWeighted daily salesCycleTarget unitsStock deductionPO deductionNet replenishmentTrace

The same stock and PO units are counted once. Low-volume SKUs retain base demand but receive no extra safety buffer; SPU risk may reduce the net purchase gap.

3 · Assign replenishment to receiving warehouses

Adjust each platform’s quantity and receiving warehouse. The final warehouse breakdown updates immediately.

IncludePlatformNet replenishmentFinal quantityReceiving warehouseSupplierLead time

Each platform line has one receiving warehouse. Multiple platform lines sent to the same warehouse are combined in the final SKU breakdown. Receiving destinations can differ from the warehouses supplying existing stock.

4 · Final warehouse demand for this SKU

Compare current stock and deducted supply with the new quantities assigned to each receiving warehouse.

WarehouseCurrent sellableStock allocatedOpen PO unitsPO units deductedNew replenishmentServing platforms

New replenishment is an order plan, not stock already received. Open PO units include all outstanding open orders; only qualifying arrival quantities appear in the PO deduction column.

SKU × warehouse demand matrix

Positive quantities form the purchase-request batch. Select a SKU to inspect its workflow.

Stockout risk dashboard

Forecast gaps within the next 7, 14 and 30 days, starting from the inventory snapshot date.

Where availability needs attention

Shared stock and on-time POs are consumed once across platforms, following the saved platform priority.

SKU / productPlatformRisk categoryFirst forecast gapDays to gapEligible stock¹Incoming ≤30d¹7d / 14d / 30d shortfallDaily forecast30d sales

¹ Eligible stock and PO quantities are shared warehouse pools; do not add them across platforms. Shortfall is forecast unmet demand by horizon, rounded up to units. POs arriving after a gap do not erase the earlier risk. Categories are 0–<7 days, 7–<14 days, and 14–<30 days; “No gap” means covered through this 30-day simulation. This forecast does not apply the 3-unit replenishment trigger.

Slow-moving inventory dashboard

Find inventory with no recent sales or more stock than the current sales pace supports.

Slow-moving risk inventory detail

Compare total sellable inventory, sales pace and time in slow-moving status.

SKU / productCategoryInventory quantity30d sales · all platformsDaily forecastStock coverSlow-moving sinceDays in slow-moving statusLast soldDetails

“No 30-day sales” is a dead-stock candidate, not proof that a product will never sell. Excess stock cover uses total sellable stock ÷ weighted daily sales across platforms. Days in slow-moving status require the snapshot’s historical slowMovingSince field; absent history is shown as Unknown and sorts last. Optional lastSoldAt shows the last sale date. Warehouse filtering changes the quantity displayed; classification remains SKU-wide.

SKU × platform demand

Base demand uses the weighted forecast. Extra safety stock is disabled below 3 sales / 14 days AND 5 sales / 28 days. SPU slow-moving risk adjusts the net gap.

SKU / productPlatform7d / 14d / 30d unitsDaily forecastCycleTargetStock allocatedPO deductionCover days¹30d turnover²ReplenishStatus / detail

¹ Allocated stock ÷ weighted daily forecast. Shared stock is consumed once across platforms. This is forward stock cover; ² Unit turnover = 30-day sales ÷ platform historical average inventory; “—” means the average was not provided. Click a row’s detail for the calculation and allocation trace. Export includes every SKU and platform, regardless of filters.

Review & confirm replenishment

Adjust quantities, verify the assigned supplier and choose a receiving warehouse before confirming.

IncludeSKUPlatformSuggestedConfirm quantitySupplierLead timeReceiving warehouse

Purchase requests split by supplier and receiving warehouse. The forecast cycles remain 14 / 28 days; supplier lead time estimates the new request’s sellable restock date. Existing incoming POs keep their individual ERP ETAs.

Supplier directory

Use the supplier ID already assigned in Dianxiaomi.

Lead time runs from confirmation to sellable receipt, including production, transit and receiving. Real requests require an ERP supplier ID. Supplier settings and confirmation records are stored on the server.

Saved suppliers

SKU → supplier bindings

Each SKU is assigned automatically to its saved supplier during confirmation.

SKU / productAssigned supplierLead time

Confirmed purchase requests

Minute-stamped in America/New_York · immutable supplier, quantity and lead-time snapshots.

Request name / referenceSupplierWarehouseUnitsEstimated restockERP statusERP referenceAction

“Awaiting connection” is saved but not sent. “Submitted” requires a verified ERP receipt. “Outcome unknown” must be reconciled by request ID before retrying. Sample confirmations never create real ERP requests. After ERP creation, pull a fresh snapshot to include actual PO quantities and ETAs in forecasts.

Warehouse inventory by SKU

Sellable balances across Xuchang, New Jersey returns, US warehouses and FBA.

Each warehouse shows sellable units (on hand − reserved − unsellable). Snapshot quantities are imported from ERP, not edited here.

Warehouse service matrix

Inventory is pooled by SKU, then allocated by platform priority.

7 warehouse groups · FBA and FBT included
勾选 FBA 的 DTC、TikTok 可使用分得的 45 天保护量以外库存。
WarehouseSellable unitsDTC websiteTikTok ShopAmazon

Sellable = on hand − reserved − unsellable. NJ returns count only after inspection and restocking. Xuchang is eligible for DTC; transfer/transit times are not assumed. FBA includes sellable FBA inventory only; receiving/inbound units belong in POs.

PO arrival deductions

Outstanding quantity = ordered − received. Only open POs with a confirmed ETA from snapshot date through platform cycle end can be deducted.

PO / SKUDestinationETALead timeOutstandingDeductedRemainingReview

Missing, overdue, cancelled, closed, late, or ineligible-destination arrivals are not credited. No PO unit is deducted twice. An ETA is not a guarantee of availability: stockout timing before arrival still needs operational review.

Weighted sales forecast

Overlapping rolling windows, normalized to daily unit sales.

daily = (7d units ÷ 7 × w7 + 14d units ÷ 14 × w14 + 30d units ÷ 30 × w30) ÷ sum(weights)
target = ceil(daily × cycle days)
replenish = max(0, target − allocated stock − eligible PO units)

Default weighting: 50 / 30 / 20. Safety eligibility uses total SKU sales across all platforms over 14 days and exact 28 days. Safety stock follows the shared owner policy; exact 28-day sales are required to enable an extra buffer.

Cycles & allocation

Default reserves Amazon’s restricted warehouse pool first. Within a platform, less-shareable warehouses are used first. All current stock is allocated before any incoming PO.

Rules and inventory snapshots are shared on the server. Recommendations require confirmation; transfer suggestions require owner approval.

Dianxiaomi data connection

Live ERP access not configured

Live inventory syncing and purchase-request creation require your Dianxiaomi API authorization and an integration service. Purchase confirmation uses a server-side adapter; the connection status is shown in the confirmation tab. Never enter API secrets into this page.

Warehouse inventoryFulfilled platform salesOpen POs & ETAs

Your integration should return one complete, consistent snapshot: canonical SKU mapping, historical platform average inventory (optional for turnover), all six warehouse groups, cumulative 7/14/30-day sales per platform, and PO destination / outstanding quantity / ETA. Aggregate all FBA locations without duplicating totals.

Read from your integration service

Optional HTTPS endpoint returning the normalized snapshot. Requires browser CORS support and service-side authorization. Never include API keys or tokens in the URL.

This is a manual data pull. Scheduled background sync is not active. API secrets and scheduled sync must be managed on your integration server; this workspace keeps adapter credentials server-side. Inventory snapshots, supplier settings and confirmation records are shared on the server with role-based access.

Snapshot requirements

Sales windows end on asOf. Use physical units, exclude cancelled orders, and reconcile partial receipts. Missing data is rejected rather than treated as zero. PO ETA is the estimated sellable receipt date, not the supplier’s shipping date. Use explicit zero balances for empty warehouses/platforms.

Confirm replenishment

Calculation detail

SKU stocking review

·

Modify stocking quantity